[Installation, Configuration & Deployment] - WAR deployment issue for Jackrabbit (JCR1.7) enabled code
by anitdp
I get the following JAXB exception while trying to deploy my war file to
jboss:
2009-10-12 14:45:38,217 SEVERE
[javax.enterprise.resource.webservices.jaxws.server.http]
(ResourceContainer.invoker.nonDaemon-1) WSSERVLET11: failed to parse runtime descriptor: javax.xml.ws.WebServiceException: Unable to create JAXBContext
javax.xml.ws.WebServiceException: Unable to create JAXBContext
at
com.sun.xml.ws.model.AbstractSEIModelImpl.createJAXBContext(AbstractSEIM
odelImpl.java:158)
at
com.sun.xml.ws.model.AbstractSEIModelImpl.postProcess(AbstractSEIModelIm
pl.java:87)
at
com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.jav
a:262)
at
com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.jav
a:322)
at
com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.jav
a:188)
at
com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467)
Caused by: java.security.PrivilegedActionException:
com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 2 counts of IllegalAnnotationExceptions
java.util.List is an interface, and JAXB can't handle interfaces.
this problem is related to the following location:
at java.util.List
java.util.List does not have a no-arg default constructor.
this problem is related to the following location:
at java.util.List
Did anyone encounter this type of issue on JBOSS or any other application server? The same WAR file deploys fine on Tomcat server.
Any suggestions would be highly appreciated.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260141#4260141
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260141
16 years, 8 months
[jBPM Users] - Re: [jBPM4] Synchronous process execution
by kukeltje
anonymous wrote : I understand what you are saying, but in my opinion the "to many (java) threads" should be at the user consideration, if I want to use them, the jBPM should give that option.
It's not something that could/should not be in jBPM, it's just that the combination of having a blocking process with waitstates is not something that has been requested a lot before (at all afaik) so there simple was not any time spent in realizing this.
With my 'previous post' I refered to the post in this topic, sorry for the confusion. Like I said, jBPM supports executing synchronous services and is blocking IF the services you call are all synchrounous. Since you do not seem to have a problem with blocking threads, you can create blocking services. That is even cleaner than jBPM providing it 'intrisically' ;-).
So this way you do not lose the 'synchronism' and I still think a thread blocking for possible long period (since you have human task) is a wrong design of a system with many downsides and possible problems like transactiontimeouts, etc.Maybe it is time to rethink some of your architecture.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4260138#4260138
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4260138
16 years, 8 months