October 2014 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3842) Cannot boot server with 2+ handlers in the same predefined configuration handler chain

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3842?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3842: --------------------------------------- WFLY master fix: https://github.com/wildfly/wildfly/commit/511e6539676770a073323598da54824... > Cannot boot server with 2+ handlers in the same predefined configuration handler chain > -------------------------------------------------------------------------------------- > > Key: JBWS-3842 > URL: https://issues.jboss.org/browse/JBWS-3842 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.3 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3.2, jbossws-cxf-5.0 > > > Commit https://github.com/wildfly/wildfly/commit/e32f27d433ad3da41ef042f1ad9b950... introduced a regressions when having multiple handlers in the same handler-chain within one of the pre-defined configuration in the webservices subsystem: > {noformat} > 5:49:24,653 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.ws.endpoint-config.Recording-Endpoint-Config.pre-handler-chain.recording-handlers: org.jboss.msc.service.StartException in service jboss.ws.endpoint-config.Recording-Endpoint-Config.pre-handler-chain.recording-handlers: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60] > Caused by: org.jboss.msc.inject.InjectionException: Value already set for this injector > at org.jboss.msc.inject.RetainingInjector.inject(RetainingInjector.java:50) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.as.webservices.dmr.ListInjector.inject(ListInjector.java:23) > at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1672) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl.access$2000(ServiceControllerImpl.java:51) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1917) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1876) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > ... 3 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3845) Injection not working in JAX-WS handlers from predefined configurations

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3845?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3845: ---------------------------------- Summary: Injection not working in JAX-WS handlers from predefined configurations (was: Injection not working in jax-ws handlers defined via CLI) > Injection not working in JAX-WS handlers from predefined configurations > ----------------------------------------------------------------------- > > Key: JBWS-3845 > URL: https://issues.jboss.org/browse/JBWS-3845 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Environment: JBoss EAP 6.3 > Reporter: Roberto Polli > Labels: cdi, handler, jax-ws > Fix For: jbossws-cxf-5.0 > > > Reproduce: > 1- deliver [the linked jaxws webapp|https://github.com/ioggstream/jboss-eap-quickstarts/tree/jaxws-han...] on EAP6.3 > 2- add the CDIHandler using the the CLI (eg.) or running the given [standalone.xml|https://github.com/ioggstream/jboss-eap-quickstarts/blob/j...] > $ cd /subsystem=webservices/endpoint-config=Standard-Endpoint-Config/ > $ /pre-handler-chain=C1:add > $ /pre-handler-chain=C1/handler=H1:add(class="org.jboss.as.quickstarts.wshelloworld.CDIHandler") > $ :reload > 3- Invoke > * HelloWorldService.sayHello() > I expect: > A- the CDIBean to be injected > B- the server replying correctly > Instead > B- the injection doesn't happen and the handler raises an exception > Running the Handler via the @HandlerChain annotation (using the provided HandlerServiceImpl) and removing the handlerchain from jboss everything works fine. > Debugging I found that those handlers are created via ConfigHelper.setupConfigHandlers which does a clazz.newInstance(). Probably this doesn't go through the CDI chain... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3845) Injection not working in jax-ws handlers defined via CLI

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3845?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3845: ---------------------------------- Fix Version/s: jbossws-cxf-5.0 > Injection not working in jax-ws handlers defined via CLI > -------------------------------------------------------- > > Key: JBWS-3845 > URL: https://issues.jboss.org/browse/JBWS-3845 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Environment: JBoss EAP 6.3 > Reporter: Roberto Polli > Labels: cdi, handler, jax-ws > Fix For: jbossws-cxf-5.0 > > > Reproduce: > 1- deliver [the linked jaxws webapp|https://github.com/ioggstream/jboss-eap-quickstarts/tree/jaxws-han...] on EAP6.3 > 2- add the CDIHandler using the the CLI (eg.) or running the given [standalone.xml|https://github.com/ioggstream/jboss-eap-quickstarts/blob/j...] > $ cd /subsystem=webservices/endpoint-config=Standard-Endpoint-Config/ > $ /pre-handler-chain=C1:add > $ /pre-handler-chain=C1/handler=H1:add(class="org.jboss.as.quickstarts.wshelloworld.CDIHandler") > $ :reload > 3- Invoke > * HelloWorldService.sayHello() > I expect: > A- the CDIBean to be injected > B- the server replying correctly > Instead > B- the injection doesn't happen and the handler raises an exception > Running the Handler via the @HandlerChain annotation (using the provided HandlerServiceImpl) and removing the handlerchain from jboss everything works fine. > Debugging I found that those handlers are created via ConfigHelper.setupConfigHandlers which does a clazz.newInstance(). Probably this doesn't go through the CDI chain... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3792) JBossWS: wsdl:import always handled as relative location

by Marc H. (JIRA)

[ https://issues.jboss.org/browse/JBWS-3792?page=com.atlassian.jira.plugin.... ] Marc H. commented on JBWS-3792: ------------------------------- Many thanks! > JBossWS: wsdl:import always handled as relative location > -------------------------------------------------------- > > Key: JBWS-3792 > URL: https://issues.jboss.org/browse/JBWS-3792 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3 > Reporter: Marc H. > Assignee: R Searls > Attachments: JBWS-3792_java.net.URL_proposal.patch, jbws3792-external-wsdl.war, jbws3792-ws-impl.war, jbws3792_example_src.tar.gz > > > As described in this thread: https://community.jboss.org/thread/240821 > wsdl:import directive seems to be always resolved as a relative location. > For example, this statement: > <wsdl:import namespace="http://foo.bar.com/foo.bar.Service" location="http://foo.bar.com/Service.svc?wsdl=wsdl0"/> > May result in this URL being resolved: > http://foo.bar.com/http://foo.bar.com/Service.svc?wsdl=wsdl0 > This prevents the WSDL file from being parsed. > This behavior seems to originate from: org.jboss.ws.common.deployment.SOAPAddressWSDLParser, line 211 in v2.3.0.Final and current trunk: > } else if (match(reader, WSDL_NS, IMPORT)) { > final String location = reader.getAttributeValue(null, LOCATION); > final String url = wsdlUrl.toString(); > final String newUrl = url.substring(0, url.lastIndexOf("/") + (location.startsWith("/") ? 0 : 1)) + location; > if (!metadata.getImports().containsKey(newUrl)) { > metadata.getImports().put(newUrl, false); > } > } -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3845) Injection not working in jax-ws handlers defined via CLI

by Roberto Polli (JIRA)

[ https://issues.jboss.org/browse/JBWS-3845?page=com.atlassian.jira.plugin.... ] Roberto Polli updated JBWS-3845: -------------------------------- Description: Reproduce: 1- deliver [the linked jaxws webapp|https://github.com/ioggstream/jboss-eap-quickstarts/tree/jaxws-han...] on EAP6.3 2- add the CDIHandler using the the CLI (eg.) or running the given [standalone.xml|https://github.com/ioggstream/jboss-eap-quickstarts/blob/j...] $ cd /subsystem=webservices/endpoint-config=Standard-Endpoint-Config/ $ /pre-handler-chain=C1:add $ /pre-handler-chain=C1/handler=H1:add(class="org.jboss.as.quickstarts.wshelloworld.CDIHandler") $ :reload 3- Invoke * HelloWorldService.sayHello() I expect: A- the CDIBean to be injected B- the server replying correctly Instead B- the injection doesn't happen and the handler raises an exception Running the Handler via the @HandlerChain annotation (using the provided HandlerServiceImpl) and removing the handlerchain from jboss everything works fine. Debugging I found that those handlers are created via ConfigHelper.setupConfigHandlers which does a clazz.newInstance(). Probably this doesn't go through the CDI chain... was: Reproduce: 1- deliver [the linked jaxws webapp|https://github.com/ioggstream/jboss-eap-quickstarts/tree/jaxws-han...] on EAP6.3 2- add the CDIHandler using the the CLI (eg.) or running the given [standalone.xml|https://github.com/ioggstream/jboss-eap-quickstarts/blob/j...] $ cd /subsystem=webservices/endpoint-config=Standard-Endpoint-Config/ $ /pre-handler-chain=C1:add $ /pre-handler-chain=C1/handler=H1:add(class="org.jboss.as.quickstarts.wshelloworld.CDIHandler") $ :reload 3- Invoke * HelloWorldService.sayHello() I expect: A- the CDIBean to be injected B- the server replying correctly Instead B- the injection doesn't happen and the handler raises an exception Running the Handler via the @HandlerChain annotation (using the provided HandlerServiceImpl) and removing the handlerchain from jboss everything works fine. > Injection not working in jax-ws handlers defined via CLI > -------------------------------------------------------- > > Key: JBWS-3845 > URL: https://issues.jboss.org/browse/JBWS-3845 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Environment: JBoss EAP 6.3 > Reporter: Roberto Polli > Labels: cdi, handler, jax-ws > > Reproduce: > 1- deliver [the linked jaxws webapp|https://github.com/ioggstream/jboss-eap-quickstarts/tree/jaxws-han...] on EAP6.3 > 2- add the CDIHandler using the the CLI (eg.) or running the given [standalone.xml|https://github.com/ioggstream/jboss-eap-quickstarts/blob/j...] > $ cd /subsystem=webservices/endpoint-config=Standard-Endpoint-Config/ > $ /pre-handler-chain=C1:add > $ /pre-handler-chain=C1/handler=H1:add(class="org.jboss.as.quickstarts.wshelloworld.CDIHandler") > $ :reload > 3- Invoke > * HelloWorldService.sayHello() > I expect: > A- the CDIBean to be injected > B- the server replying correctly > Instead > B- the injection doesn't happen and the handler raises an exception > Running the Handler via the @HandlerChain annotation (using the provided HandlerServiceImpl) and removing the handlerchain from jboss everything works fine. > Debugging I found that those handlers are created via ConfigHelper.setupConfigHandlers which does a clazz.newInstance(). Probably this doesn't go through the CDI chain... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3845) Injection not working in jax-ws handlers defined via CLI

by Roberto Polli (JIRA)

Roberto Polli created JBWS-3845: ----------------------------------- Summary: Injection not working in jax-ws handlers defined via CLI Key: JBWS-3845 URL: https://issues.jboss.org/browse/JBWS-3845 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Environment: JBoss EAP 6.3 Reporter: Roberto Polli Reproduce: 1- deliver [the linked jaxws webapp|https://github.com/ioggstream/jboss-eap-quickstarts/tree/jaxws-han...] on EAP6.3 2- add the CDIHandler using the the CLI (eg.) or running the given [standalone.xml|https://github.com/ioggstream/jboss-eap-quickstarts/blob/j...] $ cd /subsystem=webservices/endpoint-config=Standard-Endpoint-Config/ $ /pre-handler-chain=C1:add $ /pre-handler-chain=C1/handler=H1:add(class="org.jboss.as.quickstarts.wshelloworld.CDIHandler") $ :reload 3- Invoke * HelloWorldService.sayHello() I expect: A- the CDIBean to be injected B- the server replying correctly Instead B- the injection doesn't happen and the handler raises an exception Running the Handler via the @HandlerChain annotation (using the provided HandlerServiceImpl) and removing the handlerchain from jboss everything works fine. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3842) Cannot boot server with 2+ handlers in the same predefined configuration handler chain

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3842?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3842: ---------------------------------- Summary: Cannot boot server with 2+ handlers in the same predefined configuration handler chain (was: InjectionException: Value already set for this injector) > Cannot boot server with 2+ handlers in the same predefined configuration handler chain > -------------------------------------------------------------------------------------- > > Key: JBWS-3842 > URL: https://issues.jboss.org/browse/JBWS-3842 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.3 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3.2, jbossws-cxf-5.0 > > > Commit https://github.com/wildfly/wildfly/commit/e32f27d433ad3da41ef042f1ad9b950... introduced a regressions when having multiple handlers in the same handler-chain within one of the pre-defined configuration in the webservices subsystem: > {noformat} > 5:49:24,653 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.ws.endpoint-config.Recording-Endpoint-Config.pre-handler-chain.recording-handlers: org.jboss.msc.service.StartException in service jboss.ws.endpoint-config.Recording-Endpoint-Config.pre-handler-chain.recording-handlers: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60] > Caused by: org.jboss.msc.inject.InjectionException: Value already set for this injector > at org.jboss.msc.inject.RetainingInjector.inject(RetainingInjector.java:50) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.as.webservices.dmr.ListInjector.inject(ListInjector.java:23) > at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1672) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl.access$2000(ServiceControllerImpl.java:51) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1917) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1876) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > ... 3 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3838) Predefined configuration handlers executing in different order when server is restarted

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3838?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3838: ---------------------------------- Summary: Predefined configuration handlers executing in different order when server is restarted (was: SOAP Web Service Handlers executing in different order when server is restarted) > Predefined configuration handlers executing in different order when server is restarted > --------------------------------------------------------------------------------------- > > Key: JBWS-3838 > URL: https://issues.jboss.org/browse/JBWS-3838 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3 > Reporter: david.boeren > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3.2, jbossws-cxf-5.0 > > > Handler order can change after a reboot, which causes problems when one handler depends on the action of another. > * Description of the problem > The flow is basically the following: > 1) the container model is parsed; it can include jaxws configs, which are composed > of jaxws handler chains, which in turn has one or multiple jaxws handlers > 2) we have add operations for each jaxws handler and jaxws handler > chain. Each of them starts a service, which builds up the corresponding > metadata to be later used by jbossws; proper dependencies are set > between those services, so that for instance the service for a handler > chain waits for all its handlers' services. > 3) when the service for the handler chain runs, it gets the info from > the handler services and them in the chain metadata. This is where I get > unpredictable ordering, as the handler services are run in parallel > * Solution > The idea is that we need to derive the handlers' order from the add operation steps, which are executed in the same order they're created in the parser. > Brian also suggests to use the OperationContext.attach(...) API to pass data between handler invocations within an overall operation execution. All ws subsystem ops during boot are executed as steps within an overall operation. The API works like the attachment stuff that's used a lot in DeploymentUnitProcessors. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3843) EJB3 Web Service returns Invalid User on parallel invocations

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3843?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3843: ---------------------------------- Fix Version/s: jbossws-cxf-5.0 > EJB3 Web Service returns Invalid User on parallel invocations > ------------------------------------------------------------- > > Key: JBWS-3843 > URL: https://issues.jboss.org/browse/JBWS-3843 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf, jbossws-integration, ws-security > Affects Versions: jbossws-cxf-4.3.1 > Environment: JBoss EAP 6.3.1 > Reporter: Mustafa Musaji > Fix For: jbossws-cxf-5.0 > > Attachments: javaee-ws-with-security_1413372207000.zip > > > EJB3 Web Service using username token for authentication fails when you load test it with parallel invocations. See attached reproducer. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3842) InjectionException: Value already set for this injector

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3842?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3842: ----------------------------------------------- Alessio Soldano <asoldano(a)redhat.com> changed the Status of [bug 1153954|https://bugzilla.redhat.com/show_bug.cgi?id=1153954] from NEW to ASSIGNED > InjectionException: Value already set for this injector > ------------------------------------------------------- > > Key: JBWS-3842 > URL: https://issues.jboss.org/browse/JBWS-3842 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.3 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3.2, jbossws-cxf-5.0 > > > Commit https://github.com/wildfly/wildfly/commit/e32f27d433ad3da41ef042f1ad9b950... introduced a regressions when having multiple handlers in the same handler-chain within one of the pre-defined configuration in the webservices subsystem: > {noformat} > 5:49:24,653 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.ws.endpoint-config.Recording-Endpoint-Config.pre-handler-chain.recording-handlers: org.jboss.msc.service.StartException in service jboss.ws.endpoint-config.Recording-Endpoint-Config.pre-handler-chain.recording-handlers: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60] > Caused by: org.jboss.msc.inject.InjectionException: Value already set for this injector > at org.jboss.msc.inject.RetainingInjector.inject(RetainingInjector.java:50) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.as.webservices.dmr.ListInjector.inject(ListInjector.java:23) > at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1672) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl.access$2000(ServiceControllerImpl.java:51) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1917) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1876) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] > ... 3 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 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 October 2014