Need example of EJB Endpoint Doc/Lit and Standalone Client t

[acxsjones]

I have been trying to get an example of the following and can not get the stars to align and work.

We need the following
1. An EJB (HelloWorld) that takes a complex object and returns a complex object
2. The wscompile build script that builds the ejb and wsdl
3. Client build scripts that consums the wsdl (wscompile) and gen's the client stubs
4. Client side test code that hits the ejb

We are trying to switch to JBoss 4.0 but I can not seem to get a working example of Doc/Literal web service base off an ejb. I have a RPC Encoded working but that is the same as 3.2.XX JBoss.net

Any help would be great

[anil.saldhana]

Step by Step tutorials are available at the wiki page:
http://www.jboss.org/wiki/Wiki.jsp?page=JBossWS

Also if you download JBoss source code in Branch 4.0, you will find many testcases.

[acxsjones]

I have look at the wiki. I have a RPC Encoded example working but can not get document literal working.

What I am missing is an example taking it from WSDL on a pure java client. (Meaning outside of a container)

I will walk through this again, but I have been looking at this for sometime and am very frustrated.

Any help would be great

[acxsjones]

Question:
Does JBoss support client stubs gen'd from wscompile?

[anil.saldhana]

No.

Your best bet is to use "Dynamic Invocation Interface (DII)" form of client programming, for your case.

[acxsjones]

OK,
So there is NO way to generate client side subs (J2SE client) that work with a JBoss WS web service, document literal sytle, that is an endpoint in an EJB.

If this is so, I do not understand why not.

[jiwils]

Based on the other posts of this thread (and other threads in this forum), I am confused.

When you mention that JBoss does not "support" wscompile (or Axis as previous threads have indicated) on the client side, do you mean that these two options do not work with JBoss web services or that JBoss does not provide support (like a support contract) for them?

It seems to me that the point of web services is to decouple implmentations of the spec from each other (the client and server). Why would JBoss care what tool I use on the client side? Is it that neither Axis nor wscompile work correctly when building client-side stubs?

Could you comment more on the use of DII in this case? Why is this case such a good candidate for this? The inherit type-safety in these other mechanisms seems far more preferable.

[anil.saldhana]

wscompile or axis generated stubs/skeleton are implementation specific and not portable.

Dynamic Proxy or DII are about portability.

[jiwils]

Is portability the only concern that DII or Dynamic proxies avoid?

[acxsjones]

By the way,
I received a reply to one of my other posts that fixed most of my issues. There is a bug that has been fixed in JBoss 4.0.2 RC1 the reply of a document literal web service.

I have been able to get a standalone J2SE client working with my document literal web service running under 4.0.2

I was able to generate client stubs using wscompile and axis. Both work!!

The link to the other post with the answer is below

Thanks to all for the help

http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871854#3871854

[thomas.diesler]

acxsjones,

you are absolutely right: server/client are decoupled and you may of course be using jwsdp or axis generated stubs on the client side or in fact any other SOAP client you like. In that case you don't use any of the jboss supplied jars on the client side - we just don't care how you produce/consume SOAP messages.

WS4EE also comes with a client programming model that allows you todo an JNDI lookup of a preconfigured stub. Whether this is a compiled stub or a dynamic proxy is irrelevant.

If JBoss is the WS client and you want BP-1.0 compliancy which we offer with our current implementation, then the client related wikis are relevant, otherwise not.

Please indicate where the wiki is not clear enough.