January 2015 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3865) Add ability to consume jboss-webservices.xml located in META-INF of EAR archive

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3865?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3865: ---------------------------------- Fix Version/s: jbossws-cxf-5.0 > Add ability to consume jboss-webservices.xml located in META-INF of EAR archive > ------------------------------------------------------------------------------- > > Key: JBWS-3865 > URL: https://issues.jboss.org/browse/JBWS-3865 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Reporter: Rostislav Svoboda > Fix For: jbossws-cxf-5.0 > > > Motivation from IRC chat: > <rsvoboda> asoldano, ping > <asoldano> rsvoboda, pong > <rsvoboda> asoldano, Hi Alessio, my colleague asked me if it's possible to add jboss-webservices.xml into META-INF in ear ... to avoid duplication in WEB-INF for more war archive ... I'm not sure we support this > <rsvoboda> asoldano, he is interested in https://docs.jboss.org/author/display/JBWS/Apache+CXF+integration#ApacheC... > <asoldano> rsvoboda, mmh... I think that's not going to work atm, but he can create a jira and we can evaluate feasibility > <rsvoboda> asoldano, ok, he did some experiments and properties defined in META-INF weren't propagated ... and I wasn't sure we even support it :) > <asoldano> rsvoboda, when we added the jboss-webservices.xml we didn't even think about ears ;) > I think reflecting jboss-webservices.xml located in META-INF of EAR archive is "enterprise feature" we should consider. > There is open question what to do when warXY included in EAR contains jboss-webservices.xml too... > - accept only properties defined in jboss-webservices.xml from META-INF of EAR archive > - accept only properties defined in jboss-webservices.xml from WEB-INF of warXY archive > - merge properties defined in jboss-webservices.xml from both location (sub-archive jboss-webservices.xml overrides properties defined in EAR) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3865) Add ability to consume jboss-webservices.xml located in META-INF of EAR archive

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created JBWS-3865: --------------------------------------- Summary: Add ability to consume jboss-webservices.xml located in META-INF of EAR archive Key: JBWS-3865 URL: https://issues.jboss.org/browse/JBWS-3865 Project: JBoss Web Services Issue Type: Feature Request Components: jbossws-cxf Reporter: Rostislav Svoboda Motivation from IRC chat: <rsvoboda> asoldano, ping <asoldano> rsvoboda, pong <rsvoboda> asoldano, Hi Alessio, my colleague asked me if it's possible to add jboss-webservices.xml into META-INF in ear ... to avoid duplication in WEB-INF for more war archive ... I'm not sure we support this <rsvoboda> asoldano, he is interested in https://docs.jboss.org/author/display/JBWS/Apache+CXF+integration#ApacheC... <asoldano> rsvoboda, mmh... I think that's not going to work atm, but he can create a jira and we can evaluate feasibility <rsvoboda> asoldano, ok, he did some experiments and properties defined in META-INF weren't propagated ... and I wasn't sure we even support it :) <asoldano> rsvoboda, when we added the jboss-webservices.xml we didn't even think about ears ;) I think reflecting jboss-webservices.xml located in META-INF of EAR archive is "enterprise feature" we should consider. There is open question what to do when warXY included in EAR contains jboss-webservices.xml too... - accept only properties defined in jboss-webservices.xml from META-INF of EAR archive - accept only properties defined in jboss-webservices.xml from WEB-INF of warXY archive - merge properties defined in jboss-webservices.xml from both location (sub-archive jboss-webservices.xml overrides properties defined in EAR) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3859) Create WildFly 8.2 ASIL

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3859?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3859: --------------------------------------- Task completed on arquillian branch, waiting for the branch to be merged to trunk. > Create WildFly 8.2 ASIL > ----------------------- > > Key: JBWS-3859 > URL: https://issues.jboss.org/browse/JBWS-3859 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > We need a proper integration layer for WildFly 8.2 too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3859) Create WildFly 8.2 ASIL

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3859?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3859: ---------------------------------- Assignee: Alessio Soldano > Create WildFly 8.2 ASIL > ----------------------- > > Key: JBWS-3859 > URL: https://issues.jboss.org/browse/JBWS-3859 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > We need a proper integration layer for WildFly 8.2 too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3860) Require JDK 1.7+ for building JBossWS

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3860?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3860: ---------------------------------- Description: It's definitely time to require at least JDK 1.7 for building JBossWS. > Require JDK 1.7+ for building JBossWS > ------------------------------------- > > Key: JBWS-3860 > URL: https://issues.jboss.org/browse/JBWS-3860 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > It's definitely time to require at least JDK 1.7 for building JBossWS. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3860) Require JDK 1.7+ for building JBossWS

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3860?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3860: ---------------------------------- Environment: (was: It's definitely time to require at least JDK 1.7 for building JBossWS.) > Require JDK 1.7+ for building JBossWS > ------------------------------------- > > Key: JBWS-3860 > URL: https://issues.jboss.org/browse/JBWS-3860 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3838?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3838: ----------------------------------------------- Jan Blizňák <jbliznak(a)redhat.com> changed the Status of [bug 1157610|https://bugzilla.redhat.com/show_bug.cgi?id=1157610] from ON_QA to VERIFIED > 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.0.Beta2 > > > 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.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3847) Memory leak in JBoss WS CXF Client's HandlerChainSortInterceptor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3847?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3847: ----------------------------------------------- Rostislav Svoboda <rsvoboda(a)redhat.com> changed the Status of [bug 1158330|https://bugzilla.redhat.com/show_bug.cgi?id=1158330] from ON_QA to VERIFIED > Memory leak in JBoss WS CXF Client's HandlerChainSortInterceptor > ---------------------------------------------------------------- > > Key: JBWS-3847 > URL: https://issues.jboss.org/browse/JBWS-3847 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3 > Reporter: Tadayoshi Sato > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3.2, jbossws-cxf-5.0.0.Beta2 > > > {{HandlerChainSortInterceptor.handleMessage(Message)}} sorts and sets JAX-WS handlers every time it handles a SOAP message: > {code:java} > public void handleMessage(Message message) throws Fault > { > if (binding != null) { > @SuppressWarnings("rawtypes") > List<Handler> list = binding.getHandlerChain(); > if (list != null && !list.isEmpty()) { > Collections.sort(list, comparator); > binding.setHandlerChain(list); > } > } > } > {code} > However, inside the {{org.apache.cxf.jaxws.binding.AbstractBindingImpl}} and {{org.apache.cxf.jaxws.support.JaxWsEndpointImpl}} implementations the handler chain is not reset every time but piled up with interceptors, which leads to subtle but indefinite memory leak in JBoss WS CXF client. > Furthermore, {{org.apache.cxf.jaxws.support.JaxWsEndpointImpl}} holds the interceptors as a kind of {{java.util.concurrent.CopyOnWriteArrayList}}. So modifying the growing list of interceptors per each message should cause a growing performance drawback, which is also not a good implementation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3842?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3842: ----------------------------------------------- Jan Blizňák <jbliznak(a)redhat.com> changed the Status of [bug 1157607|https://bugzilla.redhat.com/show_bug.cgi?id=1157607] from ON_QA to VERIFIED > 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.0.Beta2 > > > 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.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3854) EndpointConfigAdd does not set required PropertyService dependencies

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3854?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3854: ----------------------------------------------- Jan Blizňák <jbliznak(a)redhat.com> changed the Status of [bug 1173763|https://bugzilla.redhat.com/show_bug.cgi?id=1173763] from ON_QA to VERIFIED > EndpointConfigAdd does not set required PropertyService dependencies > -------------------------------------------------------------------- > > Key: JBWS-3854 > URL: https://issues.jboss.org/browse/JBWS-3854 > 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-5.0 > > > In the container integration, the EndpointConfigAdd operation is not setting PropertyService dependencies on ConfigService created for endpoints. That can result in properties being lost. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 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 January 2015