[JBoss JIRA] Created: (JBWS-1824) Content-type header is not set in SOAP response
by Lukas Jungmann (JIRA)
Content-type header is not set in SOAP response
-----------------------------------------------
Key: JBWS-1824
URL: http://jira.jboss.com/jira/browse/JBWS-1824
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-jaxws
Affects Versions: jbossws-1.2.1
Reporter: Lukas Jungmann
-have a JAX-WS web service in a web module deployed on JBoss 4.2.1 (use JBossWS for this service)
-create a JAX-WS client for this service in java application (and use JAX-WS RI 2.1.2 from jax-ws.dev.java.net/or tools from JDK6update3)
-run the client
expected: the JBossWS web service is successfully called from JAX-WS RI client
actual: the call of the operation fails because of missing Content-Type header in the SOAP response
TCP dump from Wireshark tool:
GET /JBossWS-test/JBossWS?wsdl HTTP/1.1
User-Agent: Java/1.6.0_03-ea
Host: 127.0.0.1:8080
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.4; JBoss-4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)/Tomcat-5.5
Content-Type: text/xml
Transfer-Encoding: chunked
Date: Wed, 12 Sep 2007 13:39:11 GMT
f7
<definitions name='JBossWSService' targetNamespace='http://ws.test.jboss/' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://ws.test.jboss/' xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
...
</definitions>
0
POST /JBossWS-test/JBossWS HTTP/1.1
SOAPAction: ""
Accept: text/xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Content-Type: text/xml; charset=utf-8
User-Agent: Java/1.6.0_03-ea
Host: 127.0.0.1:8080
Connection: keep-alive
Content-Length: 189
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.4; JBoss-4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)/Tomcat-5.5
Transfer-Encoding: chunked
Date: Wed, 12 Sep 2007 13:39:11 GMT
0
<?xml version="1.0" ?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><ns2:sayHi xmlns:ns2="http://ws.test.jboss/"><name>tom</name></ns2:sayHi></S:Body></S:Envelope
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBWS-1848) Pass JavaEE5 CTS for jaxr, jaxrpc, jaxws, jws, saaj, webservice, webservices12
by Thomas Diesler (JIRA)
Pass JavaEE5 CTS for jaxr, jaxrpc, jaxws, jws, saaj, webservice, webservices12
------------------------------------------------------------------------------
Key: JBWS-1848
URL: http://jira.jboss.com/jira/browse/JBWS-1848
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: jbossws-jaxws
Reporter: Thomas Diesler
Assigned To: Thomas Diesler
Fix For: jbossws-2.0.1
Run the JavaEE5 tests with jdk-1.5 against jboss-5.0
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBWS-1799) Two ejb3s exposed as 2 different web services in the same ear file. Can't have same methods with different parameters..
by Sureshbabu Thyvalappil (JIRA)
Two ejb3s exposed as 2 different web services in the same ear file. Can't have same methods with different parameters..
-----------------------------------------------------------------------------------------------------------------------
Key: JBWS-1799
URL: http://jira.jboss.com/jira/browse/JBWS-1799
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-1.2.1
Environment: Debian etch.
Reporter: Sureshbabu Thyvalappil
Please look at the url for description. http://www.jboss.com/index.html?module=bb&op=viewtopic&t=116665
First ejb:
@WebService(name="UserAccountServiceEndPoint",
targetNamespace="namespace1", serviceName="UserAccountService1.0")
@SOAPBinding(style=SOAPBinding.Style.DOCUMENT,use=SOAPBinding.Use.LITERAL)
@Stateless
@WebContext(transportGuarantee="NONE",contextRoot="/svc-useracctv1.0",urlPattern="/UserAccountService1.0")
public class UserAccountService implements IUserAccountService
{
@WebMethod
@TransactionAttribute(javax.ejb.TransactionAttributeType.SUPPORTS)
public boolean authenticate(@WebParam(name="username") String aUsername)
{
boolean ret;
.........
return ret;
}
}
interface for 1st ejb:
@Remote
public interface IUserAccountService
{
public boolean authenticate(String aUsername);
}
second ejb:
@WebService(name="UserAccountServiceExtEndPoint",
targetNamespace="namespaceExt", serviceName="UserAccountServiceExt1.0")
@SOAPBinding(style=SOAPBinding.Style.DOCUMENT,use=SOAPBinding.Use.LITERAL)
@Stateless
@WebContext(transportGuarantee="NONE",contextRoot="/svc-useracctv1.0",urlPattern="/UserAccountServiceExt1.0")
public class UserAccountServiceExt implements IUserAccountServiceExt
{
@WebMethod
@TransactionAttribute(javax.ejb.TransactionAttributeType.SUPPORTS)
public boolean authenticate(@WebParam(name="username") String aUsername, @WebParam(name="password") String password)
{
boolean ret;
.........
return ret;
}
}
interface for 2nd ejb:
@Remote
public interface IUserAccountServiceExt
{
public boolean authenticate(String aUsername, String aPassword);
}
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBWS-1854) Cannot deploy nested JSE endpoint in SAR
by Thomas Diesler (JIRA)
Cannot deploy nested JSE endpoint in SAR
----------------------------------------
Key: JBWS-1854
URL: http://jira.jboss.com/jira/browse/JBWS-1854
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Fix For: jbossws-2.0.1.SP2
We have an issue, JBoss Portal WSRP service doesn't deploy in Branch
4.2, the issue seems to be related to the WS changes.
I noticed that in jbossws.sar/META-INF/jboss-service.xml the following
has been removed:
<!--
A deployer service for JSE endpoints that are nested in service
archives (sar).
-->
<mbean name="jboss.ws:service=DeployerInterceptorNestedJSE"
code="org.jboss.ws.integration.jboss42.DeployerInterceptorNestedJSE">
<depends optional-attribute-name="MainDeployer"
proxy-type="attribute">jboss.system:service=MainDeployer</depends>
<depends>jboss.ws:service=WebServiceDeployerJSE</depends>
</mbean>
We do have a jse included into a sar and the end result is that the WSRP
service doesn't start with the following error message:
--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@be17fae3 {
url=file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
}
deployer: null
status: Starting
state: INIT_WAITING_DEPLOYER
watch:
file:/tmp/jboss-4.2.2.GA/server/default/deploy/jboss-portal.sar/portal-wsrp.sar/portal-wsrp.jse
altDD: null
lastDeployed: 1192192027649
lastModified: 1192191975000
mbeans:
I wanted to let you know. I didn't investigate more than that, other
than trying to find the corresponding class for the deployer, but it
seems that it's not in the codebase anymore.
--
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
17 years, 1 month
[JBoss JIRA] Created: (JBWS-1798) JBossWS cannot find local schema with relative url:s
by Oskar Carlstedt (JIRA)
JBossWS cannot find local schema with relative url:s
----------------------------------------------------
Key: JBWS-1798
URL: http://jira.jboss.com/jira/browse/JBWS-1798
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: JBoss 5.0 Beta2 and integrated JBossWS (2.0.0.DEV)
Reporter: Oskar Carlstedt
I deploy an ear file in JBoss5 that contains a war and a jar fil. The jar file contains a SLSB and the war file contains the web service (implemented as a Provider<SOAPMessage>). The war file has the following file structure in the the WEB-INF/wsdl folder:
WEB-INF/wsdl
my-service.wsdl
/imported
/my-service
/1.0-SNAPSHOT
my-service.xsd
/common
/1.0-SNAPSHOT
common.xsd
the wsdl file has a schema import like
<xsd:import schemaLocation="imported/my-service/1.0-SNAPSHOT/my-service.xsd" .../>
the my service.xsd imports the common.xsd file with the following import statement
<xsd:import schemaLocation="../../common/1.0-SNAPSHOT/common.xsd" .../>
Having this configuration will put JBoss into trouble. The error message sent is telling med that parent paths are not allowed, and pointing out to use getParent() instead. So I setting the schemaLocation attribute to getParent()/getParent()/.... will point out another path, but it is completely wrong.
PS...
I hope I got all "../":s right. Anyway, I have validated my paths so they are correct. DS.
--
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
17 years, 2 months