Please have a look at jbossws-1.2.0
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4024303#4024303
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4024303
___
jboss-user mailing list
hey bk8133, thanks a lot for the last post. without that i wouldn't have known
that the issue was with jdk 1.6. i have been trying to deploy my web
services(hello worlds) in vain since my java_home was set to jdk 1.6.0 :)
i have been in the same situation as u have, evaluating web service
(dwin) Actually no. Sorry for not being clear enaugh. What i ment was.. the
confusion around [wsgen,wsimportand,apt ] and [wstools]. As wstools being the
toolset for JBoss implementation of JSR181. I'm working at a company that is
considering JBoss as AS for web services and we are facing
hey BK,
Since you're using JBoss 4.04, I am assuming you're using JBossWS 1.0.x (which
is not JAX-WS 2.0 compliant but JAX-RPC 1.x). In fact, there is no binary
release of a JAX-WS JBossWS unless you're using JBoss 5.
I had to check out the code (via SVN) for JBoss 4.0.5 and compile it myself
hey BK,
Since you're using JBoss 4.04, I am assuming you're using JBossWS 1.0.x (which
is not JAX-WS 2.0 compliant but JAX-RPC 1.x). In fact, there is no binary
release of a JAX-WS JBossWS unless you're using JBoss 5.
I had to check out the code (via SVN) for JBoss 4.0.5 and compile it myself
Hey!! Thank you very much for the best description about WS in java i ever
read. The fact was , i was wrong about the AS (i'm using 4.05). So everything
with WSTools was ok. The problem was in Java. The JDK 1.6.0 was used. And
there's a bug reported in JIRA. Sadly but trully i missed it. I
I'm facing the same issue here. It seems that wstools, jaxws implementation,
axis are trying to get along aroung jsr181. Is there a standard way to declare
web services in a war, which would be deployable to multiple app servers?
View the original post :
hey BK,
do you mean clustering of web services. Currently, web services can be exposed
as stateless session beans.
All you really need is the POJO class (with the @Webservice annotation) and the
JBossWS service runtime will take care of the rest (including the generation of
the WSDL and
dwin wrote : please clarify for me,
|
| this magic that happens behind the scene is specific to JBossWS 1.2 or to
any implementation of JAX-WS?
It's a feature specific to JBossWS. The whole reason for the JAX-WS wrapper
classes is to solve a technical problem that is specific to the
The code first approach leverages our own tools codebase internally that does
all the magic. However it's not yet ready to do WSDL first. In this case we
still point the people to wsimport.
Does this answer your question?
View the original post :
hey Heiko
thanks for the info. Yes it does answer my question!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4001837#4001837
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4001837
please clarify for me,
this magic that happens behind the scene is specific to JBossWS 1.2 or to any
implementation of JAX-WS?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4001838#4001838
Reply to the post :
I made a mistake, I actually meant ties and stubs as opposed to request
/response classes...but you guys get the idea :)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4001637#4001637
Reply to the post :
mistake again, ties are actually the response/request classes. Client side
still may need the stubs.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4001640#4001640
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4001640
14 matches
Mail list logo
