April 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2086) Update AS5 container integration to work on EJB3 integration API only

by Heiko Braun (JIRA)

Update AS5 container integration to work on EJB3 integration API only --------------------------------------------------------------------- Key: JBWS-2086 URL: http://jira.jboss.com/jira/browse/JBWS-2086 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assigned To: Heiko Braun -- 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

16 years

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2089) isXOPPackage() is returning an incorrect value

by David Boeren (JIRA)

isXOPPackage() is returning an incorrect value ---------------------------------------------- Key: JBWS-2089 URL: http://jira.jboss.com/jira/browse/JBWS-2089 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-2.0.3 Reporter: David Boeren I am trying to pass an mtom/xop attachment on a webservice call, but the attachment is not being correctly received. When I step through the JbossWS code, it gets to the org.jboss.ws.extensions.xop.jaxws.AttachmentUnmarshallerImpl class. When the isXOPPackage() method is called, the return value is false, so the getAttachmentAsDataHandler() method never gets called. If I force the isXOPPackage() to return true, then getAttachmentAsDataHandler() is called, and I can see the attachment data in the web method. So, it looks as if there is a bug in isXOPPackage() which is preventing it from recognizing the attachment. -- 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

16 years

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-2103) JBoss tools classpath problem

by Heiko Braun (JIRA)

JBoss tools classpath problem ----------------------------- Key: JBWS-2103 URL: http://jira.jboss.com/jira/browse/JBWS-2103 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-3.0.1 Reporter: Heiko Braun Priority: Critical Fix For: jbossws-3.0.2 The predefined eclipse classpath seems to contain jaxws-rt.jar which causes the service loader to fail. It then references private sun classes instead of the jboss-jaxws implementation. -- 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

16 years

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2141) SPI 3.0 Milestone 1 container integration

by Heiko Braun (JIRA)

SPI 3.0 Milestone 1 container integration ----------------------------------------- Key: JBWS-2141 URL: http://jira.jboss.com/jira/browse/JBWS-2141 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Heiko Braun -- 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

16 years

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2142) SPI 3.0 Milestone 1 stack integration

by Heiko Braun (JIRA)

SPI 3.0 Milestone 1 stack integration ------------------------------------- Key: JBWS-2142 URL: http://jira.jboss.com/jira/browse/JBWS-2142 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Heiko Braun Fix For: community contributions -- 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

16 years

1
2
0 / 0

[JBoss JIRA] Updated: (JBWS-2140) SPI 3.0 Milestone 2

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-2140?page=all ] Heiko Braun updated JBWS-2140: ------------------------------ > SPI 3.0 Milestone 2 > ------------------- > > Key: JBWS-2140 > URL: http://jira.jboss.com/jira/browse/JBWS-2140 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Heiko Braun > -- 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

16 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2140) SPI 3.0 Milestone 2

by Heiko Braun (JIRA)

SPI 3.0 Milestone 2 ------------------- Key: JBWS-2140 URL: http://jira.jboss.com/jira/browse/JBWS-2140 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Heiko Braun -- 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

16 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-2122) XmlElementWrapper + XmlElement annotations do not work on incoming SOAP

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-2122?page=all ] Thomas Diesler updated JBWS-2122: --------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > XmlElementWrapper + XmlElement annotations do not work on incoming SOAP > ----------------------------------------------------------------------- > > Key: JBWS-2122 > URL: http://jira.jboss.com/jira/browse/JBWS-2122 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-native > Environment: WIndowsXP / FreeBSD > Reporter: Sergey Abramov > Assigned To: Thomas Diesler > Fix For: jbossws-native-3.0.2 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I am using document based web services on top of EJB3 and I recently upgraded from 4.0.5.GA to 4.2.2.GA. > After the upgrade the following method stopped working when I was sending data to the JBoss from my Flex application: > @XmlElementWrapper(name="ids") > @XmlElement(name="id") > public Set<Long> getIds() { > return ids == null ? new HashSet<Long>() : ids; > } > Here is the SOAP that was sent across: > <?xml version="1.0" encoding="utf-8"?> > <SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><SOAP-ENV:Body><ns0:executeDeleteLabels xmlns:ns0="http://com.coldcore/diva2/main-service"><arg0><site>ac1</site><ids><id>62653</id></ids></arg0></ns0:executeDeleteLabels></SOAP-ENV:Body></SOAP-ENV:Envelope> > "ids" set in the method above was always null on 4.2.2.GA, and worked as expected on 4.0.5.GA > After trying to find a solution in the internet I found that this might be caused by JBossXB, so I replaced all the "jboss-xml-binding.jar" in 4.2.2.GA with older versions from 4.0.5.GA (I also replaced all the jaxb-xxx.jar just in case). And it worked! The method returned "ids" as expected. I assume that "jboss-xml-binding.jar" under 4.2.2.GA is bugged. -- 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

16 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1714) CLONE - Verify correct bahaviour of @WebService.wsdlLocation

by Heiko Braun (JIRA)

CLONE - Verify correct bahaviour of @WebService.wsdlLocation ------------------------------------------------------------ Key: JBWS-1714 URL: http://jira.jboss.com/jira/browse/JBWS-1714 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxws Reporter: Heiko Braun Assigned To: Thomas Diesler Fix For: jbossws-2.0.0 I get a wsdl now but it is not the one I defined in my wsdlLocation value in the endpoint interface in the wsdlLocation javax.jws.WebService annotation. I get datetime types set to anySimpleType and all my enumerations have camel case now like this - dropOffType - rather than DropOffType like in the wsdl. I believe a wsdl is being generated still. How do I generate and deploy a web service and have jboss use the wsdl I supply in the war? -- 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

16 years

4
11
0 / 0

[JBoss JIRA] Created: (JBWS-2083) EJB3 integration API for deployment and invocation handling

by Heiko Braun (JIRA)

EJB3 integration API for deployment and invocation handling ----------------------------------------------------------- Key: JBWS-2083 URL: http://jira.jboss.com/jira/browse/JBWS-2083 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-3.0.1 Further decouple WS from EJB3 implementation details. The associated forum thread covers the details. -- 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

16 years

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues April 2008