[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, 1 month
[JBoss JIRA] Commented: (JBWS-203) NPE in Call.getTypeMapping
by Manjunatha HG (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-203?page=comments#action_12386318 ]
Manjunatha HG commented on JBWS-203:
------------------------------------
here the code:Interface:
package com.javasrc.webservices.age;
import java.rmi.Remote;
import java.rmi.RemoteException;
public interface Age extends Remote
{
public String age( String name, Integer age ) throws RemoteException;
}
Implimentation of of the interface:
package com.javasrc.webservices.age;
public class Age_Imp
{
public String age( String name, Integer age )
{
return name + " is " + age + " years old!";
}
}
client program:
package com.javasrc.webservices.age;
import javax.xml.rpc.Service;
import javax.xml.rpc.ServiceFactory;
import com.javasrc.webservices.age.Age;
import javax.xml.namespace.QName;
import java.net.URL;
public class AgeClient
{
public static void main( String[] args ) throws Exception {
if( args.length < 3 )
{
System.out.println( "Usage: AgeClient urlstr name age" );
System.exit( 0 );
}
String urlstr = args[ 0 ];
String argument = args[ 1 ];
String argument2 = args[ 2 ];
System.out.println( "Contacting webservice at " + urlstr );
URL url = new URL(urlstr);
QName qname = new QName("http://age.webservices.javasrc.com/",
"AgeService");
ServiceFactory factory = ServiceFactory.newInstance();
Service service = factory.createService( url, qname );
Age age = ( Age ) service.getPort( Age.class );
System.out.println( "age.age(" + argument + ", " + argument2 + ")" );
System.out.println( "output:" + age.age( argument, new Integer( argument2 ) ) );
}
}
i am getting this error
Contacting webservice at http://ccgtsd8qzxf1s:8080/agews/age?wsdl
log4j:WARN No appenders could be found for logger (org.apache.axis.i18n.ProjectResourceBundle).
log4j:WARN Please initialize the log4j system properly.
age.age(manju, 29)
java.lang.NullPointerException
at org.apache.axis.client.Call.getTypeMapping(Call.java:2402)
at org.apache.axis.client.Call.setReturnType(Call.java:1230)
at org.apache.axis.client.Call.setOperation(Call.java:1412)
at org.apache.axis.client.AxisClientProxy.invoke(AxisClientProxy.java:369)
at $Proxy0.age(Unknown Source)
at com.javasrc.webservices.age.AgeClient.main(AgeClient.java:35)
Exception in thread "main"
how to resolve this
> NPE in Call.getTypeMapping
> --------------------------
>
> Key: JBWS-203
> URL: http://jira.jboss.com/jira/browse/JBWS-203
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-jaxws
> Reporter: Thomas Diesler
> Assigned To: Jason T. Greene
> Fix For: jboss-ws4ee-4.0.3
>
>
> java.lang.NullPointerException
> at org.apache.axis.client.Call.getTypeMapping(Call.java:2402)
> at org.apache.axis.client.Call.setReturnType(Call.java:1230)
> at org.apache.axis.client.Call.setOperation(Call.java:1412)
> at org.apache.axis.client.AxisClientProxy.invoke(AxisClientProxy.java:369)
> at $Proxy0.getHello(Unknown Source)
> at utils.locator.WSLocator.main(WSLocator.java:64)
> Exception in thread "main"
--
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] Commented: (JBWS-203) NPE in Call.getTypeMapping
by Manjunatha HG (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-203?page=comments#action_12386316 ]
Manjunatha HG commented on JBWS-203:
------------------------------------
i am not able to resolve this, iam using jboss4..0.5AS,and WSTOOLS for generating mapping,wsdl s
here i am posting my code pls help
> NPE in Call.getTypeMapping
> --------------------------
>
> Key: JBWS-203
> URL: http://jira.jboss.com/jira/browse/JBWS-203
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jbossws-jaxws
> Reporter: Thomas Diesler
> Assigned To: Jason T. Greene
> Fix For: jboss-ws4ee-4.0.3
>
>
> java.lang.NullPointerException
> at org.apache.axis.client.Call.getTypeMapping(Call.java:2402)
> at org.apache.axis.client.Call.setReturnType(Call.java:1230)
> at org.apache.axis.client.Call.setOperation(Call.java:1412)
> at org.apache.axis.client.AxisClientProxy.invoke(AxisClientProxy.java:369)
> at $Proxy0.getHello(Unknown Source)
> at utils.locator.WSLocator.main(WSLocator.java:64)
> Exception in thread "main"
--
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