[JBoss JIRA] Created: (JBWS-1924) Verify installation script for jboss-4.2.1.GA
by Alessio Soldano (JIRA)
Verify installation script for jboss-4.2.1.GA
---------------------------------------------
Key: JBWS-1924
URL: http://jira.jboss.com/jira/browse/JBWS-1924
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-2.0.2
Reporter: Alessio Soldano
Installing JBossWS 2.0.2.GA on JBoss 4.2.1.GA without having a JBossWS 2.0.1.GA installed result in a broken installation due to jbossws-jboss42.jar/jbossws-jboss421.jar missing in client libs.
The 2.0.2 installation script does not remove that lib, thus installing 2.0.1 and then 2.0.2 seems to be a workaround. This has to be verified as well as the 2.0.2 installation script / hudson conf for the 4.2.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years
[JBoss JIRA] Created: (JBWS-1816) JAXWS SOAPFault inheritance
by Thomas Diesler (JIRA)
JAXWS SOAPFault inheritance
---------------------------
Key: JBWS-1816
URL: http://jira.jboss.com/jira/browse/JBWS-1816
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Fix For: jbossws-2.0.2
I'm using wsprovide (an ant task in maven on windows) to generate my wsdl and then wsconsume to generate my client classes. My web service method throws multiple exceptions, some of which extend from each other.
Unfortunately that inheritance relationship is lost in the generated wsdl (no < extension base...) and of course in the client classes.
Is there some way to get the wsprovide task to do what I'm asking for? Maybe with an annotation or something specific passed in when I call the task?
Thanks in advance.
BTW - there are multiple JIRA items (like: http://jira.jboss.com/jira/browse/JBWS-251) that refer to this issue issue. However it doesn't appear that it ever valid or addressed. So I'm wondering if there's something basic that I should be doing? Like digging into the documentation on javaToWSDL which I believe is being used by wsprovide.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years
[JBoss JIRA] Created: (JBWS-1505) Methods defined in an interface superclass don't appear in WSDL.
by Iaacov Rosenberg (JIRA)
Methods defined in an interface superclass don't appear in WSDL.
----------------------------------------------------------------
Key: JBWS-1505
URL: http://jira.jboss.com/jira/browse/JBWS-1505
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-1.0.4
Environment: JBoss 4.0.5 GA, JRE 1.5.0_10, WinXP
Reporter: Iaacov Rosenberg
Given the following scenario:
public interface Intf1 {
public int getMember1();
public void setMember1(int member1);
}
public interface Intf2 extends Intf1 {
public int getMember2();
public void setMember2(int member2);
}
Whenever JBossWS uses reflection, either when generating the WSDL file or when returning values that implement Intf2, only members defined in Intf2 (i.e. Member2) are processed, while ignoring inherited members.
This only happens with interfaces. Inherited classes are processed correctly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 1 month