June 2008 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: container integration naming issue

by richard.opalka＠jboss.com

Well this is a general issue that affects all AS modules that have different (shorter) lifecycle than AS as whole has. We should ask other AS folks/leads how do they plan to deal with this kind of issues in the future and if it was investigated before mavenization process. In case there will be no appropriate and correct solution to this problem our release cycle will have to follow AS release cycle what we don't want :( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157919#4157919 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157919

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: container integration naming issue

by richard.opalka＠jboss.com

"thomas.diesler(a)jboss.com" wrote : What now? Unfortunately this is the maven artifacts naming issue. AFAIK maven doesn't enable you to specify buildnumber for non-snapshot artifacts :( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157917#4157917 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157917

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: [JBWS-2187] javax.xml.ws.Service handlers and thread saf

by darran.lofthouse＠jboss.com

>From my understanding of the evolution of this API I believe that the Observer/Observable patters was used when the configuration was set on the Service rather than when it was set on the Port - as the configuration was being set on the factory for the Ports is made sense that the Ports were notified of configuration changes to update themselves. However since the change of the API to make the configuration changed on the Port I also do not see how this would be required any more. I don't think the fix is just a case of cloning the handler chain it is the whole configuration that needs to be cloned into the Port the ConfigProvider has the following properties: - - ConfigFile - ConfigName - SecurityConfig I think when a Port is created the handlers and the configuration settings should be cloned from the Service but then further changes to these values on the Port will cause the Port to 'forget' the values loaded from the Service and load them locally to the Port. The Port can still make use of methods on the Service to perform the actual loading but these need to be thread safe to cope with concurrent calls and to prevent affecting the other Port instances. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157915#4157915 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157915

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: container integration naming issue

by thomas.diesler＠jboss.com

Consider this: #1 you put the container integration in AS trunk #2 you 'mvn deploy' jbossws-jboss-5.0.0-SNAPSHOT from AS trunk #3 CR1 gets released #4 you 'mvn deploy' jbossws-jboss-5.0.0.CR1 from AS trunk #5 you work on jbossws-3.0.3 and need to update jbossws-jboss-5.0.0.CR1 What now? Heiko's naming scheme does not work because you cannot have a dependency on the same artifact with different versions | <dependency> | <groupId>org.jboss.ws</groupId> | <artifactId>jbossws-jboss</artifactId> | <version>5.0.0.Beta4</version> | </dependency> | <dependency> | <groupId>org.jboss.ws</groupId> | <artifactId>jbossws-jboss</artifactId> | <version>5.0.0.CR1</version> | </dependency> | | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157913#4157913 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157913

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Missing Stack Specific Resources Maven Artifacts

by richard.opalka＠jboss.com

Yes, we forgot on that:( To finalize this forum thread here are the associated issues: JBWS-2228 JBWS-2229 JBWS-2231 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157895#4157895 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157895

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: container integration naming issue

by richard.opalka＠jboss.com

I don't see it as a problem at least for AS trunk. As you use to say Thomas container integration resides in AS code base. I'm going to sync AS trunk today with jboss501 integration layer, thus there's no maven artifact needed for AS trunk to include our separate jboss integration layer inside. Or did I miss something? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157878#4157878 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157878

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: container integration naming issue

by heiko.braun＠jboss.com

It could simply carry the name for the container it was released (QA'd) for: jbossws-jboss-5.0.0.CR1 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157877#4157877 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157877

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - container integration naming issue

by thomas.diesler＠jboss.com

Folks, we currently use jbossws-jboss421-3.0.2-SNAPSHOT jbossws-jboss422-3.0.2-SNAPSHOT jbossws-jboss423-3.0.2-SNAPSHOT jbossws-jboss500-3.0.2-SNAPSHOT jbossws-jboss501-3.0.2-SNAPSHOT This works on the premisses that jboss500 == jboss-5.0.0.Beta4 jboss501 == jboss-5.0.0.CR1 The naming scheme will however fail when CR1 gets released and container integration moves on towards CR2 or GA. It will also fail for jboss-4.2.2.SP1, etc More generally, this naming scheme does not support multiple versions for the same AS minor version. To fix this, we would need to factor the AS version into the naming scheme. Possibly like jbossws-jboss-5.0.0.Beta4-3.0.2-SNAPSHOT jbossws-jboss-5.0.0.CR1-3.0.2-SNAPSHOT This scheme would obviously support a matrix of multiple container versions against multiple jbossws versions, which is required according to http://jbws.dyndns.org/mediawiki/index.php?title=Supported_Target_Containers The above suggestion however fails, because maven does not support dependencies with multiple versions on the same artifact. Thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157876#4157876 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157876

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS4EE and AS5

by anil.saldhana＠jboss.com

| 15:29:39,695 WARN [MainDeployer] undeploy 'file:/home/anil/jboss-5.0/jboss-head/testsuite/output/lib/ws4ee-jbws309.jar' : package not deployed | 15:29:39,695 INFO [MainDeployer] deploy, url=file:/home/anil/jboss-5.0/jboss-head/testsuite/output/lib/ws4ee-jbws309.jar | 15:29:40,269 WARN [CollectionPropertyHandler] ClassInfo.getDeclaredConstructor(null) didn't work for org.jboss.metadata.ejb.spec.InterceptorClassesMetaData, found the default ctor in ClassInfo.getDeclaredConstructors() | 15:29:41,231 INFO [EjbDeployer] installing bean: ejb/#BasicSecuredSLSB,uid1353625448 | 15:29:41,231 INFO [EjbDeployer] with dependencies: | 15:29:41,231 INFO [EjbDeployer] and supplies: | 15:29:41,231 INFO [EjbDeployer] jndi:ejb/BasicSecuredSLSB | 15:29:41,231 INFO [EjbDeployer] installing bean: ejb/#RoleSecuredSLSB,uid644541754 | 15:29:41,232 INFO [EjbDeployer] with dependencies: | 15:29:41,232 INFO [EjbDeployer] and supplies: | 15:29:41,232 INFO [EjbDeployer] jndi:ejb/RoleSecuredSLSB | 15:29:41,374 INFO [DefaultEndpointRegistry] register: jboss.ws:context=ws4ee-jbws309,endpoint=RoleSecuredSLSB | 15:29:41,377 INFO [DefaultEndpointRegistry] register: jboss.ws:context=ws4ee-jbws309,endpoint=BasicSecuredSLSB | 15:29:41,954 INFO [WSDLFilePublisher] WSDL published to: file:/home/anil/jboss-5.0/jboss-head/build/output/jboss-5.0.0.CR1/server/jacc/data/wsdl/ws4ee-jbws309.jar/OrganizationService.wsdl | 15:29:42,134 INFO [EjbModule] Deploying BasicSecuredSLSB | 15:29:42,283 INFO [EjbModule] Deploying RoleSecuredSLSB | 15:29:42,443 INFO [ProxyFactory] Bound EJB Home 'BasicSecuredSLSB' to jndi 'ejb/BasicSecuredSLSB' | 15:29:42,454 INFO [ProxyFactory] Bound EJB Home 'RoleSecuredSLSB' to jndi 'ejb/RoleSecuredSLSB' | 15:29:42,460 INFO [TomcatDeployment] deploy, ctxPath=/ws4ee-jbws309, vfsUrl= | 15:29:42,478 WARN [config] Unable to process deployment descriptor for context '/ws4ee-jbws309' | 15:29:43,351 WARN [MainDeployer] undeploy 'file:/home/anil/jboss-5.0/jboss-head/testsuite/output/lib/ws4ee-jbws309-client.jar' : package not deployed | 15:29:43,352 INFO [MainDeployer] deploy, url=file:/home/anil/jboss-5.0/jboss-head/testsuite/output/lib/ws4ee-jbws309-client.jar | 15:29:43,564 INFO [NativeServiceRefBinderJAXRPC] setupServiceRef [jndi=ws4ee-client/env/service/BasicSecured] | 15:29:43,578 INFO [NativeServiceRefBinderJAXRPC] setupServiceRef [jndi=ws4ee-client/env/service/RoleSecured] | 15:29:43,581 INFO [JBossASKernel] Created KernelDeployment for: ws4ee-jbws309-client.jar | 15:29:43,587 INFO [JBossASKernel] installing bean: jboss.j2ee:jar=ws4ee-jbws309-client.jar,name=ws4ee-client,service=EJB3 | 15:29:43,587 INFO [JBossASKernel] with dependencies: | 15:29:43,587 INFO [JBossASKernel] and demands: | 15:29:43,588 INFO [JBossASKernel] and supplies: | 15:29:43,588 INFO [JBossASKernel] Added bean(jboss.j2ee:jar=ws4ee-jbws309-client.jar,name=ws4ee-client,service=EJB3) to KernelDeployment of: ws4ee-jbws309-client.jar | 15:29:43,635 INFO [ClientENCInjectionContainer] STARTED CLIENT ENC CONTAINER: ws4ee-client | 15:29:45,646 INFO [ClientENCInjectionContainer] STOPPED CLIENT ENC CONTAINER: ws4ee-client | 15:29:45,703 INFO [TomcatDeployment] undeploy, ctxPath=/ws4ee-jbws309, vfsUrl= | 15:29:45,731 INFO [ProxyFactory] Unbind EJB Home 'RoleSecuredSLSB' from jndi 'ejb/RoleSecuredSLSB' | 15:29:45,733 INFO [EjbModule] Undeployed RoleSecuredSLSB | 15:29:45,736 INFO [ProxyFactory] Unbind EJB Home 'BasicSecuredSLSB' from jndi 'ejb/BasicSecuredSLSB' | 15:29:45,740 INFO [EjbModule] Undeployed BasicSecuredSLSB | 15:29:45,751 INFO [DefaultEndpointRegistry] remove: jboss.ws:context=ws4ee-jbws309,endpoint=RoleSecuredSLSB | 15:29:45,766 INFO [DefaultEndpointRegistry] remove: jboss.ws:context=ws4ee-jbws309,endpoint=BasicSecuredSLSB | As you can see, I am not sure if Tomcat is really deploying the ws4ee-jbws309.war properly View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157813#4157813 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157813

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - WS4EE and AS5

by anil.saldhana＠jboss.com

I am trying to understand how JBossWS handles WS4EE for AS5. In the AS5 test suite, there is a test called as "org.jboss.test.webservice.jbws309.JBWS309TestCase". Now if you try to run this test against AS5 (no need for JACC configuration etc), I see that JBossWS is trying to deploy a web application for ejb based WS. This web application would be the entry point for the WS apps. Do you still dynamically generate the web.xml/jboss-web.xml? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157811#4157811 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157811

17 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev June 2008