February 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1510) Java To WSDL - incorrect handling of inherited classes

by Stephan Gasser (JIRA)

Java To WSDL - incorrect handling of inherited classes ------------------------------------------------------ Key: JBWS-1510 URL: http://jira.jboss.com/jira/browse/JBWS-1510 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: wstools Affects Versions: jbossws-1.0.4, jbossws-1.0.3.SP1 Reporter: Stephan Gasser -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1509) Namespace incorrect for complex types

by Peter Yuill (JIRA)

Namespace incorrect for complex types ------------------------------------- Key: JBWS-1509 URL: http://jira.jboss.com/jira/browse/JBWS-1509 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxws Affects Versions: jbossws-2.0.0.CR2, jbossws-1.0.4, jbossws-1.0.3.SP1 Environment: WindowsXP, Sun java 1.5.0_10, jboss4.0.5/jboss5.0.0.Beta1 Reporter: Peter Yuill Using a JSR181 pojo service with a targetNamespace set in the @WebService annotation creates WSDL with incorrect targetNamespace for some referenced complex types. The correct namespace is determined for types referenced directly, but the default namespace is allocated to any indirectly referenced type. For example the following service code: @WebService(targetNamespace="http://test.com") @SOAPBinding(style=SOAPBinding.Style.RPC, use=SOAPBinding.Use.LITERAL) public class TestWS implements ServiceLifecycle { @WebMethod public Type1 getType1() {return new Type1();} @WebMethod public Type2[] getType2() {return new Type2[0];} @WebMethod public Type3 getType3() {return new Type3();} generates the correct namespace (http://test.com) for Type1, Type3 and Type2.Array, but generates the default (http://test/jaws) for Type2 and Type4 (referenced by Type3). -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1487) XOP

by Thomas Diesler (JIRA)

XOP --- Key: JBWS-1487 URL: http://jira.jboss.com/jira/browse/JBWS-1487 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (JBWS-1476) Provide a Quick Start

by Thomas Diesler (JIRA)

Provide a Quick Start --------------------- Key: JBWS-1476 URL: http://jira.jboss.com/jira/browse/JBWS-1476 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: productization Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-1.2.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

17 years, 10 months

1
2
0 / 0

[JBoss JIRA] Commented: (JBWS-800) ClassCastException when trying to marshal a subclass of Date

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-800?page=comments#action_12352337 ] Thomas Diesler commented on JBWS-800: ------------------------------------- Actually jboss50 is not that relevant because it is not a production target container for jbossws-1.2.0 > ClassCastException when trying to marshal a subclass of Date > ------------------------------------------------------------ > > Key: JBWS-800 > URL: http://jira.jboss.com/jira/browse/JBWS-800 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxrpc > Affects Versions: jbossws-1.0.0.CR4 > Environment: Windows XP, JBoss 4.0.4.CR2 > Reporter: Chris Baxter > Assigned To: Alexey Loubyansky > Fix For: jbossws-1.2.0 > > > I have a EJB3 persistent bean mapped to a Sybase DB table. This table has datetime column that I have mapped back to a java.util.Date property on the persistent bean. This same bean class is returned from a webservice call. On JBoss 4.0.3SP1 (using Axis), I had no issues returning this object from my finder call. Now, when I switch to JBoss 4.0.4CR2 (using JBossWS), I get the following exception: > Caused by: java.lang.ClassCastException: com.sybase.jdbc3.tds.SybTimestamp > at org.jboss.xb.binding.SimpleTypeBindings.marshal(SimpleTypeBindings.java:1150) > at org.jboss.xb.binding.XercesXsMarshaller.marshalCharacters(XercesXsMarshaller.java:1169) > at org.jboss.xb.binding.XercesXsMarshaller.marshalSimpleType(XercesXsMarshaller.java:451) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElementType(XercesXsMarshaller.java:405) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElement(XercesXsMarshaller.java:380) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElementOccurence(XercesXsMarshaller.java:886) > at org.jboss.xb.binding.XercesXsMarshaller.marshalParticle(XercesXsMarshaller.java:823) > at org.jboss.xb.binding.XercesXsMarshaller.marshalModelGroupSequence(XercesXsMarshaller.java:1102) > at org.jboss.xb.binding.XercesXsMarshaller.marshalModelGroup(XercesXsMarshaller.java:1057) > at org.jboss.xb.binding.XercesXsMarshaller.marshalParticle(XercesXsMarshaller.java:729) > at org.jboss.xb.binding.XercesXsMarshaller.marshalComplexType(XercesXsMarshaller.java:685) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElementType(XercesXsMarshaller.java:414) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElement(XercesXsMarshaller.java:380) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElementOccurence(XercesXsMarshaller.java:886) > at org.jboss.xb.binding.XercesXsMarshaller.marshalParticle(XercesXsMarshaller.java:810) > at org.jboss.xb.binding.XercesXsMarshaller.marshalModelGroupSequence(XercesXsMarshaller.java:1102) > at org.jboss.xb.binding.XercesXsMarshaller.marshalModelGroup(XercesXsMarshaller.java:1057) > at org.jboss.xb.binding.XercesXsMarshaller.marshalParticle(XercesXsMarshaller.java:729) > at org.jboss.xb.binding.XercesXsMarshaller.marshalComplexType(XercesXsMarshaller.java:685) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElementType(XercesXsMarshaller.java:414) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElement(XercesXsMarshaller.java:380) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElementOccurence(XercesXsMarshaller.java:886) > at org.jboss.xb.binding.XercesXsMarshaller.marshallInternal(XercesXsMarshaller.java:275) > at org.jboss.xb.binding.XercesXsMarshaller.marshal(XercesXsMarshaller.java:222) > at org.jboss.ws.jaxb.JAXBMarshallerImpl.marshal(JAXBMarshallerImpl.java:172) > at org.jboss.ws.jaxrpc.encoding.JAXBSerializer.serialize(JAXBSerializer.java:100) > at org.jboss.ws.soap.SOAPContentElement.getXMLFragment(SOAPContentElement.java:172) > at org.jboss.ws.soap.SOAPContentElement.expandToDOM(SOAPContentElement.java:844) > at org.jboss.ws.soap.SOAPContentElement.getChildNodes(SOAPContentElement.java:761) > at org.jboss.util.xml.DOMWriter.printInternal(DOMWriter.java:201) > at org.jboss.util.xml.DOMWriter.printInternal(DOMWriter.java:260) > at org.jboss.util.xml.DOMWriter.printInternal(DOMWriter.java:260) > at org.jboss.util.xml.DOMWriter.print(DOMWriter.java:177) > at org.jboss.util.xml.DOMWriter.printNode(DOMWriter.java:126) > at org.jboss.ws.server.ServiceEndpoint.postProcessResponse(ServiceEndpoint.java:306) > ... 23 more > In looking at the source code, I think I see why there may be a problem: > else if(typeCode == XS_DATETIME) > { > Calendar c; > if(value.getClass() == java.util.Date.class) > { > c = Calendar.getInstance(); > c.clear(); > c.setTime((java.util.Date)value); > } > else > { > c = (Calendar)value; > } > result = marshalDateTime(c); > } > The SybaseTimestamp class extends java.sql.Timestamp which in turn extends java.util.Date. That first 'if' should hit, but it won't because SybaseTimestamp.class != java.util.Date.class. Instead, I think the if statement should be: > if(java.util.Date.class.isAssignableFrom(value.getClass())) > I made this change and recompiled and everything works as expected now. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1442) Update cruise control

by Thomas Diesler (JIRA)

Update cruise control --------------------- Key: JBWS-1442 URL: http://jira.jboss.com/jira/browse/JBWS-1442 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: documentation Reporter: Thomas Diesler Assigned To: Prabhat Jha Fix For: jbossws-1.2.0 Hi Prabhat, the jbossws build has changed and we are now using a single codebase across jbossas versions. For details please see http://www.jboss.org/index.html?module=bb&op=viewtopic&t=98635 Could you please change the jbossws cruise control projects according to this matrix jbossws jbossas jdk ----------------------------------------- trunk trunk jdk1.5 trunk Branch_4_2 jdk1.5 trunk Branch_4_0 jdk1.5 trunk Branch_4_0 jdk1.4 cheers -thomas -- 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, 10 months

3
19
0 / 0

[JBoss JIRA] Updated: (JBWS-1296) Add support for digest + nonces

by Jason T. Greene (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1296?page=all ] Jason T. Greene updated JBWS-1296: ---------------------------------- Summary: Add support for digest + nonces (was: Add support for nonces) > Add support for digest + nonces > ------------------------------- > > Key: JBWS-1296 > URL: http://jira.jboss.com/jira/browse/JBWS-1296 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Thomas Diesler > Fix For: jbossws-2.1.0 > > > Add support for nonces, as well as a configurable encoding type for them. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1504) Resolve dependency on snapshots

by Thomas Diesler (JIRA)

Resolve dependency on snapshots ------------------------------- Key: JBWS-1504 URL: http://jira.jboss.com/jira/browse/JBWS-1504 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: productization Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-1.2.0 [tdiesler@localhost build]$ cat version.properties | grep snap jboss-jbossxb=snapshot jboss-jbossretro=snapshot jboss-vfs=2.0.0.snapshot -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1503) Support XOP samples in tomcat

by Thomas Diesler (JIRA)

Support XOP samples in tomcat ----------------------------- Key: JBWS-1503 URL: http://jira.jboss.com/jira/browse/JBWS-1503 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jaxrpc, jaxws Reporter: Thomas Diesler Assigned To: Heiko Braun Fix For: jbossws-1.2.0 The tests currently rely on app clients. Have a look how other samples do it. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1451) the comparison of the mime type should not be case sensitive

by edward winston (JIRA)

the comparison of the mime type should not be case sensitive ------------------------------------------------------------ Key: JBWS-1451 URL: http://jira.jboss.com/jira/browse/JBWS-1451 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.0.4 Environment: Linux, JBoss 4.0.5GA, x86-64 and i386, jdk 5 Reporter: edward winston It appears that the comparison when looking at the Mimetype for a message with attachments is using a case sensitive comparison. According to the RFCs, the mime type comparison should be case insensitive. This means that if the correct case is not sent (the mime type in question being Multipart/Related), the request cannot be parsed and you will get a soap fault. -- 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, 10 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues February 2007