[JBoss-dev] JBoss Messaging 1.0.1.CR3 released
This is now available on jboss labs: http://labs.jboss.com/portal/jbossmessaging/downloads This recommend contains several important fixes, so I highly recommend that any users upgrade to this version if you are using an earlier version. Release notes are available here: http://labs.jboss.com/portal/jbossmessaging/downloads Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Tomcat 6 integrated
Our migration to labs is due to happen (very) soon... In the mean-time we can just edit out the tomcat from the build since we don't have any dependencies on it. Scott M Stark wrote: > Jboss5 requires a java5 runtime due to javaee5 requirements so you need > to get off of head. > > -Original Message----- > From: Tim Fox > Sent: Monday, June 26, 2006 8:09 AM > To: Stan Silvert > Cc: Ryan Campbell; JBoss.org development list; Scott M Stark; The Core; > Bill Burke > Subject: Re: [JBoss-dev] Tomcat 6 integrated > > 1.5 is a pain for us, since we need to build and test our (jboss > messaging) releases using 1.4 > > Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Tomcat 6 integrated
1.5 is a pain for us, since we need to build and test our (jboss messaging) releases using 1.4 Stan Silvert wrote: >>So, head should only be compilable with a 1.5 jdk. >> >>However, some modules will still enforce source & target at 1.4, so > > that > >>we can back merge fixes to the jboss4 tree. >> >>Correct? >> > > > What's the latest on this? The JSF integration code under the Tomcat > module needs JDK 1.5 to compile. I can change it to be 1.4-compatible > if I have to. > > Stan Silvert > JBoss, a division of RedHat > [EMAIL PROTECTED] > > >>-Original Message- >>From: Ryan Campbell >>Sent: Thursday, June 22, 2006 12:16 PM >>To: JBoss.org development list; Scott M Stark >>Cc: The Core; Bill Burke >>Subject: RE: [JBoss-dev] Tomcat 6 integrated >> >>So, head should only be compilable with a 1.5 jdk. >> >>However, some modules will still enforce source & target at 1.4, so > > that > >>we can back merge fixes to the jboss4 tree. >> >>Correct? >> >>-Original Message- >>From: [EMAIL PROTECTED] [mailto:jboss- >>[EMAIL PROTECTED] On Behalf Of Anil Saldhana >>Sent: Thursday, June 22, 2006 11:10 AM >>To: Scott M Stark >>Cc: JBoss.org development list; The Core; Bill Burke >>Subject: Re: [JBoss-dev] Tomcat 6 integrated >> >>Ruel is looking into this. The issue is that the Tomcat jars need > > JDK5 > >>for compilation and the way the current HEAD build is setup, we may > > have > >>some issues. >> >>Scott M Stark wrote: >> >>>The tomcat module needs jdk5, not all of head. jboss5 will require a >>>jdk5 runtime. >>> >>> >>> -Original Message- From: Anil Saldhana Sent: Thursday, June 22, 2006 8:06 AM To: JBoss.org development list Cc: Bill Burke; The Core Subject: Re: [JBoss-dev] Tomcat 6 integrated Hi Scott, with regard to the current TC6 integration that Bill undertook in HEAD: http://jira.jboss.com/jira/browse/JBAS-3330 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=85382 This has placed a need for JDK5 in HEAD as TC6 needs it. You will need to make a decision to make HEAD requiring JDK5. Regards, Anil >>> >>> >> >>Using Tomcat but need to do more? Need to support web services, > > security? > >>Get stuff done quickly with pre-integrated technology to make your job >>easier >>Download IBM WebSphere Application Server v.1.0.1 based on Apache > > Geronimo > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > >>___ >>JBoss-Development mailing list >>JBoss-Development@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/jboss-development > > Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Build still broken
Of course the build is still broken for other reasons I wonder if anyone's going to take a look at that anytime soon (JDK5 apache naming jar incompatibility) ? It's *definitely* time to move off HEAD and on to labs. :) Refreshing from HEAD is just too much of a lottery IMHO - you might be out of action for days.... Tim Fox wrote: > Thx, that worked. > > Adrian Brock wrote: > >>Maybe you changed the local filesystem date? >>Try deleting the directory from thirdparty. >> >>On Mon, 2006-06-26 at 10:34 +0200, Adrian Brock wrote: >> >> >>>My jbossxb is currently at "snapshot" not 1.0.0.CR4 >>>but then I'm trying to avoid resynching with head too >>>often to avoid all the build breakages. :-) >>> >>>On Mon, 2006-06-26 at 08:55 +0100, Tim Fox wrote: >>> >>> >>>>This is still occurring for me .. >>>> >>>>Is anyone else seeing this?? >>>> >>>>Ovidiu Feodorov wrote: >>>> >>>> >>>>>The 796th reason to switch to a separated build ... >>>>> >>>>>Tim Fox wrote: >>>>> >>>>> >>>>> >>>>>>I'm getting the following after doing a cvs update -C in HEAD and then a >>>>>>build clean: >>>>>> >>>>>>BUILD FAILED >>>>>>C:\dev\jboss-head\build\build.xml:999: The following error occurred >>>>>>while execut >>>>>>ing this line: >>>>>>C:\dev\jboss-head\build\build-thirdparty.xml:140: A versioning problem >>>>>>exists: >>>>>>Component: jboss/jbossxb is at version: 1.0.0.CR4 >>>>>>but it is also required to be compatible with: >>>>>>[EMAIL PROTECTED], ver >>>>>>sion=1.0.0.CR5}, [EMAIL PROTECTED], version=snapshot}] >>>>>>by: jboss/jbossws14 >>>>>> >>>>>>Using Tomcat but need to do more? Need to support web services, security? >>>>>>Get stuff done quickly with pre-integrated technology to make your job >>>>>>easier >>>>>>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >>>>>>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >>>>>>___ >>>>>>JBoss-Development mailing list >>>>>>JBoss-Development@lists.sourceforge.net >>>>>>https://lists.sourceforge.net/lists/listinfo/jboss-development >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>>Using Tomcat but need to do more? Need to support web services, security? >>>>>Get stuff done quickly with pre-integrated technology to make your job >>>>>easier >>>>>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >>>>>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >>>>>___ >>>>>JBoss-Development mailing list >>>>>JBoss-Development@lists.sourceforge.net >>>>>https://lists.sourceforge.net/lists/listinfo/jboss-development >>>>> >>>> >>>>Using Tomcat but need to do more? Need to support web services, security? >>>>Get stuff done quickly with pre-integrated technology to make your job >>>>easier >>>>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >>>>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >>>>___ >>>>JBoss-Development mailing list >>>>JBoss-Development@lists.sourceforge.net >>>>https://lists.sourceforge.net/lists/listinfo/jboss-development > > > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development > Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Build still broken
Thx, that worked. Adrian Brock wrote: > Maybe you changed the local filesystem date? > Try deleting the directory from thirdparty. > > On Mon, 2006-06-26 at 10:34 +0200, Adrian Brock wrote: > >>My jbossxb is currently at "snapshot" not 1.0.0.CR4 >>but then I'm trying to avoid resynching with head too >>often to avoid all the build breakages. :-) >> >>On Mon, 2006-06-26 at 08:55 +0100, Tim Fox wrote: >> >>>This is still occurring for me .. >>> >>>Is anyone else seeing this?? >>> >>>Ovidiu Feodorov wrote: >>> >>>>The 796th reason to switch to a separated build ... >>>> >>>>Tim Fox wrote: >>>> >>>> >>>>>I'm getting the following after doing a cvs update -C in HEAD and then a >>>>>build clean: >>>>> >>>>>BUILD FAILED >>>>>C:\dev\jboss-head\build\build.xml:999: The following error occurred >>>>>while execut >>>>>ing this line: >>>>>C:\dev\jboss-head\build\build-thirdparty.xml:140: A versioning problem >>>>>exists: >>>>>Component: jboss/jbossxb is at version: 1.0.0.CR4 >>>>> but it is also required to be compatible with: >>>>>[EMAIL PROTECTED], ver >>>>>sion=1.0.0.CR5}, [EMAIL PROTECTED], version=snapshot}] >>>>> by: jboss/jbossws14 >>>>> >>>>>Using Tomcat but need to do more? Need to support web services, security? >>>>>Get stuff done quickly with pre-integrated technology to make your job >>>>>easier >>>>>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >>>>>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >>>>>___ >>>>>JBoss-Development mailing list >>>>>JBoss-Development@lists.sourceforge.net >>>>>https://lists.sourceforge.net/lists/listinfo/jboss-development >>>>> >>>>> >>>> >>>> >>>> >>>>Using Tomcat but need to do more? Need to support web services, security? >>>>Get stuff done quickly with pre-integrated technology to make your job >>>>easier >>>>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >>>>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >>>>___ >>>>JBoss-Development mailing list >>>>JBoss-Development@lists.sourceforge.net >>>>https://lists.sourceforge.net/lists/listinfo/jboss-development >>>> >>> >>>Using Tomcat but need to do more? Need to support web services, security? >>>Get stuff done quickly with pre-integrated technology to make your job easier >>>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >>>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >>>___ >>>JBoss-Development mailing list >>>JBoss-Development@lists.sourceforge.net >>>https://lists.sourceforge.net/lists/listinfo/jboss-development Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Build still broken
This is still occurring for me .. Is anyone else seeing this?? Ovidiu Feodorov wrote: > The 796th reason to switch to a separated build ... > > Tim Fox wrote: > >>I'm getting the following after doing a cvs update -C in HEAD and then a >>build clean: >> >>BUILD FAILED >>C:\dev\jboss-head\build\build.xml:999: The following error occurred >>while execut >>ing this line: >>C:\dev\jboss-head\build\build-thirdparty.xml:140: A versioning problem >>exists: >>Component: jboss/jbossxb is at version: 1.0.0.CR4 >> but it is also required to be compatible with: >>[EMAIL PROTECTED], ver >>sion=1.0.0.CR5}, [EMAIL PROTECTED], version=snapshot}] >> by: jboss/jbossws14 >> >>Using Tomcat but need to do more? Need to support web services, security? >>Get stuff done quickly with pre-integrated technology to make your job easier >>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >>___ >>JBoss-Development mailing list >>JBoss-Development@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/jboss-development >> >> > > > > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > ___ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development > Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Can't build
I'm getting the following after doing a cvs update -C in HEAD and then a build clean: BUILD FAILED C:\dev\jboss-head\build\build.xml:999: The following error occurred while execut ing this line: C:\dev\jboss-head\build\build-thirdparty.xml:140: A versioning problem exists: Component: jboss/jbossxb is at version: 1.0.0.CR4 but it is also required to be compatible with: [EMAIL PROTECTED], ver sion=1.0.0.CR5}, [EMAIL PROTECTED], version=snapshot}] by: jboss/jbossws14 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Leading slashes on jars in build path
Yes, I've got a project called "thirdparty" at the same level as all my other projects ("jms", "messaging", "connector" etc). It's weird, as I say, if I remove the leading slash then everything works ok. Adrian Brock wrote: > The leading slash is relative to the eclipse workspace not the file > system. > > Do you create a simple project called "thirdparty" in the workspace > based on what the build/build-thirdparty.xml creates? > > On Sat, 2006-06-24 at 15:10 +0100, Tim Fox wrote: > >>I've noticed that some (most?) of the library entries on the Java build >>path (Eclipse) for many of the projects start with a leading slash: >> >>/thirdparty/jboss/profiler/jvmti/lib. >> >>This means on my system that the libraries cannot be found since I do >>not checkout jboss head into the root of the volume. >> >>So, every time I update from CVS I have to remove all the leading >>slashes so eclipse relative to the top of my workspace where the >>libraries will be found. >> >>Is there any reason for having the leading slashes? Or perhaps I am >>doing something wrong and somehow I can get eclipse to interpret the >>leading slash as being at the root of my workspace. >> >>Any ideas? >> >>Using Tomcat but need to do more? Need to support web services, security? >>Get stuff done quickly with pre-integrated technology to make your job easier >>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >>___ >>JBoss-Development mailing list >>JBoss-Development@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/jboss-development Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Leading slashes on jars in build path
I've noticed that some (most?) of the library entries on the Java build path (Eclipse) for many of the projects start with a leading slash: /thirdparty/jboss/profiler/jvmti/lib. This means on my system that the libraries cannot be found since I do not checkout jboss head into the root of the volume. So, every time I update from CVS I have to remove all the leading slashes so eclipse relative to the top of my workspace where the libraries will be found. Is there any reason for having the leading slashes? Or perhaps I am doing something wrong and somehow I can get eclipse to interpret the leading slash as being at the root of my workspace. Any ideas? Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JTA / JTS question
Thanks. This means that if I create 2 JMS XASessions, enlist them in a global tx, then receive messages 1, 2, 3 with session 1, and messages 4, 5, 6 in session2, then rollback the global tx, the messages will end up back in the queue, but for some transaction managers the order in the queue will be 1, 2, 3, 4, 5, 6, but for others it might be 4, 5, 6, 1, 2, 3. I guess this doesn't matter since the JMS message order guarantee doesn't apply after rollback anyway, but good to know. I guess some users (wrongly) might expect messages to go back in the queue in the order they were consumed. Mark Little wrote: No, there's no guaranteed order (it can be different between transaction instances and between commit phases). None of the standards provide for it (going back beyond X/Open), and in fact that's one of the reasons synchronizations were introduced as a separate protocol (to guarantee ordering). So JTA or JTS won't help you here. However, if you want to look at JBossTransactions specifics, then that can help you: we give you full control over the ordering of participants. Mark. Tim Fox wrote: One of you transaction gurus may know the answer: If I enlist 2 (or more) XAResources into a JTA transaction. Transaction tx = tm.getTransaction(); tx.enlistResource(res1); tx.enlistResource(res2); Then I rollback the transaction, which causes rollback() to be called on each of the XAResources. Are there any guarantees on the order in which rollback() is called on the resources, or is this up to the transaction manager implementation? E.g. is rollback always called in the same order the resources were enlisted? --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JTA / JTS question
One of you transaction gurus may know the answer: If I enlist 2 (or more) XAResources into a JTA transaction. Transaction tx = tm.getTransaction(); tx.enlistResource(res1); tx.enlistResource(res2); Then I rollback the transaction, which causes rollback() to be called on each of the XAResources. Are there any guarantees on the order in which rollback() is called on the resources, or is this up to the transaction manager implementation? E.g. is rollback always called in the same order the resources were enlisted? --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] jboss-head-jdk-matrix Build Failed
It's 5am, we're going through the release procedure for JBossMessaging 1.0, updated from CVS to build the release bundle, and HEAD is broken! If any one from web services is listening please *fix this* we are NOT very happy bunnies right now [EMAIL PROTECTED] wrote: View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060331153535 BUILD FAILED Ant Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-common.xml:64: Exit code: 1 See compile.log in Build Artifacts for details. Date of build: 03/31/2006 15:35:35 Time to build: 19 minutes 25 seconds Last changed: 03/31/2006 15:28:35 Last log entry: convert jbws383 to wstools Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 77) 1.3 deleted jgreene testsuite/src/resources/webservice/jbws383/config.xml convert jbws383 to wstools 1.1 added jgreene testsuite/src/resources/webservice/jbws383/wstools-config.xml convert jbws383 to wstools 1.3 modified jgreene testsuite/src/resources/webservice/jbws383/WEB-INF/jaxrpc-mapping.xml convert jbws383 to wstools 1.3 modified jgreene testsuite/src/resources/webservice/jbws383/WEB-INF/webservices.xml convert jbws383 to wstools 1.3 modified jgreene testsuite/src/resources/webservice/jbws383/WEB-INF/wsdl/TestService.wsdl convert jbws383 to wstools 1.3 modified jgreene testsuite/src/main/org/jboss/test/webservice/jbws381/WeatherForecastSoapImpl.java Convert jbws381 to wstools 1.3 modified jgreene testsuite/src/main/org/jboss/test/webservice/jbws381/WeatherForecasts.java Convert jbws381 to wstools 1.3 deleted jgreene testsuite/src/resources/webservice/jbws381/config.xml Convert jbws381 to wstools 1.1 added jgreene testsuite/src/resources/webservice/jbws381/wstools-config.xml Convert jbws381 to wstools 1.3 modified jgreene testsuite/src/resources/webservice/jbws381/WEB-INF/jaxrpc-mapping.xml Convert jbws381 to wstools 1.3 deleted jgreene testsuite/src/resources/webservice/jbws377/config.xml convert jbws377 to wstools 1.1 added jgreene testsuite/src/resources/webservice/jbws377/wstools-config.xml convert jbws377 to wstools 1.3 modified jgreene testsuite/src/resources/webservice/jbws377/WEB-INF/jaxrpc-mapping.xml convert jbws377 to wstools 1.3 modified jgreene testsuite/src/resources/webservice/jbws377/WEB-INF/webservices.xml convert jbws377 to wstools 1.3 modified jgreene testsuite/src/resources/webservice/jbws377/WEB-INF/wsdl/HelloService.wsdl convert jbws377 to wstools 1.1 added jgreene testsuite/src/resources/webservice/jbws358/wstools-config.xml convert jbws358 to wstools 1.3 modified jgreene testsuite/src/resources/webservice/jbws358/META-INF/jaxrpc-mapping.xml convert jbws358 to wstools 1.3 modified jgreene testsuite/src/resources/webservice/jbws358/META-INF/webservices.xml convert jbws358 to wstools 1.3 modified jgreene testsuite/src/resources/webservice/jbws358/META-INF/wsdl/HelloService.wsdl convert jbws358 to wstools 1.4 deleted jgreene testsuite/src/resources/webservice/jbws349/config.xml convert jbws349 to wstools 1.1 added jgreene testsuite/src/resources/webservice/jbws349/wstools-config.xml convert jbws349 to wstools 1.4 modified jgreene testsuite/src/resources/webservice/jbws349/WEB-INF/jaxrpc-mapping.xml convert jbws349 to wstools 1.3 modified jgreene testsuite/src/resources/webservice/jbws331/WS-META-INF/wsdl/HelloService.wsdl convert jbws331 to wstools 1.3 deleted jgreene testsuite/src/resources/webservice/jbws331/config.xml convert jbws331 to wstools 1.1 added jgreene testsuite/src/resources/webservice/jbws331/wstools-config.xml convert jbws331 to wstools 1.3 modified jgreene testsuite/src/resources/webservice/jbws331/WS-META-INF/jaxrpc-mapping.xml convert jbws331 to wstools 1.3 modified jgreene testsuite/src/resources/webservice/jbws331/WS-META-INF/webservices.xml convert jbws331 to wstools 1.1 added jgreene testsuite/src/resources/webservice/jbws316/wstools-config.xml convert jbws316 to wstools 1.3 modified jgreene testsuite/src/resources/webservice/jbws316/WEB-INF/TestBusinessFacadeMapping.xml convert jbws316 to wstools 1.3 modified jgreene testsuite/src/resources/webservice/jbws316/WEB-INF/webservices.xml convert jbws316 to wstools 1.3 modified jgreene testsuite/src/resources/webservice/jbws316/WEB-INF/wsdl/TestBusinessFacadeBF.wsdl convert jbws316 to wstools 1.3 deleted jgreene testsuite/src/resources/webservice/jbws309/config.xml convert jbws309 to wstools 1.1 added jgreene testsuite/src/resources/webservice/jbws309/wstools-config.xml convert jbws309 to wstools 1.3 modified jgreene testsuite/src/resources/webservice/jbws309/META-INF/jaxrpc-mapping.xml convert jbws309 to wstools 1.4 modified jgreene testsuite/src/resources/webservice/jbws309/META-INF/wsdl/OrganizationService.wsdl convert jbws309 to
Re: [JBoss-dev] jboss-head-jdk-matrix Build Failed
ok, hacked it to make it build. lucky we're not using web services Tim Fox wrote: It's 5am, we're going through the release procedure for JBossMessaging 1.0, updated from CVS to build the release bundle, and HEAD is broken! If any one from web services is listening please *fix this* we are NOT very happy bunnies right now [EMAIL PROTECTED] wrote: View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-jdk-matrix?log=log20060331153535 BUILD FAILED Ant Error Message: /services/cruisecontrol/work/scripts/build-jboss-common.xml:220: The following error occurred while executing this line: /services/cruisecontrol/work/scripts/build-jboss-common.xml:64: Exit code: 1 See compile.log in Build Artifacts for details. Date of build: 03/31/2006 15:35:35 Time to build: 19 minutes 25 seconds Last changed: 03/31/2006 15:28:35 Last log entry: convert jbws383 to wstools Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (first 50 of 77) 1.3deletedjgreene testsuite/src/resources/webservice/jbws383/config.xmlconvert jbws383 to wstools 1.1addedjgreene testsuite/src/resources/webservice/jbws383/wstools-config.xml convert jbws383 to wstools 1.3modifiedjgreene testsuite/src/resources/webservice/jbws383/WEB-INF/jaxrpc-mapping.xml convert jbws383 to wstools 1.3modifiedjgreene testsuite/src/resources/webservice/jbws383/WEB-INF/webservices.xml convert jbws383 to wstools 1.3modifiedjgreene testsuite/src/resources/webservice/jbws383/WEB-INF/wsdl/TestService.wsdl convert jbws383 to wstools 1.3modifiedjgreene testsuite/src/main/org/jboss/test/webservice/jbws381/WeatherForecastSoapImpl.java Convert jbws381 to wstools 1.3modifiedjgreene testsuite/src/main/org/jboss/test/webservice/jbws381/WeatherForecasts.java Convert jbws381 to wstools 1.3deletedjgreene testsuite/src/resources/webservice/jbws381/config.xmlConvert jbws381 to wstools 1.1addedjgreene testsuite/src/resources/webservice/jbws381/wstools-config.xml Convert jbws381 to wstools 1.3modifiedjgreene testsuite/src/resources/webservice/jbws381/WEB-INF/jaxrpc-mapping.xml Convert jbws381 to wstools 1.3deletedjgreene testsuite/src/resources/webservice/jbws377/config.xmlconvert jbws377 to wstools 1.1addedjgreene testsuite/src/resources/webservice/jbws377/wstools-config.xml convert jbws377 to wstools 1.3modifiedjgreene testsuite/src/resources/webservice/jbws377/WEB-INF/jaxrpc-mapping.xml convert jbws377 to wstools 1.3modifiedjgreene testsuite/src/resources/webservice/jbws377/WEB-INF/webservices.xml convert jbws377 to wstools 1.3modifiedjgreene testsuite/src/resources/webservice/jbws377/WEB-INF/wsdl/HelloService.wsdl convert jbws377 to wstools 1.1addedjgreene testsuite/src/resources/webservice/jbws358/wstools-config.xml convert jbws358 to wstools 1.3modifiedjgreene testsuite/src/resources/webservice/jbws358/META-INF/jaxrpc-mapping.xml convert jbws358 to wstools 1.3modifiedjgreene testsuite/src/resources/webservice/jbws358/META-INF/webservices.xml convert jbws358 to wstools 1.3modifiedjgreene testsuite/src/resources/webservice/jbws358/META-INF/wsdl/HelloService.wsdl convert jbws358 to wstools 1.4deletedjgreene testsuite/src/resources/webservice/jbws349/config.xmlconvert jbws349 to wstools 1.1addedjgreene testsuite/src/resources/webservice/jbws349/wstools-config.xml convert jbws349 to wstools 1.4modifiedjgreene testsuite/src/resources/webservice/jbws349/WEB-INF/jaxrpc-mapping.xml convert jbws349 to wstools 1.3modifiedjgreene testsuite/src/resources/webservice/jbws331/WS-META-INF/wsdl/HelloService.wsdl convert jbws331 to wstools 1.3deletedjgreene testsuite/src/resources/webservice/jbws331/config.xmlconvert jbws331 to wstools 1.1addedjgreene testsuite/src/resources/webservice/jbws331/wstools-config.xml convert jbws331 to wstools 1.3modifiedjgreene testsuite/src/resources/webservice/jbws331/WS-META-INF/jaxrpc-mapping.xml convert jbws331 to wstools 1.3modifiedjgreene testsuite/src/resources/webservice/jbws331/WS-META-INF/webservices.xml convert jbws331 to wstools 1.1addedjgreene testsuite/src/resources/webservice/jbws316/wstools-config.xml convert jbws316 to wstools 1.3modifiedjgreene testsuite/src/resources/webservice/jbws316/WEB-INF/TestBusinessFacadeMapping.xml convert jbws316 to wstools 1.3modifiedjgreene testsuite/src/resources/webservice/jbws316/WEB-INF/webservices.xml convert jbws316 to wstools 1.3modifiedjgreene testsuite/src/resources/webservice/jbws316/WEB-INF/wsdl/TestBusinessFacadeBF.wsdl convert jbws316 to wstools 1.3deletedjgreene testsuite/src/resources/webservice/jbws309/config.xmlconvert jbws309 to wstools 1.1
Re: [JBoss-dev] AspectManager.removeBindings(AspectManager.java:1240)
I've been seeing this too for some time. Alexey Loubyansky wrote: HEAD Kabir Khan wrote: Which version/branch? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexey Loubyansky Sent: 13 March 2006 14:52 To: jboss-development@lists.sourceforge.net Subject: [JBoss-dev] AspectManager.removeBindings(AspectManager.java:1240) Am I the only one who has been seeing this for quite some time now during JBoss shutdown? 14:49:41,508 ERROR [AspectDeployer] failed to stop java.lang.IndexOutOfBoundsException: Index: 1, Size: 1 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at org.jboss.aop.AspectManager.removeBindings(AspectManager.java:1240) at org.jboss.aop.AspectXmlLoader.bulkUndeploy(AspectXmlLoader.java:1098) at org.jboss.aop.AspectXmlLoader.undeployXML(AspectXmlLoader.java:1089) at org.jboss.aop.AspectXmlLoader.undeploy(AspectXmlLoader.java:1211) at org.jboss.aop.AspectXmlLoader.undeployXML(AspectXmlLoader.java:1246) at org.jboss.aop.deployment.AspectDeployer.stop(AspectDeployer.java:211) at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:658) at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:631) at org.jboss.deployment.MainDeployer.shutdown(MainDeployer.java:510) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess orImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth odAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedD ispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIn terceptor.java:138) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke (ModelMBeanOperationInterceptor.java: 140) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanI nvoker.java:262) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.system.server.ServerImpl$ShutdownHook.shutdownDeploy ments(ServerImpl.java:1049) at org.jboss.system.server.ServerImpl$ShutdownHook.shutdown(Serve rImpl.java:1024) at org.jboss.system.server.ServerImpl$ShutdownHook.run(ServerImpl .java:987) 14:49:41,638 INFO [Server] Shutdown complete --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&; dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1490) EJB component environment (ENC) is not read only
[ http://jira.jboss.com/jira/browse/JBAS-1490?page=history ] Tim Fox updated JBAS-1490: -- Description: The component JNDI environment for a Stateless session bean does not appear to be read-only. I have a SLSB running in 3.2.6. It attempts to modify it's ENC (java:comp/env environment) and succeeds. I.e. the following succeeds: InitialContext ic = new InitialContext(); Context envCtx = (Context)new InitialContext().lookup("java:comp/env"); envCtx.bind("foo", "bar"); log.debug("Worked!!"); Also bind stuff into the context works. I haven't tried with other types of EJB. According to the EJB 2.0 spec (Sec. 20.2.4) an enterprise beans's environment should be read-only. was: The component JNDI environment for a Stateless session bean does not appear to be read-only. I have a SLSB running in 3.2.6. It attempts to modify it's ENC (java:comp/env environment) and succeeds. I.e. the following succeeds: InitialContext ic = new InitialContext(); Context envCtx = (Context)new InitialContext().lookup("java:comp/env"); envCtx.bind("foo", "bar"); log.debug("Worked!!"); Also bind stuff into the context works. I haven't tried with other types of EJB. According to the EJB 2.0 spec (Sec. 20.2.4) an entity beans's environment should be read-only. > EJB component environment (ENC) is not read only > > > Key: JBAS-1490 > URL: http://jira.jboss.com/jira/browse/JBAS-1490 > Project: JBoss Application Server > Type: Bug > Components: EJBs > Versions: JBossAS-3.2.6 Final > Environment: Windows XP > Reporter: Tim Fox > > > The component JNDI environment for a Stateless session bean does not appear > to be read-only. > I have a SLSB running in 3.2.6. > It attempts to modify it's ENC (java:comp/env environment) and succeeds. I.e. > the following succeeds: > InitialContext ic = new InitialContext(); > Context envCtx = (Context)new InitialContext().lookup("java:comp/env"); > envCtx.bind("foo", "bar"); > log.debug("Worked!!"); > Also bind stuff into the context works. > I haven't tried with other types of EJB. > According to the EJB 2.0 spec (Sec. 20.2.4) an enterprise beans's environment > should be read-only. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1490) EJB component environment (ENC) is not read only
EJB component environment (ENC) is not read only Key: JBAS-1490 URL: http://jira.jboss.com/jira/browse/JBAS-1490 Project: JBoss Application Server Type: Bug Components: EJBs Versions: JBossAS-3.2.6 Final Environment: Windows XP Reporter: Tim Fox The component JNDI environment for a Stateless session bean does not appear to be read-only. I have a SLSB running in 3.2.6. It attempts to modify it's ENC (java:comp/env environment) and succeeds. I.e. the following succeeds: InitialContext ic = new InitialContext(); Context envCtx = (Context)new InitialContext().lookup("java:comp/env"); envCtx.bind("foo", "bar"); log.debug("Worked!!"); Also bind stuff into the context works. I haven't tried with other types of EJB. According to the EJB 2.0 spec (Sec. 20.2.4) an entity beans's environment should be read-only. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] loading 10 EBs takes 5s 1st time called
Have you thought of profiling the code to determine what's taking so long? > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf > Of Dain Sundstrom > Sent: 13 November 2001 15:49 > To: 'Peter Levart'; [EMAIL PROTECTED] > Subject: RE: [JBoss-dev] loading 10 EBs takes 5s 1st time called > > > > Hello! > > > > I just wanted to know if somebody has a straight answer. I'm > > using JBoss 3.0 > > alpha with CMP 2.0. > > > > The first time I reference let's say 10 Entity Beans after a > > JBoss restart it > > takes approx. 5 seconds to retrieve data from them. The > > second and subsequent > > requests to return data from the same 10 EBs take ~20ms. If I > > later request > > data from some other 10 EBs for the first time it takes > > another 5 seconds. > > I'm using commit option B. I watched the SQL that gets sent > > to database > > (using Sybase's "ribo") and it is the same SQL sequence for > > the 1st time as > > for the 2nd and subsequent requests, so this overhead is not from the > > database. > > > > I'm just curious what takes it so long (1/2 second for an EB) > > the first time > > the EB's data is referenced. Is this the time it takes to > > create new instance > > in the pool of EBs? Will this overhead go away after some > > time of running > > when the number of instances reaches the pool's limit? > > > > What I wanted to know is what is happening behind the scenes > > (I read from > > time to time on this list about dynamic bytecode generation > > and similar but I > > thought this was only used to create Proxies...). > > > > I was curious also, so I re-ran my test. The second run always takes > slightly less time ~1-2 sec. The only thing I can think of that is > different in the first execution is the bytecode generator. On > my machine, > a 1.4 athalon, it doesn't take anywhere 1/2 second per bean. I really > haven't been focusing on this type of optimization, but I can easily add a > line to the init or start method that creates an instance of the > bean. Then > it will only happen during setup. I look at it after the example > code done > (later today). > > -dain > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss 3.0
Anyone know of any timescales for the release of JBoss 3.0? TIA ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Throwing runtimeexception from the onmessage method of a message driven bean
I've noticed that if a RuntimeException is thrown from the onMessage of a message driven bean in JBoss, then the message is resent - which then throws an exception again.. ad infinitum. Does anyone know if this is expected behaviour? ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Difficulties with message driven bean
I have a simple message driven bean, listening on a queue. When I send a message to the queue, the send happens ok (ok meaning no error messages/exceptions), but the message seems to be disappear into the "void". I guess the bean isn't registered on this queue somehow, even though I'm pretty damned sure I've followed all the instructions. Any help greatly appreciated. Here is my bean: public class MailerBean implements MessageDrivenBean, MessageListener { //Private members private MessageDrivenContext _ctx; public void onMessage(Message message) { System.out.println("Receiving message"); System.out.println(message); } public void ejbCreate() { System.out.println("Mailer bean created"); } public void ejbRemove() { } public void setMessageDrivenContext(MessageDrivenContext ctx) { _ctx = ctx; } } Here is my ejb-jar.xml (excerpt): MailerBean com.blueheath.mercury.ejb.MailerBean Container Auto-acknowledge javax.jms.Queue NonDurable Here is my jboss.xml (excerpt): MailerBean Standard Message Driven Bean queue/MailerQueue Here is excerpt from jbossmq.xml: MailerQueue Here is the code I am using to send a message (exceptions etc. left out for clarity) InitialContext ic = new InitialContext(); QueueConnectionFactory queueConnectionFactory = (QueueConnectionFactory)ic.lookup("QueueConnectionFactory"); QueueConnection queueConnection = queueConnectionFactory.createQueueConnection(); QueueSession session = queueConnection.createQueueSession(true, Session.AUTO_ACKNOWLEDGE); Queue mailQueue = (Queue)ic.lookup("queue/MailerQueue"); TextMessage message = session.createTextMessage(); message.setText("to the void I go..."); QueueSender sender = session.createSender(mailQueue); sender.send(message); session.close(); queueConnection.close(); System.out.println("Sent mail"); Help! ?? ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Any examples of using the scheduler
I need to use a scheduler to hit some ejbs - apparently jboss has one, although I can find no examples/documentation on how to use this. Anyone know of any pointers? Cheers ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development