Two of the most
fundamental and important packages in Spring are theorg.springframework.beansandorg.springframework.contextpackages. Code
in these packages provides the basis for Spring'sInversion of
Control(alternately
calledDependency
Injection) features. TheBeanFactoryprovides an
advanced configuration mechanism capable of managing beans (objects) of any
nature, using potentially any kind of storage facility. TheApplicationContextbuilds on top of
the BeanFactory (it's a subclass) and adds other functionality such as easier
integration with Springs AOP features, message resource handling (for use in
internationalization), event propagation, declarative mechanisms to create the
ApplicationContext and optional parent contexts, and application-layer specific
contexts such as theWebApplicationContext,
among other enhancements.

A BeanFactory configuration consists of,
at its most basic level, definitions of one or more beans that the BeanFactory
must manage. In an XmlBeanFactory, these are configured as one or
morebean elements inside a top-level beans element.

A user who doesn't want to
touch any Spring stuff could also publish the endpoint with CXF servlet
transport. First you should extend the CXFNonSpringServlet and then override
the method loadBus, e.g.:

Comments

Popular posts from this blog

For easily monitoring the JVM metrics there is no better tool than Java VisualVM or its older counterpart JConsole; These two tools comes with the Java JDK. So it is absolutely necessary that you copy a JDK version to some temp directory in which your server runs. {Make sure that you do not install the JDK / put the java executable in the path.}

Before going in JVM monitoring, it is essential to understand a little about Java's memory model.

Note - This article is written with HotSpot JVM in mind,which is one of the most commonly used one ; implemented by OpenJDK and Oracle - formerly from Sun. This is not the only one , notable being JRockit and others; and some details would change with a different JVM.

When you are running a Java Process in a Server you allocate the Memory for the Java Virtual Machine. This memory is split to process heap { what you give withe the Xmx Xms command}where it is again subdivided on generational basis (Young, Old) and the PermGen - which is grad…

Intermittent failure in Selenium Test cases ?
After clicking the drill down sometimes web-elements are not found causing all summary table test cases to fail.
Common Root Causes
1) Prefer Selection By.ID className then By.cssSelectior and only if all else fails use By.Xpath
Selection by CSS By.CSSSelector should be preferred over XPath as this is more stable as it is natively supported by browser . XPAth is an abstraction provided by Selenium and not as performant. If XPath is used make sure that you have hand written the XPath and it is performant and not generic in that it has to to brute force search through the entire DOM to find your element.
Where ever possible , use By.ID, else By.CSSSelector and in case of no other option use XPath after proper testing.
You can use FireFinder plugin for FireFox (first add FireBug) to test your CSS or Xpath (if there is no way you can select by CSS)
For example this XPath to finding the drill down element //*[@id='scTableTest_Site-PLMN-PL…