October 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2303) Update to more recent Metro components

by Alessio Soldano (JIRA)

Update to more recent Metro components -------------------------------------- Key: JBWS-2303 URL: https://jira.jboss.org/jira/browse/JBWS-2303 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Alessio Soldano Fix For: jbossws-metro-3.0.4 We're currently using wsit 1.1, jaxws 2.1.3 and jaxb 2.1.6. The latest Metro releases use more recent versions, see https://metro.dev.java.net/nonav/1.3/docs/ for example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2318) Decouple JAX-WS/JAX-RPC from native properly and make them available as separate components/jars

by Richard Opalka (JIRA)

Decouple JAX-WS/JAX-RPC from native properly and make them available as separate components/jars ------------------------------------------------------------------------------------------------ Key: JBWS-2318 URL: https://jira.jboss.org/jira/browse/JBWS-2318 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.0.4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-2373) Dynamic address re-writing should drop :80 and :443 where appropriate.

by Darran Lofthouse (JIRA)

Dynamic address re-writing should drop :80 and :443 where appropriate. ---------------------------------------------------------------------- Key: JBWS-2373 URL: https://jira.jboss.org/jira/browse/JBWS-2373 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.4 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-metro-3.0.5 When the address is dynamically re-written based on the request address the ':80' and ':443' should be dropped when appropriate. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2266) Schema Validation Feature Fails for Special Characters

by Richard Opalka (JIRA)

Schema Validation Feature Fails for Special Characters ------------------------------------------------------ Key: JBWS-2266 URL: https://jira.jboss.org/jira/browse/JBWS-2266 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.2 Reporter: Richard Opalka -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2307) com.sun.xml.ws.client.ClientTransportException: request requires HTTP authentication: Unauthorized

by Alessio Soldano (JIRA)

com.sun.xml.ws.client.ClientTransportException: request requires HTTP authentication: Unauthorized -------------------------------------------------------------------------------------------------- Key: JBWS-2307 URL: https://jira.jboss.org/jira/browse/JBWS-2307 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-metro-3.0.3 Reporter: Alessio Soldano Running the TCK jaxws/api/javax_xml_ws/WebServiceContext tests we have an authentication exception: 09-18-2008 14:06:50: SVR-ERROR: com.sun.xml.ws.client.ClientTransportException: request requires HTTP authentication: Unauthorized at com.sun.xml.ws.transport.http.client.HttpClientTransport.checkResponseCode(HttpClientTransport.java:212) at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:149) at com.sun.xml.xwss.XWSSClientPipe.process(XWSSClientPipe.java:118) at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115) at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595) at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554) at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539) at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436) at com.sun.xml.ws.client.Stub.process(Stub.java:248) at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:135) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:109) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89) at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118) at $Proxy1066.getMessageContextTest(Unknown Source) at com.sun.ts.tests.jaxws.api.javax_xml_ws.WebServiceContext.Client.getMessageContextTest(Client.java:212) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.ts.lib.harness.EETest.run(EETest.java:495) at com.sun.ts.lib.harness.ServiceEETest.run(ServiceEETest.java:112) at com.sun.ts.tests.common.vehicle.wsejb.WSEJBVehicle.runTest(WSEJBVehicle.java:82) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69) at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73) at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59) at sun.reflect.GeneratedMethodAccessor272.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72) at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_3625037.invoke(InvocationContextInterceptor_z_fillMethod_3625037.java) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88) at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_3625037.invoke(InvocationContextInterceptor_z_setup_3625037.java) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor.invoke(ExtendedPersistenceContextPropagationInterceptor.java:59) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:81) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.security.NullInterceptor.invoke(NullInterceptor.java:42) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:157) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:647) at org.jboss.ejb3.session.InvokableContextClassProxyHack._dynamicInvoke(InvokableContextClassProxyHack.java:56) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:91) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:742) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:695) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:522) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:230) We should reproduce this use case in the jbossws-metro testsuite, then fix it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-2378) Fix remoting client usage for one-way invocations

by Alessio Soldano (JIRA)

Fix remoting client usage for one-way invocations ------------------------------------------------- Key: JBWS-2378 URL: https://jira.jboss.org/jira/browse/JBWS-2378 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.0.5 Andrew Dinn found an issue with remoting when performing one way invocations in the implementation of a WSTF addressing scenario. See the referenced forum thread for details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2335) ClassNotFoundException SAAJMetaFactoryImpl after installing metro 3.0.3 into jboss 4.2.3

by Silvano Maffeis (JIRA)

ClassNotFoundException SAAJMetaFactoryImpl after installing metro 3.0.3 into jboss 4.2.3 ---------------------------------------------------------------------------------------- Key: JBWS-2335 URL: https://jira.jboss.org/jira/browse/JBWS-2335 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Affects Versions: jbossws-metro-3.0.3 Environment: JBoss 4.2.3 GA, JDK 6, WinXP SP3 Reporter: Silvano Maffeis I've installed metro 3.0.3 into JBoss 4.2.3 GA. On deploying a WAR file holding a SOAP webservice, I'm getting the following exception. (The web service was deploying and running fine using jbossws native on Jboss 4.2.2). The cause seems to be that jbossws-client.jar is getting removed by the metro 3.0.3 installation. Caused by: java.lang.IllegalStateException: Failed to load javax.xml.soap.MetaFactory: org.jboss.ws.core.soap.SAAJMetaFactoryImpl at javax.xml.soap.SAAJFactoryLoader.loadFactory(SAAJFactoryLoader.java:131) at javax.xml.soap.SAAJMetaFactory.getInstance(SAAJMetaFactory.java:60) at javax.xml.soap.MessageFactory.newInstance(MessageFactory.java:106) at com.sun.xml.ws.api.SOAPVersion.<init>(SOAPVersion.java:178) at com.sun.xml.ws.api.SOAPVersion.<clinit>(SOAPVersion.java:83) ... 37 more Caused by: java.lang.ClassNotFoundException: org.jboss.ws.core.soap.SAAJMetaFactoryImpl at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1358) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1204) at javax.xml.soap.SAAJFactoryLoader.loadFactory(SAAJFactoryLoader.java:125) ... 41 more Also see: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174938#4174938 http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=51... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2374) wsdl and xml docs not collected with EJB3 endpoints

by Alessio Soldano (JIRA)

wsdl and xml docs not collected with EJB3 endpoints --------------------------------------------------- Key: JBWS-2374 URL: https://jira.jboss.org/jira/browse/JBWS-2374 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Alessio Soldano Assignee: Alessio Soldano The DeploymentDescriptorParserExt currently has a warning saying document collection is bypassed with EJB3 endpoints. This can lead to wrong wsdl/xsd import locations in the wsdl, as they are not rewritten by Metro without the required docs metadata. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-2206) WSDL imports are not replaced with absolute path

by Heiko Braun (JIRA)

WSDL imports are not replaced with absolute path ------------------------------------------------- Key: JBWS-2206 URL: http://jira.jboss.com/jira/browse/JBWS-2206 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro Affects Versions: jbossws-2.0.0 Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: jbossws-metro-3.0.2 SunRI does not support wsdlLocation on EJB endpoints -- 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

15 years, 6 months

2
8
0 / 0

[JBoss JIRA] Created: (JBWS-2375) Add getChildren fuctionality to UnifiedVirtualFile

by Alessio Soldano (JIRA)

Add getChildren fuctionality to UnifiedVirtualFile -------------------------------------------------- Key: JBWS-2375 URL: https://jira.jboss.org/jira/browse/JBWS-2375 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano The minimal fuctionalities provided by the UnifiedVirtualFile should include: public List<UnifiedVirtualFile> getChildren() throws IOException -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues October 2008