Hi Richard, thanks for reply!
I think that it could be better (for example) if it should be possible to
insert the @XmlSeeAlso in the service endpoint class.
In this way when you defining the XXX Service endpoint class you can indicate
implicit classes that are involved in the service execution
Hi Andrea,
you're absolutely right, it's absurd. It's the Sun wrong approach hotfix for
some
OO related issues in their JAXB tool.
Richard
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4197040#4197040
Reply to the post :
Excuse me, just a simple question...with @XmlSeeAlso annotation you MUST list
in the superclass all the required subclasses (subclasses that need to be
declared / defined in WSDL schema portion) ...isn't it absurd from an OO point
of view?
I mean, a superclass should ignore whenever there are
After some search I found that @XmlSeeAlso works with DPIM [dynamic proxy
invocation mechanism] client.
For Schema2Java approach I?ve managed to verify that this is a known JBossWS
issue that is marked to be fixed in JBossWS 2.0.2.
Hi mrokka, I encourage you to investigate this further. Please work with our
testsuite and bring your usecase into it. If you find a solution that you can
contribute - even better.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4089701#4089701
Reply to the
http://jbws.dyndns.org/mediawiki/index.php?title=FAQ#What_JIRA_issues_are_backed_up_by_tests.3F
http://jira.jboss.org/jira/browse/JBWS-1702
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4088495#4088495
Reply to the post :
After Using @XmlSeeAlso only difference I found on generated WSDL was There was
complextype name b and c which I don?t get without using @XmlSeeAlso. I have
used wsconsume to create the web service artifacts of the generated wsdl and my
client code looks like this:
MyWebService
I also have the same problem. I have used jboss4.2.0+jbossws2.0.1+jdk 1.5. I
tried using @XmlSeeAlso on base class but it also can't solved my porblem.
I have the following situation:
My Pojo classes
@XmlSeeAlso({B.class,C.class})
public class A extends java.io.Serializable{
}
public class B
Are you using the same playoad beans on the client side?
How does SOAP Message look like?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4082614#4082614
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4082614
Client is using the beans generated from the WSDL. Looks like after some minor
changes on the server finally, the SOAP response looks right..but is not being
materialized into the right type of object :
| env:Envelope xmlns:env=http://schemas.xmlsoap.org/soap/envelope/;
| env:Header/
It's fixed. You'll need to work with @XmlSeeAlso
(http://jsourcery.com/api/java.net/jaxb/2.1.2/javax/xml/bind/annotation/XmlSeeAlso.html)
on the superclass.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4082260#4082260
Reply to the post :
I am already using the XmlSeeAlso..
@XmlSeeAlso({Aa.class, Aaa.class})
public class A
{
}
@XmlSeeAlso(Aaa.class)
public class Aa extends A
{
}
public class Aaa extends Aa
{}
And the WebService ..
@WebService
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT,
use =
JBossWS 2.0.1 release notes say that JBWS-1702 is fixed which solves the
inheritance problem, but looks like it is still not fixed.
I'm usinf JBossWS 2.0.1 with JBoss 4.0.5.
I've tried both jdk 1.5 anf jdk 1.6.
View the original post :
I have testet a little bit more and now I have a little example that I can
deploy. I also startet with the wsdl file and used wsconsume to create the java
classes and annotation. Then I copied these classes in my project and so the
deployment was successful. But when I access the deployed
Ok I have managed to create a simple example of the behavior. Please note that
I am pretty new to webservices and JBossWS (started using it a few days ago) so
sorry if something is overly complicated. Feedback is highly appreciated.
I am using JBoss 4.2.0.GA and java version 1.5.0_08
I
Here are the generated XML fragments (read from the JBoss log):
Incorrect Behavior (B Transmitted)
| ns1:bResponse xmlns:ns1=http://echo/;
| something xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:nil=true/
| b
| arg01/arg0
| arg12/arg1
|
I tried to post this in JIRA but it told me I dont have permission to comment
on the issue so here it goes:
I am experiencing the same problem described by original Reporter: Subclass
information gets lost when the SOAP message is createdbut not always.. if
the class contains a variable
I tried to create an own JAXBElement as you described. But I am getting errors
when I deploy it. First I create an ObjectFactory for someElement:
| @XmlRegistry
| class ObjectFactory {
|
| @XmlElementDecl(scope=getClassBResponse.class, name=someElement,
Hmm interesting. As I said I started with a wsdl file and used wsconsume to
create the Java Classes and annotations. I have not touched the Java classes or
the ObjectFactory manually.
When I find the time I will try to create a complete, minimal example.
View the original post :
If like to get involved please add a testcase to our testsuite
http://jira.jboss.org/jira/browse/JBWS-1702
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4051714#4051714
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4051714
20 matches
Mail list logo
