[JBoss JIRA] Created: (JBWS-2405) MTOM/XOP Interoperability - cid href URLEncode/URLDecode
by Chyi Pin Lim (JIRA)
MTOM/XOP Interoperability - cid href URLEncode/URLDecode
--------------------------------------------------------
Key: JBWS-2405
URL: https://jira.jboss.org/jira/browse/JBWS-2405
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.4
Environment: 14:36:53,328 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)
14:36:56,109 INFO [ServerInfo] Java version: 1.5.0_14,Sun Microsystems Inc.
14:36:56,109 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_14-b03,Sun Microsystems Inc.
14:36:56,109 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
14:37:27,656 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
14:37:27,656 INFO [NativeServerConfig] 3.0.4.GA
Reporter: Chyi Pin Lim
WCF uses a URL Encoded href cid for xopInclude. However, the Content-Id for the attachment is not URL Encoded. As such, JBossWS is unable to find the attachment.
Example:
<xop:Include href="cid:http%3A%2F%2Ftempuri.org%2F1%2F633631227250468750" xmlns:xop="http://www.w3.org/2004/08/xop/include"/>
--uuid:357c6d9d-d6cf-42e3-bca5-75c8f3761934+id=1
Content-ID: <http://tempuri.org/1/633631227250468750>
Since this is an interoperability issue, I don't know how to create a test case under the test suite to simulate this error.
--
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, 7 months
[JBoss JIRA] Created: (JBWS-2166) WSA client handler throws exception when installing reference parameters
by Andrew Dinn (JIRA)
WSA client handler throws exception when installing reference parameters
------------------------------------------------------------------------
Key: JBWS-2166
URL: http://jira.jboss.com/jira/browse/JBWS-2166
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.1
Reporter: Andrew Dinn
WSAddressingClientHandler.handleOutbound in package org.jboss.ws.extensions.addressing.jaxws is throwing the following exception when inserting reference parameters into a reply:
10:52:44,104 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
javax.xml.ws.WebServiceException: org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR: A node is used in a different document than the one that created it.
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.processHandlerFailure(HandlerChainExecutor.java:276)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:155)
at org.jboss.ws.core.jaxws.client.ClientImpl.callRequestHandlerChain(ClientImpl.java:191)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:298)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
at $Proxy93.soapFault(Unknown Source)
at com.arjuna.webservices11.wsaddr.client.SoapFaultClient.sendSoapFault(SoapFaultClient.java:72)
at com.arjuna.webservices11.wsat.client.ParticipantClient.sendSoapFault(ParticipantClient.java:150)
at com.arjuna.wst11.messaging.CoordinatorProcessorImpl.sendInvalidState(CoordinatorProcessorImpl.java:272)
at com.arjuna.wst11.messaging.CoordinatorProcessorImpl.prepared(CoordinatorProcessorImpl.java:176)
at com.arjuna.webservices11.wsat.sei.CoordinatorPortTypeImpl$1.executeTask(CoordinatorPortTypeImpl.java:61)
at com.arjuna.services.framework.task.TaskWorker.run(TaskWorker.java:65)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR: A node is used in a different document than the one that created it.
at org.apache.xerces.dom.ParentNode.internalInsertBefore(Unknown Source)
at org.apache.xerces.dom.ParentNode.insertBefore(Unknown Source)
at org.apache.xerces.dom.NodeImpl.appendChild(Unknown Source)
at org.jboss.ws.core.soap.NodeImpl.appendChild(NodeImpl.java:477)
at org.jboss.ws.core.soap.SOAPHeaderImpl.appendChild(SOAPHeaderImpl.java:198)
at org.jboss.ws.core.soap.SOAPElementImpl.addChildElement(SOAPElementImpl.java:274)
at org.jboss.ws.core.soap.SOAPHeaderImpl.addChildElement(SOAPHeaderImpl.java:70)
at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.appendElement(SOAPAddressingPropertiesImpl.java:374)
at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.appendElements(SOAPAddressingPropertiesImpl.java:352)
at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.writeHeaders(SOAPAddressingPropertiesImpl.java:306)
at org.jboss.ws.extensions.addressing.jaxws.WSAddressingClientHandler.handleOutbound(WSAddressingClientHandler.java:113)
at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140)
... 13 more
The situation which manifests this problem is as follows:
Client A attaches WS AddressingProperties to a port for server B, It installs a ReplyTo epr whose address identifies server A. It attaches a reference parameter wsarj:identifier to the epr. Client A then invokes service B.
The implementation method of service B retrieves the request AddressingProperties from its message context and sets up a reply AddressingProperties instance by calling AddressingProperties.initializeAsReply. It obtains a port for service A, installs the reply properties on the port then invokes service A. The client handler under this invocation gets the error.
The problem is that the SOAP implementation does not copy the reference parameter Element instance when it tries to insert them into the outgoing message. intiializeAsReply retrieves these elements from the incoming context ReplyTo/FaultTo and adds them to the element extension list of the reply addressing context. The client handler calls SOAPAddressingHandlerImpl.writeHeaders to add these elements as headers in the outbound message. writeHeaders eventually calls SOAPHeaderImpl.addChildElement to add each reference parameter Element to the outgoing message header. addChildElement tests whether the Element is a SOAP element and, if so, assumes that it can be inserted directly into the outgoing message by calling appendElement. Unfortunately, the incoming reference parameters are associated with a dom node whose document is non-null and this barfs,claiming that someone is attempting a switcheroo on the 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
15 years, 8 months
[JBoss JIRA] Created: (JBWS-2248) RemoteConnectionFactory rejects valid http URL.
by Amancio Díaz (JIRA)
RemoteConnectionFactory rejects valid http URL.
------------------------------------------------
Key: JBWS-2248
URL: http://jira.jboss.com/jira/browse/JBWS-2248
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-native-3.0.2
Environment: Making a client to a external WS defined like:
<soap:address location="HTTP://URL_TO_THE_SERVICE"/>
Reporter: Amancio Díaz
org.jboss.ws.core.client.RemoteConnectionFactory makes the comparation:
String targetAddress = epInfo.getTargetAddress();
if (targetAddress == null)
throw new IllegalArgumentException("Cannot obtain target address from: " + epInfo);
String key = null;
if (targetAddress.startsWith("http"))
key = RemoteConnection.class.getName() + ".http";
else if (targetAddress.startsWith("jms"))
key = RemoteConnection.class.getName() + ".jms";
if (key == null)
throw new IllegalArgumentException("Cannot obtain remote connetion for: " + targetAddress);
if targetAddress is uppercase (HTTP://SOMETHING) this throws an exception. External client will not change the WSDL.
--
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, 8 months
[JBoss JIRA] Created: (JBWS-2349) Redeployment error when using a jbossws client proxy inside a RAR connector
by Silvano Maffeis (JIRA)
Redeployment error when using a jbossws client proxy inside a RAR connector
---------------------------------------------------------------------------
Key: JBWS-2349
URL: https://jira.jboss.org/jira/browse/JBWS-2349
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.3
Environment: JDK 6, WinXP SP3, JBoss AS 4.0.3 GA
Reporter: Silvano Maffeis
I have a JBoss JCA connector (RAR) which creates a JAX-WS client to call a Web Service.
This works fine when I deploy the RAR connector for the first time, or when I restart JBoss.
However, If I do a hot redeployment of the connector, then the next time the connector
attempts to create a JAXWS client, the following exception occurs.
Seems a JBoss AS classloader related issue.
8:44:11,890 WARN [JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
javax.xml.ws.WebServiceException: Cannot create proxy
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.createProxy(ServiceDelegateImpl.java:422)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:275)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:202)
at javax.xml.ws.Service.getPort(Service.java:143)
at com.vipera.myproj.tx.jaxws.InvokeMW.getInvokeMWSoap(InvokeMW.java:56)
at com.vipera.myproj.tx.MashreqTransactionPlugin.createSoapClient(MashreqTransactionPlugin.java:542)
at com.vipera.myproj.tx.MashreqTransactionPlugin.initSoapClient(MashreqTransactionPlugin.java:617)
at com.vipera.myproj.tx.MashreqTransactionPlugin.startup(MashreqTransactionPlugin.java:342)
at com.vipera.ts.server.jca.spi.BackendManagedConnection.<init>(BackendManagedConnection.java:88)
at com.vipera.ts.server.jca.spi.BackendManagedConnectionFactory.createManagedConnection(BackendManagedConnectionFactory.java:116)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:619)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:264)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:575)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:347)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:332)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:402)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:849)
at com.vipera.ts.server.jca.cci.BackendConnectionFactory.getConnection(BackendConnectionFactory.java:84)
at com.vipera.ts.server.tx.TransactionService.handleTransaction(TransactionService.java:142)
at com.vipera.ts.server.tx.TransactionService.handle(TransactionService.java:74)
at com.vipera.fw.be.disp.ServiceDispatcher.dispatchService(ServiceDispatcher.java:119)
at com.vipera.fw.be.disp.ServiceDispatcher.handle(ServiceDispatcher.java:92)
at com.vipera.fw.be.AbstractHandler.dispatch(AbstractHandler.java:115)
at com.vipera.ts.server.session.SessionCheckerHandler.handle(SessionCheckerHandler.java:107)
at com.vipera.fw.be.AbstractHandler.dispatch(AbstractHandler.java:115)
at com.vipera.ts.server.handler.ContainerCheckerHandler.handle(ContainerCheckerHandler.java:127)
at com.vipera.fw.be.AbstractHandler.dispatch(AbstractHandler.java:115)
at com.vipera.ts.server.handler.ServletConnectorIn.handle(ServletConnectorIn.java:32)
at com.vipera.ts.server.servlet.ConnectionServlet.doPost(ConnectionServlet.java:135)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
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:182)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
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:619)
Caused by: java.lang.IllegalArgumentException: interface com.vipera.myproj.tx.jaxws.InvokeMWSoap is not visible from class loader
at java.lang.reflect.Proxy.getProxyClass(Proxy.java:353)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.createProxy(ServiceDelegateImpl.java:402)
... 49 more
--
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, 8 months
[JBoss JIRA] Created: (JBWS-2208) Impossible to deploy WS containing binding objects that are defined by XmlAttribute from "http://www.w3.org/XML/1998/namespace"
by Toni Lopez (JIRA)
Impossible to deploy WS containing binding objects that are defined by XmlAttribute from "http://www.w3.org/XML/1998/namespace"
-------------------------------------------------------------------------------------------------------------------------------
Key: JBWS-2208
URL: http://jira.jboss.com/jira/browse/JBWS-2208
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.1
Environment: XP + jvm 1.6.0_04-b12 + jboss.4.2.2-GA
Reporter: Toni Lopez
Trying to deploy this WS
@WebMethod ( operationName="setInternationalStringType")
public void setInternationalStringType(
@WebParam(targetNamespace="urn:bug", name="InternationalStringType")
InternationalStringType ist) {
// TODO Auto-generated method stub
}
where InternationalStringType was
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "InternationalStringType", propOrder = {"value"})
public class InternationalStringType {
@XmlValue
protected String value;
@XmlAttribute(namespace = "http://www.w3.org/XML/1998/namespace", required = true)
protected String lang;
public String getValue() { return value; }
public void setValue(String value) {this.value = value;}
public String getLang() {return lang;}
public void setLang(String value) {this.lang = value;}
}
i found this error during Deployment Phase
15:44:20,903 ERROR [STDERR] [Fatal Error] :1:319: The prefix "xml" cannot be bound to any namespace other than its usual namespace; neither can the namespace for "xml" be bound to any prefix other than "xml".
15:44:20,903 ERROR [DOMUtils] Cannot parse: <definitions name='exampleService' targetNamespace='http://spi.example.org/' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://spi.example.org/' xmlns:ns2='urn:bug' xmlns:ns1='http://www.w3.org/XML/1998/namespace'><types>
<xs:schema targetNamespace='http://spi.example.org/' version='1.0' xmlns:ns1='urn:bug' xmlns:tns='http://spi.example.org/' xmlns:xs='http://www.w3.org/2001/XMLSchema'>
<xs:import namespace='urn:bug'/>
<xs:element name='setInternationalStringType' type='tns:setInternationalStringType'/>
<xs:element name='setInternationalStringTypeResponse' type='tns:setInternationalStringTypeResponse'/>
<xs:complexType name='setInternationalStringType'>
<xs:sequence>
<xs:element minOccurs='0' ref='ns1:InternationalStringType'/>
</xs:sequence>
</xs:complexType>
<xs:complexType name='setInternationalStringTypeResponse'>
<xs:sequence/>
</xs:complexType>
</xs:schema>
<xs:schema targetNamespace='http://www.w3.org/XML/1998/namespace' version='1.0' xmlns:xs='http://www.w3.org/2001/XMLSchema'>
<xs:attribute name='lang' type='xs:string'/>
</xs:schema>
<xs:schema targetNamespace='urn:bug' version='1.0' xmlns:tns='urn:bug' xmlns:xs='http://www.w3.org/2001/XMLSchema'>
<xs:import namespace='http://www.w3.org/XML/1998/namespace'/>
<xs:element name='InternationalStringType' type='tns:InternationalStringType'/>
<xs:complexType name='InternationalStringType'>
<xs:simpleContent>
<xs:extension base='xs:string'>
<xs:attribute ref='xml:lang' use='required'/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:schema>
</types><message name='example_setInternationalStringType' ><part name='setInternationalStringType' element='tns:setInternationalStringType'/></message><message name='example_setInternationalStringTypeResponse' ><part name='setInternationalStringTypeResponse' element='tns:setInternationalStringTypeResponse'/></message><portType name='example'><operation name='setInternationalStringType' parameterOrder='setInternationalStringType'><input message='tns:example_setInternationalStringType'></input><output message='tns:example_setInternationalStringTypeResponse'></output></operation></portType><binding name='exampleBinding' type='tns:example'><soap:binding transport='http://schemas.xmlsoap.org/soap/http' style='document'/><operation name='setInternationalStringType'><soap:operation soapAction=""
/><input><soap:body use='literal'/></input><output><soap:body use='literal'/></output></operation></binding><service name='exampleService'><port name='examplePort' binding='tns:exampleBinding'><soap:address location='http://pcbcn35:8080/exampleWS/service'/></port></service></definitions>
15:44:20,903 ERROR [MainDeployer] Could not start deployment: file:/D:/SadielSpace/serverspace/DEV/jboss-4.2.2.GA/server/lab_01/tmp/deploy/tmp30124ear.ear-contents/jboss-bug.jar
org.jboss.ws.WSException: Cannot write generated wsdl
at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.processOrGenerateWSDL(JAXWSWebServiceMetaDataBuilder.java:403)
at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:168)
at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:52)
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderEJB3.buildMetaData(JAXWSMetaDataBuilderEJB3.java:78)
at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(UnifiedMetaDataDeploymentAspect.java:71)
at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118)
at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy34.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
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:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.io.IOException: org.xml.sax.SAXParseException: The prefix "xml" cannot be bound to any namespace other than its usual namespace; neither can the namespace for "xml" be bound to any prefix other than "xml".
at org.jboss.wsf.common.DOMUtils.parse(DOMUtils.java:160)
at org.jboss.wsf.common.DOMUtils.parse(DOMUtils.java:141)
at org.jboss.ws.tools.wsdl.WSDL11Writer.writeBuilder(WSDL11Writer.java:157)
at org.jboss.ws.tools.wsdl.WSDL11Writer.write(WSDL11Writer.java:151)
at org.jboss.ws.tools.wsdl.WSDLWriter.write(WSDLWriter.java:89)
at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.writeWsdl(JAXWSWebServiceMetaDataBuilder.java:430)
at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.processOrGenerateWSDL(JAXWSWebServiceMetaDataBuilder.java:394)
... 82 more
--
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, 8 months
[JBoss JIRA] Created: (JBWS-1932) Unable to narrow port selection for UnifiedPortComponentRef
by Chris Laprun (JIRA)
Unable to narrow port selection for UnifiedPortComponentRef
-----------------------------------------------------------
Key: JBWS-1932
URL: http://jira.jboss.com/jira/browse/JBWS-1932
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-jaxrpc
Affects Versions: jbossws-2.0.2
Reporter: Chris Laprun
Assigned To: Thomas Diesler
Each time my client application tries to retrieve a service endpoint to invoke web service operations, I get the following warning on the console:
WARN [org.jboss.ws.core.client.ServiceObjectFactory] Unable to narrow port selection for
UnifiedPortComponentRef
serviceEndpointInterface=org.jboss.portal.wsrp.core.WSRP_v1_Registration_PortType
portQName=null
enableMTOM=false
portComponentLink=null
callProperties=[]
stubProperties=[]
configName=null
configFile=null
This doesn't seem to have any ill consequences that I can notice in my testing but I'd like to solve the problem if possible.
--
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, 8 months