June 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-1240) BaseDataTypesRpcLit_Service - RetQName - QName escape character parsing issues

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1240?page=all ] Thomas Diesler updated JBWS-1240: --------------------------------- Assignee: Thomas Diesler > BaseDataTypesRpcLit_Service - RetQName - QName escape character parsing issues > ------------------------------------------------------------------------------ > > Key: JBWS-1240 > URL: http://jira.jboss.com/jira/browse/JBWS-1240 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws > Affects Versions: jbossws-2.0.0.Beta > Reporter: Jason T. Greene > Assigned To: Thomas Diesler > Fix For: jbossws-2.0.0 > > > A namespace with escape characters fails: > <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><RetQName xmlns="http://tempuri.org/"><inQName xmlns="" xmlns:a=">:Can We do it<:">a:localname</inQName></RetQName></s:Body></s:Envelope> > A value with escape characters fails: > <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><RetQName xmlns="http://tempuri.org/"><inQName xmlns="" xmlns:a="namespace">a:<::Yes We Can ::></inQName></RetQName></s:Body></s:Envelope> -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1243) ComplexDataTypesRpcList_Service - null structures result in members with null values

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1243?page=all ] Thomas Diesler updated JBWS-1243: --------------------------------- Assignee: Thomas Diesler > ComplexDataTypesRpcList_Service - null structures result in members with null values > ------------------------------------------------------------------------------------ > > Key: JBWS-1243 > URL: http://jira.jboss.com/jira/browse/JBWS-1243 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws > Affects Versions: jbossws-2.0.0.Beta > Reporter: Jason T. Greene > Assigned To: Thomas Diesler > Fix For: jbossws-2.0.0 > > > A null structure, like the following:: > <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:Header> </s:Header> <s:Body> <RetStructS1 xmlns="http://tempuri.org/"> <inStructS1 xmlns:d4p1="http://schemas.datacontract.org/2004/07/XwsInterop.SoapWsdl.ComplexDataTy..." i:nil="true" xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="" /> </RetStructS1> </s:Body> </s:Envelope> > results in a member being set to null instead of the structure itself: > <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Body> <ns1:RetStructS1Response xmlns:ns1="http://tempuri.org/"> <RetStructS1Result xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ns_name:name xmlns:ns_name="http://schemas.datacontract.org/2004/07/XwsInterop.SoapWsdl.ComplexDataTy..." xsi:nil="1"> </ns_name:name> </RetStructS1Result> </ns1:RetStructS1Response> </env:Body> </env:Envelope> -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1281) When an element is nil, weblogic (8.1 sp3) sends an element with xsi:nil='1', however, it does not send type information with xsi:type=xxxx. It causes exception in org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.java.

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1281?page=all ] Thomas Diesler updated JBWS-1281: --------------------------------- Assignee: Thomas Diesler > When an element is nil, weblogic (8.1 sp3) sends an element with xsi:nil='1', however, it does not send type information with xsi:type=xxxx. It causes exception in org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.java. > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBWS-1281 > URL: http://jira.jboss.com/jira/browse/JBWS-1281 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws > Affects Versions: jbossws-1.0.2 > Environment: windows xp, linux, jdk1.5 > Reporter: George Gan > Assigned To: Thomas Diesler > Fix For: jbossws-2.0.0 > > Attachments: SundayContentHandler.java > > > When an element is nil, weblogic (8.1 sp3) sends an element with xsi:nil='1', however, it does not send type information with xsi:type=xxxx. It causes exception in org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.java. I hacked to code to only compare the localpart: > public void endElement(String namespaceURI, String localName, String qName) > { > ElementBinding elementBinding = null; > QName endName = localName.length() == 0 ? new QName(qName) : new QName(namespaceURI, localName); > StackItem item; > while(true) > { > item = stack.peek(); > if(item.cursor == null) > { > if(item.ended) > { > pop(); > if(item.particle.isRepeatable()) > { > endRepeatableParticle(item.particle); > } > } > else > { > elementBinding = (ElementBinding)item.particle.getTerm(); > item.ended = true; > break; > } > } > else > { > if(!item.ended) // could be ended if it's a choice > { > endParticle(item, endName, 1); > } > ParticleBinding currentParticle = item.cursor.getCurrentParticle(); > TermBinding term = currentParticle.getTerm(); > if(term.isWildcard() && currentParticle.isRepeatable()) > { > endRepeatableParticle(currentParticle); > } > pop(); > if(item.particle.isRepeatable()) > { > endRepeatableParticle(item.particle); > } > } > } > if(elementBinding == null) > { > throw new JBossXBRuntimeException("Failed to endElement " + qName + ": binding not found"); > } > //if(!elementBinding.getQName().equals(endName)) <--------------------------------------- hack starts here > // GG hack only compare the local parts. In the case of the an element is nil, > // there is no type prefix > if(!endName.getLocalPart().equals( elementBinding.getQName().getLocalPart())) > { > throw new JBossXBRuntimeException("Failed to end element " + > new QName(namespaceURI, localName) + > ": element on the stack is " + elementBinding.getQName() > ); > } > endElement(); > } -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1556) @WebWservice does not work with class isolation

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1556?page=all ] Thomas Diesler updated JBWS-1556: --------------------------------- Assignee: Thomas Diesler > @WebWservice does not work with class isolation > ------------------------------------------------ > > Key: JBWS-1556 > URL: http://jira.jboss.com/jira/browse/JBWS-1556 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-2.0.0 > > > It seems that Web Services do not work when the EAR that contains the @WebService class has an isolated classloader. Here is my take on what happens: > You deploy the ear and JBoss creates a war, that contains a web.xml, that points to the org.jboss.ws.server.ServiceEndpointServlet. > You can send a request to the web service bean no problem, but any objects that get returned from it will throw a NoClassDefFoundError because this ServiceEndpointServlet is deployed outside of the EAR and, since it has an isolated classloader, can't reference the returned class. > My application works absolutely fine when I turn off all isolation of the classloader. I don't think this can be fixed. Any ideas? -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1241) BaseDataTypesRpcLit_Service - RetString - CR and CRLF handling

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1241?page=all ] Thomas Diesler updated JBWS-1241: --------------------------------- Assignee: Thomas Diesler > BaseDataTypesRpcLit_Service - RetString - CR and CRLF handling > --------------------------------------------------------------- > > Key: JBWS-1241 > URL: http://jira.jboss.com/jira/browse/JBWS-1241 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws > Affects Versions: jbossws-2.0.0.Beta > Reporter: Jason T. Greene > Assigned To: Thomas Diesler > Fix For: jbossws-2.0.0 > > > CR Fails: > <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><RetString xmlns="http://tempuri.org/"><inString xmlns="">HelloWorld</inString></RetString></s:Body></s:Envelope> > CRLF fails: > <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><RetString xmlns="http://tempuri.org/"><inString xmlns="">Hello > World</inString></RetString></s:Body></s:Envelope> > The returned value for both is LF only, which is incorrect. -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Reopened: (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 reopened JBWS-1093: ------------------------------------ Looks like it needs to be merged again. > 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: jbossws > Affects Versions: jbossws-1.0.1 > Environment: Deploying to JBoss 4.0.4.GA > Reporter: Darran Lofthouse > Assigned To: Darran Lofthouse > Fix For: jbossws-2.0.0, 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-515) Provide an initial implementation for WS-ReliableMessaging

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-515?page=all ] Thomas Diesler updated JBWS-515: -------------------------------- Description: The relevant spec is http://docs.oasis-open.org/ws-rx/wsrm/v1.1/wsrm.html To complete this task we need #1 An initial implementation of WS-RM Version 1.1 #2 A comprehensive sample test case that shows the usage of WS-RM with JBossWS #3 Documentation about WS-RM with JBossWS on the Wiki was: The relevant spec is http://docs.oasis-open.org/ws-rx/wsrm/v1.1/wsrm.html > Provide an initial implementation for WS-ReliableMessaging > ---------------------------------------------------------- > > Key: JBWS-515 > URL: http://jira.jboss.com/jira/browse/JBWS-515 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ws-reliable > Reporter: Thomas Diesler > Fix For: jbossws-2.1.0 > > > The relevant spec is > http://docs.oasis-open.org/ws-rx/wsrm/v1.1/wsrm.html > To complete this task we need > #1 An initial implementation of WS-RM Version 1.1 > #2 A comprehensive sample test case that shows the usage of WS-RM with JBossWS > #3 Documentation about WS-RM with JBossWS on the Wiki -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-515) Provide an initial implementation for WS-ReliableMessaging

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-515?page=all ] Thomas Diesler updated JBWS-515: -------------------------------- Description: The relevant spec is http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-spec-cs-01.html > Provide an initial implementation for WS-ReliableMessaging > ---------------------------------------------------------- > > Key: JBWS-515 > URL: http://jira.jboss.com/jira/browse/JBWS-515 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ws-reliable > Reporter: Thomas Diesler > Fix For: jbossws-2.1.0 > > > The relevant spec is > http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-spec-cs-01.html -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-515) Provide an initial implementation for WS-ReliableMessaging

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-515?page=all ] Thomas Diesler updated JBWS-515: -------------------------------- Description: The relevant spec is http://docs.oasis-open.org/ws-rx/wsrm/v1.1/wsrm.html was: The relevant spec is http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-spec-cs-01.html > Provide an initial implementation for WS-ReliableMessaging > ---------------------------------------------------------- > > Key: JBWS-515 > URL: http://jira.jboss.com/jira/browse/JBWS-515 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ws-reliable > Reporter: Thomas Diesler > Fix For: jbossws-2.1.0 > > > The relevant spec is > http://docs.oasis-open.org/ws-rx/wsrm/v1.1/wsrm.html -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-515) Provide an initial implementation for WS-ReliableMessaging

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-515?page=comments#action_12364332 ] Thomas Diesler commented on JBWS-515: ------------------------------------- We decided that Richard Opalka would have a go at an initial implementation > Provide an initial implementation for WS-ReliableMessaging > ---------------------------------------------------------- > > Key: JBWS-515 > URL: http://jira.jboss.com/jira/browse/JBWS-515 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ws-reliable > Reporter: Thomas Diesler > Fix For: jbossws-2.1.0 > > -- 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

15 years, 1 month

1
0
0 / 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues June 2007