[JBossWS] - Re: JBossXBException: Failed to parse source
by electren
I use 1.0.4 and have this problem also...
I there a solution already??
Can't find some Jira-Tasks...
My exception:
| Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: org.jboss.ws.binding.BindingException: org.jboss.ws.jaxb.UnmarshalException: Failed to parse source: Requested element anmeldenamen is not allowed in this position in the sequence. The next element should be {http://cow.service.app.fm.business.de}anmeldenamen
| at com.sun.xml.ws.encoding.soap.ClientEncoderDecoder.toMessageInfo(ClientEncoderDecoder.java:84)
| at com.sun.xml.ws.encoding.soap.client.SOAPXMLDecoder.toMessageInfo(SOAPXMLDecoder.java:209)
| at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:538)
| at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:258)
| at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
| at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
| at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
| at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
| at $Proxy8.pruefeLogin(Unknown Source)
| at main.java.WsLogin.main(WsLogin.java:68)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038860#4038860
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038860
19 years
[JBoss jBPM] - Problem with building jBPM 3.2 from source code
by HLQ
I want to build the jBPM3.2 from the source code, and I followed the instructions as described in the link below:
http://wiki.jboss.org/wiki/Wiki.jsp?page=JbpmBuildingTheSources
But when I import this project into the eclipse, it shows some errors:
- EndpointMetaData cannot be resolved to a type jbpm.3_HEAD/bpel/library/src/main/java/org/jbpm/bpel/integration/server JBossWS1_2EndpointMetadataLookup.java line 41
- MessageContextJAXRPC cannot be resolved jbpm.3_HEAD/bpel/library/src/main/java/org/jbpm/bpel/integration/server JBossWS1_2EndpointMetadataLookup.java line 39
- ServiceMetaData cannot be resolved to a type jbpm.3_HEAD/bpel/library/src/main/java/org/jbpm/bpel/integration/server JBossWS1_2EndpointMetadataLookup.java line 44
- SOAPMessageContextJAXRPC cannot be resolved to a type jbpm.3_HEAD/bpel/library/src/main/java/org/jbpm/bpel/integration/server JBossWS1_2EndpointMetadataLookup.java line 38
- SOAPMessageContextJAXRPC cannot be resolved to a type jbpm.3_HEAD/bpel/library/src/main/java/org/jbpm/bpel/integration/server JBossWS1_2EndpointMetadataLookup.java line 38
- The import org.jboss.ws cannot be resolved jbpm.3_HEAD/bpel/library/src/main/java/org/jbpm/bpel/integration/server JBossWS1_2EndpointMetadataLookup.java line 22
Anybody knows what is wrong with it?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038859#4038859
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038859
19 years
[JBoss Seam] - Multiple catchall error
by Sammy8306
I'm getting this exception : java.lang.IllegalStateException: multiple catchall elements when using the following pages.xml :
| <!DOCTYPE pages PUBLIC
| "-//JBoss/Seam Pages Configuration DTD 1.2//EN"
| "http://jboss.com/products/seam/pages-1.2.dtd">
|
| <pages no-conversation-view-id="/home.xhtml">
|
| <page view-id="/newBlogEntry.xhtml">
| <navigation from-outcome="succesful">
| <end-conversation before-redirect="true" />
| <redirect view-id="/blog.xhtml">
| <param name="userId" value="#{user.id}"/>
| </redirect>
| </navigation>
| <navigation from-outcome="fail">
| </navigation>
| </page>
|
| </pages>
|
The idea is to stay on the same page when fail is returned from an action called in /newBlogEntry.xhtml, and to stay on the same page otherwise. I tried to model this by returning null when I want to stay on /newBlogEntry.xhtml, however, this still triggered the redirection to blog.xhtml. Now, I'm returning an explicit "fail" string, but now I can't view any pages in my web-app anymore because of the exception above... what's going on here?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038858#4038858
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038858
19 years