[JBoss JIRA] Created: (JBWS-2155) Not supporting JMS endpoints for WS-Addressing
by Zach Mabe (JIRA)
Not supporting JMS endpoints for WS-Addressing
----------------------------------------------
Key: JBWS-2155
URL: http://jira.jboss.com/jira/browse/JBWS-2155
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native, ws-addressing
Affects Versions: jbossws-native-3.0.1
Environment: JBoss 4.2.2.GA, Windows XP, Sun JVM 1.5.0_08
Reporter: Zach Mabe
when using a JMS endpoint at the EPR for either the faultTo or ReplyTo address within the WS-Addressing headers, the server always fails with the message
ClassNotFound org.jboss.remoting.transport.jms.TransportClientFactory.
How the faultTo is set on the client side
AddressingProperties props = (AddressingProperties) reqContext.get(JAXWSAConstants.CLIENT_ADDRESSING_PROPERTIES);
EndpointReference ep =ADDRESS_BUILDER.newEndpointReference(new URI("jms://queue/WSDropQueue"));
props.setFaultTo(ep);
This issue seems to be rooted in the fact that, on the server side, when the org.jboss.ws.core.soap.SOAPConnectionImpl is called to send the response/fault, it uses a org.jboss.ws.core.client.SOAPProtocolConnectionHTTP which in turns uses the JBoss-Remoting client which doesn't provide JMS support.
--
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, 11 months
[JBoss JIRA] Created: (JBWS-2190) Default encoding is used to decode responses.
by Sławomir Wojtasiak (JIRA)
Default encoding is used to decode responses.
---------------------------------------------
Key: JBWS-2190
URL: http://jira.jboss.com/jira/browse/JBWS-2190
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-native-3.0.1
Environment: JBoss AS 4.2, JAXWS 3.0.1 Native.
Reporter: Sławomir Wojtasiak
During response processing (on client side) JaxWS Native uses default JVM character encoding to read data from inputStream but there is always UTF-8 used as a default encoding when response is sent to the client.
Following code sets encoding while response is prepared and sent on the server side:
boolean writeXML = isWriteXMLDeclaration();
String charsetEncoding = getCharSetEncoding();
SOAPElementWriter writer = new SOAPElementWriter(outs, charsetEncoding);
// Implementation of getCharSetEncoding().
private String getCharSetEncoding() throws SOAPException
{
String charsetName = (String)getProperty(CHARACTER_SET_ENCODING);
if (charsetName == null)
charsetName = "UTF-8";
return charsetName;
}
On the client side there is no character encoding set when input stream is passed to the xml parser, so default encoding is used to decode it (which is ISO-8859-1 in my case and I can't change it only because JaxWS needs it).
I'm sure that DEFAULT encoding should be the same during processing requests and responses.
--
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, 11 months
[JBoss JIRA] Created: (JBWS-1857) Never create the same JAXBContext more than once
by Johann Gyger (JIRA)
Never create the same JAXBContext more than once
------------------------------------------------
Key: JBWS-1857
URL: http://jira.jboss.com/jira/browse/JBWS-1857
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-jaxws
Affects Versions: jbossws-1.2.1
Reporter: Johann Gyger
service.getPort() may become an expensive operation (i.e., several seconds) when using a non-trivial WSDL with complex types. We have been able to track down our performance problems to an incorrect usage of JAXB-RI in JBOSS-JAXWS. According to https://wsit.dev.java.net/servlets/ReadMsg?list=dev&msgNo=66, creating new instances of JAXBContext is an expensive operation.
In our WSDL we counted 28 instance creations of JAXBContext. Most of them are created through the following call hierarchy:
JAXBContext.newInstance(Class[], Map<String,?>) line: 570
JAXBContext.newInstance(Class...) line: 522
JAXBAccessor$1.create(Class) line: 67
JAXBAccessor$1.create(ParameterMetaData) line: 54
ParameterMetaData.eagerInitialize() line: 470
OperationMetaData.eagerInitialize(List<Method>) line: 469
ClientEndpointMetaData(EndpointMetaData).eagerInitializeOperations() line: 516
ClientEndpointMetaData(EndpointMetaData).initializeInternal() line: 502
ClientEndpointMetaData(EndpointMetaData).eagerInitialize() line: 490
JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(EndpointMetaData, Class<?>) line: 292
ServiceDelegateImpl.getPortInternal(EndpointMetaData, Class<T>) line: 274
ServiceDelegateImpl.getPort(QName, Class<T>) line: 200
A JProbe analysis (see attached file) revealed that actually most of the time (96.4%) of service.getPort() is spent in JAXBContext.newInstance(). Please see attached JProbe report.
Compared to JAX-WS RI (Metro) the performance of service.getPort() is extremely bad.
--
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, 11 months
[JBoss JIRA] Created: (JBWS-2087) WSDL fault exception is wrapped in WebService exception when using JbossWS-Metro.
by Mattias ￃﾖhrn (JIRA)
WSDL fault exception is wrapped in WebService exception when using JbossWS-Metro.
---------------------------------------------------------------------------------
Key: JBWS-2087
URL: http://jira.jboss.com/jira/browse/JBWS-2087
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-metro
Affects Versions: jbossws-metro-1.0.0
Environment: JBoss AS 4.2.2
Reporter: Mattias ￃﾖhrn
When a web service implementation bean throws a contract exception it is wrapped in a WebService exception.
The following stack trace appears in the server log:
11:21:25,122 ERROR [EndpointMethodHandler] com.acme.metroexceptiontest.MetroTestException: Test msg
javax.xml.ws.WebServiceException: com.acme.metroexceptiontest.MetroTestException: Test msg
at org.jboss.wsf.stack.sunri.InvokerEJB3.handleException(InvokerEJB3.java:117)
at org.jboss.wsf.stack.sunri.InvokerEJB3.invoke(InvokerEJB3.java:103)
at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
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.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
at org.jboss.wsf.stack.sunri.log.DumpPipe.process(DumpPipe.java:99)
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.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
at org.jboss.wsf.stack.sunri.RequestHandlerImpl.doPost(RequestHandlerImpl.java:122)
at org.jboss.wsf.stack.sunri.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:66)
at org.jboss.wsf.stack.sunri.EndpointServlet.service(EndpointServlet.java:71)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:595)
Caused by: com.acme.metroexceptiontest.MetroTestException: Test msg
at com.acme.metroexceptiontest.MetroTestServiceBean.helloWorld(MetroTestServiceBean.java:18)
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.invokeNext(MethodInvocation.java:112)
at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166)
at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.wsf.container.jboss42.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:103)
at org.jboss.wsf.stack.sunri.InvokerEJB3.invoke(InvokerEJB3.java:98)
... 40 more
A JAX-WS client accessing this web service throws a SOAPFaultException with the WebServiceException as cause.
Below follows the simple web service I created to test this:
package com.acme.metroexceptiontest;
import javax.ejb.Stateless;
import javax.jws.WebMethod;
import javax.jws.WebService;
import javax.jws.soap.SOAPBinding;
@Stateless
@WebService(
name="MetroTestService",
targetNamespace = "http://com.acme.metroexceptiontest/",
serviceName = "MetroTestService")
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
public class MetroTestServiceBean {
@WebMethod
public String helloWorld() throws MetroTestException {
throw new MetroTestException("Test msg", new MetroTestFaultInfo("test detail"));
}
}
______________________________________________
package com.acme.metroexceptiontest;
import javax.xml.ws.WebFault;
@WebFault(name="MetroTestFault", targetNamespace="http://com.acme.metroexceptiontest/")
public class MetroTestException extends Exception {
private static final long serialVersionUID = 1L;
private MetroTestFaultInfo faultInfo;
public MetroTestException(String message, MetroTestFaultInfo faultInfo) {
super(message);
this.faultInfo = faultInfo;
}
public MetroTestFaultInfo getFaultInfo() {
return faultInfo;
}
}
______________________________________________
package com.acme.metroexceptiontest;
import javax.xml.bind.annotation.XmlAccessType;
import javax.xml.bind.annotation.XmlAccessorType;
import javax.xml.bind.annotation.XmlType;
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(
name = "MetroTestFaultInfo",
namespace="http://com.acme.metroexceptiontest/",
propOrder = { "detail" }
)
public class MetroTestFaultInfo {
protected String detail;
public MetroTestFaultInfo() {
}
public MetroTestFaultInfo(String detail) {
this.detail = detail;
}
public String getDetail() {
return detail;
}
public void setDetail(String detail) {
this.detail = detail;
}
}
--
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, 11 months
[JBoss JIRA] Created: (JBWS-2136) ClassCastException: com.sun.xml.ws.server.EndpointMessageContextImpl
by Thomas Diesler (JIRA)
ClassCastException: com.sun.xml.ws.server.EndpointMessageContextImpl
--------------------------------------------------------------------
Key: JBWS-2136
URL: http://jira.jboss.com/jira/browse/JBWS-2136
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.namespace.MultipleNamespacesTestCase
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 3.735 sec
[junit] Test org.jboss.test.ws.jaxws.namespace.MultipleNamespacesTestCase FAILED
19:42:55,614 ERROR [EndpointMethodHandler] com.sun.xml.ws.server.EndpointMessageContextImpl
java.lang.ClassCastException: com.sun.xml.ws.server.EndpointMessageContextImpl
at org.jboss.test.ws.jaxws.namespace.EndpointBean.echo(EndpointBean.java:55)
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.wsf.container.jboss42.DefaultInvocationHandler.invoke(DefaultInvocationHandler.java:102)
--
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, 11 months
[JBoss JIRA] Created: (JBWS-2134) Fault string, and possibly fault code, not set
by Thomas Diesler (JIRA)
Fault string, and possibly fault code, not set
----------------------------------------------
Key: JBWS-2134
URL: http://jira.jboss.com/jira/browse/JBWS-2134
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.jbws1815.JBWS1815TestCase
[junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 1.99 sec
[junit] Test org.jboss.test.ws.jaxws.jbws1815.JBWS1815TestCase FAILED
19:34:36,016 ERROR [SyncProviderInvokerTube] Fault string, and possibly fault code, not set
javax.xml.ws.soap.SOAPFaultException: Fault string, and possibly fault code, not set
at org.jboss.test.ws.jaxws.jbws1815.ProviderImpl.invoke(ProviderImpl.java:72)
at org.jboss.test.ws.jaxws.jbws1815.ProviderImpl.invoke(ProviderImpl.java:55)
at org.jboss.wsf.stack.metro.InvokerEJB3.invokeProvider(InvokerEJB3.java:79)
at com.sun.xml.ws.server.InvokerTube$2.invokeProvider(InvokerTube.java:156)
at com.sun.xml.ws.server.provider.SyncProviderInvokerTube.processRequest(SyncProviderInvokerTube.java:78)
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.api.pipe.helper.AbstractTubeImpl.process(AbstractTubeImpl.java:106)
at org.jboss.wsf.stack.metro.log.DumpPipe.process(DumpPipe.java:99)
--
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, 11 months
[JBoss JIRA] Created: (JBWS-2135) WebServiceException: Undefined port type
by Thomas Diesler (JIRA)
WebServiceException: Undefined port type
----------------------------------------
Key: JBWS-2135
URL: http://jira.jboss.com/jira/browse/JBWS-2135
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.jbws1822.JBWS1822TestCase
[junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 3.649 sec
[junit] Test org.jboss.test.ws.jaxws.jbws1822.JBWS1822TestCase FAILED
BUILD SUCCESSFUL
Total time: 6 seconds
[tdiesler@tdvaio trunk]$ cat output/tests/reports/TEST-org.jboss.test.ws.jaxws.jbws1822.JBWS1822TestCase.txt
Testsuite: org.jboss.test.ws.jaxws.jbws1822.JBWS1822TestCase
Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 3.649 sec
Testcase: testOneEjbModule took 2.595 sec
Caused an ERROR
Undefined port type: {http://webservice.jbws1822.jaxws.ws.test.jboss.org/}EJB3RemoteIface
javax.xml.ws.WebServiceException: Undefined port type: {http://webservice.jbws1822.jaxws.ws.test.jboss.org/}EJB3RemoteIface
at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:337)
at com.sun.xml.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:343)
at javax.xml.ws.Service.getPort(Service.java:161)
at org.jboss.test.ws.jaxws.jbws1822.JBWS1822TestCase.getProxy(JBWS1822TestCase.java:55)
at org.jboss.test.ws.jaxws.jbws1822.JBWS1822TestCase.testOneEjbModule(JBWS1822TestCase.java:63)
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)
--
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, 11 months
[JBoss JIRA] Created: (JBWS-2132) IllegalArgumentException: protocol = http host = null
by Thomas Diesler (JIRA)
IllegalArgumentException: protocol = http host = null
-----------------------------------------------------
Key: JBWS-2132
URL: http://jira.jboss.com/jira/browse/JBWS-2132
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
[junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 2.132 sec
[junit] Test org.jboss.test.ws.jaxws.jbws1798.JBWS1798TestCase FAILED
Caused by: java.lang.IllegalArgumentException: protocol = http host = null
at sun.net.spi.DefaultProxySelector.select(DefaultProxySelector.java:146)
at com.sun.xml.ws.api.EndpointAddress.chooseProxy(EndpointAddress.java:165)
at com.sun.xml.ws.api.EndpointAddress.<init>(EndpointAddress.java:130)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parsePort(RuntimeWSDLParser.java:369)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parseService(RuntimeWSDLParser.java:341)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parseWSDL(RuntimeWSDLParser.java:323)
at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:227)
at com.sun.xml.ws.server.EndpointFactory.getWSDLPort(EndpointFactory.java:509)
at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:174)
--
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, 11 months