[JBoss Microcontainer Users] - EAR being deployed over and over again?!
by JBossBorot
Made a very simple EAR {in Eclipse}, using Maven, all seems to be in order for its contents and everything.
Plucked into the JBoss 5.1 default server config's deploy folder and started the server:
- the app seems to deploy the 1st time, during a start-up, just fine
- the then the server keeps trying to deploy it over and over, but of course it's already deployed, so the attempt runs into this error:
org.jboss.deployers.spi.DeploymentException:
Error deploying jboss-poc-ejb.jar: Error creating ejb container FubarBean1: Container jboss.j2ee:ear=ejb-app.ear,jar=jboss-poc-ejb.jar,name=FubarBean1,service=EJB3,VMID=026595140065ca82:1b62e705:1247d602e95:-7fc2 + is already registered
What am I doing wrong? New to JBoss, but have done Weblogic development for years and have done this on WL a number of times before, if that makes much difference.
Thanks,
Karoy
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261773#4261773
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261773
16 years, 6 months
[JBoss Web Services Users] - Custom JAXBContext search path for JAXWS EJB endpoint
by mckibben
Hi All,
I have a JAXWS EJB endpoint implementation using JBossWS 3.2 Native, and I need to customize the JAXBContext package search path used to unmarshall the SOAP payload.
My wsdl is using document literal to send the payload, and one of the message elements has a child element that is of type "xs:any". I have the JAXB generated Java classes for the actual element being added as a child in the xml, but the object is still being unmarshalled as a DOM Element instead of my JAXB class.
It seems like this should be possible, but I can't find any way to do this looking through the user docs. I thought by adding an @XmlSeeAlso annotation to my JAXWS EJB SEI implementation should've added that JAXB class to the JAXBContext used for unmarshalling, but that didn't work.
Anybody have a solution? Or is this a JBoss bug? The JAXWS 2.1 spec (see section 2.2) seems to imply the @XmlSeeAlso should work, but their examples show the annotation on the SEI and not on the SEI implementation.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261770#4261770
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4261770
16 years, 6 months