RE: [JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Results: 81 % ( 1014 / 1240 ) - come on - pull your finger out
Hi Chris, Why are the linux tests running against the "default" instead of the "all" configuration? Regards, Adrian Adrian Brock Director of Support Back Office JBoss Group, LLC > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Chris Kimpton > Sent: 29 May 2003 04:10 > To: [EMAIL PROTECTED] > Subject: [JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test > Results: 81 % ( 1014 / 1240 ) - come on - pull your finger out > > > == > = > ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ > FOR DETAILS== > == > = > > > > JBoss daily test results > > SUMMARY > > Number of tests run: 1240 > > > > Successful tests: 1014 > > Errors:203 > > Failures: 23 > > > > > > [time of test: 2003-05-29.02-15 GMT] > [java.version: 1.4.1_02] > [java.vendor: Sun Microsystems Inc.] > [java.vm.version: 1.4.1_02-b06] > [java.vm.name: Java HotSpot(TM) Client VM] > [java.vm.info: mixed mode] > [os.name: Linux] > [os.arch: i386] > [os.version: 2.4.18-27.7.x] > > See > http://jboss1.kimptoc.net/linux1/logtests/testresults/reports/ > html//. 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: AOPUnitTestCase > Test:testBasic(org.jboss.test.aop.test.AOPUnitTestCase) > Type:error > Exception: javax.management.InstanceNotFoundException > Message: jboss.aop:name=AOPTester is not registered. > - > > > > Suite: AOPUnitTestCase > Test:testInheritance(org.jboss.test.aop.test.AOPUnitTestCase) > Type:error > Exception: javax.management.InstanceNotFoundException > Message: jboss.aop:name=AOPTester is not registered. > - > > > > Suite: AOPUnitTestCase > Test:testMetadata(org.jboss.test.aop.test.AOPUnitTestCase) > Type:error > Exception: javax.management.InstanceNotFoundException > Message: jboss.aop:name=AOPTester is not registered. > - > > > > Suite: AOPUnitTestCase > Test: > testDynamicInterceptors(org.jboss.test.aop.test.AOPUnitTestCase) > Type:error > Exception: javax.management.InstanceNotFoundException > Message: jboss.aop:name=AOPTester is not registered. > - > > > > Suite: AOPUnitTestCase > Test: > testFieldInterception(org.jboss.test.aop.test.AOPUnitTestCase) > Type:error > Exception: javax.management.InstanceNotFoundException > Message: jboss.aop:name=AOPTester is not registered. > - > > > > Suite: AOPUnitTestCase > Test:testMixin(org.jboss.test.aop.test.AOPUnitTestCase) > Type:error > Exception: javax.management.InstanceNotFoundException > Message: jboss.aop:name=AOPTester is not registered. > - > > > > == > =Thu May 29 04:09:53 BST 2003 > == > =Linux quarks2 2.4.18-27.7.x #1 Fri Mar 14 > 06:58:54 EST 2003 i686 unknown > == > =java version "1.4.1_02" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06) > Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode) > > > --- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Shutdown failed
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === Exception in thread "main" javax.naming.CommunicationException. Root exception is java.rmi.UnmarshalException: Error unmarshaling return; nested exception is: java.io.EOFException at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:217) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133) at org.jnp.server.NamingServer_Stub.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:500) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:479) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.Shutdown.main(Shutdown.java:185) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2438) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1245) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215) ... 6 more JBOSS SHUTDOWN FAILED ===Thu May 29 04:08:53 BST 2003 ===Linux quarks2 2.4.18-27.7.x #1 Fri Mar 14 06:58:54 EST 2003 i686 unknown ===java version "1.4.1_02" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06) Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode) --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Results: 81 % ( 1014 / 1240 ) - come on - pull your finger out
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === JBoss daily test results SUMMARY Number of tests run: 1240 Successful tests: 1014 Errors:203 Failures: 23 [time of test: 2003-05-29.02-15 GMT] [java.version: 1.4.1_02] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.1_02-b06] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.18-27.7.x] See http://jboss1.kimptoc.net/linux1/logtests/testresults/reports/html//. 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: AOPUnitTestCase Test:testBasic(org.jboss.test.aop.test.AOPUnitTestCase) Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.aop:name=AOPTester is not registered. - Suite: AOPUnitTestCase Test:testInheritance(org.jboss.test.aop.test.AOPUnitTestCase) Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.aop:name=AOPTester is not registered. - Suite: AOPUnitTestCase Test:testMetadata(org.jboss.test.aop.test.AOPUnitTestCase) Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.aop:name=AOPTester is not registered. - Suite: AOPUnitTestCase Test:testDynamicInterceptors(org.jboss.test.aop.test.AOPUnitTestCase) Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.aop:name=AOPTester is not registered. - Suite: AOPUnitTestCase Test:testFieldInterception(org.jboss.test.aop.test.AOPUnitTestCase) Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.aop:name=AOPTester is not registered. - Suite: AOPUnitTestCase Test:testMixin(org.jboss.test.aop.test.AOPUnitTestCase) Type:error Exception: javax.management.InstanceNotFoundException Message: jboss.aop:name=AOPTester is not registered. - ===Thu May 29 04:09:53 BST 2003 ===Linux quarks2 2.4.18-27.7.x #1 Fri Mar 14 06:58:54 EST 2003 i686 unknown ===java version "1.4.1_02" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_02-b06) Java HotSpot(TM) Client VM (build 1.4.1_02-b06, mixed mode) --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss (HEAD/linux1) Test Job Failed to Complete Successfully
=== ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss1.kimptoc.net/ FOR DETAILS== === tests-jsr77-unit: [junit] Running org.jboss.test.management.test.JSR77SpecUnitTestCase [junit] Tests run: 16, Failures: 0, Errors: 15, Time elapsed: 5.336 sec [junit] TEST org.jboss.test.management.test.JSR77SpecUnitTestCase FAILED tests-util-unit: [junit] Running org.jboss.test.util.test.PropertyEditorsUnitTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 1.11 sec [junit] Running org.jboss.test.util.test.PropertyPatternUnitTestCase [junit] Tests run: 15, Failures: 0, Errors: 0, Time elapsed: 0.692 sec [junit] Running org.jboss.test.util.test.Scheduler2UnitTestCase [junit] TEST org.jboss.test.util.test.Scheduler2UnitTestCase FAILED (timeout) [junit] Running org.jboss.test.util.test.SchedulerUnitTestCase [junit] TEST org.jboss.test.util.test.SchedulerUnitTestCase FAILED (timeout) [junit] Running org.jboss.test.util.test.ServerSideExampleUnitTestCase [junit] TEST org.jboss.test.util.test.ServerSideExampleUnitTestCase FAILED (timeout) tests-jbossmx-compliance: [junit] Running org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 1.002 sec [junit] Running org.jboss.test.jbossmx.compliance.monitor.BasicTestCase [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 6.798 sec [junit] Running org.jboss.test.jbossmx.compliance.notcompliant.NCMBeanTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 1.05 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.BasicTestCase [junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.465 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.CanonicalTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.339 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.MalformedTestCase [junit] Tests run: 53, Failures: 0, Errors: 0, Time elapsed: 1.948 sec [junit] Running org.jboss.test.jbossmx.compliance.objectname.PatternTestCase [junit] Tests run: 12, Failures: 0, Errors: 0, Time elapsed: 0.571 sec [junit] Running org.jboss.test.jbossmx.compliance.registration.RegistrationTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.972 sec [junit] Running org.jboss.test.jbossmx.compliance.relation.BasicTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.242 sec [junit] Running org.jboss.test.jbossmx.compliance.server.MBeanServerFactoryTestCase [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 1.15 sec [junit] Running org.jboss.test.jbossmx.compliance.server.MBeanServerTestCase [junit] Tests run: 13, Failures: 0, Errors: 0, Time elapsed: 1.658 sec [junit] Running org.jboss.test.jbossmx.compliance.standard.InfoTortureTestCase [junit] Tests run: 38, Failures: 0, Errors: 0, Time elapsed: 1.604 sec [junit] Running org.jboss.test.jbossmx.compliance.standard.InheritanceTestCase [junit] Tests run: 21, Failures: 0, Errors: 0, Time elapsed: 0.851 sec [junit] Running org.jboss.test.jbossmx.compliance.standard.TrivialTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1.034 sec [junit] Running org.jboss.test.jbossmx.compliance.timer.BasicTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 30.76 sec tests-jbossmx-implementation: [junit] Running org.jboss.test.jbossmx.implementation.persistence.OnTimerPersistenceTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 11.045 sec [junit] Running org.jboss.test.jbossmx.implementation.server.ContextCLTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.089 sec [junit] Running org.jboss.test.jbossmx.implementation.util.AgentIDTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.893 sec [junit] Running org.jboss.test.jbossmx.implementation.util.MBeanProxyTestCase [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 1.008 sec tests-jbossmx-performance: [junit] Running org.jboss.test.jbossmx.performance.dynamic.InvocationTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 2.934 sec [junit] Running org.jboss.test.jbossmx.performance.standard.InvocationTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 8.408 sec tests-iiop-stress: [junit] Running org.jboss.test.bankiiop.test.BankStressTestCase [junit] TEST org.jboss.test.bankiiop.test.BankStressTestCase FAILED (timeout) [junit] Running org.jboss.test.helloiiop.test.HelloTimingStressTestCase [junit] TEST org.jboss.test.helloiiop.test.HelloTimingStressTestCase FAILED (timeout) [junit] Running org.jboss.test.helloj
[JBoss-dev] [ jboss-Bugs-745277 ] AuthenticationException thrown on invalid LDAP passwd given
Bugs item #745277, was opened at 2003-05-29 02:51 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=745277&group_id=22866 Category: None Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Erik Reuter (erikreut) Assigned to: Nobody/Anonymous (nobody) Summary: AuthenticationException thrown on invalid LDAP passwd given Initial Comment: I'm getting a pretty annoying reoccurring error in the server log: javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials] Isnt this a bit harsh to log as an error, just because a user typed in the wrong password? JBoss should just silently swallow this - the user is already being notified of the mistake he/she made. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=745277&group_id=22866 --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: Re: Why go forward with buildmagic?
On Tue, 20 May 2003 14:04:37 +0700, Jason Dillon wrote: > And when will 1.6 be out? Using a development release of Ant is not going > to fly. Like most open source ... when it's ready :). As a note there is a major re-write (the third I know of) of maven going on at the moment. -k. -- If you don't test then your code is only a collection of bugs which apparently behave like a working program. Website: http://www.rocketred.com.au/blogs/kevin/ --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] ServiceController "Invalid transition from..."
They've been in jboss 4 for several months. How many of them are necessary is another question. david jencks On 2003.05.27 21:56 Nathan Phelps wrote: > Are these messages new? What do they mean? They are all over the place > in JB4 and I don't recall seeing them before. > > 2003-05-27 20:45:21,328 DEBUG [org.jboss.system.ServiceController] > Creating service jboss:service=EJBTimerService > 2003-05-27 20:45:21,328 INFO [org.jboss.system.ServiceController] > returning from create for service jboss:service=EJBTimerService, invalid > transition from CREATED > . > 2003-05-27 20:45:21,859 DEBUG [org.jboss.system.ServiceController] > starting service jboss:service=EJBTimerService > 2003-05-27 20:45:21,859 INFO [org.jboss.system.ServiceController] > Returning from start request for service: jboss:service=EJBTimerService, > invalid transition from state RUNNING > > 2003-05-27 20:45:22,109 DEBUG [org.jboss.system.ServiceController] > starting service jboss.admin:service=PluginManager > 2003-05-27 20:45:22,109 INFO [org.jboss.system.ServiceController] > Returning from start request for service: > jboss.admin:service=PluginManager, invalid transition from state > CONFIGURED > . > 2003-05-27 20:45:22,109 DEBUG [org.jboss.system.ServiceController] > starting service jboss.admin:service=PluginManager > 2003-05-27 20:45:22,109 INFO [org.jboss.system.ServiceController] > Returning from start request for service: > jboss.admin:service=PluginManager, invalid transition from state > CONFIGURED > . > 2003-05-27 20:45:22,109 DEBUG [org.jboss.system.ServiceController] > starting service jboss.admin:service=PluginManager > 2003-05-27 20:45:22,109 INFO [org.jboss.system.ServiceController] > Returning from start request for service: > jboss.admin:service=PluginManager, invalid transition from state > CONFIGURED > . > 2003-05-27 20:45:23,640 DEBUG [org.jboss.system.ServiceController] > starting service jboss.jca:service=BaseWorkManager > 2003-05-27 20:45:23,640 INFO [org.jboss.system.ServiceController] > Returning from start request for service: > jboss.jca:service=BaseWorkManager, invalid transition from state > CONFIGURED > . > etc. > . > 2003-05-27 20:45:48,750 DEBUG [org.jboss.system.ServiceController] > Creating service jboss.j2ee:jndiName=ejb/jmx/ejb/Adaptor,service=EJB > 2003-05-27 20:45:48,750 INFO [org.jboss.system.ServiceController] > returning from create for service > jboss.j2ee:jndiName=ejb/jmx/ejb/Adaptor,service=EJB, invalid transition > from CREATED > > Thanks, > > Nathan > > > > > > > > ServiceController "Invalid transition from..." > > > > > Are these > messages new? What do they mean? T LANG="en-us">hey are > all over the place LANG="en-us"> in JB4 LANG="en-us"> and I > don SIZE=2 FACE="Arial">’ LANG="en-us">t recall seeing them > before. LANG="en-us"> > > 2003-05-27 > 20:45:21,328 DEBUG [org.jboss.system.ServiceController] Creating service > jboss:service=EJBTimerService > > 2003-05-27 > 20:45:21,328 INFO [org.jboss.system.ServiceController] returning > from create for service jboss:service=EJBTimerService, LANG="en-us"> FACE="Arial">invalid transition from CREATED LANG="en-us"> > > FACE="Arial">… LANG="en-us"> > > 2003-05-27 > 20:45:21,859 DEBUG [org.jboss.system.ServiceController] starting service > jboss:service=EJBTimerService > > 2003-05-27 > 20:45:21,859 INFO [org.jboss.system.ServiceController] Returning > from start request for service: jboss:service=EJBTimerService, LANG="en-us"> FACE="Arial">invalid transition from state RUNNING LANG="en-us"> > > 2003-05-27 > 20:45:22,109 DEBUG [org.jboss.system.ServiceController] starting service > jboss.admin:service=PluginManager > > 2003-05-27 > 20:45:22,109 INFO [org.jboss.system.ServiceController] Returning > from start request for service: jboss.admin:service=PluginManager, LANG="en-us"> FACE="Arial">invalid transition from state LANG="en-us"> > CONFIGURED LANG="en-us"> > > FACE="Arial">… LANG="en-us"> > > 2003-05-27 > 20:45:22,109 DEBUG [org.jboss.system.ServiceController] starting service > jboss.admin:service=PluginManager > > 2003-05-27 > 20:45:22,109 INFO [org.jboss.system.ServiceController] Returning > from start request for service: jboss.admin:service=PluginManager, LANG="en-us"> FACE="Arial">invalid transition from state LANG="en-us"> FACE="Arial"> LANG="en-us"> CONFIGURED LANG="en-us"> > > FACE="Arial">… LANG="en-us"> > > 2003-05-27 > 20:45:22,109 DEBUG [org.jboss.system.ServiceController] starting service > jboss.admin:service=PluginManager > > 2003-05-27 > 20:45:22,109 INFO [org.jboss.system.ServiceController] Returning > from start request for service: jboss.admin:service=PluginManager, LANG="en-us"> FACE="Arial">invalid transition from state LANG="en-us"> FACE="Arial"> LANG="en-us"> CONFIGURED LANG="en-us"> > > FACE="Arial">… LANG="en-us"> > > 2003-05-27 > 20:45:23,640 DEBUG [org.jboss.system.ServiceController] starting service > jboss.jca:service=BaseWorkManager > > 2003-05-27 > 20:45:23,64
RE: [JBoss-dev] releasing on Sunday
Sorry Francisco, this is my fault. I put the InvocationResponse stuff in. Bill > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > Francisco Reverbel > Sent: Wednesday, May 28, 2003 5:20 PM > To: Jboss-Dev > Subject: Re: [JBoss-dev] releasing on Sunday > > > Replying to my own message before anybody else spends time on this... > > On Wed, 28 May 2003, Francisco Reverbel wrote: > > > All IIOP tests fail in the 4.0 branch. Does anybody know why? > > I thought there were no IIOP changes in head since it was branched > > off 3.x. > > This was the problem. There should have been some IIOP changes, since > the invoker interface changed (invoke now returns an InvocationResponse). > > Commiting a fix... > > Francisco > > > > > There are some IIOP fixes in 3.2 that need to be merged into head. > > Following the usual "test before, test after" procedure, I run > > the tests before doing it, only to find out that IIOP was already > > broken. :-( > > > > Cheers, > > > > Francisco > > > > > > On Tue, 27 May 2003, Bill Burke wrote: > > > > > We'll be doing the DR1 release on Sunday. Please ask Scott > or me before > > > committing. We'll be more and more reluctant to allow > commits as we get > > > closer. We should be stabalizing not adding new features at the last > > > minute. > > > > > > Thanks, > > > > > > Bill > > > > > > > > > Bill Burke > > > Chief Architect > > > JBoss Group, LLC > > > > > > > > > Cast your vote for JBoss as JDJ Best App Server > > > > > > http://www.sys-con.com/java/readerschoice2003/vote.cfm > > > > > > > > > > > > --- > > > This SF.net email is sponsored by: ObjectStore. > > > If flattening out C++ or Java code to make your application fit in a > > > relational database is painful, don't do it! Check out ObjectStore. > > > Now part of Progress Software. http://www.objectstore.net/sourceforge > > > ___ > > > Jboss-development mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > > > > > --- > > This SF.net email is sponsored by: ObjectStore. > > If flattening out C++ or Java code to make your application fit in a > > relational database is painful, don't do it! Check out ObjectStore. > > Now part of Progress Software. http://www.objectstore.net/sourceforge > > ___ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > --- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] releasing on Sunday
Replying to my own message before anybody else spends time on this... On Wed, 28 May 2003, Francisco Reverbel wrote: > All IIOP tests fail in the 4.0 branch. Does anybody know why? > I thought there were no IIOP changes in head since it was branched > off 3.x. This was the problem. There should have been some IIOP changes, since the invoker interface changed (invoke now returns an InvocationResponse). Commiting a fix... Francisco > > There are some IIOP fixes in 3.2 that need to be merged into head. > Following the usual "test before, test after" procedure, I run > the tests before doing it, only to find out that IIOP was already > broken. :-( > > Cheers, > > Francisco > > > On Tue, 27 May 2003, Bill Burke wrote: > > > We'll be doing the DR1 release on Sunday. Please ask Scott or me before > > committing. We'll be more and more reluctant to allow commits as we get > > closer. We should be stabalizing not adding new features at the last > > minute. > > > > Thanks, > > > > Bill > > > > > > Bill Burke > > Chief Architect > > JBoss Group, LLC > > > > > > Cast your vote for JBoss as JDJ Best App Server > > > > http://www.sys-con.com/java/readerschoice2003/vote.cfm > > > > > > > > --- > > This SF.net email is sponsored by: ObjectStore. > > If flattening out C++ or Java code to make your application fit in a > > relational database is painful, don't do it! Check out ObjectStore. > > Now part of Progress Software. http://www.objectstore.net/sourceforge > > ___ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > --- > This SF.net email is sponsored by: ObjectStore. > If flattening out C++ or Java code to make your application fit in a > relational database is painful, don't do it! Check out ObjectStore. > Now part of Progress Software. http://www.objectstore.net/sourceforge > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] releasing on Sunday
All IIOP tests fail in the 4.0 branch. Does anybody know why? I thought there were no IIOP changes in head since it was branched off 3.x. There are some IIOP fixes in 3.2 that need to be merged into head. Following the usual "test before, test after" procedure, I run the tests before doing it, only to find out that IIOP was already broken. :-( Cheers, Francisco On Tue, 27 May 2003, Bill Burke wrote: > We'll be doing the DR1 release on Sunday. Please ask Scott or me before > committing. We'll be more and more reluctant to allow commits as we get > closer. We should be stabalizing not adding new features at the last > minute. > > Thanks, > > Bill > > > Bill Burke > Chief Architect > JBoss Group, LLC > > > Cast your vote for JBoss as JDJ Best App Server > > http://www.sys-con.com/java/readerschoice2003/vote.cfm > > > > --- > This SF.net email is sponsored by: ObjectStore. > If flattening out C++ or Java code to make your application fit in a > relational database is painful, don't do it! Check out ObjectStore. > Now part of Progress Software. http://www.objectstore.net/sourceforge > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Servlet Spec Question
The containers do not care about the ids. Some third party tool that is generating an app server specific descriptor like jboss-web.xml could be using the id as an index into the tool database when generating the jboss-web.xml descriptor. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 28, 2003 8:25 AM Subject: Re: [JBoss-dev] Servlet Spec Question > > Let me see if I understand correctly: > > In my web.xml I would put: > > > ... > > > > In my web containers proprietary descriptor file I would put: > > > ... > > > So when I deploy, the container will match up the extra description > information in my proprietary descriptor with the element in the web.xml > based on the id? > > Thanks, > -Phil --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Servlet Spec Question
Not so much for deployment, but for development tools. If the user, through some tool, deletes the servlet in the main dd, then that tool can delete information related to that servlet in the app-server-specific dd. Again, servlets have names so this might not be the best example. The id mechanism, IMHO, is used to establish relationships that tools need to have to be user friendly and to offer something like foreign key constraints in a database (if that analogy makes sense). Brian Original Message Follows From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Servlet Spec Question Date: Wed, 28 May 2003 09:25:46 -0600 Let me see if I understand correctly: In my web.xml I would put: ... In my web containers proprietary descriptor file I would put: ... So when I deploy, the container will match up the extra description information in my proprietary descriptor with the element in the web.xml based on the id? Thanks, -Phil _ --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Servlet Spec Question
Let me see if I understand correctly: In my web.xml I would put: ... In my web containers proprietary descriptor file I would put: ... So when I deploy, the container will match up the extra description information in my proprietary descriptor with the element in the web.xml based on the id? Thanks, -Phil Jules Gosnell <[EMAIL PROTECTED]> Sent by: To: [EMAIL PROTECTED] [EMAIL PROTECTED] cc: ceforge.netSubject: Re: [JBoss-dev] Servlet Spec Question 05/28/03 05:53 AM Please respond to jboss-development I've seen what I think was this at work in a WebSphere descriptor... The idea is that you can unambigously identify any element in the standard dd, by adding an 'ID="xxx"' attribute, then in your proprietary dd you can add further information about that element and use the ID to unify the two descriptions. Some things in the standard dd already have unique names (servlets etc..), some things may not and thus the vendor might need recourse to this mechanism. Jetty, AFAIK, does not make use of this, Jules [EMAIL PROTECTED] wrote: >I am working on a deployment plugin for JBoss IDE and had a question about >the servlet spec (I was reading 2.3). On pages 112-116 it describes an ID >mechanism so that tools can provide additional deployment information. I >don't really understand what it is talking about. Does anyone have an >example of how these are used? Do Jetty and Tomcat have different >non-standard depoyment information? > >Thanks, >-Phil > >Here is a portion of the spec I was referencing. It is several pages so I >have just reprinted the beginning: > > > > > > > > >[snip] > > > > >--- >This SF.net email is sponsored by: ObjectStore. >If flattening out C++ or Java code to make your application fit in a >relational database is painful, don't do it! Check out ObjectStore. >Now part of Progress Software. http://www.objectstore.net/sourceforge >___ >Jboss-development mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-development > > --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-742633 ] JBOSS 3.2.1 / Jetty and Tag Support
Bugs item #742633, was opened at 2003-05-24 09:12
Message generated for change (Comment added) made by janb
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=742633&group_id=22866
Category: JBossWeb
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: roberto (rroberto)
Assigned to: Nobody/Anonymous (nobody)
Summary: JBOSS 3.2.1 / Jetty and Tag Support
Initial Comment:
The servlet engine doesn't call the release method on
tags every time is used from jsp pages.
This because a pool is used .
this is the servlet code generated from a jsp
private org.apache.jasper.runtime.TagHandlerPool
_jspx_tagPool_ABSTag_CustomButton_xmlDocument_s
cope;
/* ABSTag:CustomButton */
com.dat.abs.web.tags.ABSCustomButtonTag
_jspx_th_ABSTag_CustomButton_0 =
(com.dat.abs.web.tags.ABSCustomButtonTag)
_jspx_tagPool_ABSTag_CustomButton_xmlDocument_s
cope.get
(com.dat.abs.web.tags.ABSCustomButtonTag.class);
_jspx_th_ABSTag_CustomButton_0.setPageContext
(pageContext);
_jspx_th_ABSTag_CustomButton_0.setParent
(_jspx_th_ABSTag_ButtonBody_0);
_jspx_th_ABSTag_CustomButton_0.setXmlDocument
(vXmlDocument);
_jspx_th_ABSTag_CustomButton_0.setScope(vScope);
int _jspx_eval_ABSTag_CustomButton_0 =
_jspx_th_ABSTag_CustomButton_0.doStartTag();
if (_jspx_th_ABSTag_CustomButton_0.doEndTag() ==
javax.servlet.jsp.tagext.Tag.SKIP_PAGE)
return;
_jspx_tagPool_ABSTag_CustomButton_xmlDocument_s
cope.reuse(_jspx_th_ABSTag_CustomButton_0)
the method "reuse" on TagHandlerPool is..
/**
* Adds the given tag handler to this tag handler pool,
unless this tag
* handler pool has already reached its capacity, in which
case the tag
* handler's release() method is called.
*
* @param handler Tag handler to add to this tag handler
pool
*/
public synchronized void reuse(Tag handler) {
if (current < (handlers.length - 1))
handlers[++current] = handler;
else
handler.release();
}
so only when handler pool has already reached its
capacity the tag's release() method is called.
>From the sun javadoc about interface
javax.servlet.jsp.tagext.Tag:
"Called on a Tag handler to release state. The page
compiler guarantees that JSP page implementation
objects will invoke this method on all tag handlers".
This cause that the global internal variable of the tag are
not "clear".
It's a jetty bug ? or i can't use internal variable (or i must
reset it)
There is no problem this optional tag attributes, because
a pool is created for each combination of tag/arguments
passed.
ty
Roberto
--
Comment By: Jan Bartel (janb)
Date: 2003-05-28 14:15
Message:
Logged In: YES
user_id=45251
Roberto,
AFAIK, all jsp stuff is handled by JASPER, not Jetty itself.
This issue may be better off raised on the Jakarta Tomcat lists.
Jan
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=742633&group_id=22866
---
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
