September 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3642) Replace gnu-getopt:getopt with gnu.getopt:java-getopt

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3642?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3642: ----------------------------------------------- Pavel Jelinek <pjelinek(a)redhat.com> made a comment on [bug 1007527|https://bugzilla.redhat.com/show_bug.cgi?id=1007527] Fixed in EAP 6.2.0 ER3. > Replace gnu-getopt:getopt with gnu.getopt:java-getopt > ----------------------------------------------------- > > Key: JBWS-3642 > URL: https://issues.jboss.org/browse/JBWS-3642 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: productization > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > We're including gnu getopt (for jaxws tooling) from the jboss thirdparty repository; we should replace that with the gnu.getopt:java-getopt from maven central. That would help for building jbossws using the maven central repo only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3642) Replace gnu-getopt:getopt with gnu.getopt:java-getopt

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3642?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3642: ----------------------------------------------- Pavel Jelinek <pjelinek(a)redhat.com> changed the Status of [bug 1007527|https://bugzilla.redhat.com/show_bug.cgi?id=1007527] from ON_QA to VERIFIED > Replace gnu-getopt:getopt with gnu.getopt:java-getopt > ----------------------------------------------------- > > Key: JBWS-3642 > URL: https://issues.jboss.org/browse/JBWS-3642 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: productization > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > We're including gnu getopt (for jaxws tooling) from the jboss thirdparty repository; we should replace that with the gnu.getopt:java-getopt from maven central. That would help for building jbossws using the maven central repo only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3711) Refactor exising tests to use ShrinkWrap

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3711: ------------------------------------- Summary: Refactor exising tests to use ShrinkWrap Key: JBWS-3711 URL: https://issues.jboss.org/browse/JBWS-3711 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-4.3 See JBWS-3667, we should refactor the existing tests (some of them? all?) to use ShrinkWrap for building deployment archives. Also check comment at https://issues.jboss.org/browse/JBWS-3667?focusedCommentId=12801222&page=... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3710) appclient test failures against WFLY master

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3710: ------------------------------------- Summary: appclient test failures against WFLY master Key: JBWS-3710 URL: https://issues.jboss.org/browse/JBWS-3710 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.3 {noformat} Starting appclient process: /data/workspace/jbossws-hudson-4.2.0-SNAPSHOT/hudson-home/jobs/CXF-CORE-AS-8.0.0-SPRING-SUN-JDK-6/workspace/stack-cxf/modules/testsuite/shared-tests/target/test-libs/jaxws-samples-serviceref-appclient.ear#jaxws-samples-serviceref-appclient.jar... [0m23:07:48,092 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final [0m[0m23:07:48,350 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.0.Beta2 [0m[0m23:07:48,476 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015899: WildFly 8.0.0.Beta1-SNAPSHOT "WildFly" starting [0m23:07:50,583 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 11) JBAS011800: Activating Naming Subsystem 23:07:50,585 INFO [org.jboss.as.security] (ServerService Thread Pool -- 12) JBAS013171: Activating Security Subsystem 23:07:50,588 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.17.SP1 23:07:50,644 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 14) JBAS015537: Activating WebServices Extension 23:07:50,723 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.1.0.CR7 23:07:50,733 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.1.0.CR7 23:07:50,758 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.0.Beta1 23:07:51,021 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service 23:07:51,097 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:4448 23:07:51,215 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.txn.ArjunaRecoveryManager (missing) dependents: [service jboss.ejb.tx-recovery-service] service jboss.txn.CoreEnvironment (missing) dependents: [service jboss.ejb.tx-recovery-service] service jboss.txn.UserTransactionAccessControlService (missing) dependents: [service jboss.ejb3.EJB3UserTransactionAccessControlService] 23:07:51,237 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "jaxws-samples-serviceref-appclient.ear" (runtime-name: "jaxws-samples-serviceref-appclient.ear") 23:07:51,364 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "null" (runtime-name: "jaxws-samples-serviceref-appclient.jar") 23:07:52,410 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.0.0.Beta1-SNAPSHOT "WildFly" started (with errors) in 6458ms - Started 110 of 116 services (4 services failed or missing dependencies, 9 services are lazy, passive or on-demand) 23:07:52,412 ERROR [org.jboss.as.controller.management-operation] (Thread-24) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "jaxws-samples-serviceref-appclient.ear")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => [ "jboss.concurrent.ee.context.config.jaxws-samples-serviceref-appclient.jaxws-samples-serviceref-appclient.AppClientComponent is missing [jboss.txn.TransactionManager]", "jboss.concurrent.ee.context.config.jaxws-samples-serviceref-appclient.jaxws-samples-serviceref-appclient is missing [jboss.txn.TransactionManager]" ]} 23:07:52,416 ERROR [org.jboss.as.server] (Thread-24) JBAS015870: Deploy of deployment "jaxws-samples-serviceref-appclient.ear" was rolled back with the following failure message: {"JBAS014771: Services with missing/unavailable dependencies" => [ "jboss.concurrent.ee.context.config.jaxws-samples-serviceref-appclient.jaxws-samples-serviceref-appclient.AppClientComponent is missing [jboss.txn.TransactionManager]", "jboss.concurrent.ee.context.config.jaxws-samples-serviceref-appclient.jaxws-samples-serviceref-appclient is missing [jboss.txn.TransactionManager]" ]} 23:07:52,449 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment null (runtime-name: jaxws-samples-serviceref-appclient.jar) in 30ms 23:07:52,448 ERROR [org.jboss.as.appclient.logging] (Thread-25) JBAS013201: InterruptedException running app client main: java.lang.InterruptedException at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:996) [rt.jar:1.7.0_15] at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303) [rt.jar:1.7.0_15] at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236) [rt.jar:1.7.0_15] at org.jboss.as.appclient.service.ApplicationClientStartService$1.run(ApplicationClientStartService.java:108) at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_15] 23:07:52,480 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment jaxws-samples-serviceref-appclient.ear (runtime-name: jaxws-samples-serviceref-appclient.ear) in 62ms 23:07:52,492 INFO [org.jboss.as.controller] (Thread-24) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.txn.TransactionManager (missing) dependents: [service jboss.concurrent.ee.context.config.jaxws-samples-serviceref-appclient.jaxws-samples-serviceref-appclient, service jboss.concurrent.ee.context.config.jaxws-samples-serviceref-appclient.jaxws-samples-serviceref-appclient.AppClientComponent] 23:07:52,511 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015950: WildFly 8.0.0.Beta1-SNAPSHOT "WildFly" stopped in 36ms {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3642) Replace gnu-getopt:getopt with gnu.getopt:java-getopt

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3642?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3642: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1007527|https://bugzilla.redhat.com/show_bug.cgi?id=1007527] from MODIFIED to ON_QA > Replace gnu-getopt:getopt with gnu.getopt:java-getopt > ----------------------------------------------------- > > Key: JBWS-3642 > URL: https://issues.jboss.org/browse/JBWS-3642 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: productization > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > We're including gnu getopt (for jaxws tooling) from the jboss thirdparty repository; we should replace that with the gnu.getopt:java-getopt from maven central. That would help for building jbossws using the maven central repo only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3709) WSDiscoveryTestCase failures related to network environment

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3709?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3709: ---------------------------------- Fix Version/s: jbossws-cxf-4.3 > WSDiscoveryTestCase failures related to network environment > ----------------------------------------------------------- > > Key: JBWS-3709 > URL: https://issues.jboss.org/browse/JBWS-3709 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2 > Reporter: Petr Sakař > Priority: Minor > Fix For: jbossws-cxf-4.3 > > Attachments: patch_jbossws_cxf_trunk_modules_testsuite_JBWS-3709.txt > > > This test depends on network environment in which it runs. If there exists another server bound to public network interface with enabled WS-Discovery announcements, the test will fail, as it will discover services on the other server as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3709) WSDiscoveryTestCase failures related to network environment

by Petr Sakař (JIRA)

[ https://issues.jboss.org/browse/JBWS-3709?page=com.atlassian.jira.plugin.... ] Petr Sakař updated JBWS-3709: ----------------------------- Attachment: patch_jbossws_cxf_trunk_modules_testsuite_JBWS-3709.txt proposed changes to test case to ignore services not related to this test > WSDiscoveryTestCase failures related to network environment > ----------------------------------------------------------- > > Key: JBWS-3709 > URL: https://issues.jboss.org/browse/JBWS-3709 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2 > Reporter: Petr Sakař > Priority: Minor > Attachments: patch_jbossws_cxf_trunk_modules_testsuite_JBWS-3709.txt > > > This test depends on network environment in which it runs. If there exists another server bound to public network interface with enabled WS-Discovery announcements, the test will fail, as it will discover services on the other server as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3709) WSDiscoveryTestCase failures related to network environment

by Petr Sakař (JIRA)

Petr Sakař created JBWS-3709: -------------------------------- Summary: WSDiscoveryTestCase failures related to network environment Key: JBWS-3709 URL: https://issues.jboss.org/browse/JBWS-3709 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-4.2 Reporter: Petr Sakař Priority: Minor This test depends on network environment in which it runs. If there exists another server bound to public network interface with enabled WS-Discovery announcements, the test will fail, as it will discover services on the other server as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3690) XMLJavaTypeAdapter not working in Exception Classes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3690?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3690: ----------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> made a comment on [bug 999893|https://bugzilla.redhat.com/show_bug.cgi?id=999893] Alessio, thanks for clarification. I didn't check the pom for cxf version. > XMLJavaTypeAdapter not working in Exception Classes > --------------------------------------------------- > > Key: JBWS-3690 > URL: https://issues.jboss.org/browse/JBWS-3690 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2 > Reporter: Mustafa Musaji > Assignee: Mustafa Musaji > Fix For: jbossws-cxf-4.3 > > Attachments: cxf5219.diff, cxfTest.jar > > > @XMLJavaTypeAdapter usage in Exception Classes does not work when mapping to a class not in the JAXB Context. > {code:title=MyEJB.java} > @Stateless > @WebService > public class MyEJB { > public void launcheMyException() throws MyException { > return; > } > } > {code} > {code:title=MyException.java} > @XmlAccessorType(XmlAccessType.FIELD) > public class MyException extends Exception { > @XmlJavaTypeAdapter(Cl1ToCl2Adapter.class) > MyClass1 obj1; > @XmlJavaTypeAdapter(NoArgObjAdapter.class) > NoArgObj obj2; > public MyClass1 getObj1() { > return obj1; > } > > public void setObj1(MyClass1 obj1) { > this.obj1 = obj1; > } > public NoArgObj getObj2() { > return obj2; > } > public void setObj2(NoArgObj obj2) { > this.obj2 = obj2; > } > } > {code} > {code:title=Cl1ToCl2Adapter.java} > public class Cl1ToCl2Adapter extends XmlAdapter<MyClass2,MyClass1> { > @Override > public MyClass2 marshal(MyClass1 v) throws Exception { > return new MyClass2(); > } > @Override > public MyClass1 unmarshal(MyClass2 v) throws Exception { > MyClass1 mc1 = new MyClass1(v.getS2()); > return mc1; > } > } > {code} > This is what the resulting WSDL contains. Obj2 is mapped fine to a String, but MyClass1 is not and should have the MyClass2 mapping here. > {code:xml} > <xs:complexType name="MyException"> > <xs:sequence> > <xs:element name="str" nillable="true" type="xs:string"/> > <xs:element name="obj2" nillable="true" type="xs:string"/> > </xs:sequence> > </xs:complexType> > {code} > If you add the same adapter to a non Exception class it works just fine. > This is NOT a duplicate of JBWS-3552 as I believe in that use case only known JAXB types were tested (HashMap, Strings etc). This issue is when you are using custom classes that need to be mapped. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3708) Enforce client/endpoint config immutability at runtime

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3708?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3708: ---------------------------------- Summary: Enforce client/endpoint config immutability at runtime (was: Enforce client/endpoint config immutability) > Enforce client/endpoint config immutability at runtime > ------------------------------------------------------ > > Key: JBWS-3708 > URL: https://issues.jboss.org/browse/JBWS-3708 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > The client and endpoint predefined configs should be considered immutable after the server has booted. Unless we decide to explicitly support on-the-fly user modification of configs (e.g. for adding handlers, changing props, etc.) we need to return immutable versions / deep copy of them from the ServerConfig (AbstractServerConfig). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues September 2013