November 2007 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: Missing BasicInvocationContext class

by mark.little＠jboss.com

This shows the version was 1.2.1, so we're safe, i.e., no issue with EAP. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104647#4104647 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104647

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Missing BasicInvocationContext class

by mark.little＠jboss.com

OK, so the disconnect may be on my side. I was under the impression that JBossAS 4.2.1 used JBossWS 2.0.0GA, but that may be wrong. If it was an earlier version of JBossWS then there is no problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104645#4104645 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104645

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: jUDDI tables dropped at server shutdown

by Kevin.Conner＠jboss.com

Just to clarify, this is also a problem in the 'production' profile of the SOA platform. This is why Trev needs to know how to tidy this up. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104607#4104607 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104607

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Missing BasicInvocationContext class

by mark.little＠jboss.com

Yes, but if it was a public API then it has clearly changed between 2.0.0 and 2.0.1. Unless it was marked as a "technology preview" or "unofficial release" or something like that, we now have users who are potentially using this SPI that has changed. You cannot go changing public interfaces like this in minor releases. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104604#4104604 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104604

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: jUDDI tables dropped at server shutdown

by kurt.stam＠jboss.com

This is only a problem in the 'all' profile of JBossAS, where AS ships the juddi.sar. From an ESB perspective this should get removed, and we should deploy our juddi.war by default into the jbossesb.sar to bring up the juddi WSs. We *should* not break anything by doing that, but it would be nice if Thomas can tell us what to do to proof this out. --Kurt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104598#4104598 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104598

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Missing BasicInvocationContext class

by heiko.braun＠jboss.com

With 2.0.0 the SPI did inherit the version from the core code base, because it wasn't released as a standalone binary. This changed with jboss native 2.0.1, which is using the SPI 1.0.0.GA. The SPI shipped with the 2.0.0 code base was actually some 0.x.CR release. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104597#4104597 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104597

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Missing BasicInvocationContext class

by mark.little＠jboss.com

Well that's kind of what I'm pushing towards. AFAICT it was there in 2.0.0GA. Unless it was documented as a work in progress then it cannot be changed because it is a public SPI. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104591#4104591 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104591

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Missing BasicInvocationContext class

by Kevin.Conner＠jboss.com

"thomas.diesler(a)jboss.com" wrote : The problem is that jbossws-spi-1.0.0.GA is the first release of our SPI, which was not available with jbossws-2.0.0.GA. Hence the ESB has been using a "work in progress" SPI prior to jbossws-2.0.1.GA | What is the version of jbossws-spi which is included in 2.0.0 in that case? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104590#4104590 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104590

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Missing BasicInvocationContext class

by Kevin.Conner＠jboss.com

"mark.little(a)jboss.com" wrote : Ah, OK. I assumed that this was capability in 2.0.0GA and now missing. Are you sure this was not in 2.0.0GA ;-)? So that won't be the class found in jbossws-spi.jar in the 2.0.0 downloads then ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104589#4104589 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104589

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Missing BasicInvocationContext class

by mark.little＠jboss.com

Another question: the SPI that ESB was using was available in 2.0.0GA, correct? If so, was it clearly marked as a work in progress? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104588#4104588 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104588

16 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-dev November 2007