Development

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”);

if you use JAAS to login to your application, you are able to get the active user(name) the following way: final Principal principal = FacesContext.getCurrentInstance() .getExternalContext().getUserPrincipal(); if (null == principal) { return null; } return principal.getName();

If you need to create a link with the actual location in it you can use #{request.contextPath}. here an example: <a href=”#{request.contextPath}/some/dir/test.jsf”>GO</a>

If you want log4j-style logging under a JBoss AS7 project, just include the seam solder jar which abstracts the log4j-logger and use the org.jboss.logging.Logger as log-provider. For maven: <dependency> <groupId>org.jboss.seam.solder</groupId> <artifactId>seam-solder</artifactId> <version>3.0.0.Final</version> </dependency> And if you want to use all loglevels you can change your loglevel in your standalone.xml file by changing the subsystem. I

If you want to create Soap WebServices you first have to extend your standalone.xml file. Add the module and it’s configuration: … <extensions> … <extension module=”org.jboss.as.webservices”/> … </extensions> … <profile> … <subsystem xmlns=”urn:jboss:domain:webservices:1.0″ xmlns:javaee=”http://java.sun.com/xml/ns/javaee” xmlns:jaxwsconfig=”urn:jboss:jbossws-jaxws-config:4.0″> <wsdl-host> localhost </wsdl-host> <modify-wsdl-address> true </modify-wsdl-address> <endpoint-config> <jaxwsconfig:config-name> Standard-Endpoint-Config </jaxwsconfig:config-name> </endpoint-config> <endpoint-config> <jaxwsconfig:config-name> Recording-Endpoint-Config </jaxwsconfig:config-name> <jaxwsconfig:pre-handler-chains> <javaee:handler-chain> <javaee:protocol-bindings> ##SOAP11_HTTP ##SOAP11_HTTP_MTOM