March 2008 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: Dependency on container configurations and JBWS-1992

by thomas.diesler＠jboss.com

Generally, the container integration lives with the container | Branch_4_2 | |_ webservice | | trunk | |_ webservice | If we have an issue with the container integration it should be fixed there in a compatible way with already released containers. Then it should be made available in the repository for WS stack consumption and finally must be deployed to all containers were it applies. i.e. When you remove the WSEndpointRegistry from all stacks you must make sure that you deploy compatible container integration jars/resources to all supported containers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137689#4137689 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137689

16 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Dependency on container configurations and JBWS-1992

by richard.opalka＠jboss.com

In other words we could have correct solution for all 4.2.x servers, 5 CR1 server and ugly hack for AS 5 Beta 4 (which could be removed in the future when Beta4 will become unsupported) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137681#4137681 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137681

16 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Dependency on container configurations and JBWS-1992

by richard.opalka＠jboss.com

I know, what I intended is if it's possible to create some ugly hack for AS Beta4 only that could be removed in the future when Beta 4 will become unsupported ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137679#4137679 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137679

16 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Dependency on container configurations and JBWS-1992

by alessio.soldano＠jboss.com

"richard.opalka(a)jboss.com" wrote : "alessio.soldano(a)jboss.com" wrote : This however proved not to be a valid solution for some reasons, the most important being that even if I can manage to fix the 4.2 integration, JBoss 5.0.0 Beta4 is already out and its jbossws-deployer-beans.xml config cannot be easily modified. Therefore I would say that we can't easily have the correct dependency of WSEndpointRegistryDeploymentAspect on the WSEndpointRegistry bean, since we can't change the configuration that declares it. | | I think it's correct solution, the question is if we will support AS 5 Beta 4 when AS CR1 will be out. I think we will not support it. Hi Richard, apart from the fact that this solution has other problem (see http://fisheye.jboss.com/changelog/JBossWS/?cs=6012), AS 5 beta4 is a target container righ now, so imho we have to support it, even if CR1 will be out at some point in the future. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137676#4137676 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137676

16 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Dependency on container configurations and JBWS-1992

by richard.opalka＠jboss.com

"alessio.soldano(a)jboss.com" wrote : This however proved not to be a valid solution for some reasons, the most important being that even if I can manage to fix the 4.2 integration, JBoss 5.0.0 Beta4 is already out and its jbossws-deployer-beans.xml config cannot be easily modified. Therefore I would say that we can't easily have the correct dependency of WSEndpointRegistryDeploymentAspect on the WSEndpointRegistry bean, since we can't change the configuration that declares it. I think it's correct solution, the question is if we will support AS 5 Beta 4 when AS CR1 will be out. I think we will not support it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137655#4137655 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137655

16 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Dependency on container configurations and JBWS-1992

by alessio.soldano＠jboss.com

I'm posting here to keep track of what happened. I tried moving the WSEndpointRegistry to the container configuration (at first duplicating the container config in the stacks, then manually creating a new jbossws-jboss42=4.2.3.CR1 dependency). This however proved not to be a valid solution for some reasons, the most important being that even if I can manage to fix the 4.2 integration, JBoss 5.0.0 Beta4 is already out and its jbossws-deployer-beans.xml config cannot be easily modified. Therefore I would say that we can't easily have the correct dependency of WSEndpointRegistryDeploymentAspect on the WSEndpointRegistry bean, since we can't change the configuration that declares it. On chat Thomas suggested checking for the existence of the mbeanServer before the unregister process. This would have been an idea for the first exception (ie. the one thrown by the EndpointRecordProcessorDeploymentAspect.). Speaking of the WSEndpointRegistry issue, instead, my thought is that if we can't assure the registry bean is available, then we could only handle the exception, supposing the server is shutting down, but of course this doesn't mean really solving the issue. Otherwise we can only put up with the shutdown KernelRegistryEntryNotFoundException. Do anybody have better idea than me? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137625#4137625 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137625

16 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - XmlSeeAlso

by darran.lofthouse＠jboss.com

I am just trying to find out some further information on the level of support of XmlSeeAlso for. This annotation was added to JAXB 2.1 so on a super type the sub classes can be identified and used by the JAXB context. The JAX-WS 2.1 specification allows this annotation to be added to the service endpoint interface. We have JAXB 2.1 but not JAX-WS 2.1 so I can add the annotation to a type known to JAXB but not to the SEI. The scenario I have requires this annotation to be added when using wsconsume. One of the return types being returned from my SEI wraps an Object as in the WSDL it is defined as wrapping an xsd:anyType I need the object instance assigned to this to be marshaled correctly. The only way that I have found to get round this is to extend the object that is returned from the method an annotate that with XmlSeeAlso and return an instance of this instead. Do we have any other support for XmlSeeAlso? Adding it manually to the SEI did not achieve anything? Is there any way to get wsconsume to add it to the generated classes so I don't need this workaround? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137512#4137512 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137512

16 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Interop endpoints down

by heiko.braun＠jboss.com

It's enabled for the hudson runs by default. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137439#4137439 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137439

16 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Interop endpoints down

by heiko.braun＠jboss.com

The system property -Dinterop=true forces the interop test clients to work against the pulic endpoints. | [hbraun@localhost trunk]$ ant -Dtest=org.jboss.test.ws.interop.wsa.AddressingTestCase -Dinterop=true -Ddebug=true one-test | | [junit] Tests run: 19, Failures: 0, Errors: 0, Time elapsed: 29.31 sec | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137438#4137438 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137438

16 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Interop endpoints down

by heiko.braun＠jboss.com

Right, I think the interop endpoints need to be revisited at all. I've created a JIRA for collecting issues. Monitoring is already one of them: [url] http://jira.jboss.org/jira/browse/JBWS-2068 [/url] View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137419#4137419 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137419

16 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-dev March 2008