April 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2077) Provide JMS Binding in generated WSDL

by Thomas Diesler (JIRA)

Provide JMS Binding in generated WSDL -------------------------------------- Key: JBWS-2077 URL: http://jira.jboss.com/jira/browse/JBWS-2077 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Thomas Diesler Fix For: jbossws-3.x Currently, the client will have to use the JMS API directly InitialContext context = new InitialContext(); QueueConnectionFactory connectionFactory = (QueueConnectionFactory)context.lookup("ConnectionFactory"); Queue reqQueue = (Queue)context.lookup("queue/RequestQueue"); Queue resQueue = (Queue)context.lookup("queue/ResponseQueue"); QueueConnection con = connectionFactory.createQueueConnection(); QueueSession session = con.createQueueSession(false, Session.AUTO_ACKNOWLEDGE); QueueReceiver receiver = session.createReceiver(resQueue); ResponseListener responseListener = new ResponseListener(); receiver.setMessageListener(responseListener); con.start(); TextMessage message = session.createTextMessage(reqMessage); message.setJMSReplyTo(resQueue); waitForResponse = true; QueueSender sender = session.createSender(reqQueue); sender.send(message); sender.close(); int timeout = 5000; while (waitForResponse && timeout > 0) { Thread.sleep(100); timeout -= 100; } assertNotNull("Expected response message", responseListener.resMessage); assertEquals(DOMUtils.parse(resMessage), DOMUtils.parse(responseListener.resMessage)); con.stop(); session.close(); con.close(); Instead, the client should use the standard JAX-WS API to consume a wsdl that defines the jms binding -- 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, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-2062) JSON message type

by Thomas Diesler (JIRA)

JSON message type ----------------- Key: JBWS-2062 URL: http://jira.jboss.com/jira/browse/JBWS-2062 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

16 years, 9 months

1
6
0 / 0

[JBoss JIRA] Created: (JBWS-2061) JSON wsdl generation

by Thomas Diesler (JIRA)

JSON wsdl generation -------------------- Key: JBWS-2061 URL: http://jira.jboss.com/jira/browse/JBWS-2061 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

16 years, 9 months

1
5
0 / 0

[JBoss JIRA] Created: (JBWS-2120) @WebWservice does not work with class isolation

by Thomas Diesler (JIRA)

@WebWservice does not work with class isolation ------------------------------------------------ Key: JBWS-2120 URL: http://jira.jboss.com/jira/browse/JBWS-2120 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-2.0.0 It seems that Web Services do not work when the EAR that contains the @WebService class has an isolated classloader. Here is my take on what happens: You deploy the ear and JBoss creates a war, that contains a web.xml, that points to the org.jboss.ws.server.ServiceEndpointServlet. You can send a request to the web service bean no problem, but any objects that get returned from it will throw a NoClassDefFoundError because this ServiceEndpointServlet is deployed outside of the EAR and, since it has an isolated classloader, can't reference the returned class. My application works absolutely fine when I turn off all isolation of the classloader. I don't think this can be fixed. Any ideas? -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2053) Client side transport abstraction

by Heiko Braun (JIRA)

Client side transport abstraction --------------------------------- Key: JBWS-2053 URL: http://jira.jboss.com/jira/browse/JBWS-2053 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-3.0.2 -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Updated: (JBWS-1526) Automated testing and availablity checks of public endpoints (interop)

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1526?page=all ] Thomas Diesler updated JBWS-1526: --------------------------------- Due Date: 16/May/08 > Automated testing and availablity checks of public endpoints (interop) > ---------------------------------------------------------------------- > > Key: JBWS-1526 > URL: http://jira.jboss.com/jira/browse/JBWS-1526 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Heiko Braun > Assigned To: Heiko Braun > Fix For: jbossws-3.0.2 > > > Is this a duplicate? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2008) EJB3 WS API

by Heiko Braun (JIRA)

EJB3 WS API ----------- Key: JBWS-2008 URL: http://jira.jboss.com/jira/browse/JBWS-2008 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jbossws-3.0.0 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-3.0.1 Further decoupling from the EJB project. Actually there should only be a dependency on the ejb3-ws.jar (to be defined) and the EE5 API. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Commented: (JBWS-1566) Invalid wsdl using @XmlSchema annotations on Types

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1566?page=comments#action_12407858 ] Thomas Diesler commented on JBWS-1566: -------------------------------------- [tdiesler@tddell trunk]$ ant -Dtest=jaxws/jbws1566 test tests-run-internal: [junit] Running org.jboss.test.ws.jaxws.jbws1566.c.JBWS1566TestCase [junit] wsdl URL:http://localhost:8080/jaxwstest/Jaxb20StatelessTestBean?wsdl [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 6.004 sec [junit] Test org.jboss.test.ws.jaxws.jbws1566.c.JBWS1566TestCase FAILED > Invalid wsdl using @XmlSchema annotations on Types > -------------------------------------------------- > > Key: JBWS-1566 > URL: http://jira.jboss.com/jira/browse/JBWS-1566 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-native > Affects Versions: jbossws-1.2.0 > Environment: JBossAS-4.0.5, jdk 5, jbossws 1.2.0.GA > Reporter: Robert Mlekus > Assigned To: Heiko Braun > Fix For: jbossws-2.0.0 > > Attachments: JBWS-1566-JbossWS-Samples-001.patch > > > While the @javax.xml.bind.annotation.XmlSchema annotation within the package-info.java of an class not inheriting from other packages works perfectly, JBossWS generates the following error for derived datatypes: > <code> > 14:35:02,173 ERROR [ServiceEndpointPublisher] Cannot obtain waURL for: webservice-test.ear/webservic > e-test.jar > 14:35:02,283 ERROR [JBossXSErrorHandler] [domain:http://www.w3.org/TR/xml-schema-1]::[key=src-resolv > e.4.2]::Message=src-resolve.4.2: Error resolving component 'ns1:aClass'. It was detected that 'ns1:a > Class' is in namespace 'http://test.org/wsclient/a', but components from this namespace are not refe > renceable from schema document 'null'. If this is the incorrect namespace, perhaps the prefix of 'ns > 1:aClass' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag sh > ould be added to 'null'. > <code> > The Parameter classes causing this problem are a.AClass, b.Bclass defined in the packages a, and b with the following package-info.java @XmlSchema annotations: > The following examples will be attached as a patch for the jbossws-samples, too but are given here for a short summary on the problem. > file a/package-info.java: > ------ > @javax.xml.bind.annotation.XmlSchema(namespace = http://test.org/wsclient/a" ) > package a; > ------ > > file a/AClass.java: > ------ > package a; > public class AClass { > int a; > > public int getA() { > return a; > } > public void setA(int testInt) { > this.a = testInt; > } > } > ------ > file b/package-info.java: > ------ > @javax.xml.bind.annotation.XmlSchema(namespace = http://test.org/wsclient/b" ) > package b; > ------ > > file b/BClass.java > ------ > package b; > public class BClass extends a.AClass { > String b; > > public String getB() { > return b; > } > public void setB(String testString) { > this.b = testString; > } > } > ------ > > The relevant part of the generated WSDL (which is visible under jbossws/service is: > <xs:schema targetNamespace="http://test.org/wsclient/b" version="1.0"> > <xs:complexType name="bClass"> > <xs:complexContent> > <xs:extension base="ns1:aClass"> > <xs:sequence> > <xs:element minOccurs="0" name="b" type="xs:string"/> > </xs:sequence> > </xs:extension> > </xs:complexContent> > </xs:complexType> > </xs:schema> > <xs:schema targetNamespace="http://test.org/wsclient/a" version="1.0"> > <xs:complexType name="aClass"> > <xs:sequence> > <xs:element name="a" type="xs:int"/> > </xs:sequence> > </xs:complexType> > </xs:schema> > > where the declaration of bClass references the ns1 namespace without declaring it. > The same thing happens when aClass is aggreagated by bClass. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2000) Chunked encoding transfer problem

by Heiko Braun (JIRA)

Chunked encoding transfer problem --------------------------------- Key: JBWS-2000 URL: http://jira.jboss.com/jira/browse/JBWS-2000 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-2.0.3 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-native-2.0.4 When transferring attachments with chunked encoding enabled you can see sporadic memory peaks and get 'Cannot close output stream' errors at the console log -- 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, 9 months

3
9
0 / 0

[JBoss JIRA] Updated: (JBWS-1544) SAML support

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1544?page=all ] Thomas Diesler updated JBWS-1544: --------------------------------- Comment: was deleted > SAML support > ------------ > > Key: JBWS-1544 > URL: http://jira.jboss.com/jira/browse/JBWS-1544 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: William DeCoste > > Intuit request. Notes: > Support of single sign-on using Liberty, SAML and WS-Federation. > Support of SAML profile. -- 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, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues April 2008