war deploying affects WS

[shel]

I have a JAX-RPC WebService based on a SLSB, it's accessed thru the code:
ServiceFactory serviceFactory = ServiceFactory.newInstance();
Service service = serviceFactory.createService(
new URL( "http://localhost:2000/ka/LSService?WSDL" ),
new QName( "http://webservice.ejb.ka.plesk.com", "LSEndpointService" ));
LSEndpoint endpoint = (LSEndpoint) service.getPort( LSEndpoint.class );

while just one jar is deployed everything is ok, but when i also deploy my war i get:
[java] javax.xml.rpc.ServiceException: Error processing WSDL document:
[java] java.io.FileNotFoundException: http://localhost:2000/ka/LSService?WSDL
[java] at org.jboss.axis.client.Service.initService(Service.java:287)
[java] at org.jboss.axis.client.Service.(Service.java:189)
[java] at org.jboss.webservice.client.ServiceImpl.(ServiceImpl.java:108)
[java] at org.jboss.webservice.client.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:111)

in fact, the last war i tried i specially made as an empty war with just a META-INF/MANIFEST.MF inside, and anyway it breaks WS call from a client.

jar redeploying solves the problem, but this affects my web,
i get on my login page at http://localhost:2000/ka:
And now... Some Services
* ka.jar#LSEndpoint (wsdl)
...

though the page looked fine before.

the problem is present on 4.0.0 and the latest 4.0.2RC1.

[shel]

another thing, i've redesigned access to the WS and made it from another SLSB.
again, when only my jar with that WS is deployed (and also with the client SLSB which calls the WS) it works fine... just an empty war deploying causes to:

17:16:20,042 ERROR [PortProxy] Port error
AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (404)/ka/LSService
faultActor:
faultNode:
faultDetail:
{}string: return code: 404
...
The requested resource (/ka/LSService) is not available.
...

[shel]

am i to separate somehow these contexts? i'd like to have a single one as i always had (before i started WS-stuff), may be just /ka/services like a sub path for all my services (but inside /ka).

[shel]

ok, it seems that if both web and ws are accessed thru the http://localhost:2000/ka there is no way to keep them together, so i'll have to separate it by making another context for ws (e.g. /ka-ws).
but this way i will also have to make another jaas domain configuration additionaly to existing /ka (what in fact i was trying to avoid).

[thomas.diesler]

This is explained here

http://jira.jboss.com/jira/browse/JBWS-165