Author name: Manuel Bogner

Since 7.1 the following warning appears during server startup: WARNING: -logmodule is deprecated. Please use the system property ‘java.util.logging.manager’ or the ‘java.util.logging.LogManager’ service loader. This can be fixed be removing the following part from the launch configuration in the “Program arguments” section: -logmodule org.jboss.logmanager

to include the source-code-generation wsimport does for you into your maven build you can use the cxf-codegen-plugin as follows: <plugin> <groupId>org.apache.cxf</groupId> <artifactId>cxf-codegen-plugin</artifactId> <version>2.5.2</version> <executions> <execution> <id>generate-sources</id> <phase>generate-sources</phase> <configuration> <sourceRoot>src/main/java</sourceRoot> <wsdlOptions> <wsdlOption> <wsdl>http://localhost:8080/SoapService?wsdl</wsdl> <extraargs> <extraarg>-client</extraarg> </extraargs> </wsdlOption> </wsdlOptions> </configuration> <goals> <goal>wsdl2java</goal> </goals> </execution> </executions> </plugin> This adds the generated resources to your maven source folder. Eclipse

to use apache CXF to consume webservices in a maven project you have to inlcude the following dependencies – of course you can change the logging part if you don’t use log4j like me. <dependency> <groupId>org.apache.cxf</groupId> <artifactId>cxf-rt-frontend-jaxws</artifactId> <version>2.5.2</version> <scope>compile</scope> </dependency> <dependency> <groupId>org.apache.cxf</groupId> <artifactId>cxf-rt-transports-http</artifactId> <version>2.5.2</version> <scope>compile</scope> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>1.6.4</version> <scope>compile</scope> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId>

To consume a JAX-WS webservice you first have to generate portable artifacts to handle the service. Therefor first get the wsdl-file of the service to consume. You should be able to get this by simply adding ?wsdl to the serivce url. Save the wsdl locally and open a terminal. Then you generate the JAX-WS portable

getting JMS running wasn’t as easy as I thought, but after some research I found out how to get as7 with included hornetq up and running. First copy the messaging part from standalone-preview.xml to standalone.xml. Then look for ejb3 configuration and set lite=”false” instead of true (default) as in light mode MDBs are not supported

You can read GET parameters with the RequestParameterMap as follows: final String id = FacesContext.getCurrentInstance() .getExternalContext().getRequestParameterMap().get(“id”);