October 2006 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-1093) Deploying a war that also contains normal servlets the web.xml is modified as if they are all endpoints

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1093?page=all ] Darran Lofthouse updated JBWS-1093: ----------------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92773 > Deploying a war that also contains normal servlets the web.xml is modified as if they are all endpoints > ------------------------------------------------------------------------------------------------------- > > Key: JBWS-1093 > URL: http://jira.jboss.com/jira/browse/JBWS-1093 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxrpc > Affects Versions: jbossws-1.0.1 > Environment: Deploying to JBoss 4.0.4.GA > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-1.0.4 > > > When deploying a war that contains web services the servlet definitions for the endpoints need to be modified so that they reference a JBossWS servlet instead of the endpoint implementation, this JBossWS implementation then delegates to the endpoint. > For JBossWS 1.0.0 servlet entries were only modified if they were identified as endpoints based on the deployment of the webservices.xml > For JBossWS 1.0.1 as part of removing the dependencies on JBossAS this was refactored and now the non web services servlets are identified if their name ends 'Servlet'. The original logic from JBossWS 1.0.0 needs to be reimplemented but we also need to take into acount the different deployment scenarios. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1133) Unpacked JSR-181 POJO deployment fails for subsquent deployment.

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1133?page=all ] Darran Lofthouse updated JBWS-1133: ----------------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92767 > Unpacked JSR-181 POJO deployment fails for subsquent deployment. > ---------------------------------------------------------------- > > Key: JBWS-1133 > URL: http://jira.jboss.com/jira/browse/JBWS-1133 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxws > Affects Versions: jbossws-1.0.1 > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-1.0.4 > > > Unpacked JSR-181 POJO deployments are not deployed correctly for subsequent server starts. > This is because when this is first deployed the web.xml which is part of the deployment is modified so that the JBossServiceEndpointServlet servlet is used. > On subsequent deployments the web.xml is parsed but because all of the servlet classes have been replaced with the JBossServiceEndpointServlet it is JBossServiceEndpointServlet that is checked for annotations instead of the endpoint class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1079) Incorrect WSDL to Java mapping for anonymous struct.

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1079?page=all ] Darran Lofthouse updated JBWS-1079: ----------------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92728 > Incorrect WSDL to Java mapping for anonymous struct. > ---------------------------------------------------- > > Key: JBWS-1079 > URL: http://jira.jboss.com/jira/browse/JBWS-1079 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: wstools > Affects Versions: jbossws-1.0.0, jbossws-1.0.1 > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-1.0.4 > > > When running wsdl to java for a wsdl that contains a complex type that contains an anonymous struct the class generated for the anonymous struct is incorrect. > <xsd:complexType name="Person"> > <xsd:sequence> > <xsd:element name="Address"> > <xsd:complexType> > <xsd:sequence> > <xsd:element name="Address1" /> > </xsd:sequence> > </xsd:complexType> > </xsd:element> > </xsd:sequence> > </xsd:complexType> > The above example would generate an class with the name 'PersonAddress'. > From the jax-rpc specification (section 4.2.3) : - > " An XML struct maps to a JavaBeans class with the same name as the type of the XML struct. If the struct is anonymous, then the name of the nearest enclosing xsd:element, xsd:complexType or xsd:simpleType is used instead." > So the name of the generated type should be Address. > The generation of the jaxrpc-mapping actually does assume the generated class was generated with the name 'Address' so the code generation and jaxrpc-mapping generation are out of synch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBWS-868) BPEL in jbossws-samples

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-868?page=all ] Thomas Diesler reopened JBWS-868: --------------------------------- After a clean checkout I see BUILD FAILED /home/tdiesler/svn/jbossws/branches/jbossws-1.0/src/test/build.xml:288: Problem creating zip: /home/tdiesler/svn/jbossws/branches/jbossws-1.0/output/tests/libs/ jaxrpc-samples-wsbpel-hello-process.zip (No such file or directory) (and the archive is probably corrupt but I could not delete it) > BPEL in jbossws-samples > ----------------------- > > Key: JBWS-868 > URL: http://jira.jboss.com/jira/browse/JBWS-868 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Alejandro Guizar > Fix For: jbossws-1.0.4 > > > Every chapter in the userguide is backed up with one/more testcase in the jbossws testsuite. The tests are then compiled together in a standlaone sample zip. > Please show us how to use BPEL with some samples. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1133) Unpacked JSR-181 POJO deployment fails for subsquent deployment.

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1133?page=all ] Darran Lofthouse updated JBWS-1133: ----------------------------------- Component/s: jaxws (was: jaxrpc) > Unpacked JSR-181 POJO deployment fails for subsquent deployment. > ---------------------------------------------------------------- > > Key: JBWS-1133 > URL: http://jira.jboss.com/jira/browse/JBWS-1133 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxws > Affects Versions: jbossws-1.0.1 > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-1.0.4 > > > Unpacked JSR-181 POJO deployments are not deployed correctly for subsequent server starts. > This is because when this is first deployed the web.xml which is part of the deployment is modified so that the JBossServiceEndpointServlet servlet is used. > On subsequent deployments the web.xml is parsed but because all of the servlet classes have been replaced with the JBossServiceEndpointServlet it is JBossServiceEndpointServlet that is checked for annotations instead of the endpoint class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1078) WSDL11ToJavaTestCase - Should verify the SEIs that are generated.

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1078?page=all ] Darran Lofthouse updated JBWS-1078: ----------------------------------- Fix Version/s: jbossws-1.0.5 (was: jbossws-1.0.4) Deferring as enhancement to testsuite not bug/feature request for JBossWS itself. > WSDL11ToJavaTestCase - Should verify the SEIs that are generated. > ----------------------------------------------------------------- > > Key: JBWS-1078 > URL: http://jira.jboss.com/jira/browse/JBWS-1078 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: wstools > Affects Versions: jbossws-1.0.1 > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-1.0.5 > > > WSDL11ToJavaTestCase - Should verify the SEIs that are generated. > Also this test case should be expanded to incude all of the available WSDLs under 'src\test\resources\wsdlfixture'. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-868) BPEL in jbossws-samples

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-868?page=comments#action_12345256 ] Alejandro Guizar commented on JBWS-868: --------------------------------------- OK, I updated the test to make it runnable as part of the testsuite. C:\dev\jbossws\jbossws-1.0\src\test>ant -Dtest=org.jboss.test.ws.jaxrpc.samples.wsbpel.hello.BpelHelloTestCase one-test Buildfile: build.xml prepare: [echo] ----------------------------------------------- [echo] jboss.home = C:/dev/jboss/Branch_4_0/build/output/jboss-4.0.5.GA-ejb3 [echo] tomcat.home = ${tomcat.home} [echo] java.home = C:\dev\jdk1.5.0_07\jre [echo] ----------------------------------------------- thirdparty-get: thirdparty-classpath: thirdparty: init: deploy-jbpmbpel: one-test: [junit] Running org.jboss.test.ws.jaxrpc.samples.wsbpel.hello.BpelHelloTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.203 sec > BPEL in jbossws-samples > ----------------------- > > Key: JBWS-868 > URL: http://jira.jboss.com/jira/browse/JBWS-868 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Alejandro Guizar > Fix For: jbossws-1.0.4 > > > Every chapter in the userguide is backed up with one/more testcase in the jbossws testsuite. The tests are then compiled together in a standlaone sample zip. > Please show us how to use BPEL with some samples. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1181) SOAPAction field not populated on outgoing requests

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1181?page=all ] Thomas Diesler updated JBWS-1181: --------------------------------- Fix Version/s: jbossws-1.0.4 > SOAPAction field not populated on outgoing requests > --------------------------------------------------- > > Key: JBWS-1181 > URL: http://jira.jboss.com/jira/browse/JBWS-1181 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxrpc > Affects Versions: jbossws-1.0.3 > Reporter: David Boeren > Assigned To: David Boeren > Fix For: jbossws-1.0.4 > > > Related to support case: https://na1.salesforce.com/50030000002VWUh > I used wstools to generate a client for the Amazon webservice (http://www.xmlme.com/WSAmazonBox.asmx?wsdl), which specifies a SOAPAction value on their webmethods. When I attempt to call them using the generated classes I receive an error indicating that the SOAPAction is unpopulated: > Exception in thread "main" java.rmi.RemoteException: Call invocation failed with code [Client] because of: Server did not recognize the value of HTTP Header SOAPAction: .; nested exception is: > javax.xml.rpc.soap.SOAPFaultException: Server did not recognize the value of HTTP Header SOAPAction: . > at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:715) > at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:398) > at org.jboss.ws.jaxrpc.CallProxy.invoke(CallProxy.java:164) > at $Proxy0.bookBox(Unknown Source) > at com.xmlme.client.TestClient.main(TestClient.java:31) > Caused by: javax.xml.rpc.soap.SOAPFaultException: Server did not recognize the value of HTTP Header SOAPAction: . > at org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper.getSOAPFaultException(SOAPFaultExceptionHelper.java:100) > at org.jboss.ws.binding.soap.SOAPBindingProvider.unbindResponseMessage(SOAPBindingProvider.java:505) > at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:704) > ... 4 more > According to the spec, this field should be populated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1137) DOMEnvelopeBuilder builds SOAPEnvelope reading only the first child of SOAPBody element

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1137?page=all ] Thomas Diesler updated JBWS-1137: --------------------------------- Fix Version/s: jbossws-1.0.4 (was: jbossws-1.0.5) > DOMEnvelopeBuilder builds SOAPEnvelope reading only the first child of SOAPBody element > --------------------------------------------------------------------------------------- > > Key: JBWS-1137 > URL: http://jira.jboss.com/jira/browse/JBWS-1137 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jaxrpc > Affects Versions: jbossws-1.0.2 > Environment: Linux 2.6.12-12mdk, jdk 1.5.0_06, jboss 4.0.4GA with jbossws 1.0.2 > Reporter: Alessio Soldano > Assigned To: Thomas Diesler > Fix For: jbossws-1.0.4 > > Attachments: DOMEnvelopeBuilder.patch > > > When trying to build a SOAPMessage out of an InputStream containing a response to a SOAP request, MessageFactoryImpl's createMessageInternal method uses DOMEnvelopeBuilder. This build the envelope correctly except for the soap body if it contains more than one child element. In case of rpc/encoded soap messages, you can have multiref elements at the same level of the soapbody main child, ie for example: > <soapenv:Body soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> > <ns1:getUltimoElencoSociResponse xmlns:ns1="http://bean.service.rivendell.lince.it"> > <ns1:getUltimoElencoSociResponse href="#id0" /> > </ns1:getUltimoElencoSociResponse> > <multiRef xmlns:ns2="http://net.jboss.org/rivendell" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:UltimoElencoSoci"> > <aggiornato xsi:type="xsd:boolean">true</aggiornato> > <dataDeposito xsi:type="xsd:date">2006-06-19Z</dataDeposito> > <dataUltimoElencoSoci xsi:type="xsd:date">2006-05-22Z</dataUltimoElencoSoci> > </multiRef> > </soapenv:Body> > DOMEnvelopeBuilder parses the ns1:getUltimoElencoSociResponse tag only, so at the end of the process the multiref element is missing, thus the message is incomplete. > I know that rpc/encoded (used in the above example) won't be supported anymore in future, however I think this issue should be fixed in order to correctly parse every SOAPMessage. Moreover consider that your MessageFactory may be used also to manually parse (through SOAPMessage, SOAPEnvelope, and so on) messages coming from legacy system that still use rpc/encoded (that is exactly what I'm doing). > I fixed the issue simply by changing the "if" at line 99 of DOMEnvelopeBuilder into a "while". Here is the patch file you could use: > 99c99 > < if (itBody.hasNext()) > --- > > while (itBody.hasNext()) > Thank you in advance > Alessio Soldano -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-868) BPEL in jbossws-samples

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-868?page=comments#action_12345191 ] Thomas Diesler commented on JBWS-868: ------------------------------------- The samples are just an aggregation of unit tests. In that way we have self verifying sample code. Every sample test should run successfully as part of the testsuite. > BPEL in jbossws-samples > ----------------------- > > Key: JBWS-868 > URL: http://jira.jboss.com/jira/browse/JBWS-868 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Alejandro Guizar > Fix For: jbossws-1.0.4 > > > Every chapter in the userguide is backed up with one/more testcase in the jbossws testsuite. The tests are then compiled together in a standlaone sample zip. > Please show us how to use BPEL with some samples. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues October 2006