August 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2740) Add Class-Path attribute to jbossws-cxf-client manifest file

by Alessio Soldano (JIRA)

Add Class-Path attribute to jbossws-cxf-client manifest file ------------------------------------------------------------ Key: JBWS-2740 URL: https://jira.jboss.org/jira/browse/JBWS-2740 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-3.2.1 The jbossws-cxf-client.jar we produce has a manifest file without the Class-Path attribute (see jbossws-native-client.jar instead). That is required for easy client classpath configuration when not using maven. Perhaps there's even a test for this (in native testsuite, as that would fail in cxf if it's in framework) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2741) Evaluate removal of JAXWS API interfaces from jbossws-native-jaxws

by Alessio Soldano (JIRA)

Evaluate removal of JAXWS API interfaces from jbossws-native-jaxws ------------------------------------------------------------------ Key: JBWS-2741 URL: https://jira.jboss.org/jira/browse/JBWS-2741 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-3.2.1 At the current state there's probably no more reason for shipping the jaxws api inside the jbossws-native-jaxws instead of using the "official" jaxws api artifact. We might keep the jbossws-native-jaxws just for the service loads (the javax.xml.ws.spi.Provider for instance). This would simplify the m2 dependencies of projects referring to jaxws stuff (for instance jboss ejb3 client requires the jaxws api, but it's not good having that reference the jbossws-native-jaxws when using native and the jaxws-api when using metro/cxf stack). This need to be evaluated (both with jdk1.5 and jdk1.6), then changes to code, poms, manifests etc. can be done. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2613) Ensure correct line ends in windows shell scripts (CRNL)

by Richard Opalka (JIRA)

Ensure correct line ends in windows shell scripts (CRNL) -------------------------------------------------------- Key: JBWS-2613 URL: https://jira.jboss.org/jira/browse/JBWS-2613 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.2.0, jbossws-cxf-3.2.0, jbossws-metro-3.2.0 It will be more comfortable for our users to modify these scripts. Now before touching them they need to convert them to correct windows format. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-2739) Make OneWay operation non-blocking (client side)

by Alessio Soldano (JIRA)

Make OneWay operation non-blocking (client side) ------------------------------------------------ Key: JBWS-2739 URL: https://jira.jboss.org/jira/browse/JBWS-2739 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.2.0 Currently the @OneWay operations block while the business logic executes on the server and does not return a response until processing is complete. This feature request is to modify one-way operations to be non-blocking. On client side, we'd need to fork thread for the call, whenever allowed (cfr. maintain session prop) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2745) Issue with stack switch and binary distro install

by Alessio Soldano (JIRA)

Issue with stack switch and binary distro install ------------------------------------------------- Key: JBWS-2745 URL: https://jira.jboss.org/jira/browse/JBWS-2745 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: productization Reporter: Alessio Soldano Fix For: jbossws-cxf-3.2.1, jbossws-native-3.2.1, jbossws-metro-3.2.1 There seems to be an issue in the binary distro installation when switching stack on AS 5.1.0 (perhaps the AS version doesn't even matter). The deployers are probably not being replaced or something else weird is happening. http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252402#4252402 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2648) WSDL is not refreshing after the web service implementation has been updated

by Gina Kim (JIRA)

WSDL is not refreshing after the web service implementation has been updated ---------------------------------------------------------------------------- Key: JBWS-2648 URL: https://jira.jboss.org/jira/browse/JBWS-2648 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native, tools-jaxws Affects Versions: jbossws-native-3.1.0 Environment: JBoss AS 4.2.3 Eclipse 4.2.1 Reporter: Gina Kim I've created a bottom up web service and it deployed successfully. I then made a small change in the java implementation of the web service and tried to redeploy the web service. Now I'm getting this error: ERROR [MainDeployer] Could not start deployment: ... org.jboss.ws.WSException: patientID is not a valid property on class AuditPhiExport at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getElementPropertyAccessor(JAXBContextImpl.java:926) at org.jboss.ws.metadata.accessor.JAXBAccessorFactory.create(JAXBAccessorFactory.java:49) at org.jboss.ws.metadata.umdm.EndpointMetaData.createAccessor(EndpointMetaData.java:717) at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeAccessors(EndpointMetaData.java:673) ... Previously the parameter was called patientId (lower case d), and I just changed it to uppder case D. I tried refreshing the projects and wsdls but this error won't go away. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2655) no soap 1.2 inline multireferences support

by Wojciech Oczkowski (JIRA)

no soap 1.2 inline multireferences support ------------------------------------------ Key: JBWS-2655 URL: https://jira.jboss.org/jira/browse/JBWS-2655 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.2 Environment: debian, jboss-4.2, sun-java-6 Reporter: Wojciech Oczkowski jbossws doesn't seem to support inline multireferences from soap 1.2 while consuming webservices from other enviroments (php for example) result like: <item> <name>item1</name> <product enc:id="ref1"> <name>product1</name> </product> </item> <item> <name>item2</name> <product enc:ref="#ref1"/> </item> is unmarshaled with item2 object with product object filled with null's -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2262) WSDL is not correctly modified to use the configured https port

by Richard Nagy (JIRA)

WSDL is not correctly modified to use the configured https port --------------------------------------------------------------- Key: JBWS-2262 URL: https://jira.jboss.org/jira/browse/JBWS-2262 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBOSS version JBOSS-4.2.2.GA Linux 2.6.9-55.0 ELsmp Reporter: Richard Nagy When an ear file is deployed and used with the https protocol, the WSDL is not correctly modified to use the configured port numbers. The endpoint url in the wsdl is expected to be dynamically rebuilt during deployment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2687) JBossWS commandline tools requires Sun JDK to work. This dependency must be removed

by Richard Opalka (JIRA)

JBossWS commandline tools requires Sun JDK to work. This dependency must be removed ----------------------------------------------------------------------------------- Key: JBWS-2687 URL: https://jira.jboss.org/jira/browse/JBWS-2687 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Richard Opalka Assignee: Alessio Soldano Priority: Critical Fix For: jbossws-native-3.2.0 One of the goals for the next SOA-P CP is to see the whole platform certified with OpenJDK 1.6 I tried to run JBossWS on OpenJDK 1.6 and found the following dependency in our code: --- [ERROR] com.sun.tools.javac.Main is not available in the classpath, requires Suns JDK version 5.0 or latter. compilation failed, errors should have been reported Failed to invoke WsImport java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for more information at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:233) at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:222) at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:80) --- This dependency causes our command line tools (at least wsconsume) doesn't work on Open JDK :( -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (JBWS-2743) Make sure all maven dependencies are downloaded only from JBoss repositories

by Richard Opalka (JIRA)

Make sure all maven dependencies are downloaded only from JBoss repositories ---------------------------------------------------------------------------- Key: JBWS-2743 URL: https://jira.jboss.org/jira/browse/JBWS-2743 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Reporter: Richard Opalka Fix For: jbossws-cxf-3.2.1, jbossws-native-3.2.1, jbossws-metro-3.2.1 The problem in general is we're depending on thirdparty maven repositories. This is not acceptable because of reproducability of the builds in the future. We need to remove the following repositories from our poms: maven/parent/trunk/pom.xml <repository> <id>maven2.java.net</id> <name>Java.net Repository for Maven 2</name> <url>http://download.java.net/maven/2/</url> </repository> <repository> <id>java.net</id> <url>http://download.java.net/maven/1/</url> <layout>legacy</layout> </repository> stack/cxf/trunk/pom.xml <repository> <id>repository-snapshots-apache</id> <url>http://repository.apache.org/snapshots</url> <releases> <enabled>false</enabled> </releases> <snapshots> <enabled>true</enabled> </snapshots> </repository> and make sure all artifacts we're downloading from these repositories are available in jboss repositories. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues August 2009