November 2007 - jbossws-dev - Jboss List Archives

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

by mark.little＠jboss.com

One last question: was this a change between the previous official release (CP1)? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104585#4104585 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104585

16 years, 6 months

1
0
0 / 0

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

by mark.little＠jboss.com

OK, in which case there is no problem after all! Phew! ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104582#4104582 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104582

16 years, 6 months

1
0
0 / 0

Re: Cannot lookup ejb3 remote proxy

by Thomas Diesler

You could start by reading the jira comments ;-) It sais Tests may be excluded from the compile target by the exclude file https://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-... This allows us to detect regression and have a unified testsuite across all supported containers You will need to comment the exclude before you run tests-main cheers -thomas On Tue, 2007-11-13 at 14:11 +0100, Carlo de Wolf wrote: > How do I run this test? > > I already did a 'ant' & 'ant jars' > > Carlo > > carlo@alien:~/work/jbossws-native-2.0.2$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase one-test > Buildfile: build.xml > > prepare: > > thirdparty-init: > [echo] checksum.ok = true > > thirdparty-get: > > thirdparty-classpath: > > tests-prepare: > > [echo] ----------------------------------------------- > [echo] jboss.home = /home/carlo/work/jboss-head/build/output/jboss-5.0.0.Beta3 > [echo] excludesfile = /home/carlo/work/jbossws-native-2.0.2/src/test/resources/test-excludes-jboss500.txt > [echo] java.home = /opt/jdk1.5.0_11/jre > [echo] jboss.bind = localhost > [echo] ----------------------------------------------- > > tests-classpath-jboss50: > > tests-classpath-jboss42: > > tests-classpath-jboss40: > > tests-classpath-jboss40-no-ejb3: > > tests-classpath: > > tests-init: > > one-test: > [junit] Running org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase > [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec > [junit] Test org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase FAILED > > BUILD SUCCESSFUL > Total time: 1 second > carlo@alien:~/work/jbossws-native-2.0.2$ cat output/tests/reports/TEST-org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase.txt > Testsuite: org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase > Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec > > Caused an ERROR > org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase > java.lang.ClassNotFoundException: org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase > at java.net.URLClassLoader$1.run(URLClassLoader.java:200) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) > at java.lang.ClassLoader.loadClass(ClassLoader.java:251) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:164) > > On Tue, 2007-11-13 at 12:09 +0100, Thomas Diesler wrote: > > Hi Carlo, > > > > could you please comment on > > > > Cannot lookup ejb3 remote proxy > > http://jira.jboss.com/jira/browse/JBAS-4930 > > > > cheers > > -thomas > > > -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

16 years, 6 months

1
0
0 / 0

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

by thomas.diesler＠jboss.com

anonymous wrote : | Are you sure this was not in 2.0.0GA ;-)? | yes very much so anonymous wrote : | Did this change between 2.0.1GA and the CP? | Not at all View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104581#4104581 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104581

16 years, 6 months

1
0
0 / 0

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

by mark.little＠jboss.com

Did this change between 2.0.1GA and the CP? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104575#4104575 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104575

16 years, 6 months

1
0
0 / 0

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

by mark.little＠jboss.com

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 ;-)? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104572#4104572 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104572

16 years, 6 months

1
0
0 / 0

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

by thomas.diesler＠jboss.com

anonymous wrote : | What is the problem with adding jbossws-spi-1.0.0GA and maintaining backward compatibility with JBossWS 2.0.0GA? | 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 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104569#4104569 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104569

16 years, 6 months

1
0
0 / 0

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

by mark.little＠jboss.com

Thomas, thanks for putting this into the forums but can you please expend effort on resolving the issue? We can make sure it is documented in the forums afterwards. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104568#4104568 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104568

16 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Missing BasicInvocationContext class

by thomas.diesler＠jboss.com

Thomas Diesler [14/Nov/07 06:35 AM] As of jbossws-spi-1.0.0, you should be using org.jboss.wsf.spi.invocation.InvocationContext Mark Little [14/Nov/07 06:44 AM] Thomas, unless this was previously documented as a non-public API then it cannot be removed in the 2.0.x codebase. You can support it elsewhere, but you need to be backwardly compatible. Thanks. Thomas Diesler [14/Nov/07 07:01 AM] jbossws-2.0.1 was the first release that used jbossws-spi-1.0.0.GA as a standalone project. Before that the SPI was still work in progress and an integral part of the jbossws core code base. I understand your backward compatibility concerns and yes, everything in jbossws-spi-1.0.0.GA is public and can be used (from that release onward) I hope we can resolve possible API/SPI incompatibility issues between 2.0.0 and 2.0.1 in an unbureaucratic way and jbossws-spi-1.0.0.GA can be our baseline to move forward Alternatively, we would need to create a SP branch for jbossws-spi-1.0.0 where we restore the API that the ESB is using. For many a reason I would recommend the ESB uses the 1.0.0.GA SPI/API Mark Little [14/Nov/07 08:26 AM] Thomas, this isn't bureaucratic: we have a message around the platforms that there will be no backward compatibility issues within minor version numbers of the individual projects. Unless you made this change because of a bug, then this has to be changed as well. If something was available in JBossWS 2.0.0GA it needs to continue to be available in JBossWS 2.0.1GA and CPs. We've been over this before and if the other projects can work within this approach I'd expect the same from your project. What is the problem with adding jbossws-spi-1.0.0GA and maintaining backward compatibility with JBossWS 2.0.0GA? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104564#4104564 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104564

16 years, 6 months

1
0
0 / 0

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

by mark.little＠jboss.com

What is the conclusion? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104554#4104554 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104554

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