[JBoss JIRA] Created: (JBWS-2016) Add support for visibility atributes on WSDL policy elements
by Heiko Braun (JIRA)
Add support for visibility atributes on WSDL policy elements
-------------------------------------------------------------
Key: JBWS-2016
URL: http://jira.jboss.com/jira/browse/JBWS-2016
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Heiko Braun
Fix For: jbossws-native-2.0.5
I.e. WSSE config (an example taken from Metro, but it applies to our wsse config as well):
<wsp:Policy wsu:Id="MyServicePortBindingPolicy">
<wsp:ExactlyOne>
<wsp:All>
<sc:TrustStore wspp:visibility="private" peeralias="testclient"
storepass="client" type="JKS"
location="D:\full_path_to_my\client_keystore.jks"/>
<sc:CallbackHandlerConfiguration wspp:visibility="private">
<sc:CallbackHandler default="password" name="passwordHandler"/>
<sc:CallbackHandler default="ThisDoesNotMatter" name="usernameHandler"/>
</sc:CallbackHandlerConfiguration>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
The key is 'wspp:visibility="private"'
--
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 months
[JBoss JIRA] Created: (JBWS-2137) @WebWservice does not work with class isolation
by Thomas Diesler (JIRA)
@WebWservice does not work with class isolation
------------------------------------------------
Key: JBWS-2137
URL: http://jira.jboss.com/jira/browse/JBWS-2137
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, 4 months
[JBoss JIRA] Created: (JBWS-1673) Fix JAXR samples for SunRI
by Thomas Diesler (JIRA)
Fix JAXR samples for SunRI
--------------------------
Key: JBWS-1673
URL: http://jira.jboss.com/jira/browse/JBWS-1673
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: integration-sunri
Reporter: Thomas Diesler
Fix For: jbossws-2.1.0
2007-06-01 06:12:43,257 ERROR [org.jboss.jaxr.juddi.transport.SaajTransport:94] Exception::
org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.checkDOMNSErr(CoreDocumentImpl.java:2409)
at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.setName(AttrNSImpl.java:150)
at com.sun.org.apache.xerces.internal.dom.AttrNSImpl.<init>(AttrNSImpl.java:111)
at com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl.createAttributeNS(CoreDocumentImpl.java:2012)
at com.sun.xml.messaging.saaj.soap.SOAPDocumentImpl.createAttributeNS(SOAPDocumentImpl.java:161)
at com.sun.org.apache.xerces.internal.dom.ElementImpl.setAttributeNS(ElementImpl.java:684)
at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.setAttributeNS(ElementImpl.java:1241)
at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.addAttributeBare(ElementImpl.java:499)
at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.addAttributeBare(ElementImpl.java:471)
at com.sun.xml.messaging.saaj.soap.impl.ElementImpl.addAttribute(ElementImpl.java:454)
at org.jboss.jaxr.juddi.transport.SaajTransport.appendAttributes(SaajTransport.java:156)
at org.jboss.jaxr.juddi.transport.SaajTransport.appendElements(SaajTransport.java:180)
at org.jboss.jaxr.juddi.transport.SaajTransport.appendElements(SaajTransport.java:181)
at org.jboss.jaxr.juddi.transport.SaajTransport.createSOAPMessage(SaajTransport.java:136)
at org.jboss.jaxr.juddi.transport.SaajTransport.send(SaajTransport.java:77)
at org.apache.juddi.proxy.RegistryProxy.execute(RegistryProxy.java:368)
at org.apache.juddi.AbstractRegistry.saveBusiness(AbstractRegistry.java:582)
at org.apache.ws.scout.registry.BusinessLifeCycleManagerImpl.executeOperation(BusinessLifeCycleManagerImpl.java:532)
at org.apache.ws.scout.registry.BusinessLifeCycleManagerImpl.saveOrganizations(BusinessLifeCycleManagerImpl.java:389)
at org.jboss.test.ws.jaxws.samples.jaxr.scout.query.JaxrBusinessQueryTestCase.setUp(JaxrBusinessQueryTestCase.java:58)
--
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 months
[JBoss JIRA] Created: (JBWS-2133) Failed to access the WSDL
by Thomas Diesler (JIRA)
Failed to access the WSDL
-------------------------
Key: JBWS-2133
URL: http://jira.jboss.com/jira/browse/JBWS-2133
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-metro
Affects Versions: jbossws-metro-1.0.1
Reporter: Thomas Diesler
tests-run-internal:
[junit] Running org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 2.68 sec
[junit] Test org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase FAILED
BUILD SUCCESSFUL
Total time: 5 seconds
[tdiesler@tdvaio trunk]$ cat output/tests/reports/TEST-org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase.txt
Testsuite: org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase
Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 2.68 sec
Testcase: testPositive took 1.368 sec
Caused an ERROR
Failed to access the WSDL at: http://localhost:8080/test-context?wsdl. It failed with:
http://localhost:8080/test-context?wsdl.
javax.xml.ws.WebServiceException: Failed to access the WSDL at: http://localhost:8080/test-context?wsdl. It failed with:
http://localhost:8080/test-context?wsdl.
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(RuntimeWSDLParser.java:162)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:144)
at com.sun.xml.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:263)
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:226)
at com.sun.xml.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:174)
at com.sun.xml.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:104)
at javax.xml.ws.Service.<init>(Service.java:56)
at javax.xml.ws.Service.create(Service.java:680)
at org.jboss.test.ws.jaxws.jbws1813.JBWS1813TestCase.testPositive(JBWS1813TestCase.java:61)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
Caused by: java.io.FileNotFoundException: http://localhost:8080/test-context?wsdl
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1168)
at java.net.URL.openStream(URL.java:1007)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.createReader(RuntimeWSDLParser.java:805)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(RuntimeWSDLParser.java:262)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:129)
--
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, 5 months
[JBoss JIRA] Created: (JBWS-2088) Relax matching requirements in decodeMultipartRelatedMessage()
by David Boeren (JIRA)
Relax matching requirements in decodeMultipartRelatedMessage()
--------------------------------------------------------------
Key: JBWS-2088
URL: http://jira.jboss.com/jira/browse/JBWS-2088
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-2.0.4
Reporter: David Boeren
Apache Axis sends a slightly non-standard value in the Content-Type which many WS implementations accept but JBossWS does not, and this is interfering with multipart related service calls.
The "start" tag in the Content-Type has an incorrect format. It is this:
start="0.urn:uuid:278C3ADFCFF3AF170A1206560191992@apache.org";
but it should be this:
start="<0.urn:uuid:278C3ADFCFF3AF170A1206560191992@apache.org>";
To work around that problem, change this method: org.jboss.ws.core.soap.attachment.MultipartRelatedDecoder.decodeMultipartRelatedMessage
Change this:
public void decodeMultipartRelatedMessage(InputStream stream) throws IOException, MessagingException
{
String boundaryParameter = contentType.getParameter("boundary");
String start = contentType.getParameter("start");
to this:
public void decodeMultipartRelatedMessage(InputStream stream) throws IOException, MessagingException
{
String boundaryParameter = contentType.getParameter("boundary");
String start = null
--
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, 5 months