November 2006 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-1276) apache-tomcat (jdk1.5)

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1276?page=all ] Thomas Diesler updated JBWS-1276: --------------------------------- Priority: Major (was: Critical) > apache-tomcat (jdk1.5) > ---------------------- > > Key: JBWS-1276 > URL: http://jira.jboss.com/jira/browse/JBWS-1276 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-1.0.5 > > > Run these tests with jdk1.5 > tdiesler@tdvaio /cygdrive/d/svn/jbossws/branches/jbossws-1.0/output/jbossws-samples-1.1.x.GA > $ ant tests > [PASS] -- 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1276) apache-tomcat (jdk1.5)

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1276?page=all ] Thomas Diesler updated JBWS-1276: --------------------------------- Assignee: Thomas Diesler (was: Prabhat Jha) > apache-tomcat (jdk1.5) > ---------------------- > > Key: JBWS-1276 > URL: http://jira.jboss.com/jira/browse/JBWS-1276 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Priority: Critical > Fix For: jbossws-1.0.5 > > > Run these tests with jdk1.5 > tdiesler@tdvaio /cygdrive/d/svn/jbossws/branches/jbossws-1.0/output/jbossws-samples-1.1.x.GA > $ ant tests > [PASS] -- 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1275) jboss-4.0.x (jdk1.5)

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1275?page=all ] Thomas Diesler updated JBWS-1275: --------------------------------- Assignee: Thomas Diesler (was: Prabhat Jha) > jboss-4.0.x (jdk1.5) > -------------------- > > Key: JBWS-1275 > URL: http://jira.jboss.com/jira/browse/JBWS-1275 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-1.0.5 > > > Run these tests with jdk1.5 > tdiesler@tdvaio /cygdrive/d/svn/jbossws/branches/jbossws-1.0/src/test > $ ant tests > [PASS] > tdiesler@tdvaio /cygdrive/d/svn/jbossws/branches/jbossws-1.0/output/jbossws-samples-1.1.x.GA > $ ant tests > [PASS] > tdiesler@tdvaio /cygdrive/d/cvs/jboss-branch/jboss-4.0.x/testsuite > $ ant tests-webservice > [PASS] -- 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1273) Release jbossws-1.0.5.GA binary

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1273?page=all ] Thomas Diesler updated JBWS-1273: --------------------------------- Assignee: Thomas Diesler (was: Prabhat Jha) > Release jbossws-1.0.5.GA binary > ------------------------------- > > Key: JBWS-1273 > URL: http://jira.jboss.com/jira/browse/JBWS-1273 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-1.0.5 > > > The release criteria for jbossws-1.1.0.GA are: > * pass all internal jbossws tests > * pass all portable j2ee-1.4 tests from the jboss testsuite > * pass all tests in module jaxr,jaxrpc,saaj,webservice from the Sun compatiblity testsuite > * generate all test artifacts with wstools -- 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

17 years, 7 months

1
0
0 / 0

[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: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) If this issue has been rescheduled to 1.0.6 it is because we currently focus 80% of our effort on JAXWS. If need a particular feature or bugfix to be included in 1.0.5 you are welcome to get involved and contribute. > 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: binding > Affects Versions: jbossws-2.0.0.Beta > Reporter: Jason T. Greene > Fix For: jbossws-1.0.6 > > > 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1278) Add option for all generated data types are serializable.

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1278?page=all ] Thomas Diesler updated JBWS-1278: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) If this issue has been rescheduled to 1.0.6 it is because we currently focus 80% of our effort on JAXWS. If need a particular feature or bugfix to be included in 1.0.5 you are welcome to get involved and contribute. > Add option for all generated data types are serializable. > --------------------------------------------------------- > > Key: JBWS-1278 > URL: http://jira.jboss.com/jira/browse/JBWS-1278 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: wstools > Affects Versions: jbossws-1.0.3 > Reporter: Darran Lofthouse > Fix For: jbossws-1.0.6 > > > Add option for all generated data types are serializable. -- 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1218) Circular schema definitions lead to stack overflow

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1218?page=all ] Thomas Diesler updated JBWS-1218: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) If this issue has been rescheduled to 1.0.6 it is because we currently focus 80% of our effort on JAXWS. If need a particular feature or bugfix to be included in 1.0.5 you are welcome to get involved and contribute. > Circular schema definitions lead to stack overflow > -------------------------------------------------- > > Key: JBWS-1218 > URL: http://jira.jboss.com/jira/browse/JBWS-1218 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: wstools > Reporter: Aladdin El-Nattar > Assigned To: David Boeren > Fix For: jbossws-1.0.6 > > > An element definition like the following will trigger a stack overflow: > <xsd:element name="Foo"> > <xsd:complexType> > <xsd:sequence> > <xsd:element ref="Foo" minOccurs="0" maxOccurs="unbounded"/> > </xsd:sequence> > <xsd:complexType> > </xsd:element> -- 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1284) Gracefully handle invalid ImageIO mime types

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1284?page=all ] Thomas Diesler updated JBWS-1284: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) If this issue has been rescheduled to 1.0.6 it is because we currently focus 80% of our effort on JAXWS. If need a particular feature or bugfix to be included in 1.0.5 you are welcome to get involved and contribute. > Gracefully handle invalid ImageIO mime types > -------------------------------------------- > > Key: JBWS-1284 > URL: http://jira.jboss.com/jira/browse/JBWS-1284 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: binding > Reporter: Jason T. Greene > Assigned To: Magesh Kumar B > Fix For: jbossws-1.0.6 > > > org.jboss.ws.soap.attachment.ImageDataContentHandler.buildFlavors calls ImageIO.getReaderMIMETypes() to determine the list of supported mime types. It has been reported that their are ImagIO plugins in the wild that return invalid mime types. Instead of aborting a warning message should be triggered in this case. -- 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

17 years, 7 months

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: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) If this issue has been rescheduled to 1.0.6 it is because we currently focus 80% of our effort on JAXWS. If need a particular feature or bugfix to be included in 1.0.5 you are welcome to get involved and contribute. > 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: binding > Affects Versions: jbossws-1.0.2 > Environment: windows xp, linux, jdk1.5 > Reporter: George Gan > Fix For: jbossws-1.0.6 > > 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1231) wstools/java-wsdl does not handle recursive types

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1231?page=all ] Thomas Diesler updated JBWS-1231: --------------------------------- Fix Version/s: jbossws-1.0.6 (was: jbossws-1.0.5) If this issue has been rescheduled to 1.0.6 it is because we currently focus 80% of our effort on JAXWS. If need a particular feature or bugfix to be included in 1.0.5 you are welcome to get involved and contribute. > wstools/java-wsdl does not handle recursive types > ------------------------------------------------- > > Key: JBWS-1231 > URL: http://jira.jboss.com/jira/browse/JBWS-1231 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: wstools > Affects Versions: jbossws-1.0.3 > Reporter: Ole Matzura > Fix For: jbossws-1.0.6 > > > Hello, > I have the following fault class (generated from an existing wsdl with wstool/wsdl-java) > package v1.publishmessage.integrations.bis_bonnier_se; > public class BisFault extends Exception { > private java.lang.String code; > private java.lang.String message; > private v1.publishmessage.integrations.bis_bonnier_se.BisFault wrappedFault; > public BisFault(java.lang.String code, java.lang.String message, > v1.publishmessage.integrations.bis_bonnier_se.BisFault wrappedFault) { > super(code); > this.code = code; > this.message = message; > this.wrappedFault = wrappedFault; > } > public java.lang.String getCode() { > return code; > } > public java.lang.String getMessage() { > return message; > } > public v1.publishmessage.integrations.bis_bonnier_se.BisFault getWrappedFault() { > return wrappedFault; > } > } > as you can see, it contains a member of its own type (getWrappedFault..).. when I now try to publish a service using this fault with wstools/java-wsdl I get an error: > Exception in thread "main" java.lang.StackOverflowError > at java.util.TreeMap.access$300(TreeMap.java:81) > at java.util.TreeMap$PrivateEntryIterator.<init>(TreeMap.java:1015) > at java.util.TreeMap$KeyIterator.<init>(TreeMap.java:1056) > at java.util.TreeMap$KeyIterator.<init>(TreeMap.java:1056) > at java.util.TreeMap$1.iterator(TreeMap.java:580) > at org.jboss.ws.tools.schema.SchemaTypeCreator.generateExceptionParticles(SchemaTypeCreator.java:834) > at org.jboss.ws.tools.schema.SchemaTypeCreator.getComplexTypeForJavaException(SchemaTypeCreator.java:712) > at org.jboss.ws.tools.schema.SchemaTypeCreator.getType(SchemaTypeCreator.java:269) > at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:132) > at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:127) > at org.jboss.ws.tools.schema.SchemaTypeCreator.createFieldParticle(SchemaTypeCreator.java:607) > at org.jboss.ws.tools.schema.SchemaTypeCreator.generateExceptionParticles(SchemaTypeCreator.java:838) > at org.jboss.ws.tools.schema.SchemaTypeCreator.getComplexTypeForJavaException(SchemaTypeCreator.java:712) > at org.jboss.ws.tools.schema.SchemaTypeCreator.getType(SchemaTypeCreator.java:269) > etc... > seems there is a problem with this kind of recursive structure.. any workaround available? > regards! > /Ole -- 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

17 years, 7 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 November 2006