January 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1500) Improve etc/jboss.sh to reliably start/shutdown server instances

by Thomas Diesler (JIRA)

Improve etc/jboss.sh to reliably start/shutdown server instances ---------------------------------------------------------------- Key: JBWS-1500 URL: http://jira.jboss.com/jira/browse/JBWS-1500 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: productization Reporter: Thomas Diesler Fix For: jbossws-1.2.0 We need to reliably detect that jboss is up and that jbossws got deployed correctly. On shutdown, the server should be killed if ordinary shutdown fails. A failing shutdown should not hang the entire QA matrix -- 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-76) Vote for WS-Reliable Messaging

by Alexandre Reis (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-76?page=comments#action_12351923 ] Alexandre Reis commented on JBWS-76: ------------------------------------ The WS-RM spec may be dead on improvements, but it is a established way or doing reliable messaging using web services, and has many implementations that adopt is such as Apache Sandesha, IBM Websphere 6.1 with extensions and BEA Weblogic 10.0. I need WS-RM in my current project, and it is the main point why I'm dropping JBoss as an option and going for a commercial app server instead. > Vote for WS-Reliable Messaging > ------------------------------ > > Key: JBWS-76 > URL: http://jira.jboss.com/jira/browse/JBWS-76 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jaxrpc > Reporter: Thomas Diesler > Fix For: jbossws-voting > > > Please vote for WS-ReliableMessaging if this is relevant to your enterprise web services > http://www-106.ibm.com/developerworks/library/ws-rm/ > This specification (WS-ReliableMessaging) describes a protocol that allows messages to be delivered reliably between distributed applications in the presence of software component, system, or network failures. The updates are based upon the suggestions collected from the WS-ReliableMessaging Feedback Workshop held in July 2003 and the Interoperability Workshop help in October 2003. The protocol is described in this specification in an independent manner allowing it to be implemented using different network transport technologies. To support interoperable Web services, a SOAP binding is defined within this specification. > The protocol defined in this specification depends upon other Web services specifications for the identification of service endpoint addresses and policies. How these are identified and retrieved are detailed within those specifications and are out of scope for this document. -- 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-1499) Revisit WebServiceRefHandler JNDI rebind

by Thomas Diesler (JIRA)

Revisit WebServiceRefHandler JNDI rebind ---------------------------------------- Key: JBWS-1499 URL: http://jira.jboss.com/jira/browse/JBWS-1499 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jaxws Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-2.0.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
0
0 / 0

[JBoss JIRA] Reopened: (JBWS-1086) Conformance Requirements: Java to WSDL

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1086?page=all ] Thomas Diesler reopened JBWS-1086: ---------------------------------- Why should this being resolved "Out of Date"? > Conformance Requirements: Java to WSDL > -------------------------------------- > > Key: JBWS-1086 > URL: http://jira.jboss.com/jira/browse/JBWS-1086 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: wstools > Reporter: Thomas Diesler > Assigned To: Jason T. Greene > Fix For: jbossws-2.0.0 > > > Please make sure jbossws conforms to these requirements. > Resolving this issue means we do conform unless you create new issues that are linked to this one and are beeing dealt with seperately. > 3.1 WSDL 1.1 support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 > 3.2 Standard annotations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 > 3.3 Java identifier mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 > 3.4 Method name disambiguation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 > 3.5 Package name mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 > 3.6 WSDL and XML Schema import directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 > 128 JAX-WS 2.0 April 19, 2006 > 3.7 Class mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 > 3.8 portType naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 > 3.9 Inheritance flattening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 > 3.10 Inherited interface mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 > 3.11 Operation naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 > 3.12 One-way mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 > 3.13 One-way mapping errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 > 3.14 Parameter classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 > 3.15 Parameter naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 > 3.16 Result naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 > 3.17 Header mapping of parameters and results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 > 3.18 Default wrapper bean names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 > 3.19 Default wrapper bean package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 > 3.20 Wrapper element names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 > 3.21 Wrapper bean name clash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 > 3.22 Null Values in rpc/literal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 > 3.23 Exception naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 > 3.24 Fault bean name clash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 > 3.25 Binding selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 > 3.26 SOAP binding support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 > 3.27 SOAP binding style required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 > 3.28 Service creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 > 3.29 Port selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 > 3.30 Port binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 -- 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-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 reopened JBWS-800: --------------------------------- Assignee: Alexey Loubyansky (was: Thomas Diesler) Please create a (non-snapshot) jdk14 release that works in jboss50,42,40 > 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-1497) Fix failed resource lookup when offline

by Thomas Diesler (JIRA)

Fix failed resource lookup when offline --------------------------------------- Key: JBWS-1497 URL: http://jira.jboss.com/jira/browse/JBWS-1497 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: ws-eventing Reporter: Thomas Diesler Assigned To: Heiko Braun Fix For: jbossws-1.2.0 Failed org.jboss.test.ws.jaxws.samples.wseventing.SysmonTestCase.testSubscribe Caused by: java.net.UnknownHostException: www.w3.org at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177) at java.net.Socket.connect(Socket.java:516) at java.net.Socket.connect(Socket.java:466) at sun.net.NetworkClient.doConnect(NetworkClient.java:157) at sun.net.www.http.HttpClient.openServer(HttpClient.java:365) at sun.net.www.http.HttpClient.openServer(HttpClient.java:477) at sun.net.www.http.HttpClient.<init>(HttpClient.java:214) at sun.net.www.http.HttpClient.New(HttpClient.java:287) at sun.net.www.http.HttpClient.New(HttpClient.java:299) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:796) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:748) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:673) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:917) at java.net.URL.openStream(URL.java:1007) at org.jboss.ws.core.utils.ResourceURL.openStream(ResourceURL.java:57) at org.jboss.ws.tools.JavaToXSD.parseSchema(JavaToXSD.java:175) Standard Error -- 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-868) BPEL in jbossws-samples

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-868?page=all ] Thomas Diesler updated JBWS-868: -------------------------------- Comment: was deleted > BPEL in jbossws-samples > ----------------------- > > Key: JBWS-868 > URL: http://jira.jboss.com/jira/browse/JBWS-868 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Alejandro Guizar > Fix For: jbossws-1.0.4 > > > Every chapter in the userguide is backed up with one/more testcase in the jbossws testsuite. The tests are then compiled together in a standlaone sample zip. > Please show us how to use BPEL with some samples. -- 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-868) BPEL in jbossws-samples

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-868?page=all ] Thomas Diesler updated JBWS-868: -------------------------------- Fix Version/s: (was: jbossws-1.2.0) > BPEL in jbossws-samples > ----------------------- > > Key: JBWS-868 > URL: http://jira.jboss.com/jira/browse/JBWS-868 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Alejandro Guizar > Fix For: jbossws-1.0.4 > > > Every chapter in the userguide is backed up with one/more testcase in the jbossws testsuite. The tests are then compiled together in a standlaone sample zip. > Please show us how to use BPEL with some samples. -- 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-868) BPEL in jbossws-samples

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-868?page=all ] Thomas Diesler updated JBWS-868: -------------------------------- Fix Version/s: jbossws-1.2.0 > BPEL in jbossws-samples > ----------------------- > > Key: JBWS-868 > URL: http://jira.jboss.com/jira/browse/JBWS-868 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Alejandro Guizar > Fix For: jbossws-1.0.4, jbossws-1.2.0 > > > Every chapter in the userguide is backed up with one/more testcase in the jbossws testsuite. The tests are then compiled together in a standlaone sample zip. > Please show us how to use BPEL with some samples. -- 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-868) BPEL in jbossws-samples

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-868?page=all ] Thomas Diesler reopened JBWS-868: --------------------------------- Please fix for 1.2.0 This is seen in jboss50 java.lang.NullPointerException at org.jbpm.bpel.integration.server.SoapHandler.handleRequest(SoapHandler.java:183) at org.jboss.ws.core.jaxrpc.handler.HandlerWrapper.handleRequest(HandlerWrapper.java:121) at org.jboss.ws.core.jaxrpc.handler.HandlerChainBaseImpl.handleRequestInternal(HandlerChainBaseImpl.java:275) at org.jboss.ws.core.jaxrpc.handler.HandlerChainBaseImpl.handleRequest(HandlerChainBaseImpl.java:235) at org.jboss.ws.core.jaxrpc.handler.ServerHandlerChain.handleRequest(ServerHandlerChain.java:53) at org.jboss.ws.core.jaxrpc.handler.HandlerDelegateJAXRPC.callRequestHandlerChain(HandlerDelegateJAXRPC.java:96) at org.jboss.ws.core.server.AbstractServiceEndpointInvoker.callRequestHandlerChain(AbstractServiceEndpointInvoker.java:99) To do the QA run $ cd build $ ant hudson-setup > BPEL in jbossws-samples > ----------------------- > > Key: JBWS-868 > URL: http://jira.jboss.com/jira/browse/JBWS-868 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Alejandro Guizar > Fix For: jbossws-1.0.4 > > > Every chapter in the userguide is backed up with one/more testcase in the jbossws testsuite. The tests are then compiled together in a standlaone sample zip. > Please show us how to use BPEL with some samples. -- 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