[jboss-user] [JBossWS] - Re: Problem importing multiple schema from the same namespac

2008-02-04 Thread Didi1976
Created the JIRA Feature Request: http://jira.jboss.org/jira/browse/JBWS-1980

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126044#4126044

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126044
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: Problem importing multiple schema from the same namespac

2008-01-22 Thread Didi1976
I checked the WSDL-2.0 spec at http://www.w3.org/TR/wsdl20/.

anonymous wrote : 
  | 3.1.2 Inlining XML Schema
  | ...
  | A WSDL 2.0 document MAY inline two or more schemas from the same 
targetNamespace. For example, two or more inlined schemas can have the same 
targetNamespace provided that they do not define the same elements or types. A 
WSDL 2.0 document MUST NOT define the same element or type in more than one 
inlined schema.
  | ...
  | 

The server.log shows that only the last inlined schema seems to be recognized / 
remembered (see TypesMetaData):


  | UnifiedMetaData: 
  |  implementation: jbossws-native-2.0.1.SP2 (build=200710210837)
  |  deploymentName: null
  |  securityDomain: null
  | 
  | ServiceMetaData:
  |  qname={http://www.openuri.org/}testAllParts
  |  refName=null
  |  wsdName=null
  |  wsdlFile=null
  |  wsdlLocation=file:/home/scd/workspace/TestWSDL/src/wsdl/testAllParts.wsdl
  |  jaxrpcMapping=null
  |  publishLocation=null
  |  securityConfig=null
  |  properties=null
  | 
  | TypesMetaData: 
  | 
  |  
  |  
  |   
  |
  | 
  | 
  |
  |   
  |  
  | 
  | 
  |  
  |  
  |   
  |
  |   
  |  
  |  
  |   
  |  
  | 
  | 
  | 
  | ClientEndpointMetaData:
  |  type=JAXWS
  |  qname={http://www.openuri.org/}testAllPartsSoap
  |  address=http://xpscd:7001/TestWeb/testAllParts.jpd
  |  binding=http://schemas.xmlsoap.org/wsdl/soap/http
  |  seiName=null
  |  configFile=META-INF/standard-jaxws-client-config.xml
  |  configName=Standard Client
  |  authMethod=null
  |  properties={}
  | 
  | OperationMetaData:
  |  qname={http://www.openuri.org/}clientRequest
  |  javaName={http://www.openuri.org/}clientRequest
  |  style=document/literal/WRAPPED
  |  oneWay=false
  |  soapAction=http://www.openuri.org/clientRequest
  | 

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122099#4122099

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122099
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [JBossWS] - Re: Problem importing multiple schema from the same namespac

2008-01-21 Thread Didi1976
Is there any solution till now? We ran in a similar problem:

A SLSB calls a WebService on a Bea WLI to trigger there some processing. The 
generated WSDL from the WLI looks like:


  | 
  | http://www.openuri.org/2002/04/soap/conversation/"; 
  |   xmlns:cw="http://www.openuri.org/2002/04/wsdl/conversation/"; 
  |   xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; 
  |   xmlns:jms="http://www.openuri.org/2002/04/wsdl/jms/"; 
  |   xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"; 
  |   xmlns:s="http://www.w3.org/2001/XMLSchema"; 
  |   xmlns:s0="http://www.openuri.org/"; 
  |   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; 
  |   xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; 
  |   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; 
  |   targetNamespace="http://www.openuri.org/";>
  |   
  | http://www.w3.org/2001/XMLSchema"; 
xmlns:test="http://test.softsolution.at"; elementFormDefault="qualified" 
targetNamespace="http://www.openuri.org/";>
  |   http://test.softsolution.at"/>
  |   
  | 
  |   
  | 
  |   
  | 
  |   
  |   
  | 
  |   
  | 
  |   
  | 
  | http://www.w3.org/2001/XMLSchema"; 
xmlns:tns="http://test.softsolution.at"; 
targetNamespace="http://test.softsolution.at"; elementFormDefault="qualified" 
attributeFormDefault="unqualified">
  |   
  | 
  |   Combine PartA and PartB
  | 
  | 
  |   
  | 
  | 
  |   
  | 
  |   
  | 
  | http://www.w3.org/2001/XMLSchema"; 
xmlns:tns="http://test.softsolution.at"; 
targetNamespace="http://test.softsolution.at"; elementFormDefault="qualified" 
attributeFormDefault="unqualified">
  |   
  | 
  |   First Part of the Test
  | 
  | 
  |   
  | 
  | 
  |   
  | 
  |   
  | 
  | http://www.w3.org/2001/XMLSchema"; 
xmlns:tns="http://test.softsolution.at"; 
targetNamespace="http://test.softsolution.at"; elementFormDefault="qualified" 
attributeFormDefault="unqualified">
  |   
  | 
  |   Second Part of the Test
  | 
  | 
  |   
  | 
  | 
  |   
  | 
  |   
  | 
  | 
  |   
  |   
  | 
  |   
  |   
  | 
  |   
  |   
  | 
  |   
  |   
  | 
  |   
  |   
  | http://schemas.xmlsoap.org/soap/http"; 
style="document"/>
  | 
  |   http://www.openuri.org/clientRequest"; 
style="document"/>
  |   
  | 
  |   
  |   
  | 
  |   
  | 
  |   
  |   
  | 
  |   http://xpscd:7001/TestWeb/testAllParts.jpd"/>
  | 
  |   
  | 
  | 

The following error is logged by the JBoss Server (4.2.2.GA):


  | 2008-01-21 11:08:04,342 ERROR 
[org.jboss.ws.metadata.wsdl.xmlschema.JBossXSErrorHandler] 
JBossWS_www.openuri.org_23041.xsd[domain:http://www.w3.org/TR/xml-schema-1]::[key=src-resolve]::Message=src-resolve:
 Cannot resolve the name 'test:AllParts' to a(n) 'element declaration' 
component.
  | 

It seems that there is a problem in handling multiple schemas mapped to the 
same targetNamespace.

The ws-client classes are generated and work correctly without any error if 
used directly with jax-ws.

The error does not prevent the WebService from being called. So the error can 
be ignored (should it be ignored?).

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121761#4121761

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121761
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [EJB 3.0] - Re: EJB3 over HTTP and Reverse Proxy

2007-12-13 Thread Didi1976
An upgrade from JBoss 4.2.0.GA to 4.2.2.GA solved the issue ... seemed to be 
some problem in the remoting.

So I hopefully end this thread and maybe its of some help for others.

P.S.: Now the trouble moved towards jbossws, but thats an other story ...

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112581#4112581

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4112581
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [EJB 3.0] - Re: EJB3 over HTTP and Reverse Proxy

2007-12-13 Thread Didi1976
One last problem remains. Everything is working perfekt as long as I use http. 
As soon as I use https, only fetching the InitialContext works and the lookup 
ends up with:


  | 12:15:47,484 DEBUG [SSLSocketBuilder] Could not find keystore url.  Can not 
find store file for url because store url is null.
  | javax.naming.NamingException: Could not dereference object [Root exception 
is java.lang.reflect.UndeclaredThrowableException]
  | at 
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1150)
  | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:705)
  | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
  | at javax.naming.InitialContext.lookup(InitialContext.java:351)
  | at 
at.softsolution.esa.client.gui.LoginPanel$LoginAction$1.run(LoginPanel.java:1022)
  | Caused by: java.lang.reflect.UndeclaredThrowableException
  | at $Proxy1.createProxy(Unknown Source)
  | at 
org.jboss.ejb3.JndiProxyFactory.getObjectInstance(JndiProxyFactory.java:53)
  | at 
javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
  | at 
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1125)
  | at 
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1142)
  | ... 4 more
  | Caused by: java.lang.reflect.InvocationTargetException
  | 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.remoting.InvokerRegistry.loadClientInvoker(InvokerRegistry.java:419)
  | at 
org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:320)
  | at org.jboss.remoting.Client.connect(Client.java:441)
  | at 
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:61)
  | at 
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | at 
org.jboss.ejb3.remoting.IsLocalProxyFactoryInterceptor.invoke(IsLocalProxyFactoryInterceptor.java:70)
  | at 
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:61)
  | ... 9 more
  | Caused by: java.lang.NullPointerException
  | at 
org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory(HTTPSClientInvoker.java:144)
  | at 
org.jboss.remoting.RemoteClientInvoker.(RemoteClientInvoker.java:46)
  | at 
org.jboss.remoting.transport.http.HTTPClientInvoker.(HTTPClientInvoker.java:105)
  | at 
org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.(HTTPSClientInvoker.java:63)
  | at 
org.jboss.remoting.transport.https.TransportClientFactory.createClientInvoker(TransportClientFactory.java:39)
  | 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.remoting.InvokerRegistry.loadClientInvoker(InvokerRegistry.java:419)
  | at 
org.jboss.remoting.InvokerRegistry.createClientInvoker(InvokerRegistry.java:320)
  | at org.jboss.remoting.Client.connect(Client.java:441)
  | at 
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:61)
  | at 
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | at 
org.jboss.ejb3.remoting.IsLocalProxyFactoryInterceptor.invoke(IsLocalProxyFactoryInterceptor.java:70)
  | at 
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
  | at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:61)
  | at $Proxy1.createProxy(Unknown Source)
  | at 
org.jboss.ejb3.JndiProxyFactory.getObjectInstance(JndiProxyFactory.java:53)
  | at 
javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
  | at 
org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1125)
  | at 
org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1142)
  | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:705)
  | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
  | at javax.naming.InitialContext.lookup(InitialContext.java:351)
  | at 
at.softsolution.esa.client.gui.LoginPanel$LoginAction$1.run(LoginPanel.java:1022)
  | at 
org.jboss

[jboss-user] [EJB 3.0] - Re: EJB3 over HTTP and Reverse Proxy

2007-12-12 Thread Didi1976
And again something I missed.

You have to use the http://www.jboss.org/j2ee/schema/jboss_5_0.xsd.

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112192#4112192

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4112192
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [EJB 3.0] - Re: EJB3 over HTTP and Reverse Proxy

2007-12-12 Thread Didi1976
Found it myself. Here is an example:


  | 
  |   
  | 
  |   TestSessionBean
  |   
  | test/TestSessionBean/remote
  | 
  |   http://localhost:8080/servlet-invoker/ServerInvokerServlet
  | 
  |   
  | 
  |   
  | 
  | 

This still leaves the problem of an invalid DTD. As soon as you add the DOCTYPE 
to jboss.xml it will not deploy.

  | http://www.jboss.org/j2ee/dtd/jboss_4_2.dtd";>
  | 

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112164#4112164

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4112164
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [EJB 3.0] - Re: EJB3 over HTTP and Reverse Proxy

2007-12-11 Thread Didi1976
Could you please post an example of the jboss.xml. I was searching in the DTD 
(http://www.jboss.org/j2ee/dtd/jboss_4_2.dtd) but I did not find the tags.

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112157#4112157

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4112157
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [EJB 3.0] - Re: EJB3 over HTTP and Reverse Proxy

2007-12-11 Thread Didi1976
I know that it is possible to specify the RemoteBinding also in an XML file 
(did not test it till now) but I dont wanna let a customer edit such files.

Maybe it would help to explain by the fact that most customers run different 
systems for QA, training and production. Each time I move a release from QA to 
training to production, it would be neccessary to adapt files within the 
EAR/JAR/...

In the old style (InvokerURL in JBoss 4.0.x) all this was not affected by any 
file inside my EAR. I had preconfigured AS where I deployed the same EAR 
without any changes.

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111949#4111949

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111949
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user


[jboss-user] [EJB 3.0] - EJB3 over HTTP and Reverse Proxy

2007-12-11 Thread Didi1976
All examples regarding Remoting only work for the simple scenario where a 
client directly connects to the Server. This configuration is already working 
(even over HTTP). I used the description in the wiki 
(http://wiki.jboss.org/wiki/Wiki.jsp?page=Accessing_EJB3s_over_HTTP_HTTPS).

Our destination scenario looks like:

Java Client --HTTP(S)--> Reverse Proxy (httpd/mod_proxy) --AJP/HTTP/HTTPS--> 
JBoss

My main problem is to reconfigure the 
@RemoteBinding/ServerInvokerServlet/Remoting to connect to my reverse proxy 
instead of directly trying to contact the AS. clientConnectAddress and 
clientConnectPort dont work as supposed.

In "good old days" of JBoss 4.0.x all this was configurable by setting a simple 
InvokerURL. Now, in JBoss 4.2.x, this feature is lost (or not obvious to me ... 
what I really hope). It was even possible to switch from http to https by 
changing that. Now you have to define two different RemoteBindings and access 
your EJB3 SLSB/SFSB using different JNDI-Names (again, do I miss anything here).

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111931#4111931

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111931
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user