January 2007 - jbossws-issues - Jboss List Archives

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

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-800?page=all ] Thomas Diesler updated JBWS-800: -------------------------------- Summary: ClassCastException when trying to marshal a subclass of Date (was: ClassCastException when trying to marshal a SybaseTimestamp) > 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] Commented: (JBWS-1260) WSDL To Java - Parameter unwrapping fails for a lot of scenarios.

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1260?page=comments#action_12350666 ] Darran Lofthouse commented on JBWS-1260: ---------------------------------------- Design discussions: - such a part must refer to an element named after - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=97638 Sequence containing 2 elements - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=97270 What when we cannot unwrap the message parts? - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=97271 Unwrapping empty sequences - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=97608 Naming for anonymous types. - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=97450 Unwrapping and complex types with attributes. - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=97266 WSDL to Java Array Mappings - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=97264 > WSDL To Java - Parameter unwrapping fails for a lot of scenarios. > ----------------------------------------------------------------- > > Key: JBWS-1260 > URL: http://jira.jboss.com/jira/browse/JBWS-1260 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: wstools > Affects Versions: jbossws-1.0.4 > Reporter: Ole Matzura > Assigned To: Darran Lofthouse > Fix For: jbossws-1.2.0 > > > Testing parameter unwrapping when using wsdl to java with the following scenarios: - > A - Element contains anonymous complex type which contains a single element. > B - Element contains anonymous complex type which contains two elements. > C - Element references complex type which contains a single element. > D - Element references complex type which contains two elements. > E - Element references complex type which contains an anonymous type which contains a single element. > F - Element references complex type which contains an anonymous type which contains two elements. > G - Element contains anonymous complex type which contains a single element which is an array. (1) > H - Element references complex type which contains a single element which is an array. (3) > I - Element references complex type which contains an anonymous type which contains a single element which is an array. (5) > J - Element contains anonymout complex type which contains an empty sequence. > K - Element references complex type which contains an empty sequence. > L - Element references complex type which contains an anonymous type which contains an empty sequence. > Scenarios A, B, and G are failing with the following error: - > org.jboss.ws.WSException: String passed is null > at org.jboss.ws.metadata.wsdl.WSDLUtils.firstLetterUpperCase(WSDLUtils.java:455) > at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:137) > at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:113) > Scenario D > The parameter is being unwrapped even though it contains two elements, one of the elements is being lost. > Scenarios E, F, I, and L are failing with the following error: - > java.lang.IllegalArgumentException: local part cannot be "null" when creating a QName > at javax.xml.namespace.QName.<init>(Unknown Source) > at javax.xml.namespace.QName.<init>(Unknown Source) > at org.jboss.ws.tools.WSDLToJava.unwrapResponseParticles(WSDLToJava.java:316) > Scenarios J, and K are failing with the following error: - > org.jboss.ws.WSException: Attempt to unwrap a response type with no particles > at org.jboss.ws.tools.WSDLToJava.unwrapResponse(WSDLToJava.java:285) > at org.jboss.ws.tools.WSDLToJava.getReturnType(WSDLToJava.java:540) -- 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] Reopened: (JBWS-1260) WSDL To Java - Parameter unwrapping fails for a lot of scenarios.

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1260?page=all ] Darran Lofthouse reopened JBWS-1260: ------------------------------------ Add JAX-RPC spec section numbers to errors raised when unwrapping can not occur. > WSDL To Java - Parameter unwrapping fails for a lot of scenarios. > ----------------------------------------------------------------- > > Key: JBWS-1260 > URL: http://jira.jboss.com/jira/browse/JBWS-1260 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: wstools > Affects Versions: jbossws-1.0.4 > Reporter: Ole Matzura > Assigned To: Darran Lofthouse > Fix For: jbossws-1.2.0 > > > Testing parameter unwrapping when using wsdl to java with the following scenarios: - > A - Element contains anonymous complex type which contains a single element. > B - Element contains anonymous complex type which contains two elements. > C - Element references complex type which contains a single element. > D - Element references complex type which contains two elements. > E - Element references complex type which contains an anonymous type which contains a single element. > F - Element references complex type which contains an anonymous type which contains two elements. > G - Element contains anonymous complex type which contains a single element which is an array. (1) > H - Element references complex type which contains a single element which is an array. (3) > I - Element references complex type which contains an anonymous type which contains a single element which is an array. (5) > J - Element contains anonymout complex type which contains an empty sequence. > K - Element references complex type which contains an empty sequence. > L - Element references complex type which contains an anonymous type which contains an empty sequence. > Scenarios A, B, and G are failing with the following error: - > org.jboss.ws.WSException: String passed is null > at org.jboss.ws.metadata.wsdl.WSDLUtils.firstLetterUpperCase(WSDLUtils.java:455) > at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:137) > at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:113) > Scenario D > The parameter is being unwrapped even though it contains two elements, one of the elements is being lost. > Scenarios E, F, I, and L are failing with the following error: - > java.lang.IllegalArgumentException: local part cannot be "null" when creating a QName > at javax.xml.namespace.QName.<init>(Unknown Source) > at javax.xml.namespace.QName.<init>(Unknown Source) > at org.jboss.ws.tools.WSDLToJava.unwrapResponseParticles(WSDLToJava.java:316) > Scenarios J, and K are failing with the following error: - > org.jboss.ws.WSException: Attempt to unwrap a response type with no particles > at org.jboss.ws.tools.WSDLToJava.unwrapResponse(WSDLToJava.java:285) > at org.jboss.ws.tools.WSDLToJava.getReturnType(WSDLToJava.java:540) -- 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-1328) Client security configuration not loaded when client deployed with issolated classloader.

by Thomas Diesler (JIRA)

Client security configuration not loaded when client deployed with issolated classloader. ----------------------------------------------------------------------------------------- Key: JBWS-1328 URL: http://jira.jboss.com/jira/browse/JBWS-1328 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-1.0.2 Reporter: Thomas Diesler Assigned To: Darran Lofthouse Fix For: jbossws-1.0.3 When a client is deployed using an issolated classloader the security configuration of the client is not loaded as the wrong classloader is used to load the resource. This results in a warning being logged and the client sending messages that are not signed / encrypted. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBWS-1447) Handle @WebResult(header=true) correctly with document/literal wrapped

by Jason T. Greene (JIRA)

Handle @WebResult(header=true) correctly with document/literal wrapped ---------------------------------------------------------------------- Key: JBWS-1447 URL: http://jira.jboss.com/jira/browse/JBWS-1447 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxws Environment: com/sun/ts/tests/jws/webresult/webresult2/client/Client.java#testWSDL4_from_wsappclient Reporter: Jason T. Greene Fix For: jbossws-2.0.0 Since header is enabled on the return type, it overwrites the resposne wrapper (See below). The fix is probably to add header support to WrappedParameter. OperationMetaData: qname={http://server.webresult2.webresult.jws.tests.ts.sun.com/}helloString4 javaName=hello4 style=document/literal/WRAPPED oneWay=false soapAction=urn:HelloString4 ParameterMetaData: xmlName={http://server.webresult2.webresult.jws.tests.ts.sun.com/}helloSt... partName=helloString4 xmlType={http://server.webresult2.webresult.jws.tests.ts.sun.com/}helloSt... javaType=com.sun.ts.tests.jws.webresult.webresult2.server.jaxws.Hello4 mode=IN inHeader=false index=0 wrappedParameters=[[name = arg1, type = java.lang.String, typeArgs = null, variable = arg1, index = 1]] ParameterMetaData: xmlName={hello4/employee}EmployeeName partName=EmployeeName xmlType={http://server.webresult2.webresult.jws.tests.ts.sun.com/}employee javaType=com.sun.ts.tests.jws.common.Employee mode=IN inHeader=true index=0 ReturnMetaData: xmlName={hello4/employee}employee partName=Employee xmlType={http://server.webresult2.webresult.jws.tests.ts.sun.com/}employee javaType=com.sun.ts.tests.jws.common.Employee mode=OUT inHeader=true index=-1 FaultMetaData xmlName={http://server.webresult2.webresult.jws.tests.ts.sun.com/}NameExc... xmlType={http://server.webresult2.webresult.jws.tests.ts.sun.com/}NameExc... javaType=com.sun.ts.tests.jws.common.NameException faultBean=com.sun.ts.tests.jws.webresult.webresult2.server.jaxws.NameExceptionBean -- 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] Updated: (JBWS-1294) Add support for mapping async methods

by Jason T. Greene (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1294?page=all ] Jason T. Greene updated JBWS-1294: ---------------------------------- Fix Version/s: jbossws-2.0.0 (was: jbossws-1.2.0) There is already support for this that works in most cases, although it needs to be updated to allow the async method to have any name > Add support for mapping async methods > ------------------------------------- > > Key: JBWS-1294 > URL: http://jira.jboss.com/jira/browse/JBWS-1294 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxws > Reporter: Jason T. Greene > Assigned To: Jason T. Greene > Fix For: jbossws-2.0.0 > > > JSR181MetaDataBuilder, the UnifiedMetaDataModel, and ClientProxy need to be refactored. -- 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] Updated: (JBWS-652) Add JAAS certificate authentication support to ws-security implementation

by Jason T. Greene (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-652?page=all ] Jason T. Greene updated JBWS-652: --------------------------------- Fix Version/s: jbossws-2.1.0 (was: jbossws-1.2.0) > Add JAAS certificate authentication support to ws-security implementation > ------------------------------------------------------------------------- > > Key: JBWS-652 > URL: http://jira.jboss.com/jira/browse/JBWS-652 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Jason T. Greene > Assigned To: Jason T. Greene > Fix For: jbossws-2.1.0 > > > Currently X.509 tokens are validated against a truststore that is local to the ws-security deployment. We should offer support for delegating to JAAS/JBossSX so that JEE declarative security can reference known certificates. There is one problem with adding support for this, which is that a WS-Security message may contain many X.509 tokens (perhaps one for signature, and one for encryption), so we would have to somehow decide to pick one. -- 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] Commented: (JBWS-652) Add JAAS certificate authentication support to ws-security implementation

by Jason T. Greene (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-652?page=comments#action_12350553 ] Jason T. Greene commented on JBWS-652: -------------------------------------- The customer decided they didn't need this, so I am rescheduling after 2.0.0. > Add JAAS certificate authentication support to ws-security implementation > ------------------------------------------------------------------------- > > Key: JBWS-652 > URL: http://jira.jboss.com/jira/browse/JBWS-652 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Jason T. Greene > Assigned To: Jason T. Greene > Fix For: jbossws-1.2.0 > > > Currently X.509 tokens are validated against a truststore that is local to the ws-security deployment. We should offer support for delegating to JAAS/JBossSX so that JEE declarative security can reference known certificates. There is one problem with adding support for this, which is that a WS-Security message may contain many X.509 tokens (perhaps one for signature, and one for encryption), so we would have to somehow decide to pick one. -- 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] 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: Prabhat Jha (was: Thomas Diesler) > 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: Prabhat Jha > Fix For: jbossws-1.2.0 > > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1274) jboss-4.0.4.GA (jdk1.4)

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1274?page=all ] Thomas Diesler updated JBWS-1274: --------------------------------- Assignee: Prabhat Jha (was: Thomas Diesler) > jboss-4.0.4.GA (jdk1.4) > ----------------------- > > Key: JBWS-1274 > URL: http://jira.jboss.com/jira/browse/JBWS-1274 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Prabhat Jha > Fix For: jbossws-1.2.0 > > > Run these tests with jdk1.4 > 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-archive/jboss-4.0.4/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, 10 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 January 2007