Ensure that JAXWS libraries are not in the classpath
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4023885#4023885
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4023885
___
If you could wait until tomorrow (or alittle after), JBoss 1.2 should be out
soon (binary release). That supports 181 annotations and is much simpler to
develop.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4023349#4023349
Reply to the post :
You can use JAXB to specify the name of class
For example,
| @XmlType(name=ColorVariant)
| public class ColorVariant {
| ...
| }
|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4019378#4019378
Reply to the post :
To make it easier, you guys may want to consider using SOAPUI
http://www.soapui.org/jbossws/index.html
if you use eclipse, you simply right click on the POJO and generate the
webservice from it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4017388#4017388
The JBoss guys can probably help you better than I can. But I'd imagine any
later version than beta is acceptable.
In fact, it could just be something is not configured properly. Last time I
tried JBoss 5, nothing really worked for me so I am on 4.0.5 instead with
JBossWS 1.2
Try going to
To answer your question,
check out 2.0 CR3
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQBuildAndInstall
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4016405#4016405
Reply to the post :
CR3 should be 1.2ws,
whats the exact link that you downloaded from? Or did you checkout the code
and build it yourself?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4016542#4016542
Reply to the post :
CR3 should be 1.2ws,
whats the exact link that you downloaded from? Or did you checkout the code
and build it yourself?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4016544#4016544
Reply to the post :
Yes, ws1.2 is very similiar to 2.0...I am not even sure what the differences
are.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4016567#4016567
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4016567
oooh I see
that clears it up a bunch
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4016675#4016675
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4016675
___
jboss-user mailing
its a moot issue,
it generates two wsdls because
the SEI has a different name space than its implementing class
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4016676#4016676
Reply to the post :
your testUI does not extend HTTPServlet or implement the servlet interface
itself.
Your webservice will not deploy regardless though, you need to add the
annotation @stateless and not make it a servlet but rather a POJO
View the original post :
That guide is for JAX-RPC, JBossWS 1.0.x, this is a more relevant guide (
http://tddell.dyndns.org/mediawiki/index.php/JAX-WS_User_Guide
The JBossWS version you're using is JBoss 2.x (JAX-WS), alot of it is not
applicable (although some of it is though)
When I meant POJO I meant as in
you may want to grab the latest JBossWS 2.0 from SVN then, the WSDL should show
up
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4015278#4015278
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4015278
ensure that your JDK is 1.5 and not 1..6
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4012404#4012404
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4012404
___
jboss-user mailing
For Glassfish JAXWS 2.1
it seems that the annotations
@Stateful and
@Addressing are supported
so you basically annotate your web service with
@Stateful
@Addressing
@Webservice
along with a reference to a StatefulWebServiceManager
JBoss guys,
would you say upcoming or existing JAXWS
try using @WebContext
as defined here
http://labs.jboss.com/file-access/default/members/jbossws/downloads/api-docs/index.html?org/jboss/ws/annotation/package-summary.html
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4012061#4012061
Reply to the post :
there is a tutorial on how to implement ws eventing for JBossWS 1.0.x (JAX-RPC)
but I am not sure if the same procedure is the same for JBossWS 1.2.
Can any of the JBoss people provide some hints or documentation (or a simple
sample using annotations) for WS-eventing?
View the original post :
hey Andrea
you can use the annotation @wsdlLocation to bind your SEI (service end point)
to a WSDL. That way the SEI has to confirm to the WSDL.
also, you could always do wsgen (WSDL to java) to generate the SEI and the
relevant datatypes.
To answer your question about moving your JBossWS
Add the annotation @WebService
and deploy as any EJB jar
then check
localhost:8080/jbossws/services (granted localhost:8080 is your webserver host
and 8080 is your http port)
if your service appears
View the original post :
hey Andrea
as of JAX-WS 2.0, there is no supprt for stateful sessions. In JAX-WS 2.1,
there is a concept of stateful webservices which is done through ws-addressing.
I would not recommend serializing the Handle object, if need be make a
representation (or key) of the handle and pass that
Are you using JBossWS 1.0.x (JAX RPC)?
If so, make LoanProcessor extend java.rmi.Remote
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4008394#4008394
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4008394
Hey guys
Do you guys know how to change the context root and the service uri of a web
service in JBossWS 1.2 +?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4008505#4008505
Reply to the post :
Hey Deployer
I think its more of a JBoss 5 issue more than a JBossWS issue.
It seems that JBoss 5 is not picking up any application at all and I am not
quite sure why.
you can check
http://localhost:8080/status
to check any deployed applications
you should post in the JBoss AS forum to
ensure that the current JDK is 1.5 and not 1.6
there is a conflict with JDK 6 and JBossWS
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4007952#4007952
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4007952
also
did you compile the stubs (against the WSDL) for the client class?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4008087#4008087
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4008087
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
just curious, what do you have in your ejb jar?
or better yet, how are you deploying the EJB? In a jar within an EAR? do you
use an IDE to deploy it for you?
What is the output as soon as you put the jar in the default/deploy folder?
You see some messages that it was deployed or
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
what do you mean by it doesn't deploy? Do you get exceptions thrown by the
JBoss runtime?
(assuming your http port is 8080 and you're publishing on your localhost) you
can try going to
http://localhost:8080/jbossws/services
you should see the WSDL there
View the original post :
Hey JBoss team
just curious how I would enable SOAP 1.2 support for JBossWS
I tried
@BindingType(value=SOAPBinding.SOAP12HTTP_MTOM_BINDING)
but it doesn't seem to do anything.
In Glass fish, to enable SOAP is
@BindingType(value=http://java.sun.com/xml/ns/jaxws/2003/05/soap/bindings/HTTP/;)
yes, you can use a UDDI
more info can be found here
http://wiki.jboss.org/wiki/Wiki.jsp?page=UDDIExample
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4006556#4006556
Reply to the post :
Hey JBoss team
I was wondering what causes wsdls to be generated within each other.
I am getting a wsdl that imports another wsdl.
I would just like everything to be in a single wsdl.
any info would be apperciated.
View the original post :
Are you considering clustering as well?
Remember that a singleton is per JVM, If you're not clustering...although this
is bad practice...you could just use a regular POJO as a singleton.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4006562#4006562
Reply to
Hey guys
I was wondering how I could leverage SOAP 1.2 along with JBossWS 1.2?
Does the annotation @BindingType for a SEI work?
@BindingType (value=SOAPBinding.SOAP12HTTP)
I am kinda lost as to how to map fault codes to specific java exceptions.
any info would be much apperciated.
View
Hey guys
JBoss AS's JMX has the ability to set the logging levels dynamically, the
service is called Logging
Domain Name:jboss.system
service:Logging
type: Log4jService
MBean Java Class: org.jboss.mx.modelmbean.XMBean
I was wondering as opposed to using log4j to log my
In my experience, JBoss does not running correctly with JDK 6. I've heard
several issues, especially when using JBoss web services.
Until there is an official release and assurance that JBoss 4.x or even JBoss
5.x will comply with Java 6..
Eventually, I am guessing that they will modify and
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 :
Hey guys
Some aspects of the WSDL can be enforced via annotations such as webParam
and @WebService but some things cannot be enforced via annotations such as
adding non-nillable arguments to specific web parameters.
Is it possible to modify the generated WSDL (at runtime) and use
Also,
this maybe a very trivial question to some but I am kinda lost
Is there a place in an ejb jar or ear to store the WSDL file so that the
annotation @Webservice(wsdlLocation=) such that I can place it so that it
doesn't need an absolute URL.
For example, if I could make a folder called
Ok, just found a way...
you put the wsdl in the META-INF folder which is the root,
so if you have a file META-INF/wsdl/myWSDL.wsdl
your annotation would look like such
@WebService (wsdlLocation='META-INF/wsdl/myWSDL.wsdl)
However, it seems that the changes I made to META-INF/wsdl/myWSDL.wsdl do
Ok, correction...some ant scripts did not deploy right.
enforcing the WSDL through wsdlLocation does work and it is used.
You just have to ensure that the wsdl in wsdl location does not contradict the
web service implementation.
So if you want to add comments using xs:documentation, you can
Hey guys
Just out of curiousity, is @Remote the same as extending java.rmi.Remote?
In the previous J2EE, EJBObject extends java.rmi.Remote, in the context of the
JBoss EJB 3.0 implementation, is there any difference between
@Remote
public interface myInterface
and
public interface
hey Michae
Perhaps, you could try to @WebServiceRef annotation.
Also, you could post the code too.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4001596#4001596
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4001596
When is the expected binary release of JBossWS 1.2? And will it be compatible
with all versions of JBoss 4.0.x?
I am not too familiar with the version naming scheme of JBoss, I recognize that
the current version of JBossWS 1.2 is CR2. Does this mean its almost ready for
release?
any
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
Hey guys
I relatively new to web services
I am deploying a stateless session bean (EJB 3.0) on JBoss 4.0.5 with JBossWS
1.2 (JAXWS). Bottom to top development.
I use the @WebService and @webmethod annotation on my EJB with no real config
files (other than the application.xml). I deploy the
Thomas,
with regards to changing out the jax-rpc.jar to use JBoss' implementation,
would you say its safe to use 1.6 to run the latest JBoss 4.x AS and JBossWS
(JAXWS)?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4001141#4001141
Reply to the post :
not sure why some of the text is missing but the code should be:
@stateless
@Webservice
public class foo{
@WebMethod
public void bar (@WebParam (name=x, nillable = false ) String x){
System.out.println (x);
}
}
View the original post :
Hey guys
I was wondering if there is documentation on developing Web services for
JBossWS 2.0 (on JBoss 4.x).
Previously, I used the SOAPui plugin (bundled with JBossEclipse) to generate
the WSDL and the objects (webservices.xml, the request/response classes, etc)
associated with the
53 matches
Mail list logo
