Thomas,
Are you trying to say that it should be possible to install JBoss as a minimal
configuration at the (remote) client?
To be honest, the whole picture of a J2EE client to me is not very clear. I
know that a J2EE client has access to all J2EE internal services such as the
JNDI ENC etc.
Thanks for the description of the testsuite. That part succeeded.
But the test is a J2EE client. The WARNING at the beginning of this thread was
from a standalone client with JAXRPC dynamic proxy invocation.
The normal JAXRPC method is : Service service = factory.createService(url,
qname);
Johan,
when the J2EE client looks up the JAXRPC service from JNDI, it provides the
properties for the JNDI initial context. Like this
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
|
Yes, jaxrpc-mapping files (jsr 109) was only intended for J2EE clients/servers.
If you app is a non-J2EE client, then I would use the JWSDP with generated
stubs or JWSDP with DII.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858373#3858373
Reply to
Not many people realize that jboss is sufficiently light weight that it can be
used as a container for client apps. As your client evolves it may have needs
for a nameing service (JNDI), management (JMX), plugable service architecture,
messageing (JMS) etc ...
A minimal jboss installation has
Actually there is a dependency on the jboss build, so you have to build jboss
first so .
1. cd jboss-4.0 (source checkout)
2. Unix: ./build/build.sh Windows: build\build
3. cd testsuite
4. ant
5. ant -Dtest=org.jboss.test.webservice.exception.ExceptionTestCase one-test
6. ant tests-report
You need to build the testsuite first, by running the default task.
1. ant
2. ant -Dtest=org.jboss.test.webservice.exception.ExceptionTestCase one-test
3. ant tests-report
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858195#3858195
Reply to the post :
I did get the same error : Guessing fault java type from qname:
nl.borsoft.www.FacadeException.
It is happening with a standalone java client dynamically looking up the web
service endpoint. And if there is a custom type in the element of the WSDL
file which can't be mapped to a known java
Exceptions were fixed in 4.0.1RC2, why dont you give that a shot?
The 4.0.1 release is coming very soon.
-Jason
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858103#3858103
Reply to the post :
Also if you do a cvs checkout of 4.0 branch, there is a test case in the
testsuite which demonstrates exceptions.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858104#3858104
Reply to the post :
cvs co -r Branch_4_0 jboss-4.0
cd jboss-4.0/testsuite
ant -Dtest=org.jboss.test.webservice.exception.ExceptionTestCase one-test
To run all WS tests, use
ant tests-webservice
ant tests-report
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858124#3858124
11 matches
Mail list logo
