RE: [JBoss-dev] Head testsuite compile errors
Scott, Bela is in the middle check in some codes. I have left him a message. Thanks, -Ben -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Monday, November 24, 2003 3:58 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] Head testsuite compile errors The jboss-head/testsuite is not compiling due to the following errors: [javac] /cvs/JBossHead/jboss-head/testsuite/src/main/org/jboss/test/cache/bean/T reeCacheTesterBean.java:118: incompatible types [javac] found : java.lang.String [javac] required: int [javac] return cache.getCacheMode(); [javac] ^ [javac] /cvs/JBossHead/jboss-head/testsuite/src/main/org/jboss/test/cache/bean/T reeCacheTesterBean.java:151: incompatible types [javac] found : java.lang.String [javac] required: int [javac] return cache.getLockingLevel(); -- Scott Stark Chief Technology Officer JBoss Group, LLC --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] 3.2.3 Release is due this weekend
Please make sure that the 3.2 branch is stable by the Thu-Fri timeframe so that I can put together the 3.2.3 release this weekend. -- Scott Stark Chief Technology Officer JBoss Group, LLC --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Head testsuite compile errors
The jboss-head/testsuite is not compiling due to the following errors: [javac] /cvs/JBossHead/jboss-head/testsuite/src/main/org/jboss/test/cache/bean/TreeCacheTesterBean.java:118: incompatible types [javac] found : java.lang.String [javac] required: int [javac] return cache.getCacheMode(); [javac] ^ [javac] /cvs/JBossHead/jboss-head/testsuite/src/main/org/jboss/test/cache/bean/TreeCacheTesterBean.java:151: incompatible types [javac] found : java.lang.String [javac] required: int [javac] return cache.getLockingLevel(); -- Scott Stark Chief Technology Officer JBoss Group, LLC --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Sampiyonlar Ligi heyecani tum hiziyla devam ediyor!!!
Title: Sampiyonlar Ligi heyecani tum hiziyla devam ediyor!!! Bahisnette Oyna Kazan! ŞAMPİYONLAR LİGİNDE Anderlecht-Lyon Celtic-Bayern Internazionale-Arsenal Lokomotiv Moskova-Dynamo Kyiv Deportivo-AEK Monaco-PSV Olympiyakos-Real Sociedad maclarının oranları BAHİSNET ile OYNAYIN KAZANIN!!! Bizden mail almak istemiyorsanız lutfen buraya tıklayınız.
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
Mon Nov 24 22:54:35 GMT 2003
===
HERE ARE THE LAST 100 LINES OF THE LOG:
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/classloader/circularity/test/CircularityErrorTests.java:40:
warning: org.jboss.mx.loading.UnifiedLoaderRepository2 in org.jboss.mx.loading has
been deprecated
[javac] UnifiedLoaderRepository2 repository = new UnifiedLoaderRepository2();
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/DurableSubscriberTest.java:77:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/DurableSubscriberTest.java:121:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/DurableSubscriberTest.java:143:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/DurableSubscriberTest.java:161:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/ExceptionListenerTest.java:63:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:111:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:113:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:168:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:170:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MassiveTest.java:75:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MassiveTest.java:129:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MassiveTest.java:133:
warning: stop() in java.lang.Thread has been deprecated
[javac] tf.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:74:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:116:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:100:
warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
[javac] SSLContext sslCtx = null;
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:103:
warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
[javac] sslCtx = SSLContext.getInstance("TLS");
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
Mon Nov 24 22:42:16 GMT 2003
===
HERE ARE THE LAST 100 LINES OF THE LOG:
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/classloader/circularity/test/CircularityErrorTests.java:40:
warning: org.jboss.mx.loading.UnifiedLoaderRepository2 in org.jboss.mx.loading has
been deprecated
[javac] UnifiedLoaderRepository2 repository = new UnifiedLoaderRepository2();
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/DurableSubscriberTest.java:77:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/DurableSubscriberTest.java:121:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/DurableSubscriberTest.java:143:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/DurableSubscriberTest.java:161:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/ExceptionListenerTest.java:63:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:111:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:113:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:168:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:170:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MassiveTest.java:75:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MassiveTest.java:129:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MassiveTest.java:133:
warning: stop() in java.lang.Thread has been deprecated
[javac] tf.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:74:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:116:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:100:
warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
[javac] SSLContext sslCtx = null;
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:103:
warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
[javac] sslCtx = SSLContext.getInstance("TLS");
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/winxp/1.4.2_01) [AUTOMATED]
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
Mon Nov 24 22:39:50 GMTST 2003
===
HERE ARE THE LAST 100 LINES OF THE LOG:
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\classloader\circularity\test\CircularityErrorTests.java:40:
warning: org.jboss.mx.loading.UnifiedLoaderRepository2 in org.jboss.mx.loading has
been deprecated
[javac] UnifiedLoaderRepository2 repository = new UnifiedLoaderRepository2();
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:77:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:121:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:143:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:161:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\ExceptionListenerTest.java:63:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:75:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:129:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:133:
warning: stop() in java.lang.Thread has been deprecated
[javac] tf.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:111:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:113:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:168:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:170:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:74:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:116:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:100:
warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
[javac] SSLContext sslCtx = null;
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:103:
warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
[javac] sslCtx = SSLContext.getInstance("TLS");
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:112:
warning: com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been deprecated
[javac]
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/winxp/1.4.1_05) [AUTOMATED]
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
Mon Nov 24 22:30:47 GMTST 2003
===
HERE ARE THE LAST 100 LINES OF THE LOG:
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\classloader\circularity\test\CircularityErrorTests.java:40:
warning: org.jboss.mx.loading.UnifiedLoaderRepository2 in org.jboss.mx.loading has
been deprecated
[javac] UnifiedLoaderRepository2 repository = new UnifiedLoaderRepository2();
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:77:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:121:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:143:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:161:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\ExceptionListenerTest.java:63:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:75:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:129:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:133:
warning: stop() in java.lang.Thread has been deprecated
[javac] tf.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:111:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:113:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:168:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:170:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:74:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:116:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:100:
warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
[javac] SSLContext sslCtx = null;
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:103:
warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
[javac] sslCtx = SSLContext.getInstance("TLS");
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:112:
warning: com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been deprecated
[javac]
[JBoss-dev] Re: [ANN] JBoss-IDE 1.2.2 released
Hi, I have made some rough testing on Eclipse 3.0.0 M5, and it looks good. Any feedback would be appreciated if not. Laurent. "Laurent Etiemble" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > Damn, it's going too fast for me !!! > > The 1.2.2 is out since the 9 of Novemeber (unofficially). I have just finish > to update the doco and made an official release yesterday. > > Since they have announced an API freeze for M4, it should work on M5. I will > make some tests. > > Laurent. > > "Ricardo Argüello" <[EMAIL PROTECTED]> wrote in message > news:<[EMAIL PROTECTED]>... > Doesn't it work with recently released Eclipse M5? > > Ricardo Argüello > > Laurent Etiemble wrote: > > > Hi, > > > > The JBoss-IDE 1.2.2 release is available. It is a maintenance release > which > > addresses many bugs. See release notes for more details : > > https://sourceforge.net/project/shownotes.php?release_id=199388 > > > > Available releases are : > > - JBoss-IDE 1.2.2 for Eclipse 2.1.1 or higher > > - JBoss-IDE 1.2.2330 for Eclipes 3.0.0M4 > > > > There is no more bundle available for download. All installation/upgrade > > must be done through the Eclipse install/update manager. See the > > documentation for that. > > > > Available documentation are : > > - Installation Guide : contains all you need to install/upgrade JBoss-IDE > > http://prdownloads.sourceforge.net/jboss/Install-1.2.2.pdf?download > > - Quick Start Guide : provides an overview of what brings JBoss-IDE > > http://prdownloads.sourceforge.net/jboss/QuickStart-1.2.2.pdf?download > > - Tutorial Guide : provides a tutorial to explore some features of > JBoss-IDE > > http://prdownloads.sourceforge.net/jboss/Tutorial-1.2.2.pdf?download > > > > Bugs can be reported here (don't forget to put everything needed to help) > : > > https://sourceforge.net/tracker/?group_id=22866&atid=376685 > > > > Any feedback can be posted through the JBoss Forums (don't forget to put > > everything needed to help) : > > http://www.jboss.org/forum.jsp?forum=162 > > > > Enjoy and code. > > > > > > Laurent Etiemble, > > JBoss-IDE project lead. > > > > > > > > --- > > This SF.net email is sponsored by: SF.net Giveback Program. > > Does SourceForge.net help you be more productive? Does it > > help you create better code? SHARE THE LOVE, and help us help > > YOU! Click Here: http://sourceforge.net/donate/ > > ___ > > JBoss-Development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > -- > > > Ricardo Argüello > [EMAIL PROTECTED] > www.ndeveloper.com > > > > --- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > -- > > > > --- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/linux1/1.4.2_01) [AUTOMATED]
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
Mon Nov 24 19:57:09 GMT 2003
===
HERE ARE THE LAST 100 LINES OF THE LOG:
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/classloader/circularity/test/CircularityErrorTests.java:40:
warning: org.jboss.mx.loading.UnifiedLoaderRepository2 in org.jboss.mx.loading has
been deprecated
[javac] UnifiedLoaderRepository2 repository = new UnifiedLoaderRepository2();
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/DurableSubscriberTest.java:77:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/DurableSubscriberTest.java:121:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/DurableSubscriberTest.java:143:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/DurableSubscriberTest.java:161:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/ExceptionListenerTest.java:63:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:111:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:113:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:168:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:170:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MassiveTest.java:75:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MassiveTest.java:129:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MassiveTest.java:133:
warning: stop() in java.lang.Thread has been deprecated
[javac] tf.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:74:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:116:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:100:
warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
[javac] SSLContext sslCtx = null;
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:103:
warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
[javac] sslCtx = SSLContext.getInstance("TLS");
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/winxp/1.4.1_05) [AUTOMATED]
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
Mon Nov 24 19:36:20 GMTST 2003
===
HERE ARE THE LAST 100 LINES OF THE LOG:
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\classloader\circularity\test\CircularityErrorTests.java:40:
warning: org.jboss.mx.loading.UnifiedLoaderRepository2 in org.jboss.mx.loading has
been deprecated
[javac] UnifiedLoaderRepository2 repository = new UnifiedLoaderRepository2();
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:77:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:121:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:143:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:161:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\ExceptionListenerTest.java:63:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:75:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:129:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:133:
warning: stop() in java.lang.Thread has been deprecated
[javac] tf.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:111:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:113:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:168:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:170:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:74:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:116:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:100:
warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
[javac] SSLContext sslCtx = null;
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:103:
warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
[javac] sslCtx = SSLContext.getInstance("TLS");
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:112:
warning: com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been deprecated
[javac]
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/winxp/1.4.2_01) [AUTOMATED]
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
Mon Nov 24 19:45:20 GMTST 2003
===
HERE ARE THE LAST 100 LINES OF THE LOG:
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\classloader\circularity\test\CircularityErrorTests.java:40:
warning: org.jboss.mx.loading.UnifiedLoaderRepository2 in org.jboss.mx.loading has
been deprecated
[javac] UnifiedLoaderRepository2 repository = new UnifiedLoaderRepository2();
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:77:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:121:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:143:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\DurableSubscriberTest.java:161:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\ExceptionListenerTest.java:63:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:75:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:129:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MassiveTest.java:133:
warning: stop() in java.lang.Thread has been deprecated
[javac] tf.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:111:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:113:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:168:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\MultipleDurableSubscribers.java:170:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:74:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\jbossmq\stress\QueueTest.java:116:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:100:
warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
[javac] SSLContext sslCtx = null;
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:103:
warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
[javac] sslCtx = SSLContext.getInstance("TLS");
[javac] ^
[javac]
D:\jboss\jboss-head\testsuite\src\main\org\jboss\test\security\test\HttpsUnitTestCase.java:112:
warning: com.sun.net.ssl.KeyManagerFactory in com.sun.net.ssl has been deprecated
[javac]
[JBoss-dev] Testsuite Compilation Failed! JBoss (HEAD/linux1/1.4.1_05) [AUTOMATED]
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
Mon Nov 24 19:44:41 GMT 2003
===
HERE ARE THE LAST 100 LINES OF THE LOG:
===
==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS==
===
===
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/classloader/circularity/test/CircularityErrorTests.java:40:
warning: org.jboss.mx.loading.UnifiedLoaderRepository2 in org.jboss.mx.loading has
been deprecated
[javac] UnifiedLoaderRepository2 repository = new UnifiedLoaderRepository2();
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/DurableSubscriberTest.java:77:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/DurableSubscriberTest.java:121:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/DurableSubscriberTest.java:143:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/DurableSubscriberTest.java:161:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/ExceptionListenerTest.java:63:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:111:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:113:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:168:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MultipleDurableSubscribers.java:170:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MassiveTest.java:75:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MassiveTest.java:129:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/MassiveTest.java:133:
warning: stop() in java.lang.Thread has been deprecated
[javac] tf.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:74:
warning: stop() in java.lang.Thread has been deprecated
[javac] t1.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/jbossmq/stress/QueueTest.java:116:
warning: stop() in java.lang.Thread has been deprecated
[javac] t2.stop();
[javac]^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:100:
warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
[javac] SSLContext sslCtx = null;
[javac] ^
[javac]
/home/jbossci/jbossci2/jboss-head/testsuite/src/main/org/jboss/test/security/test/HttpsUnitTestCase.java:103:
warning: com.sun.net.ssl.SSLContext in com.sun.net.ssl has been deprecated
[javac] sslCtx = SSLContext.getInstance("TLS");
Re: [JBoss-dev] Build in 3.2
On Sun, 2003-11-23 at 14:09, Bill Burke wrote: > I think buildmagic files were moved around. One shapshot I had recently > wouldn't build, but I got latest, and it worked. I am very conservative when it comes to checking for changes. If build/build.xml, module/build.xml, tools or thirdparty changes everything is rebuilt. Of course you can force this yourself with ./build.sh clean first. The big problem (which probably hit Bill) is that a cvs update doesn't pull down new jars in thirdparty. Regards, Adrian > > Sacha Labourey wrote: > > > Has anything changed recently? Adrian had optimized the build process a few > > months ago so that rebuilding JBoss (build after build) was taking MUCH less > > time and it seems this doesn't work anymore. > > > > > > > > > > --- > > This SF.net email is sponsored by: SF.net Giveback Program. > > Does SourceForge.net help you be more productive? Does it > > help you create better code? SHARE THE LOVE, and help us help > > YOU! Click Here: http://sourceforge.net/donate/ > > ___ > > JBoss-Development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Build in 3.2
Ok, I get it, I had most probably modified a moduleXXX/build.xml Thanks adrian. Cheers, sacha > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Adrian Brock > Sent: lundi, 24 novembre 2003 20:12 > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] Build in 3.2 > > On Sun, 2003-11-23 at 14:09, Bill Burke wrote: > > I think buildmagic files were moved around. One shapshot I had > > recently wouldn't build, but I got latest, and it worked. > > I am very conservative when it comes to checking for changes. > If build/build.xml, module/build.xml, tools or thirdparty > changes everything is rebuilt. > > Of course you can force this yourself with ./build.sh clean first. > The big problem (which probably hit Bill) is that a cvs > update doesn't pull down new jars in thirdparty. > > Regards, > Adrian > > > > > Sacha Labourey wrote: > > > > > Has anything changed recently? Adrian had optimized the build > > > process a few months ago so that rebuilding JBoss (build after > > > build) was taking MUCH less time and it seems this > doesn't work anymore. > > > > > > > > > > > > > > > --- > > > This SF.net email is sponsored by: SF.net Giveback Program. > > > Does SourceForge.net help you be more productive? Does > it help you > > > create better code? SHARE THE LOVE, and help us help YOU! Click > > > Here: http://sourceforge.net/donate/ > > > ___ > > > JBoss-Development mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > > > > --- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us > help YOU! Click Here: http://sourceforge.net/donate/ > ___ > JBoss-Development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] ClientDeployer, EJBDeployer, AbstractWebContainer delegate to JSR109ClientService
Hi Scott, I put in the JSR109 client programming model, for J2EE application, EJB, end web component clients. As you suggested, I use a 'delegate to service' rather than subdeployment approach. Here a few details modified ApplicationMetaData, ClientMetaData, WebMetaData to conatain a 'Object webservicesClient' if the EJBDeployer, ClientDeployer, AbstractWebContainer find a webservicesclient.xml (in create) they delegate to JSR109ClientService to do the XML parsing after they established their respective ENC, they delegate again to JSR109ClientService to have the javax.xml.rpc.Service bound to the ENC cheers -thomas --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] WebServer: howto obtain the host and port generically
Hallo Christoph, do we realy? In case of JSR109 is it not just a matter of feeding back the user suplied WSDL in webservices.xml? How can you define (in the spirit of JSR109) webservices that spawn ofer more than one endpoint? Thanks -thomas > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Behalf Of Jung > , Dr. Christoph > Sent: Monday, November 24, 2003 2:11 PM > To: '[EMAIL PROTECTED]' > Subject: AW: [JBoss-dev] WebServer: howto obtain the host and port > generically > > > That is what the dynamic wsdl generation facilities of > Axis/Jboss.net use > and what I was thinking about initially, too. > > Hoever, you should consider that the wsdl file will spawn > over several web > services (ejb+war) only one of them > is hit over a particular transport (and hence msgcontext > properties) and you > would have to adjust the > other entries (for which you have no transport information) > as well to get a > valid wsdl ... > > > CGJ > > > > > > -Ursprüngliche Nachricht- > > Von: Thomas Diesler [mailto:[EMAIL PROTECTED] > > Gesendet: Samstag, 22. November 2003 17:33 > > An: [EMAIL PROTECTED] > > Betreff: RE: [JBoss-dev] WebServer: howto obtain the host and > > port generically > > > > > > It is much simpler than that, with RPCProvider.generateWSDL > > you get a MessageContext that actually contains all the info > > we need to do the mapping. It contains a (large) bag of > > random things - axis comment: 'in case somebody needs it'. > > > > I thought, I share this one :-) > > > > -thomas > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On > > Behalf Of Jung , Dr. Christoph > > Sent: Freitag, 21. November 2003 10:38 > > To: '[EMAIL PROTECTED]' > > Subject: AW: [JBoss-dev] WebServer: howto obtain the host and > > port generically > > > > > > Hi, > > > > > -Ursprüngliche Nachricht- > > > Von: Thomas Diesler (E-mail) [mailto:[EMAIL PROTECTED] > > > Gesendet: Freitag, 21. November 2003 10:13 > > > An: [EMAIL PROTECTED] > > > Betreff: [JBoss-dev] WebServer: howto obtain the host and > > > port generically > > > > > > > > > Hi all, > > > > > > during webservice deployment the WSDL file may specify a > dummy port > > > location. When feeding back the deployed WSDL I would like > > to (must) > > > tweak the port location such that it reflects the actual URL the > > > webservice is available at. > > > > You may want to have a look at the servlet > > spec/implementation. From its initialisation on, any servlet > > (including our jboss.net transport servlets > > org.jboss.net.axis.server.AxisServiceServlet and > > org.jboss.net.ws4ee.server.WebInvokerServlet) has access to > > its javax.servlet.ServletConfig and hence its > > javax.servlet.ServletContext which, to my knowledge, will > > provide these bits of information. > > > > Since AxisServiceServlet is quasi-static to the webservice > > deployments, registering such data centrally (like in the > > org.jboss.net.axis.service.AxisService indexed with a > > transport protocol id "http" or so) should not be a problem. > > > > When it comes to the WebInvokerServlets, this could be a > > problem of the start order since servlet.init(config) will be > > called after > > JSR109Deployer.start() ... maybe we should implement the > > patching lazily such that the servlets register in the > > ServiceImplBean upon init(), but WSDL patching is not done > > until all related deployments have been started and the first > > WSDL request is done? > > > > CGJ > > ### > > > > This message has been scanned by F-Secure Anti-Virus for > > Microsoft Exchange. For more information, connect to > http://www.F-Secure.com/ > > > --- > This SF.net email is sponsored by: SF.net Giveback Program. Does > SourceForge.net help you be more productive? Does it help > you create better > code? SHARE THE LOVE, and help us help YOU! Click Here: > http://sourceforge.net/donate/ > ___ > JBoss-Development mailing list [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > --- > This SF.net email is sponsored by: SF.net Giveback Program. Does > SourceForge.net help you be more productive? Does it help > you create better > code? SHARE THE LOVE, and help us help YOU! Click Here: > http://sourceforge.net/donate/ > ___ > JBoss-Development mailing list [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ### > > This message has been scanned by F-Secure Anti-Virus for > Microsoft Exchange. > For more information, connect to http://www.F-Secure.com/ > > > --- > This SF.net email is sponsored by: SF.net Giveback Program. > Does Sou
[JBoss-dev] [ jboss-Change Notes-848291 ] J2EE1.4 compatible webservices HOWTO - server model
Change Notes item #848291, was opened at 2003-11-24 14:03
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=381174&aid=848291&group_id=22866
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: thomas diesler (tdiesler)
Assigned to: Nobody/Anonymous (nobody)
Summary: J2EE1.4 compatible webservices HOWTO - server model
Initial Comment:
This tracker describes how to implement J2EE1.4
compatible webservices in JBoss4.x. I will focus on the
'pure' JSR109 implementation for stateless session beans
and web components. See the reference at the end for
more about the specs and recomended reading.
The basic notion is, that a stateless session bean, or web
component can make all or part of its public interface
available as a webservice. Hence that server component
can then be accessed (interoperability constraints given)
by any webservice client.
Packaging
===
The server deployment should contain the following files:
#1 Service Endpoint Interface (SEI) class
#2 Web services deployment descriptor (webservices.
xml)
#3 WSDL file
#4 JAX-RPC mapping file
#1 Service Endpoint Interface
-
Is the public interface of the webservice's business
methods
public interface HelloWs extends Remote {
public String sayHello(String input) throws
RemoteException;
}
#2 webservices.xml
--
Is the webservice deployment descriptor, it lives in
META-INF for EJB and in WEB-INF for web components.
http://www.ibm.
com/webservices/dtd/j2ee_web_services_1_0.dtd">
HelloWs
META-INF/Hello.wsdl
META-INF/HelloMapping.
xml
HelloPortComponentEJB
http://test.jboss.
org/ws4eesimple
HelloPortComponent
org.jboss.test.
webservice.ws4eesimple.
HelloWs
HelloEjb
This example names the webservice port component, the
SEI, the WSDL and JAX-RPC maping files.
The port component name specifies the webservice name
in JBoss.NET, ie http://localhost:
8080/jboss-net/services/HelloPortComponentEJB
The element corresponds to a in
ejb-jar.xml.
To make a web component available, use:
HelloJavaBean
Then, the element corresponds to a
in web.xml. However please note, that
the service implementation bean,
you would specify in does not necessarily
have to be a javax.servlet.Servlet.
#3 WSDL file
Is in the standard WSDL format. Axis comes with a tool
Java2WSDL that can help you generate this file.
http://test.jboss.
org/ws4eesimple"
xmlns:intf="http://test.jboss.org/ws4eesimple";
xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:SOAP-ENC="http://schemas.xmlsoap.
org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.
org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
http://test.jboss.org/ws4eesimple";
use="encoded"/>
http://test.jboss.org/ws4eesimple";
use="encoded"/>
One point to notice is, that the port address can be set
to dummy values, which will be corrected by the axis
JBoss.NET server implementation at access time.
The sucessfully deployed service's WSDL can accessed
at: http://localhost:
8080/jboss-net/services/HelloPortComponentEJB?wsdl
#4 JAX-RPC mapping file
---
Describes the Java mapping to a known WSDL document.
It contains the mapping between package names and
XML namespaces, WSDL root types and Java artifacts,
and the set of mappings for services.
http://www.ibm.
com/webservices/dtd/j2ee_jaxrpc_mapping_1_0.dtd">
org.jboss.test.webservice.
ws4eesimple
http://test.jboss.
org/ws4eesimple
Webservice access
==
Below you see a test that accesses the stateless session
bean webservice:
public void helpTestSayHello() throws Exception
{
Service service = new org.apache.axis.client.
Service();
Call call = (Call) service.createCall();
call.setTargetEndpointAddress("http://localhost:
8080/jboss-net/services/HelloPortComponentEJB");
call.setOperationName("sayHello");
String retstr = (String) call.invoke(new Object[]
{"Hello"});
assertEquals("'Hello' to you too!", retstr);
}
Thats it, have fun.
References
==
JSR109 spec
http://jcp.
org/aboutJava/communityprocess/final/jsr109/index.html
Build interoperable Web services
[JBoss-dev] [ jboss-Bugs-848106 ] ClassCastException on SOAP calls upon redeployment
Bugs item #848106, was opened at 2003-11-24 08:55
Message generated for change (Comment added) made by cgjung
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=848106&group_id=22866
Category: JBossSOAP
Group: v3.2
Status: Open
Resolution: Works For Me
Priority: 5
Submitted By: Stephane Nicoll (stephane_nicoll)
Assigned to: Dr. Christoph Georg Jung (cgjung)
Summary: ClassCastException on SOAP calls upon redeployment
Initial Comment:
OS: Redhat linux 9
Java: SUN VM 1.4.1_02
The bug is reproductible with both JBoss 3.2.2 and
3.2.3RC1
We have an application, packaged as an EAR and
containing mainly:
- an EJB module JAR containing SessionBeans, Entity
Beans and MDB
- an WSR module JARr containing a web service
declaration
- Some librairies
The WSR module defines a web service that use a
SessionBean to process incoming SOAP calls
Eveything runs fine but when we hot-redeploy the EAR,
we have a ClassCastException and the web service does
not work anymore (we need to restart JBoss to fix this).
My guesses is that this is an Axis bug but I already
opened a bug @t apache without any feedback. We
discussed this issue in the JBoss-user mailing list see the
thread:
JBossNET hot deployment problem (ClassCastException)
This shows the classes / interfaces are OK after un
hotdeploy (see the thread for test output suggested by
Adrian)
What we have after the hot-redeploy at server side is
the following:
2003-11-24 08:40:57,873 INFO
[org.apache.axis.utils.bytecode.ParamNameExtractor]
AXIS error:java.io.IOException: Unable to load bytecode
for
class "com.kiala.kserver.driver.nodesynch.NodeSyncherLo
cal"
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}
Server.userException
faultSubcode:
faultString: java.lang.ClassCastException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:
java.lang.ClassCastException
at
com.sun.corba.se.internal.javax.rmi.PortableRemoteObjec
t.narrow(PortableRemoteObject.java:293)
at javax.rmi.PortableRemoteObject.narrow
(PortableRemoteObject.java:134)
at
org.apache.axis.providers.java.EJBProvider.createRemote
EJB(EJBProvider.java:168)
at
org.apache.axis.providers.java.EJBProvider.makeNewServi
ceObject(EJBProvider.java:147)
at
org.apache.axis.providers.java.JavaProvider.getNewServi
ceObject(JavaProvider.java:261)
at
org.apache.axis.providers.java.JavaProvider.getServiceOb
ject(JavaProvider.java:138)
at
org.apache.axis.providers.java.JavaProvider.invoke
(JavaProvider.java:313)
at
org.apache.axis.strategies.InvocationStrategy.visit
(InvocationStrategy.java:71)
at org.apache.axis.SimpleChain.doVisiting
(SimpleChain.java:150)
at org.apache.axis.SimpleChain.invoke
(SimpleChain.java:120)
at
org.apache.axis.handlers.soap.SOAPService.invoke
(SOAPService.java:481)
at org.apache.axis.server.AxisServer.invoke
(AxisServer.java:323)
at
org.apache.axis.transport.http.AxisServlet.doPost
(AxisServlet.java:854)
at javax.servlet.http.HttpServlet.service
(HttpServlet.java:760)
at
org.apache.axis.transport.http.AxisServletBase.service
(AxisServletBase.java:339)
Should you need further info, let me know.
Regards,
Stephane Nicoll
--
>Comment By: Dr. Christoph Georg Jung (cgjung)
Date: 2003-11-24 14:45
Message:
Logged In: YES
user_id=175199
Our EJBprovider is derived from the axis one and ovverides
only the necessary bits with regard to container integration.
We did not override the urn shortcuts for handlerclasses
(would be an idea, maybe I will take this as a feature
request ;-), so you would have to use
in your wsdd service declaration
But the wsdl should of course be the same, if it isn´t please
let me know or file a bug!
CGJ
--
Comment By: Stephane Nicoll (stephane_nicoll)
Date: 2003-11-24 14:15
Message:
Logged In: YES
user_id=448198
I suspect this could be the problem :/
We didn't changed anything because our WSDL should not
change at all. We have a C++ client running on a palm and
the SOAP library is lacking of features. So if we change the
WSDL a bit (names are changing) the client could not
connect anymore.
I hope chaning the provider will note change the generation
of the WSDL
Changing to provider java:/EJB is enough?
Regards,
Stephane
--
Comment By: Dr. Christoph Georg Jung (cgjung)
Date: 2003-11-24 14:06
Message:
Logged In: YES
user_id=175199
You should use the org.jboss.net.axis.server.EJBProvider
instead of the axis one (this is what i suspect from your
trace) as our provider is especially designed to cope with the
classloading environment of jboss (and does not employ all
the complicated jndi/narrow stuff
AW: [JBoss-dev] WebServer: howto obtain the host and port generic ally
That is what the dynamic wsdl generation facilities of Axis/Jboss.net use and what I was thinking about initially, too. Hoever, you should consider that the wsdl file will spawn over several web services (ejb+war) only one of them is hit over a particular transport (and hence msgcontext properties) and you would have to adjust the other entries (for which you have no transport information) as well to get a valid wsdl ... CGJ > -Ursprüngliche Nachricht- > Von: Thomas Diesler [mailto:[EMAIL PROTECTED] > Gesendet: Samstag, 22. November 2003 17:33 > An: [EMAIL PROTECTED] > Betreff: RE: [JBoss-dev] WebServer: howto obtain the host and > port generically > > > It is much simpler than that, with RPCProvider.generateWSDL > you get a MessageContext that actually contains all the info > we need to do the mapping. It contains a (large) bag of > random things - axis comment: 'in case somebody needs it'. > > I thought, I share this one :-) > > -thomas > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Jung , Dr. Christoph > Sent: Freitag, 21. November 2003 10:38 > To: '[EMAIL PROTECTED]' > Subject: AW: [JBoss-dev] WebServer: howto obtain the host and > port generically > > > Hi, > > > -Ursprüngliche Nachricht- > > Von: Thomas Diesler (E-mail) [mailto:[EMAIL PROTECTED] > > Gesendet: Freitag, 21. November 2003 10:13 > > An: [EMAIL PROTECTED] > > Betreff: [JBoss-dev] WebServer: howto obtain the host and > > port generically > > > > > > Hi all, > > > > during webservice deployment the WSDL file may specify a dummy port > > location. When feeding back the deployed WSDL I would like > to (must) > > tweak the port location such that it reflects the actual URL the > > webservice is available at. > > You may want to have a look at the servlet > spec/implementation. From its initialisation on, any servlet > (including our jboss.net transport servlets > org.jboss.net.axis.server.AxisServiceServlet and > org.jboss.net.ws4ee.server.WebInvokerServlet) has access to > its javax.servlet.ServletConfig and hence its > javax.servlet.ServletContext which, to my knowledge, will > provide these bits of information. > > Since AxisServiceServlet is quasi-static to the webservice > deployments, registering such data centrally (like in the > org.jboss.net.axis.service.AxisService indexed with a > transport protocol id "http" or so) should not be a problem. > > When it comes to the WebInvokerServlets, this could be a > problem of the start order since servlet.init(config) will be > called after > JSR109Deployer.start() ... maybe we should implement the > patching lazily such that the servlets register in the > ServiceImplBean upon init(), but WSDL patching is not done > until all related deployments have been started and the first > WSDL request is done? > > CGJ > ### > > This message has been scanned by F-Secure Anti-Virus for > Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-848106 ] ClassCastException on SOAP calls upon redeployment
Bugs item #848106, was opened at 2003-11-24 07:55
Message generated for change (Comment added) made by stephane_nicoll
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=848106&group_id=22866
Category: JBossSOAP
Group: v3.2
Status: Open
Resolution: Works For Me
Priority: 5
Submitted By: Stephane Nicoll (stephane_nicoll)
Assigned to: Dr. Christoph Georg Jung (cgjung)
Summary: ClassCastException on SOAP calls upon redeployment
Initial Comment:
OS: Redhat linux 9
Java: SUN VM 1.4.1_02
The bug is reproductible with both JBoss 3.2.2 and
3.2.3RC1
We have an application, packaged as an EAR and
containing mainly:
- an EJB module JAR containing SessionBeans, Entity
Beans and MDB
- an WSR module JARr containing a web service
declaration
- Some librairies
The WSR module defines a web service that use a
SessionBean to process incoming SOAP calls
Eveything runs fine but when we hot-redeploy the EAR,
we have a ClassCastException and the web service does
not work anymore (we need to restart JBoss to fix this).
My guesses is that this is an Axis bug but I already
opened a bug @t apache without any feedback. We
discussed this issue in the JBoss-user mailing list see the
thread:
JBossNET hot deployment problem (ClassCastException)
This shows the classes / interfaces are OK after un
hotdeploy (see the thread for test output suggested by
Adrian)
What we have after the hot-redeploy at server side is
the following:
2003-11-24 08:40:57,873 INFO
[org.apache.axis.utils.bytecode.ParamNameExtractor]
AXIS error:java.io.IOException: Unable to load bytecode
for
class "com.kiala.kserver.driver.nodesynch.NodeSyncherLo
cal"
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}
Server.userException
faultSubcode:
faultString: java.lang.ClassCastException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:
java.lang.ClassCastException
at
com.sun.corba.se.internal.javax.rmi.PortableRemoteObjec
t.narrow(PortableRemoteObject.java:293)
at javax.rmi.PortableRemoteObject.narrow
(PortableRemoteObject.java:134)
at
org.apache.axis.providers.java.EJBProvider.createRemote
EJB(EJBProvider.java:168)
at
org.apache.axis.providers.java.EJBProvider.makeNewServi
ceObject(EJBProvider.java:147)
at
org.apache.axis.providers.java.JavaProvider.getNewServi
ceObject(JavaProvider.java:261)
at
org.apache.axis.providers.java.JavaProvider.getServiceOb
ject(JavaProvider.java:138)
at
org.apache.axis.providers.java.JavaProvider.invoke
(JavaProvider.java:313)
at
org.apache.axis.strategies.InvocationStrategy.visit
(InvocationStrategy.java:71)
at org.apache.axis.SimpleChain.doVisiting
(SimpleChain.java:150)
at org.apache.axis.SimpleChain.invoke
(SimpleChain.java:120)
at
org.apache.axis.handlers.soap.SOAPService.invoke
(SOAPService.java:481)
at org.apache.axis.server.AxisServer.invoke
(AxisServer.java:323)
at
org.apache.axis.transport.http.AxisServlet.doPost
(AxisServlet.java:854)
at javax.servlet.http.HttpServlet.service
(HttpServlet.java:760)
at
org.apache.axis.transport.http.AxisServletBase.service
(AxisServletBase.java:339)
Should you need further info, let me know.
Regards,
Stephane Nicoll
--
>Comment By: Stephane Nicoll (stephane_nicoll)
Date: 2003-11-24 13:15
Message:
Logged In: YES
user_id=448198
I suspect this could be the problem :/
We didn't changed anything because our WSDL should not
change at all. We have a C++ client running on a palm and
the SOAP library is lacking of features. So if we change the
WSDL a bit (names are changing) the client could not
connect anymore.
I hope chaning the provider will note change the generation
of the WSDL
Changing to provider java:/EJB is enough?
Regards,
Stephane
--
Comment By: Dr. Christoph Georg Jung (cgjung)
Date: 2003-11-24 13:06
Message:
Logged In: YES
user_id=175199
You should use the org.jboss.net.axis.server.EJBProvider
instead of the axis one (this is what i suspect from your
trace) as our provider is especially designed to cope with the
classloading environment of jboss (and does not employ all
the complicated jndi/narrow stuff which is faster).
CGJ
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=848106&group_id=22866
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
___
JBoss-Development mailing list
[EMAIL
[JBoss-dev] [ jboss-Bugs-848106 ] ClassCastException on SOAP calls upon redeployment
Bugs item #848106, was opened at 2003-11-24 08:55
Message generated for change (Comment added) made by cgjung
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=848106&group_id=22866
Category: JBossSOAP
Group: v3.2
Status: Open
>Resolution: Works For Me
Priority: 5
Submitted By: Stephane Nicoll (stephane_nicoll)
>Assigned to: Dr. Christoph Georg Jung (cgjung)
Summary: ClassCastException on SOAP calls upon redeployment
Initial Comment:
OS: Redhat linux 9
Java: SUN VM 1.4.1_02
The bug is reproductible with both JBoss 3.2.2 and
3.2.3RC1
We have an application, packaged as an EAR and
containing mainly:
- an EJB module JAR containing SessionBeans, Entity
Beans and MDB
- an WSR module JARr containing a web service
declaration
- Some librairies
The WSR module defines a web service that use a
SessionBean to process incoming SOAP calls
Eveything runs fine but when we hot-redeploy the EAR,
we have a ClassCastException and the web service does
not work anymore (we need to restart JBoss to fix this).
My guesses is that this is an Axis bug but I already
opened a bug @t apache without any feedback. We
discussed this issue in the JBoss-user mailing list see the
thread:
JBossNET hot deployment problem (ClassCastException)
This shows the classes / interfaces are OK after un
hotdeploy (see the thread for test output suggested by
Adrian)
What we have after the hot-redeploy at server side is
the following:
2003-11-24 08:40:57,873 INFO
[org.apache.axis.utils.bytecode.ParamNameExtractor]
AXIS error:java.io.IOException: Unable to load bytecode
for
class "com.kiala.kserver.driver.nodesynch.NodeSyncherLo
cal"
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}
Server.userException
faultSubcode:
faultString: java.lang.ClassCastException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:
java.lang.ClassCastException
at
com.sun.corba.se.internal.javax.rmi.PortableRemoteObjec
t.narrow(PortableRemoteObject.java:293)
at javax.rmi.PortableRemoteObject.narrow
(PortableRemoteObject.java:134)
at
org.apache.axis.providers.java.EJBProvider.createRemote
EJB(EJBProvider.java:168)
at
org.apache.axis.providers.java.EJBProvider.makeNewServi
ceObject(EJBProvider.java:147)
at
org.apache.axis.providers.java.JavaProvider.getNewServi
ceObject(JavaProvider.java:261)
at
org.apache.axis.providers.java.JavaProvider.getServiceOb
ject(JavaProvider.java:138)
at
org.apache.axis.providers.java.JavaProvider.invoke
(JavaProvider.java:313)
at
org.apache.axis.strategies.InvocationStrategy.visit
(InvocationStrategy.java:71)
at org.apache.axis.SimpleChain.doVisiting
(SimpleChain.java:150)
at org.apache.axis.SimpleChain.invoke
(SimpleChain.java:120)
at
org.apache.axis.handlers.soap.SOAPService.invoke
(SOAPService.java:481)
at org.apache.axis.server.AxisServer.invoke
(AxisServer.java:323)
at
org.apache.axis.transport.http.AxisServlet.doPost
(AxisServlet.java:854)
at javax.servlet.http.HttpServlet.service
(HttpServlet.java:760)
at
org.apache.axis.transport.http.AxisServletBase.service
(AxisServletBase.java:339)
Should you need further info, let me know.
Regards,
Stephane Nicoll
--
>Comment By: Dr. Christoph Georg Jung (cgjung)
Date: 2003-11-24 14:06
Message:
Logged In: YES
user_id=175199
You should use the org.jboss.net.axis.server.EJBProvider
instead of the axis one (this is what i suspect from your
trace) as our provider is especially designed to cope with the
classloading environment of jboss (and does not employ all
the complicated jndi/narrow stuff which is faster).
CGJ
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=848106&group_id=22866
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Change Notes-848220 ] J2EE1.4 compatible webservices HOWTO - client model
Change Notes item #848220, was opened at 2003-11-24 11:27
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=381174&aid=848220&group_id=22866
Category: None
Group: v4.0
Status: Open
Priority: 5
Submitted By: thomas diesler (tdiesler)
Assigned to: Nobody/Anonymous (nobody)
Summary: J2EE1.4 compatible webservices HOWTO - client model
Initial Comment:
J2EE1.4 compatible webservices HOWTO - client model
=
This tracker describes how to implement J2EE1.4
compatible webservice clients in JBoss4.x.
The basic notion is, that the client can lookup a Service
Interface (javax.xml.rpc.Service) as defined by the the
JAX-RPC specification from its JNDI environment context
(ENC) and invoke the methods of the webservice like a
local method call.
A client can be any of the following: J2EE application
client, EJB component, web component, or another
webservice. (see Scott's tracker on J2EE application
clients)
Packaging
===
The client deployment should contains the following files:
#1 Service Endpoint Interface (SEI) class
#2 Web services client deployment descriptor
(webservicesclient.xml)
#3 WSDL file
#4 JAX-RPC mapping file
#1 Service Endpoint Interface
-
Is the public interface of the webservice's business
methods
public interface HelloWs extends Remote {
public String sayHello(String input) throws
RemoteException;
}
#2 webservicesclient.xml
Is webservice client deployment descriptor, it lives in
META-INF for application and EJB clients and in WEB-INF
for web component clients.
http://www.ibm.
com/webservices/dtd/j2ee_web_services_client_1_0.
dtd">
service/HelloWsService
javax.xml.rpc.
Service
META-INF/HelloClient.wsdl
META-INF/HelloMapping.
xml
org.jboss.test.
webservice.ws4eesimple.
HelloWs
As you can see, it names the webservice, the SEI, the
WSDL and JAX-RPC maping files.
The webservice interface (javax.xml.rpc.Service) is
boound into the client's ENC under the name given in the
.
#3 WSDL file
Is in the standard WSDL format. Axis comes with a tool
Java2WSDL that can help you generate this file.
http://test.jboss.
org/ws4eesimple"
xmlns:intf="http://test.jboss.org/ws4eesimple";
xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:SOAP-ENC="http://schemas.xmlsoap.
org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.
org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
http://test.jboss.org/ws4eesimple";
use="encoded"/>
http://test.jboss.org/ws4eesimple";
use="encoded"/>
http://localhost:
8080/jboss-net/services/HelloPortComponentEJB"/>
One point to notice is, that the port address (in our case
http://localhost:
8080/jboss-net/services/HelloPortComponentEJB) can
point to any available webservice not just one hosted by
JBoss.NET. The webservice must be available at call time,
not necessarily at deploy time.
#4 JAX-RPC mapping file
---
Describes the Java mapping to a known WSDL document.
It contains the mapping between package names and
XML namespaces, WSDL root types and Java artifacts,
and the set of mappings for services.
http://www.ibm.
com/webservices/dtd/j2ee_jaxrpc_mapping_1_0.dtd">
org.jboss.test.webservice.
ws4eesimple
http://test.jboss.
org/ws4eesimple
Webservice access
=
Below you see a stateless session bean accessing a
webservice. First is the lookup from the bean ENC. Then
it obtains the service endpoint interface from the Service
object. The webservice runtime is required to provide
access to the webservice either through a generated
stub, a dynamic proxy, or through dynamic port access
(DII).
In our case we get a dynamic proxy generated by the
Axis client runtime.
public class HelloClientBean implements SessionBean
{
public String sayHello(String input) throws
RemoteException
{
try
{
InitialContext iniCtx = new InitialContext();
Context envCtx = (Context)iniCtx.lookup("java:
comp/env");
javax.xml.rpc.Service svc = (javax.xml.rpc.
Service)envCtx.lookup("service/HelloWsService");
HelloWs sei = (HelloWs)svc.getPort(HelloWs.
class);
String output = sei.sayHello(input);
return output;
}
catch (Exc
[JBoss-dev] [ jboss-Bugs-848106 ] ClassCastException on SOAP calls upon redeployment
Bugs item #848106, was opened at 2003-11-24 07:55
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=848106&group_id=22866
Category: JBossSOAP
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Stephane Nicoll (stephane_nicoll)
Assigned to: Nobody/Anonymous (nobody)
Summary: ClassCastException on SOAP calls upon redeployment
Initial Comment:
OS: Redhat linux 9
Java: SUN VM 1.4.1_02
The bug is reproductible with both JBoss 3.2.2 and
3.2.3RC1
We have an application, packaged as an EAR and
containing mainly:
- an EJB module JAR containing SessionBeans, Entity
Beans and MDB
- an WSR module JARr containing a web service
declaration
- Some librairies
The WSR module defines a web service that use a
SessionBean to process incoming SOAP calls
Eveything runs fine but when we hot-redeploy the EAR,
we have a ClassCastException and the web service does
not work anymore (we need to restart JBoss to fix this).
My guesses is that this is an Axis bug but I already
opened a bug @t apache without any feedback. We
discussed this issue in the JBoss-user mailing list see the
thread:
JBossNET hot deployment problem (ClassCastException)
This shows the classes / interfaces are OK after un
hotdeploy (see the thread for test output suggested by
Adrian)
What we have after the hot-redeploy at server side is
the following:
2003-11-24 08:40:57,873 INFO
[org.apache.axis.utils.bytecode.ParamNameExtractor]
AXIS error:java.io.IOException: Unable to load bytecode
for
class "com.kiala.kserver.driver.nodesynch.NodeSyncherLo
cal"
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}
Server.userException
faultSubcode:
faultString: java.lang.ClassCastException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:
java.lang.ClassCastException
at
com.sun.corba.se.internal.javax.rmi.PortableRemoteObjec
t.narrow(PortableRemoteObject.java:293)
at javax.rmi.PortableRemoteObject.narrow
(PortableRemoteObject.java:134)
at
org.apache.axis.providers.java.EJBProvider.createRemote
EJB(EJBProvider.java:168)
at
org.apache.axis.providers.java.EJBProvider.makeNewServi
ceObject(EJBProvider.java:147)
at
org.apache.axis.providers.java.JavaProvider.getNewServi
ceObject(JavaProvider.java:261)
at
org.apache.axis.providers.java.JavaProvider.getServiceOb
ject(JavaProvider.java:138)
at
org.apache.axis.providers.java.JavaProvider.invoke
(JavaProvider.java:313)
at
org.apache.axis.strategies.InvocationStrategy.visit
(InvocationStrategy.java:71)
at org.apache.axis.SimpleChain.doVisiting
(SimpleChain.java:150)
at org.apache.axis.SimpleChain.invoke
(SimpleChain.java:120)
at
org.apache.axis.handlers.soap.SOAPService.invoke
(SOAPService.java:481)
at org.apache.axis.server.AxisServer.invoke
(AxisServer.java:323)
at
org.apache.axis.transport.http.AxisServlet.doPost
(AxisServlet.java:854)
at javax.servlet.http.HttpServlet.service
(HttpServlet.java:760)
at
org.apache.axis.transport.http.AxisServletBase.service
(AxisServletBase.java:339)
Should you need further info, let me know.
Regards,
Stephane Nicoll
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=848106&group_id=22866
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
___
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss Test Results: 63 % ( 657 / 1039 ) - could do better. JBoss (HEAD/winxp/1.4.2_01) [AUTOMATED]
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === Mon Nov 24 07:37:54 GMTST 2003 === HERE ARE THE LAST 100 LINES OF THE LOG: === ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net/ FOR DETAILS== === === JBoss daily test results SUMMARY Number of tests run: 1039 Successful tests: 657 Errors:358 Failures: 24 [time of test: 2003-11-24.02-18 GMT] [java.version: 1.4.2_01] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.2_01-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Windows XP] [os.arch: x86] [os.version: 5.1] Useful resources: - http://jboss.kimptoc.net/winxp/1.4.2_01/logtests/testresults/reports/html//2003-11-24.02-18 for the junit report of this test. NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS Suite: LocalUnitTestCase Test:testSetup Type:error Exception: java.rmi.NoSuchObjectException Message: Could not activate; failed to restore state; CausedByException is: D:\jboss\jboss-head-test\build\output\testbuild\server\all\tmp\sessions\test\TreeCacheAopTester-dndwd9gl-16\dndwdabu-19.ser (The system cannot find the file specified) - Suite: IdentityLockUnitTestCase Test:testNullOwner_RWLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireWriteLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner_SimpleLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireWriteLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner2_RWLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireReadLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner2_SimpleLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireReadLock(): null owner object. - Suite: IdentityLockUnitTestCase Test:testNullOwner3_RWLock Type:error Exception: java.lang.IllegalArgumentException Message: IdentityLock.acquireWriteLock(): null owner object. === Mon Nov 24 07:37:56 GMTST 2003 === CYGWIN_NT-5.1 quarks2 1.5.4(0.94/3/2) 2003-09-12 23:08 i686 unknown unknown Cygwin === java -version java version "1.4.2_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
