RE: [JBoss-dev] Need to change the dist structure for final 3.0 release
Scott, I think that we should also change the JARs in JBOSS_HOME/client: currently we have half a thousand (well, almost) jbossXX-client.jar in this folder and it makes running client application a nightmare: you need to add almost all of them to your classpath to be able to work with a simple helloworld SLSB. Why not building a simple jboss-client.jar that fits 90% of all needs? Cheers, Sacha -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Scott M Stark Envoyé : mardi, 28 mai 2002 01:04 À : [EMAIL PROTECTED] Objet : [JBoss-dev] Need to change the dist structure for final 3.0 release There are now 54 jars in lib. Over half of these are not required for a minimal JMX + JNDI server configuration. I want to create a server/conf/lib directory for jars not required by the core and create minimal, default and all configurations: minimal = JMX + JNDI naming default = base J2EE server, no clustering, JBoss.NET, IIOP? all = every service Scott Stark Chief Technology Officer JBoss Group, LLC ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 28-May-2002
Number of tests run: 604 Successful tests: 602 Errors:1 Failures: 1 [time of test: 28 May 2002 0:29 GMT] [java.version: 1.3.1] [java.vendor: Apple Computer, Inc.] [java.vm.version: 1.3.1] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Mac OS X] [os.arch: ppc] [os.version: 10.1.4] See http://lubega.com/testarchive/${build.uid} for details of this test. See http://lubega.com for general test information. 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. Remember - if a test becomes broken after your changes - fix it or fix the test! Oh dear - still got some errors! Thanks for all your effort - we really do love you! ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-561405 ] catalina jndi: url protocol support
Patches item #561405, was opened at 2002-05-28 08:09 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=561405group_id=22866 Category: None Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Claas Thiele (cthiele) Assigned to: Nobody/Anonymous (nobody) Summary: catalina jndi: url protocol support Initial Comment: since introducing new class loader mechanism loading of catalinas jndi url protocol handler doesn't work. catalina uses urlhandlerfactory but this is used by jboss at first. so catalina fails. one application not working is cocoon... this patch registers catalinas url handler via system property. that is working since rc3. additionally there is a possibilty setting a context-dir trough mbean configuration. but its the same dir for all deployed wars. so it is a hack. and for development only. needs to be reviewed due to the last fact. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=561405group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Problem with UCL.equals and Proxies
this will break the classes we generate in memory though, as they do not have an url On Mon, 27 May 2002, marc fleury wrote: |The result is that UnifiedClassLoader can't override equals. To validate On the top of my head (but I don't remember too well these days) this wouldn't break stuff marcf |that duplicate URLs are not placed into the UnifiedLoaderRepository |the UnifiedClassLoader URL must be used as the unique key. | | |Scott Stark |Chief Technology Officer |JBoss Group, LLC | | | |___ | |Don't miss the 2002 Sprint PCS Application Developer's Conference |August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development -- Juha Lindfors Author of JMX: Managing J2EE with Java Management Extensions Senior Developer, JBoss Group LLC ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Problem with UCL.equals and Proxies
ignore, I misunderstood your message On Tue, 28 May 2002, Juha-P Lindfors wrote: this will break the classes we generate in memory though, as they do not have an url On Mon, 27 May 2002, marc fleury wrote: |The result is that UnifiedClassLoader can't override equals. To validate On the top of my head (but I don't remember too well these days) this wouldn't break stuff marcf |that duplicate URLs are not placed into the UnifiedLoaderRepository |the UnifiedClassLoader URL must be used as the unique key. | | |Scott Stark |Chief Technology Officer |JBoss Group, LLC | | | |___ | |Don't miss the 2002 Sprint PCS Application Developer's Conference |August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development -- Juha Lindfors Author of JMX: Managing J2EE with Java Management Extensions Senior Developer, JBoss Group LLC -- Juha Lindfors Author of JMX: Managing J2EE with Java Management Extensions Senior Developer, JBoss Group LLC ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-Dev] DeployServiceUnitTestCase.testDependsElement failure
Hi, It is trying to start TestDeployerC, but it is not actually starting. The test in ServiceMBeanSupport.start() should now be -if (getState() != STOPPED getState() != FAILED) +if (getState() != DESTROYED getState() != STOPPED getState() != FAILED) return; This fixes the test. But I have a more complete fix in the ServiceController. Is anybody else seeing the testsuite hanging? The 3.1 testsuite was hanging at the weekend. The 3.0 testsuite started hanging after I synched last night. Windows XP Sun VM build 1.3.1_02-b02 I'll try a full checkout this evening. Regards, Adrian _ Chat with friends online, try MSN Messenger: http://messenger.msn.com ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-561546 ] Scoped ear classloading not working
Bugs item #561546, was opened at 2002-05-28 16:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561546group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Marius Kotsbak (mkotsbak) Assigned to: Nobody/Anonymous (nobody) Summary: Scoped ear classloading not working Initial Comment: Bug 1: Steps to reproduce the bug (ejb 1.x-beans taken from the manual, but the problem is the same on 2.x): 1. Deploy test1.ear 2. Deploy test2.ear ( the order of 1,2 is important!) 3. It gives this error: 13:27:46,694 WARN [CMPFieldMetaData] ERROR : Nested Field does not have a get method because test2 has a bean-class with the same name, but with an extra field (year) that test1 does't have. It is deployed with the class of test1 even with the jboss-app.xml is present. 4. Remove both 5. Deploy test2.ear 6. Deploy test1.ear 7. The error above does not appear, because test1.ears bean-class is used, and since it incudes abstract accessor method of all fields (also year) both deploys. test1 and 2 are deployed on different jndi-names (else it complains). bug 2: * And I would say that it is a bug that jboss-app is needed at all in this case. Since the beans are deployed on different jndi-names there are no conflicts. Jboss should use the classes in the jar it is deploying while deploying an ejb-jar. (and if it doesn't find one, then go to other classloaders maybe, if someone like to place them outside). I can't see the current behavior as a feature. Marius K Boostcom -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561546group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-Dev] DeployServiceUnitTestCase.testDependsElement failure
3.0 tests-unit is running for me on without any hangs/timeouts on w2k with Sun 1.3.1_03-b03. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Adrian Brock [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, May 28, 2002 3:38 AM Subject: Re: [JBoss-Dev] DeployServiceUnitTestCase.testDependsElement failure Hi, It is trying to start TestDeployerC, but it is not actually starting. The test in ServiceMBeanSupport.start() should now be -if (getState() != STOPPED getState() != FAILED) +if (getState() != DESTROYED getState() != STOPPED getState() != FAILED) return; This fixes the test. But I have a more complete fix in the ServiceController. Is anybody else seeing the testsuite hanging? The 3.1 testsuite was hanging at the weekend. The 3.0 testsuite started hanging after I synched last night. Windows XP Sun VM build 1.3.1_02-b02 I'll try a full checkout this evening. Regards, Adrian _ Chat with friends online, try MSN Messenger: http://messenger.msn.com ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBOSS 3.0 - RC3 - Can't find org.jboss.jdbc.JdbcProvider class
I've tried to use mySQL with JBoss3.0 RC3. I modified the file jboss-service.xml in order to create a pool of connections: mbean code=org.jboss.jdbc.JdbcProvider name=DefaultDomain:service=JdbcProvider attribute name=Driversorg.gjt.mm.mysql.Driver/attribute /mbean mbean code=org.jboss.jdbc.XADataSourceLoader name=DefaultDomain:service=XADataSource,name=DefaultDS attribute name=PoolNameDefaultDS/attribute attribute name=DataSourceClassorg.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl/attribut e attribute name=URLjdbc:mysql://localhost:3306/test/attribute attribute name=JDBCUserroot/attribute attribute name=Password/attribute attribute name=MinSize1/attribute attribute name=MaxSize5/attribute /mbean Unfortunalty, JBoss is unable to create bean, I always receive this message (in JBOSS_DIST\server\default\log\server.log): 2002-05-28 13:15:03,770 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss:service=JdbcProvider 2002-05-28 13:15:03,770 DEBUG [org.jboss.system.ServiceCreator] code: org.jboss.jdbc.JdbcProvider 2002-05-28 13:15:03,880 DEBUG [org.jboss.system.ServiceCreator] Class not found for mbean: jboss:service=JdbcProvider 2002-05-28 13:15:03,880 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss:service=XADataSource,name=DefaultDS 2002-05-28 13:15:03,880 DEBUG [org.jboss.system.ServiceCreator] code: org.jboss.jdbc.XADataSourceLoader 2002-05-28 13:15:03,940 DEBUG [org.jboss.system.ServiceCreator] Class not found for mbean: jboss:service=XADataSource,name=DefaultDS I went over every jar files, and I didn't manage to find any classes Can someone help me ? Thx Anjarivo RAZAFINIMANANA ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JBOSS 3.0 - RC3 - Can't find org.jboss.jdbc.JdbcProvider class
datapool configuration has changed from 2.4.x to 3.0 look in $JBOSS_HOME/docs/example/jca for example db configuration files. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, May 28, 2002 11:05 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] JBOSS 3.0 - RC3 - Can't find org.jboss.jdbc.JdbcProvider class I've tried to use mySQL with JBoss3.0 RC3. I modified the file jboss-service.xml in order to create a pool of connections: mbean code=org.jboss.jdbc.JdbcProvider name=DefaultDomain:service=JdbcProvider attribute name=Driversorg.gjt.mm.mysql.Driver/attribute /mbean mbean code=org.jboss.jdbc.XADataSourceLoader name=DefaultDomain:service=XADataSource,name=DefaultDS attribute name=PoolNameDefaultDS/attribute attribute name=DataSourceClassorg.jboss.pool.jdbc.xa.wrapper.XADataSource Impl/attribut e attribute name=URLjdbc:mysql://localhost:3306/test/attribute attribute name=JDBCUserroot/attribute attribute name=Password/attribute attribute name=MinSize1/attribute attribute name=MaxSize5/attribute /mbean Unfortunalty, JBoss is unable to create bean, I always receive this message (in JBOSS_DIST\server\default\log\server.log): 2002-05-28 13:15:03,770 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss:service=JdbcProvider 2002-05-28 13:15:03,770 DEBUG [org.jboss.system.ServiceCreator] code: org.jboss.jdbc.JdbcProvider 2002-05-28 13:15:03,880 DEBUG [org.jboss.system.ServiceCreator] Class not found for mbean: jboss:service=JdbcProvider 2002-05-28 13:15:03,880 DEBUG [org.jboss.system.ServiceCreator] About to create bean: jboss:service=XADataSource,name=DefaultDS 2002-05-28 13:15:03,880 DEBUG [org.jboss.system.ServiceCreator] code: org.jboss.jdbc.XADataSourceLoader 2002-05-28 13:15:03,940 DEBUG [org.jboss.system.ServiceCreator] Class not found for mbean: jboss:service=XADataSource,name=DefaultDS I went over every jar files, and I didn't manage to find any classes Can someone help me ? Thx Anjarivo RAZAFINIMANANA ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Change Notes-561570 ] ModelBase renamed to ModelMBeanInvoker
Change Notes item #561570, was opened at 2002-05-28 18:31 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=381174aid=561570group_id=22866 Category: JBossMX Group: None Status: Open Priority: 5 Submitted By: Juha Lindfors (juhalindfors) Assigned to: Juha Lindfors (juhalindfors) Summary: ModelBase renamed to ModelMBeanInvoker Initial Comment: org.jboss.mx.modelmbean.ModelBase has been renamed to ModelMBeanInvoker to more accurately reflect its role in the JBossMX MBean server. This affects any Model MBean implementations that extended from this class. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=381174aid=561570group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Change Notes-561588 ] SAX parser class no longer hard coded
Change Notes item #561588, was opened at 2002-05-28 19:11 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=381174aid=561588group_id=22866 Category: JBossMX Group: None Status: Open Priority: 5 Submitted By: Juha Lindfors (juhalindfors) Assigned to: Juha Lindfors (juhalindfors) Summary: SAX parser class no longer hard coded Initial Comment: The metadata builder implementations no longer hard code the SAX parser class (this was done to avoid conflicts with JAXP version in the build system). By default, the SAX parser set up by JAXP will be used in all JDOM based implementations (you can set JAXP SAX class by -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl, for example). The user can still override the JAXP settings by configuring the builder implementation via the MetaDataBuilder interface. Setting: builder.setProperty(SAX_PARSER, org.apache.crimson.parser.XMLReaderImpl); will set the Crimson SAX parser and override the JAXP defaults. XML validation can be similarly controlled by setting builder.setProperty(XML_VALIDATION, true); -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=381174aid=561588group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Change Notes-561590 ] MetaDataBuilder interface change
Change Notes item #561590, was opened at 2002-05-28 19:13 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=381174aid=561590group_id=22866 Category: JBossMX Group: None Status: Open Priority: 5 Submitted By: Juha Lindfors (juhalindfors) Assigned to: Juha Lindfors (juhalindfors) Summary: MetaDataBuilder interface change Initial Comment: The MetaDataBuilder has changed by adding two methods, setProperty() and getProperty() to the interface. This change affects all builder implementations. An abstract class AbstractBuilder is provided in the metadata package which implements both methods. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=381174aid=561590group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss compilation failed
= ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.4.0 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92) Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE build.sh: build.sh: No such file or directory ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-all daily clean failed
= ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.4.0 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92) Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE build.sh: build.sh: No such file or directory ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-559628 ] Incorrectly throwing RollbackException
Bugs item #559628, was opened at 2002-05-23 08:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Michael Hussey (mhussey) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrectly throwing RollbackException Initial Comment: Using bean managed persistence, and container managed transactions, if the ejbStore method of an entity bean fails by throwing an EJBException, a javax.transaction.RollbackException is thrown instead of a javax.transaction.TransactionRolledBackException. This is a problem because the client will not be able to get a nested exception to find the original problem. For example, in our case, our EJBException wraps an exception describing which unique constraint was violated. The user needs that nested exception to modify his/her entry on the screen to successfully update the object. Weblogic throws its own exception in this case which extends RollbackException and has methods to obtain the nested exception. They also should be throwing TransactionRolledBackException for portability, but at least their solution is useable in the current form. I'm using jboss 2.4.4 windows 2000 ejb 2.0 dtd commit option A for the entity. -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 13:20 Message: Logged In: YES user_id=357070 I'm looking at the EJB 2.0 specifications from Sun: Please see table 15 on page 375. Or clarifying text on page 379 If the exception or error happened during the processing of a client invoked method, throw the java.rmi.RemoteException to the client if the client is a remote client or throw the javax.ejb.EJBException to the client if the client is a local client. If the instance exe-cuted in the client#8217;s transaction, the Container should throw the javax.transac-tion. TransactionRolledbackException to a remote client or the javax.ejb.TransactionRolledbackLocalException to a local client, because it provides more information to the client. (The client knows that it is fruitless to continue the transaction.) -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-559628 ] Incorrectly throwing RollbackException
Bugs item #559628, was opened at 2002-05-23 08:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Michael Hussey (mhussey) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrectly throwing RollbackException Initial Comment: Using bean managed persistence, and container managed transactions, if the ejbStore method of an entity bean fails by throwing an EJBException, a javax.transaction.RollbackException is thrown instead of a javax.transaction.TransactionRolledBackException. This is a problem because the client will not be able to get a nested exception to find the original problem. For example, in our case, our EJBException wraps an exception describing which unique constraint was violated. The user needs that nested exception to modify his/her entry on the screen to successfully update the object. Weblogic throws its own exception in this case which extends RollbackException and has methods to obtain the nested exception. They also should be throwing TransactionRolledBackException for portability, but at least their solution is useable in the current form. I'm using jboss 2.4.4 windows 2000 ejb 2.0 dtd commit option A for the entity. -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 13:42 Message: Logged In: YES user_id=357070 if you interpret the call to ejbStore as a method invocation on the bean, instead of some helper method called by the container, then it should throw TransactionRolledBackException because the bean method (ejbStore) runs in the context of the callers transaction. -- Comment By: Michael Hussey (mhussey) Date: 2002-05-28 13:20 Message: Logged In: YES user_id=357070 I'm looking at the EJB 2.0 specifications from Sun: Please see table 15 on page 375. Or clarifying text on page 379 If the exception or error happened during the processing of a client invoked method, throw the java.rmi.RemoteException to the client if the client is a remote client or throw the javax.ejb.EJBException to the client if the client is a local client. If the instance exe-cuted in the client#8217;s transaction, the Container should throw the javax.transac-tion. TransactionRolledbackException to a remote client or the javax.ejb.TransactionRolledbackLocalException to a local client, because it provides more information to the client. (The client knows that it is fruitless to continue the transaction.) -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=559628group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss compilation failed
= ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.3.0 Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)) = HERE ARE THE LAST 50 LINES OF THE LOG FILE build.sh: build.sh: No such file or directory ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-all daily clean failed
= ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.3.0 Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)) = HERE ARE THE LAST 50 LINES OF THE LOG FILE build.sh: build.sh: No such file or directory ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 28-May-2002
Number of tests run: 604 Successful tests: 604 Errors:0 Failures: 0 [time of test: 28 May 2002 12:32 GMT] [java.version: 1.3.1] [java.vendor: Apple Computer, Inc.] [java.vm.version: 1.3.1] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Mac OS X] [os.arch: ppc] [os.version: 10.1.4] See http://lubega.com/testarchive/${build.uid} for details of this test. See http://lubega.com for general test information. 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. Remember - if a test becomes broken after your changes - fix it or fix the test! HURRAY - everything worked! Thanks for all your effort - we really do love you! ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss compilation failed
= ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.3.0 Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)) = HERE ARE THE LAST 50 LINES OF THE LOG FILE build.sh: build.sh: No such file or directory ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-all daily clean failed
= ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.3.0 Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)) = HERE ARE THE LAST 50 LINES OF THE LOG FILE build.sh: build.sh: No such file or directory ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] jboss-all daily clean failed
Either this was in the middle of some checkins or the working dir is hosed as I am able to do a clean build and build main without any errors using JDK 1.3.1_03-b03 Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, May 28, 2002 10:41 AM Subject: [JBoss-dev] jboss-all daily clean failed = ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.3.0 Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0) Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)) = HERE ARE THE LAST 50 LINES OF THE LOG FILE build.sh: build.sh: No such file or directory ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-all daily clean failed
= ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.4.0 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92) Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE build.sh: build.sh: No such file or directory ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss compilation failed
= ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.4.0 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92) Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE build.sh: build.sh: No such file or directory ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-561683 ] Remove log4j dependency on client side
Bugs item #561683, was opened at 2002-05-28 22:19 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561683group_id=22866 Category: None Group: v3.1 Status: Open Resolution: None Priority: 3 Submitted By: Sacha Labourey (slaboure) Assigned to: Nobody/Anonymous (nobody) Summary: Remove log4j dependency on client side Initial Comment: Currently, log4.jar is needed by some jbossXX-client.jar. Consequently, log4j.jar is needed on the client side for no good reason. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561683group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 28-May-2002
Number of tests run: 604 Successful tests: 603 Errors:1 Failures: 0 [time of test: 28 May 2002 13:39 GMT] [java.version: 1.3.1_03] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1_03-b03] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.18-3] See http://lubega.com/testarchive/${build.uid} for details of this test. See http://lubega.com for general test information. 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. Remember - if a test becomes broken after your changes - fix it or fix the test! Oh dear - still got some errors! Thanks for all your effort - we really do love you! ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-all daily clean failed
= ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.4.0 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92) Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE build.sh: build.sh: No such file or directory ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss compilation failed
= ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.4.0 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92) Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE build.sh: build.sh: No such file or directory ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Change Notes-561710 ] XMBean supports Descriptor resource type
Change Notes item #561710, was opened at 2002-05-29 01:21 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=381174aid=561710group_id=22866 Category: JBossMX Group: None Status: Open Priority: 5 Submitted By: Juha Lindfors (juhalindfors) Assigned to: Juha Lindfors (juhalindfors) Summary: XMBean supports Descriptor resource type Initial Comment: XMBean Model MBean implementation now supports DESCRIPTOR (value defined in XMBeanConstants) as its resource type. Using a descriptor allows property map to be supplied to the Model MBean instance describing how to initialize and configure the Model MBean instance to represent the managed resource. You can use either one of the two constructors: XMBean(Object resource, String type) XMBean(Descriptor) The former requires an instance of javax.management.Descriptor supplied as resource object and XMBeanConstants.DESCRIPTOR supplied as type. The descriptor MUST contain at least two fields: RESOURCE_REFERENCE and RESOURCE_TYPE. Former must have the reference to the actual resource object as its value, and the latter must include the actual type of the resource object. The XMBean implementation will extract this information and use it to register the Model MBean. For instance: Descriptor d = new DescriptorSupport(); d.setField(RESOURCE_REFERENCE, new SomeObject()); d.setField(RESOURCE_TYPE, http://URL/intrface.xml;); ModelMBean mmb = new XMBean(d); server.registerMBean(name, mmb); to set up a resource object whose management interface is generated from the given XML document instance. Descriptors allow client more control on how the Model MBean is configured. For instance, to disable the validation of the XML document instance the client can provide the following descriptor: Descriptor d = new DescriptorSupport(); d.setField(RESOURCE_REFERENCE, new Object()); d.setField(RESOURCE_TYPE, http://URL/intrface.xml;); d.setField(XML_VALIDATION, true); ModelMBean mmb = new XMBean(d); server.registerMBean(name, mmb); The descriptor fields define a naming pattern scheme similar to JMX notifications: a dot separated identity string. These are defined as part XMBEAN_DESCRIPTOR_PREFIX, RESOURCE_DESCRIPTOR_PREFIX and METADATA_DESCRIPTOR_PREFIX. For instance, all fields matching the METADATA_DESCRIPTOR_PREFIX will be automatically delegated by the XMBean implementation to all MetaDataBuilder implementations via the setProperty() method. This allows the client to configure and extend custom builder implementations. Descriptors will later be used to setup ModelMBean instances mapping to multiple resource objects. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=381174aid=561710group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] What does this [XATxConnectionManager] WARN mean?
Earlier versions of the connection managers expected this attribute to look like java:/jaas/MyDBDomain When I changed it to expect MyDBDomain instead I left some backward compatibility with the warning. To make the warning go away, remove java:/jaas from the start of this attribute value david On 2002.05.28 18:42:41 -0400 Jason Dillon wrote: Can someone (probably David) explain to me what the follwing WARN means and how I can make it shut up: 15:40:48,541 WARN [XATxConnectionManager] WARNING: UPDATE YOUR SecurityDomainJndiName! REMOVE java:/jaas/ --jason ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] What does this [XATxConnectionManager] WARN mean?
Something in the build is defaulting to use this... which is why I don't understand why I am getting this warn. Any reason why we want to hide the exact JNDI location here? --jason On Tuesday 28 May 2002 04:02 pm, David Jencks wrote: Earlier versions of the connection managers expected this attribute to look like java:/jaas/MyDBDomain When I changed it to expect MyDBDomain instead I left some backward compatibility with the warning. To make the warning go away, remove java:/jaas from the start of this attribute value david On 2002.05.28 18:42:41 -0400 Jason Dillon wrote: Can someone (probably David) explain to me what the follwing WARN means and how I can make it shut up: 15:40:48,541 WARN [XATxConnectionManager] WARNING: UPDATE YOUR SecurityDomainJndiName! REMOVE java:/jaas/ --jason ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-561737 ] Base64Encoder in wrong jar
Bugs item #561737, was opened at 2002-05-28 23:45 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561737group_id=22866 Category: JBossSX Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Dmitri Colebatch (dimc) Assigned to: Nobody/Anonymous (nobody) Summary: Base64Encoder in wrong jar Initial Comment: I tried to create my own LoginModule that used password hashing, by subclassing UsernamePasswordLoginModule (you can get the same result by enabling hashing in any of the existing subclasses of that login module - eg DatabaseServerLoginModule). And got a NoClassDefFoundError whilst looking for Base64Encoder. The problem is that Base64Encoder is in jbosssx.jar when it should be in jboss-jaas.jar. Adding this: exclude name=org/jboss/security/Base64Encoder.class / to the list of excludes for jbosssx.jar, and adding the corresponding include to jboss-jaas.jar, fixes the problem. This bug report is based on the JBoss_2_4_4 branch, although may also apply to other branches. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561737group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-561737 ] Base64Encoder in wrong jar
Bugs item #561737, was opened at 2002-05-28 16:45 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561737group_id=22866 Category: JBossSX Group: v2.4 (stable) Status: Closed Resolution: Out of Date Priority: 5 Submitted By: Dmitri Colebatch (dimc) Assigned to: Nobody/Anonymous (nobody) Summary: Base64Encoder in wrong jar Initial Comment: I tried to create my own LoginModule that used password hashing, by subclassing UsernamePasswordLoginModule (you can get the same result by enabling hashing in any of the existing subclasses of that login module - eg DatabaseServerLoginModule). And got a NoClassDefFoundError whilst looking for Base64Encoder. The problem is that Base64Encoder is in jbosssx.jar when it should be in jboss-jaas.jar. Adding this: exclude name=org/jboss/security/Base64Encoder.class / to the list of excludes for jbosssx.jar, and adding the corresponding include to jboss-jaas.jar, fixes the problem. This bug report is based on the JBoss_2_4_4 branch, although may also apply to other branches. -- Comment By: Scott M Stark (starksm) Date: 2002-05-28 16:50 Message: Logged In: YES user_id=175228 Get the 2.4.6 release [starksm@banshee JBoss-2.4.6]$ jar -tf lib/jboss-jaas.jar | grep Base org/jboss/security/Base64Encoder.class -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561737group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(HEAD) Testsuite Results: 29-May-2002
Number of tests run: 744 Successful tests: 731 Errors:8 Failures: 5 [time of test: 29 May 2002 1:4 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.9-31] Useful resources: - http://lubega.com/testarchive/ibm_jdk13_20010626 for the junit report of this test. - http://lubega.com/testarchive/ibm_jdk13_20010626/logs/ for the logs for this test. - http://lubega.com for general test information. 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. Remember - if a test becomes broken after your changes - fix it or fix the test! Oh dear - still got some errors! Thanks for all your effort - we really do love you! ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-561752 ] Include cmp field name in warnings
Bugs item #561752, was opened at 2002-05-28 17:44 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561752group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Scott M Stark (starksm) Assigned to: Nobody/Anonymous (nobody) Summary: Include cmp field name in warnings Initial Comment: If a cmp2 bean is missing its field accessors in the implementation class, these warnings are generated but they do not specify what the field is: 2002-05-28 17:38:09,578 INFO [org.jboss.ejb.EJBDeployer] Bean : GangsterEJB Section: 10.6.2 Warning: The entity bean class must define a get accessor for each CMP field. 2002-05-28 17:38:09,593 INFO [org.jboss.ejb.EJBDeployer] Bean : GangsterEJB Section: 10.6.2 Warning: The entity bean class must define a set accessor for each CMP field. 2002-05-28 17:38:09,593 DEBUG [org.jboss.ejb.EJBDeployer] OrgManagerEJB: Verifie d. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=561752group_id=22866 ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(HEAD) Testsuite Results: 29-May-2002
Number of tests run: 749 Successful tests: 737 Errors:8 Failures: 4 [time of test: 29 May 2002 2:19 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20020124 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.9-31] Useful resources: - http://lubega.com/testarchive/ibm_jdk13_20020124 for the junit report of this test. - http://lubega.com/testarchive/ibm_jdk13_20020124/logs/ for the logs for this test. - http://lubega.com for general test information. 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. Remember - if a test becomes broken after your changes - fix it or fix the test! Oh dear - still got some errors! Thanks for all your effort - we really do love you! ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development