[JBoss-dev] XDoclet in /tools has BUGSSSSSS
Hi David What shall I do with you ? The current XDoclet in /tools is buggy !!! It does not work with EJB-CMP column-names (the good old @jboss:column-name is not working and the new @ejb-persistence is not working, either). ATTENTION: when you change /tools you change this also for jboss-website (maybe more). Maybe it would be a good idea if we label beta archives with another name to indicate that this is not a fully tested version ? Have fun x Andreas Schaefer Senior Consultant JBoss Group, LLC x ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-544848 ] EAR Deployments don't work
Bugs item #544848, was opened at 2002-04-16 13:19 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=544848group_id=22866 Category: None Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 9 Submitted By: Peter Luttrell (objec) Assigned to: Nobody/Anonymous (nobody) Summary: EAR Deployments don't work Initial Comment: with jboss3.0rc1 with tomcat4.0.3 if I create an ear file such as this: one.war two.war struts.jar META-INF/application.xml where one.war and two.war depend on structs.jar, jboss blows up when one.war attempts to preload the structs servlet. with jboss3.0b1 with tomcat4.0.3, the above configuration worked perfectly. was this intentionally changed? or is it a bug? if i use the Class-Path entry to specify the structs.jar file in the manifest file for both one.war and two.war it also works. I've only tested this on rc1. -- Comment By: Larry Sanderson (lsanders) Date: 2002-04-17 15:00 Message: Logged In: YES user_id=379453 I'm looking into it. I'll get back soon. -Larry -- Comment By: Peter Luttrell (objec) Date: 2002-04-16 14:35 Message: Logged In: YES user_id=472835 when I mentioned that if I use the Class-Path in the war it worked, i meant that the deployment didn't throw any exceptions. however when I actually go to a page that requires classes in the jar, tomcat blows up indicating that it cannot find them. This may be a seperate issue - let me know if you want me to post another issue about it. the work around at this point is just include the struts.jar in both war files. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=544848group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Multiple Instance - continued
I think that Mark mentioned that JXTA might be appropriate for this and I'd like to second it. If clusters of jboss are distributed all over the place - not just on dedicated server boxes - then a loosely coupled protocol/service framework would be ideal. Setting up known 'rendezvous' points will help to discover and use a robust port service. I hope to start adding jxta bits to jboss in about six months time, but for the moment I'm totally swamped. Jason Dillon wrote: I am glad someone is looking into this. I wish I had more time to review what is going on here add input, but I am loaded with tasks at the moment. From my brief overviews of your emails, look like you are on the case. --jason Quoting Mike Finn [EMAIL PROTECTED]: You guys probably have more to worry about right now, with RC1 and all, but: A while back there was a thread regarding the whole 'multiple instance detection' thing - where the problem of managing multiple listeners vying for the same port was discussed (JNDI, RMI, etc). Was there any resolution or direction? This is of interest to me as we do often have multiple JBosses running on a single box (to make it more challenging - we share a box with another group that has pure RMI apps running on it..). One of the options was a 'port manager' that would (if I understand) forward traffic (like a proxy) to the correct port for the requested service. 1) To do this, I imagine the 'port mgr' would have to be able to sniff the incoming bytestream and determine the requested service by interrogating the content. This imposes the restriction that only one instance of a service (service being wire protocol - JNDI, HTTP, RMI, etc) can be routed, since there probably would be no unambiguous way to differentiate between two HTTP streams (for instance). 2) The port mgr (MBean?) would somehow need to be aware of the 'real' ports being used within the JBoss process space by the managed services. Would the MBean Notification mechanism suffice? Where each MBean that owns a managed port would send a notification with the port/s onwhich it it is listening. Or, as (I think) Marc suggested, a P2P solution like JXTA (which may be a better solution than JMX Notifications?). Or a config file (less than optimal, IMO). Thoughts? I would definitely be interested in contributing on this. Or maybe no one cares about this one anymore. :-) Mike - This mail sent through IMP: http://horde.org/imp/ ___ 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] Automated JBoss Testsuite Results: 18-April-2002
Number of tests run: 561 Successful tests: 538 Errors:16 Failures: 7 [time of test: 18 April 2002 7:34 GMT] [java.version: 1.3.1_02] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1_02-b02] [java.vm.name: Java HotSpot(TM) Server VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com/testarchive/sun_jdk131_02 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! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-542371 ] 2.4.5 no XA JDBC w/ XADataSourceLoader
Bugs item #542371, was opened at 2002-04-11 07:17 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=542371group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Closed Resolution: Fixed Priority: 5 Submitted By: Chris Harris (charris) Assigned to: Scott M Stark (starksm) Summary: 2.4.5 no XA JDBC w/ XADataSourceLoader Initial Comment: Testing an upgrade from 2.4.3 to 2.4.5RC1 we find we are unable to use our existing configuration for our database connections. mbean code=org.jboss.jdbc.XADataSourceLoader name=DefaultDomain:service=XADataSource,name=DefaultDS attribute name=PoolNameDefaultDS/attribute attribute name=DataSourceClasscom.inet.tds.XDataSource/attrib ute attribute name=DataSourceClassorg.jboss.pool.jdbc.xa.wrapper.X ADataSourceImpl/attribute attribute name=URLjdbc:inetdae7:127.0.0.1/attribute attribute name=JDBCUserchrisharris/attribute attribute name=Passwordchrisharris/attribute attribute name=LoggingEnabledfalse/attribute attribute name=Propertieshost=127.0.0.1;database=chrisharris/ attribute attribute name=GCMinIdleTime120/attribute attribute name=MaxSize20/attribute attribute name=GCEnabledfalse/attribute attribute name=InvalidateOnErrorfalse/attribute attribute name=TimestampUsedfalse/attribute attribute name=Blockingtrue/attribute attribute name=GCInterval12/attribute attribute name=IdleTimeout180/attribute attribute name=IdleTimeoutEnabledfalse/attribute attribute name=MaxIdleTimeoutPercent1.0/attribute attribute name=MinSize0/attribute /mbean This previously worked very well, but now triggers ClassCastExceptions in XAConnectionFactory because it is assumed that all JDBC Connections are in fact jboss' own XAConnectionImpl. In other words, using XADataSourceLoader is now *only* possible if you have a non-XA driver and the loader uses its own datasource implementation (XADataSourceImpl)! I will try and use a RAR instead from the 3.0 codebase. However this is a big, incompatible, change and I don't know if the JCA support is there in 2.4.5. -- Comment By: Chris Harris (charris) Date: 2002-04-18 07:26 Message: Logged In: YES user_id=8915 (I erroneously talked about XADataSourceImpl in my last comment - I mean XAConnectionImpl) Anyway, it looks like you've already submitted a fix in cvs 1.2.2.4 of XAConnectionFactory which will fix this. I now see from your comment that you were talking about the 'new' username and password checking logic and were referring to that fix. I haven't tried it yet but that should do the trick. Thanks. -- Comment By: Scott M Stark (starksm) Date: 2002-04-18 00:01 Message: Logged In: YES user_id=175228 Have you tried this fix and it is still not working or are you just speculating. The cast to a XADataSourceImpl has everything to do with username and password checking. -- Comment By: Chris Harris (charris) Date: 2002-04-17 21:37 Message: Logged In: YES user_id=8915 I'm not sure what you are getting at here. It's nothing to do with username and password checking - it's the fact that you can no longer use your own datasource class because you have to produce connections that cast to XADataSourceImpl, which is a JBoss-specific jdbc connection class. That is what the CCE is about in the stack trace - previous versions did not attempt this cast and would permit the use of vendor DataSource classes. -- Comment By: Chris Harris (charris) Date: 2002-04-17 21:37 Message: Logged In: YES user_id=8915 I'm not sure what you are getting at here. It's nothing to do with username and password checking - it's the fact that you can no longer use your own datasource class because you have to produce connections that cast to XADataSourceImpl, which is a JBoss-specific jdbc connection class. That is what the CCE is about in the stack trace - previous versions did not attempt this cast and would permit the use of vendor DataSource classes. -- Comment By: Scott M Stark (starksm) Date: 2002-04-17 17:25 Message: Logged In: YES user_id=175228 The new username and password checking logic is only applied if the source is a XAConnectionImpl. Else the previous behavior is used. -- Comment By: Chris Harris (charris) Date: 2002-04-11 08:33 Message: Logged In: YES user_id=8915 Stack trace follows: java.lang.ClassCastException: com.inet.tds.k at org.jboss.pool.jdbc.xa.XAConnectionFactory.checkValidObject
[JBoss-dev] Automated JBoss Testsuite Results: 18-April-2002
Number of tests run: 569 Successful tests: 540 Errors:21 Failures: 8 [time of test: 18 April 2002 8:28 GMT] [java.version: 1.4.0] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.4.0-b92] [java.vm.name: Java HotSpot(TM) Server VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com/testarchive/sun_j2sdk140 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! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[Xdoclet-user] RE: [JBoss-dev] XDoclet in /tools has BUGSSSSSS
Andy, David has tagged xdoclet cvs with a Jboss specific tag sometimes ago. The version today is very very more confident for CMP. Come and tag whenever you want :) Don't forget (amazing) xjavadoc. I take the opportunity to launch a call for help (crossed post to xdoclet lists) There are still some issues (fucking bugs is a better word imho) with Jboss 3 CMP 2 engine. If somebody can report Unit Tests for that it would be great. The idea is simple : provide two beans with generic names (OneOneMasterCMPBean, OneOneChildCMPBean, OneManyMasterCMPBean, OneManyChildCMPBean, etc...) with all needed xdoclet tags PLUS a reference ejb-jar.xml PLUS a reference jboss-cmp.xml. That's all. Then the unit tests system will generate the DD, do xml comparisons and report errors. Very easy. Come to xdoclet devel to help. This is unacceptable that weblogic cmp works and not jboss. Thanks. Vincent -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Andreas Schaefer Sent: jeudi 18 avril 2002 8:27 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [JBoss-dev] XDoclet in /tools has BUGSS Hi David What shall I do with you ? The current XDoclet in /tools is buggy !!! It does not work with EJB-CMP column-names (the good old @jboss:column-name is not working and the new @ejb-persistence is not working, either). ATTENTION: when you change /tools you change this also for jboss-website (maybe more). Maybe it would be a good idea if we label beta archives with another name to indicate that this is not a fully tested version ? Have fun x Andreas Schaefer Senior Consultant JBoss Group, LLC x ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [Xdoclet-devel] [Xdoclet-user] RE: [JBoss-dev] XDoclet in /tools has BUGSSSSSS
Come to xdoclet devel to help. This is unacceptable that weblogic cmp works and not jboss. WebLogic rocks, JBoss sucks! (That should wake them up, Vincent ;- ). Aslak Thanks. Vincent https://lists.sourceforge.net/lists/listinfo/xdoclet-devel ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Java based web CMS
Sorry, another off question... Do any of you know of any production quality content managment systems for Java? I have only found one, OpenCMS (http://www.opencms.org/opencms/opencms/index.html), which is currently being maintained. If you know of another system could you point me at it. If you have actually used one of these I would also appreciate any comments and insight you have on the matter. This is related to some pending changes to the JBoss website (so it sort of related)... but still sorry for the noise. Thanks, --jason * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=13303 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] unsubscribe please...
Hi! I really need urgently to be unsubscribed from this email list. Please send me the details I need. Which kind of subjectbody of the email I need to send and to which address? Thanks a lot, florin ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: RE: [Xdoclet-devel] [Xdoclet-user] RE: [JBoss-dev] XDoclet in /tools has BUGSSSSSS
What kind of crap noise is this? --jason * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=13300 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] unsubscribe please...
You need to unsubscribe yourself here: http://lists.sourceforge.net/lists/listinfo/jboss-development --jason Quoting Florin Popa [EMAIL PROTECTED]: Hi! I really need urgently to be unsubscribed from this email list. Please send me the details I need. Which kind of subjectbody of the email I need to send and to which address? Thanks a lot, florin ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development - This mail sent through IMP: http://horde.org/imp/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Missing URL Protocol Handler (JNDI) / jboss-3.0.0RC1_tomcat-4.0.3Posted: Apr 17, 2002 11:10 AM
After switching from jboss-3.0.0beta to jboss-3.0.0RC1_tomcat-4.0.3 the servlet that I try to deploy in JBoss throws an exception: java.net.MalformedURLException: unknown protocol: jndi This occurs in the init() method of the servlet. The exact message is: [exec] javax.servlet.ServletException: Unable to determine servlet context URL. [exec] at org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:262) [exec] at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:91 6) [exec] at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:808) [exec] at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java: 3266) [exec] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3395) [exec] at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785) [exec] at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:454) [exec] at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.createWebContext(EmbeddedCa talinaServiceSX.java:284) [exec] at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.performDeploy(EmbeddedCatal inaServiceSX.java:204) [exec] at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:405) [exec] at org.jboss.deployment.MainDeployer.start(MainDeployer.java:665) [exec] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:507) [exec] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:470) [exec] at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) [exec] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:492) [exec] at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) [exec] at $Proxy4.deploy(Unknown Source) [exec] at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanne r.java:350) [exec] at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymen tScanner.java:530) [exec] at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner. java:410) [exec] at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(Ab stractDeploymentScanner.java:202) [exec] at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(Abs tractDeploymentScanner.java:191) [exec] 18:11:32,879 ERROR [Engine] - Root Cause - [exec] java.net.MalformedURLException: unknown protocol: jndi [exec] at java.net.URL.init(URL.java:586) [exec] at java.net.URL.init(URL.java:476) [exec] at java.net.URL.init(URL.java:425) [exec] at org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:257) [exec] at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:91 6) [exec] at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:808) [exec] at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java: 3266) [exec] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3395) [exec] at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785) [exec] at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:454) [exec] at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.createWebContext(EmbeddedCa talinaServiceSX.java:284) [exec] at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.performDeploy(EmbeddedCatal inaServiceSX.java:204) [exec] at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:405) [exec] at org.jboss.deployment.MainDeployer.start(MainDeployer.java:665) [exec] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:507) [exec] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:470) [exec] at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) [exec] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) [exec] at java.lang.reflect.Method.invoke(Method.java:324) [exec] at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat cher.java:284) [exec] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:492) [exec] at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) [exec] at $Proxy4.deploy(Unknown Source) [exec] at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanne r.java:350) [exec] at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymen tScanner.java:530) [exec] at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner. java:410) [exec] at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(Ab stractDeploymentScanner.java:202) [exec] at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(Abs tractDeploymentScanner.java:191) The source code looks like this (CocoonServlet.java): try
Re: [JBoss-dev] Re: mysql-service.xml
Hi. Thank you for you input. This is a message for JBoss people. What do you believe that works with JBoss 3.0 beta but does not work on the RC or My jdbc-connection to PostgreSQL works fine now. I haven't made any comparisons apart from my formerly 'missing link'. Other than that I beleive that if you get it going with RC1, stay there unless you have compelling reasons to upgrade to have features added/fixed into your release. Thank you, João Your welcome. regards Claus _ Yahoo! Mail - din for livet. www.yahoo.dk/mail ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
AW: [JBoss-dev] Old servlet.jar vs. jboss.net/jetty dependency?
Me too ;-) No objections against depending on jetty ;-) CGJ -Ursprüngliche Nachricht- Von: Scott M Stark [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 18. April 2002 06:15 An: [EMAIL PROTECTED] Betreff: Re: [JBoss-dev] Old servlet.jar vs. jboss.net/jetty dependency? Yes. We shoould not even include the sun provided binary since we are building this from source. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Frederick N. Brier [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 17, 2002 8:36 PM Subject: [JBoss-dev] Old servlet.jar vs. jboss.net/jetty dependency? I need to use the class javax.servlet.http.HttpServletRequestWrapper for the Flash/Axis servlet, but it can't be found in servlet.jar. Looking closer, I noticed that the build.xml for JBoss.net is referencing a servlet.jar in jboss-all/thirdparty/sun/servlet/lib. The files in the archive are dated 7/11/2000. The actual archive in the JBoss distribution is javax.servlet.jar which is a superset of the older archive, has the current build date, and the required file. The problem is that the javax.servlet.jar is built in the jboss-all/jetty/output/lib directory. So this would require modifying the root build.xml file to make the _module-jboss.net-most dependent on _module-jetty-most, and then modifying the build.xml [lines 91-94] in jboss-all/jboss.net to specify the javax.servlet.jar in the jetty output directory. Is this reasonable? Thank you. Frederick N. Brier Sr. Software Engineer Multideck Corporation ___ 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] CVS update: jboss/src/resources/org/jboss/verifier DefaultMessages.properties
User: lqd Date: 02/04/18 03:27:49 Modified:src/resources/org/jboss/verifier DefaultMessages.properties Log: - fix messages for section 10.6.7 (ejbSelectXXX methods) Revision ChangesPath 1.15 +2 -2 jboss/src/resources/org/jboss/verifier/DefaultMessages.properties Index: DefaultMessages.properties === RCS file: /cvsroot/jboss/jboss/src/resources/org/jboss/verifier/DefaultMessages.properties,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- DefaultMessages.properties14 Apr 2002 01:12:05 - 1.14 +++ DefaultMessages.properties18 Apr 2002 10:27:48 - 1.15 @@ -180,8 +180,8 @@ 10.6.6.c = Home methods of an entity bean class must not define java.rmi.RemoteException. 10.6.7.a = Select methods of an entity bean class must be declared as public. -10.6.7.b = Select methods of an entity bean class must not be declared abstract. -10.6.7.c = Select methods of an entity bean class must not define java.rmi.RemoteException. +10.6.7.b = Select methods of an entity bean class must be declared abstract. +10.6.7.c = Select methods of an entity bean class must define javax.ejb.FinderException in their throws clause. 10.8.1.a = The type of the primkey-field must match the primary key class. 10.8.1.b = The primkey-field must be one of the CMP fields of the entity bean. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/resources/org/jboss/verifier DefaultMessages.properties
User: lqd Date: 02/04/18 03:25:19 Modified:src/resources/org/jboss/verifier Tag: Branch_3_0 DefaultMessages.properties Log: - fix messages for section 10.6.7 (ejbSelectXXX methods) Revision ChangesPath No revision No revision 1.14.2.1 +2 -2 jboss/src/resources/org/jboss/verifier/DefaultMessages.properties Index: DefaultMessages.properties === RCS file: /cvsroot/jboss/jboss/src/resources/org/jboss/verifier/DefaultMessages.properties,v retrieving revision 1.14 retrieving revision 1.14.2.1 diff -u -r1.14 -r1.14.2.1 --- DefaultMessages.properties14 Apr 2002 01:12:05 - 1.14 +++ DefaultMessages.properties18 Apr 2002 10:25:06 - 1.14.2.1 @@ -180,8 +180,8 @@ 10.6.6.c = Home methods of an entity bean class must not define java.rmi.RemoteException. 10.6.7.a = Select methods of an entity bean class must be declared as public. -10.6.7.b = Select methods of an entity bean class must not be declared abstract. -10.6.7.c = Select methods of an entity bean class must not define java.rmi.RemoteException. +10.6.7.b = Select methods of an entity bean class must be declared abstract. +10.6.7.c = Select methods of an entity bean class must define javax.ejb.FinderException in their throws clause. 10.8.1.a = The type of the primkey-field must match the primary key class. 10.8.1.b = The primkey-field must be one of the CMP fields of the entity bean. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Multiple Instance - continued
Good - that is the approach that made the most sense to me. I think JXTA has promise as a complement to JMX/MBeans. It provides a better communication model than the notify mechanism in JMX, IMO. It may also be worth a look down the road as a vehicle for managing cluster nodes (?) Anyways, I am working on the plumbing stuff now (stream handling, thread pooling, etc). Should be to the MBean/JXTA stuff shortly. This job thing is just getting the way. #mike -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Nick Betteridge Sent: Thursday, April 18, 2002 2:39 AM To: Jboss-Development-List Subject: Re: [JBoss-dev] Multiple Instance - continued I think that Mark mentioned that JXTA might be appropriate for this and I'd like to second it. If clusters of jboss are distributed all over the place - not just on dedicated server boxes - then a loosely coupled protocol/service framework would be ideal. Setting up known 'rendezvous' points will help to discover and use a robust port service. I hope to start adding jxta bits to jboss in about six months time, but for the moment I'm totally swamped. Jason Dillon wrote: I am glad someone is looking into this. I wish I had more time to review what is going on here add input, but I am loaded with tasks at the moment. From my brief overviews of your emails, look like you are on the case. --jason Quoting Mike Finn [EMAIL PROTECTED]: You guys probably have more to worry about right now, with RC1 and all, but: A while back there was a thread regarding the whole 'multiple instance detection' thing - where the problem of managing multiple listeners vying for the same port was discussed (JNDI, RMI, etc). Was there any resolution or direction? This is of interest to me as we do often have multiple JBosses running on a single box (to make it more challenging - we share a box with another group that has pure RMI apps running on it..). One of the options was a 'port manager' that would (if I understand) forward traffic (like a proxy) to the correct port for the requested service. 1) To do this, I imagine the 'port mgr' would have to be able to sniff the incoming bytestream and determine the requested service by interrogating the content. This imposes the restriction that only one instance of a service (service being wire protocol - JNDI, HTTP, RMI, etc) can be routed, since there probably would be no unambiguous way to differentiate between two HTTP streams (for instance). 2) The port mgr (MBean?) would somehow need to be aware of the 'real' ports being used within the JBoss process space by the managed services. Would the MBean Notification mechanism suffice? Where each MBean that owns a managed port would send a notification with the port/s onwhich it it is listening. Or, as (I think) Marc suggested, a P2P solution like JXTA (which may be a better solution than JMX Notifications?). Or a config file (less than optimal, IMO). Thoughts? I would definitely be interested in contributing on this. Or maybe no one cares about this one anymore. :-) Mike - This mail sent through IMP: http://horde.org/imp/ ___ 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-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] HTTP Sessions broken in jboss2.4.5-tomcat4.0.3
try it, youll be trying to guess that number forever. when you run the catalina in the distribution standalone sessions work fine, so its the jboss-catalina combo thats the problem. sorry i cant give more information, dont know where to start looking. c * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=13329 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb/plugins AbstractInstanceCache.java
User: starksm
Date: 02/04/18 06:22:48
Modified:src/main/org/jboss/ejb/plugins Tag: Branch_3_0
AbstractInstanceCache.java
Log:
The call to register with the passivation thread was lost in the last change.
This restores the registration.
Revision ChangesPath
No revision
No revision
1.30.2.2 +7 -2 jboss/src/main/org/jboss/ejb/plugins/AbstractInstanceCache.java
Index: AbstractInstanceCache.java
===
RCS file:
/cvsroot/jboss/jboss/src/main/org/jboss/ejb/plugins/AbstractInstanceCache.java,v
retrieving revision 1.30.2.1
retrieving revision 1.30.2.2
diff -u -r1.30.2.1 -r1.30.2.2
--- AbstractInstanceCache.java17 Apr 2002 20:17:56 - 1.30.2.1
+++ AbstractInstanceCache.java18 Apr 2002 13:22:46 - 1.30.2.2
@@ -48,7 +48,7 @@
* @author a href=[EMAIL PROTECTED]Bill Burke/a
* @author a href=[EMAIL PROTECTED]Marc Fleury/a
*
- * @version $Revision: 1.30.2.1 $
+ * @version $Revision: 1.30.2.2 $
*
* pbRevisions:/b
*
@@ -181,6 +181,7 @@
catch (Exception x)
{
freeContext(ctx);
+ log.error(Activation failure, x);
throw new NoSuchObjectException(x.getMessage());
}
}
@@ -639,7 +640,11 @@
{
if (m_passivationJobs.get(key) == null)
{
-
+ // Register job
+ m_passivationJobs.put(key, job);
+
+ // Schedule the job for passivation
+ m_passivator.putJob(job);
}
else
{
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Possible bug ?
Hello, I am running JBoss 3.1.0alpha(200204181002) on Win2k SP2 with jdk 1.4. I have a problem, and I do not know what it is related to, my application or JBoss. Let me explain: I have n CMP 2.x entity beans with local interfaces. For testing purposes, I use a stateless session bean to access those entity beans. This session bean itself is instanciated within a servlet. Here is the code used in the servlet init method: InitialContext jndiContext = new InitialContext(); Object ref = jndiContext.lookup(ejb/ServiceBean); ServiceBeanHome home = (ServiceBeanHome) PortableRemoteObject.narrow(ref, ServiceBeanHome.class ); target = home.create(); My ejb-jar.xml is ok, my web.xml defines an ejb-ref which in turn is defined in jboss-web.xml. As a matter of fact, everything works fine on first deployment. The problem is that if I modify the ear file, and then redeploy it, I get a ClassCastException on PortableRemoteObject.narrow. I read a bug report a while ago (#516684) which was related to a problem looking like this one. There was a patch by David Jencks which consisted in using the remote interface ClassLoader to get the class descriptor instead of the one in the loading thread. But it does not work here, the problem remains. I tought it was related to my own code, but then why would it work on first deploy, and not after redeploy ? Could it be anything related to the ClassLoader ? Or is there anything else that needs to be configured inside JBoss when using servlets ? Thanks, Jerome. 2002-04-18 12:38:59,510 ERROR [STDERR] java.lang.ClassCastException 2002-04-18 12:38:59,510 ERROR [STDERR] at com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:293) 2002-04-18 12:38:59,510 ERROR [STDERR] at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:134) 2002-04-18 12:38:59,510 ERROR [STDERR] at mypackage.init(MyServlet.java:37) 2002-04-18 12:38:59,510 ERROR [STDERR] at org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:261) 2002-04-18 12:38:59,510 ERROR [STDERR] at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:308) 2002-04-18 12:38:59,510 ERROR [STDERR] at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:595) 2002-04-18 12:38:59,510 ERROR [STDERR] at org.mortbay.http.HttpContext.handle(HttpContext.java:1357) 2002-04-18 12:38:59,510 ERROR [STDERR] at org.mortbay.http.HttpContext.handle(HttpContext.java:1309) 2002-04-18 12:38:59,510 ERROR [STDERR] at org.mortbay.http.HttpServer.service(HttpServer.java:744) 2002-04-18 12:38:59,510 ERROR [STDERR] at org.jboss.jetty.Jetty.service(Jetty.java:527) 2002-04-18 12:38:59,510 ERROR [STDERR] at org.mortbay.http.HttpConnection.service(HttpConnection.java:743) 2002-04-18 12:38:59,510 ERROR [STDERR] at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:916) 2002-04-18 12:38:59,510 ERROR [STDERR] at org.mortbay.http.HttpConnection.handle(HttpConnection.java:758) 2002-04-18 12:38:59,510 ERROR [STDERR] at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:145) 2002-04-18 12:38:59,520 ERROR [STDERR] at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) 2002-04-18 12:38:59,520 ERROR [STDERR] at org.mortbay.util.ThreadPool$JobRunner.run(ThreadPool.java:715) 2002-04-18 12:38:59,520 ERROR [STDERR] at java.lang.Thread.run(Thread.java:536) * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=1 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] XDoclet in /tools has BUGSSSSSS
andreas can you take care of it? marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |Andreas Schaefer |Sent: Wednesday, April 17, 2002 11:27 PM |To: [EMAIL PROTECTED] |Cc: [EMAIL PROTECTED] |Subject: [JBoss-dev] XDoclet in /tools has BUGSS | | |Hi David | |What shall I do with you ? | |The current XDoclet in /tools is buggy !!! |It does not work with EJB-CMP column-names |(the good old @jboss:column-name is not |working and the new @ejb-persistence is not |working, either). | |ATTENTION: when you change /tools you change |this also for jboss-website (maybe more). | |Maybe it would be a good idea if we label beta |archives with another name to indicate that this |is not a fully tested version ? | |Have fun | |x |Andreas Schaefer |Senior Consultant |JBoss Group, LLC |x | | | |___ |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] CVS update: jboss/src/main/org/jboss/ejb/plugins AbstractInstanceCache.java
User: starksm
Date: 02/04/18 06:39:12
Modified:src/main/org/jboss/ejb/plugins AbstractInstanceCache.java
Log:
The call to register with the passivation thread was lost in the last change.
This restores the registration.
Revision ChangesPath
1.32 +6 -2 jboss/src/main/org/jboss/ejb/plugins/AbstractInstanceCache.java
Index: AbstractInstanceCache.java
===
RCS file:
/cvsroot/jboss/jboss/src/main/org/jboss/ejb/plugins/AbstractInstanceCache.java,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- AbstractInstanceCache.java17 Apr 2002 20:19:20 - 1.31
+++ AbstractInstanceCache.java18 Apr 2002 13:39:12 - 1.32
@@ -48,7 +48,7 @@
* @author a href=[EMAIL PROTECTED]Bill Burke/a
* @author a href=[EMAIL PROTECTED]Marc Fleury/a
*
- * @version $Revision: 1.31 $
+ * @version $Revision: 1.32 $
*
* pbRevisions:/b
*
@@ -639,7 +639,11 @@
{
if (m_passivationJobs.get(key) == null)
{
-
+ // Register job
+ m_passivationJobs.put(key, job);
+
+ // Schedule the job for passivation
+ m_passivator.putJob(job);
}
else
{
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-537990 ] Nested CMRs Fail
Bugs item #537990, was opened at 2002-04-01 12:50 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=537990group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 5 Submitted By: Dan Bunker (danbunker) Assigned to: Dain Sundstrom (dsundstrom) Summary: Nested CMRs Fail Initial Comment: When performing a one level CMR, the CMP engine succeeds. However, if you start relating more than one table in a nested fashion the CMP engine produces errors. The test that I ran performed a master -- detail1 -- detail2 relationship. I can submit these files if they are needed. The test produced the following stack trace. I have added additional debugging code the CMP classes for clarity. 2002-04-01 12:44:20,265 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCFindByPrimaryKeyQue ry.MEntity.findByPrimaryKey] Executing SQL: SELECT field1 FROM coM WHERE field1=? 2002-04-01 12:44:20,312 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.MEntity.field1] PrimaryKey: dms.framework.tests.MEntityPK@35135a, value: 1 2002-04-01 12:44:20,312 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.MEntity.field1] Meta Data: Column Name: field1 2002-04-01 12:44:20,312 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.MEntity.field1] Meta Data: Field Name: field1 2002-04-01 12:44:20,312 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.MEntity.field1] Meta Data: Field Type: int 2002-04-01 12:44:20,312 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.MEntity.field1] Meta Data: PK Field name: field1 2002-04-01 12:44:20,312 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.MEntity.field1] Meta Data: PK Field type: int 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand .MEntity] Object PK: dms.framework.tests.MEntityPK@35135a 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand .MEntity] Key Fields: [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge@2fbf49] 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand .MEntity] Related Key Fields: [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge@377d92] 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand .MEntity] Preload Fields: [] 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand .MEntity] Relation Table: coD1 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand .MEntity] Related Table: coD1 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand .MEntity] Key Count: 1 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand .MEntity] Do Join: false 2002-04-01 12:44:20,343 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand .MEntity] Executing SQL: SELECT field1 FROM coD1 WHERE (detail1=?) 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.D1Entity.field1] PrimaryKey: dms.framework.tests.D1EntityPK@6bf551, value: 1 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.D1Entity.field1] Meta Data: Column Name: field1 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.D1Entity.field1] Meta Data: Field Name: field1 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.D1Entity.field1] Meta Data: Field Type: int 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.D1Entity.field1] Meta Data: PK Field name: field1 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.D1Entity.field1] Meta Data: PK Field type: int 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.D1Entity.field1] PrimaryKey: dms.framework.tests.D1EntityPK@2aa392, value: 2 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.D1Entity.field1] Meta Data: Column Name: field1 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.D1Entity.field1] Meta Data: Field Name: field1 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.D1Entity.field1] Meta Data: Field Type: int 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.D1Entity.field1] Meta Data: PK Field name: field1 2002-04-01 12:44:20,343 INFO [org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP2xFieldBr idge.D1Entity.field1] Meta Data: PK Field type: int 2002-04-01 12:44:20,375 INFO [org.jboss.ejb.plugins.cmp.jdbc.JDBCLoadRelationCommand .D1Entity] Object PK: dms.framework.tests.D1EntityPK@6bf551 2002-04-01 12:44:20,375 INFO
Re: [JBoss-dev] Possible bug ?
Could you run the naming tests and tell me what you get? testsuite/build.sh -Dtest=naming test (for linux, I hope you can translate) I was having a similar (I think) problem which Scott and others could not reproduce. I added the InternalNamingClassReplacementUnitTestCase which shows the problem I have in one step. Running the ejb link test twice also demonstrates it. Thanks david jencks On 2002.04.18 10:07:10 -0400 JL@esial wrote: Hello, I am running JBoss 3.1.0alpha(200204181002) on Win2k SP2 with jdk 1.4. I have a problem, and I do not know what it is related to, my application or JBoss. Let me explain: I have n CMP 2.x entity beans with local interfaces. For testing purposes, I use a stateless session bean to access those entity beans. This session bean itself is instanciated within a servlet. Here is the code used in the servlet init method: InitialContext jndiContext = new InitialContext(); Object ref = jndiContext.lookup(ejb/ServiceBean); ServiceBeanHome home = (ServiceBeanHome) PortableRemoteObject.narrow(ref, ServiceBeanHome.class ); target = home.create(); My ejb-jar.xml is ok, my web.xml defines an ejb-ref which in turn is defined in jboss-web.xml. As a matter of fact, everything works fine on first deployment. The problem is that if I modify the ear file, and then redeploy it, I get a ClassCastException on PortableRemoteObject.narrow. I read a bug report a while ago (#516684) which was related to a problem looking like this one. There was a patch by David Jencks which consisted in using the remote interface ClassLoader to get the class descriptor instead of the one in the loading thread. But it does not work here, the problem remains. I tought it was related to my own code, but then why would it work on first deploy, and not after redeploy ? Could it be anything related to the ClassLoader ? Or is there anything else that needs to be configured inside JBoss when using servlets ? Thanks, Jerome. 2002-04-18 12:38:59,510 ERROR [STDERR] java.lang.ClassCastException 2002-04-18 12:38:59,510 ERROR [STDERR]at com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:293) 2002-04-18 12:38:59,510 ERROR [STDERR]at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:134) 2002-04-18 12:38:59,510 ERROR [STDERR]at mypackage.init(MyServlet.java:37) 2002-04-18 12:38:59,510 ERROR [STDERR]at org.mortbay.jetty.servlet.ServletHolder.getServlet(ServletHolder.java:261) 2002-04-18 12:38:59,510 ERROR [STDERR]at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:308) 2002-04-18 12:38:59,510 ERROR [STDERR]at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:595) 2002-04-18 12:38:59,510 ERROR [STDERR]at org.mortbay.http.HttpContext.handle(HttpContext.java:1357) 2002-04-18 12:38:59,510 ERROR [STDERR]at org.mortbay.http.HttpContext.handle(HttpContext.java:1309) 2002-04-18 12:38:59,510 ERROR [STDERR]at org.mortbay.http.HttpServer.service(HttpServer.java:744) 2002-04-18 12:38:59,510 ERROR [STDERR]at org.jboss.jetty.Jetty.service(Jetty.java:527) 2002-04-18 12:38:59,510 ERROR [STDERR]at org.mortbay.http.HttpConnection.service(HttpConnection.java:743) 2002-04-18 12:38:59,510 ERROR [STDERR]at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:916) 2002-04-18 12:38:59,510 ERROR [STDERR]at org.mortbay.http.HttpConnection.handle(HttpConnection.java:758) 2002-04-18 12:38:59,510 ERROR [STDERR]at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:145) 2002-04-18 12:38:59,520 ERROR [STDERR]at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) 2002-04-18 12:38:59,520 ERROR [STDERR]at org.mortbay.util.ThreadPool$JobRunner.run(ThreadPool.java:715) 2002-04-18 12:38:59,520 ERROR [STDERR]at java.lang.Thread.run(Thread.java:536) * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=1 ___ 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
Re: [JBoss-dev] tomcat4 log dir in jboss3-rc1
The sourceforge project page is the gateway to all requests: http://sourceforge.net/projects/jboss/ Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: David Ward [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; Scott M Stark [EMAIL PROTECTED] Sent: Thursday, April 18, 2002 9:59 AM Subject: [JBoss-dev] tomcat4 log dir in jboss3-rc1 I don't know the ins-and-outs of creating a change request, but was wondering if for the next rc of jboss3-tomcat4 the tomcat4-service.xml file could be changed in this way: From this: Valve className = org.apache.catalina.valves.AccessLogValve prefix = localhost_access suffix = .log pattern = common directory = ../jboss/log / To this: Valve className = org.apache.catalina.valves.AccessLogValve prefix = localhost_access suffix = .log pattern = common directory = ../server/default/log / Currently it assumes the old JBoss-2.4.x-Tomcat-x.x.x dir structure where jboss and tomcat/catalina were next to eachother as subdirs, which isn't the case anymore. Thanks, David As an aside, I like how the Ajp13 connector example is included in the XML, but personally I think it would be cool to (leave it in there) but comment it out by default. Maybe also include (but leave commented out) Warp - and maybe the new Coyote (http://cvs.apache.org/viewcvs/jakarta-tomcat-connectors/coyote/)? - Connector lines. Thanks again. ___ 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] CVS update: jboss/src/main/org/jboss/ejb LocalHomeObjectFactory.java
User: starksm Date: 02/04/18 09:48:46 Removed: src/main/org/jboss/ejb Tag: Branch_3_0 LocalHomeObjectFactory.java Log: Remove obsolete jndi object factory ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/cts/META-INF ejb-jar.xml jboss.xml
User: starksm Date: 02/04/18 09:52:54 Modified:src/resources/cts/META-INF Tag: Branch_3_0 ejb-jar.xml jboss.xml Log: Add a local entity interface and set the stateful session container max cache size to 1 to force passivation for testing Revision ChangesPath No revision No revision 1.8.2.1 +73 -68jbosstest/src/resources/cts/META-INF/ejb-jar.xml Index: ejb-jar.xml === RCS file: /cvsroot/jboss/jbosstest/src/resources/cts/META-INF/ejb-jar.xml,v retrieving revision 1.8 retrieving revision 1.8.2.1 diff -u -r1.8 -r1.8.2.1 --- ejb-jar.xml 16 Feb 2002 05:37:35 - 1.8 +++ ejb-jar.xml 18 Apr 2002 16:52:54 - 1.8.2.1 @@ -1,74 +1,79 @@ ?xml version=1.0 encoding=UTF-8? ejb-jar - descriptionjBoss CTS application/description - display-namejBoss CTS/display-name - enterprise-beans - session - display-nameStateless Session/display-name - ejb-nameStatelessSessionBean/ejb-name - homeorg.jboss.test.cts.interfaces.StatelessSessionHome/home - remoteorg.jboss.test.cts.interfaces.StatelessSession/remote - ejb-classorg.jboss.test.cts.ejb.StatelessSessionBean/ejb-class - session-typeStateless/session-type - transaction-typeContainer/transaction-type - /session - session - display-nameStateful Session/display-name - ejb-nameStatefulSessionBean/ejb-name - homeorg.jboss.test.cts.interfaces.StatefulSessionHome/home - remoteorg.jboss.test.cts.interfaces.StatefulSession/remote - ejb-classorg.jboss.test.cts.ejb.StatefulSessionBean/ejb-class - session-typeStateful/session-type - transaction-typeContainer/transaction-type - security-role-ref -descriptionThis is to test the isCallerInRole( ) method on the SessionBean./description -role-namebean tester/role-name - /security-role-ref - /session - entity - descriptionTest for BEAN managed persistence/description - ejb-nameBMPBean/ejb-name - homeorg.jboss.test.cts.interfaces.CtsBmpHome/home - remoteorg.jboss.test.cts.interfaces.CtsBmp/remote - ejb-classorg.jboss.test.cts.ejb.CtsBmpBean/ejb-class - persistence-typeBean/persistence-type - prim-key-classorg.jboss.test.cts.keys.AccountPK/prim-key-class - reentrantTrue/reentrant - resource-ref -res-ref-namedatasource/res-ref-name -res-typejavax.sql.DataSource/res-type -res-authContainer/res-auth - /resource-ref - /entity - entity - descriptionTest for BEAN managed persistence (Callbacks)/description - ejb-nameBMPCallbackBean/ejb-name - homeorg.jboss.test.cts.interfaces.BmpCallbackHome/home - remoteorg.jboss.test.cts.interfaces.BmpCallback/remote - ejb-classorg.jboss.test.cts.ejb.BmpCallbackBean/ejb-class - persistence-typeBean/persistence-type - prim-key-classorg.jboss.test.cts.keys.AccountPK/prim-key-class - reentrantTrue/reentrant - resource-ref -res-ref-namedatasource/res-ref-name -res-typejavax.sql.DataSource/res-type -res-authContainer/res-auth - /resource-ref - /entity - entity - descriptionTest for CONTAINER managed persistence /description - ejb-nameCMPBean/ejb-name - homeorg.jboss.test.cts.interfaces.CtsCmpHome/home - remoteorg.jboss.test.cts.interfaces.CtsCmp/remote - ejb-classorg.jboss.test.cts.ejb.CtsCmpBean/ejb-class - persistence-typeContainer/persistence-type - prim-key-classorg.jboss.test.cts.keys.AccountPK/prim-key-class - reentrantTrue/reentrant + descriptionjBoss CTS application/description + display-namejBoss CTS/display-name + enterprise-beans + session + display-nameStateless Session/display-name + ejb-nameStatelessSessionBean/ejb-name + homeorg.jboss.test.cts.interfaces.StatelessSessionHome/home + remoteorg.jboss.test.cts.interfaces.StatelessSession/remote + ejb-classorg.jboss.test.cts.ejb.StatelessSessionBean/ejb-class + session-typeStateless/session-type + transaction-typeContainer/transaction-type + /session + session + display-nameStateful Session/display-name + ejb-nameStatefulSessionBean/ejb-name + homeorg.jboss.test.cts.interfaces.StatefulSessionHome/home + remoteorg.jboss.test.cts.interfaces.StatefulSession/remote + ejb-classorg.jboss.test.cts.ejb.StatefulSessionBean/ejb-class + session-typeStateful/session-type + transaction-typeContainer/transaction-type + ejb-local-ref +ejb-ref-nameejb/CMPBeanLocalHome/ejb-ref-name +
[JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb/plugins/local EntityProxy.java StatefulSessionProxy.java StatelessSessionProxy.java BaseLocalContainerInvoker.java LocalHomeProxy.java LocalProxy.java
User: starksm
Date: 02/04/18 09:44:33
Modified:src/main/org/jboss/ejb/plugins/local Tag: Branch_3_0
BaseLocalContainerInvoker.java LocalHomeProxy.java
LocalProxy.java
Added: src/main/org/jboss/ejb/plugins/local Tag: Branch_3_0
EntityProxy.java StatefulSessionProxy.java
StatelessSessionProxy.java
Log:
Make the local and local home interface handlers serializable to simplify
binding into jndi and passivation of references
Revision ChangesPath
No revision
No revision
1.21.2.1 +81 -297
jboss/src/main/org/jboss/ejb/plugins/local/BaseLocalContainerInvoker.java
Index: BaseLocalContainerInvoker.java
===
RCS file:
/cvsroot/jboss/jboss/src/main/org/jboss/ejb/plugins/local/BaseLocalContainerInvoker.java,v
retrieving revision 1.21
retrieving revision 1.21.2.1
diff -u -r1.21 -r1.21.2.1
--- BaseLocalContainerInvoker.java12 Apr 2002 19:30:44 - 1.21
+++ BaseLocalContainerInvoker.java18 Apr 2002 16:44:32 - 1.21.2.1
@@ -6,59 +6,44 @@
*/
package org.jboss.ejb.plugins.local;
-import java.awt.Component;
-import java.io.File;
-import java.io.IOException;
+import java.lang.reflect.InvocationHandler;
import java.lang.reflect.Method;
-import java.lang.reflect.Constructor;
+import java.lang.reflect.Proxy;
+import java.rmi.AccessException;
+import java.rmi.NoSuchObjectException;
import java.security.Principal;
import java.util.ArrayList;
import java.util.Collection;
+import java.util.Collections;
+import java.util.HashMap;
import java.util.Iterator;
import java.util.Map;
-import java.util.HashMap;
-import java.util.Properties;
-import java.lang.reflect.InvocationHandler;
-import java.lang.reflect.Proxy;
-
-import javax.ejb.EJBMetaData;
+import javax.ejb.AccessLocalException;
import javax.ejb.EJBLocalHome;
import javax.ejb.EJBLocalObject;
-import javax.ejb.AccessLocalException;
-import java.rmi.AccessException;
+import javax.ejb.EJBMetaData;
import javax.ejb.NoSuchObjectLocalException;
-import java.rmi.NoSuchObjectException;
import javax.ejb.TransactionRequiredLocalException;
-import javax.transaction.TransactionRequiredException;
import javax.ejb.TransactionRolledbackLocalException;
-import javax.transaction.TransactionRolledbackException;
-
-import javax.naming.Name;
-import javax.naming.InitialContext;
import javax.naming.Context;
-import javax.naming.NamingException;
+import javax.naming.InitialContext;
+import javax.naming.Name;
import javax.naming.NameNotFoundException;
-import javax.naming.Reference;
-import javax.naming.StringRefAddr;
-
+import javax.naming.NamingException;
import javax.transaction.Transaction;
import javax.transaction.TransactionManager;
+import javax.transaction.TransactionRequiredException;
+import javax.transaction.TransactionRolledbackException;
import org.jboss.ejb.Container;
import org.jboss.ejb.ContainerInvokerContainer;
-import org.jboss.ejb.Interceptor;
import org.jboss.ejb.LocalContainerInvoker;
-import org.jboss.ejb.LocalHomeObjectFactory;
-import org.jboss.deployment.DeploymentException;
import org.jboss.invocation.Invocation;
import org.jboss.invocation.MarshalledInvocation;
import org.jboss.logging.Logger;
-import org.jboss.metadata.MetaData;
-import org.jboss.metadata.EntityMetaData;
-import org.jboss.metadata.SessionMetaData;
+import org.jboss.metadata.BeanMetaData;
import org.jboss.naming.Util;
import org.jboss.security.SecurityAssociation;
-import org.jboss.tm.TransactionPropagationContextFactory;
/** The LocalContainerInvoker implementation that handles local ejb interface
@@ -71,31 +56,27 @@
{
// Attributes
protected static Logger log = Logger.getLogger(BaseLocalContainerInvoker.class);
+ /** A map of the BaseLocalContainerInvoker instances keyed by localJndiName */
+ protected static Map invokerMap = Collections.synchronizedMap(new HashMap());
+
protected Container container;
- protected String jndiName;
+ /** The JNDI name of the local home interface binding */
+ protected String localJndiName;
protected TransactionManager transactionManager;
// The home can be one.
protected EJBLocalHome home;
// The Stateless Object can be one.
protected EJBLocalObject statelessObject;
-
+
protected Map beanMethodInvokerMap;
protected Map homeMethodInvokerMap;
// Static
- private static TransactionPropagationContextFactory tpcFactory;
-
// Constructors
[JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb/plugins/local EntityProxy.java StatefulSessionProxy.java StatelessSessionProxy.java BaseLocalContainerInvoker.java LocalHomeProxy.java LocalProxy.java
User: starksm
Date: 02/04/18 09:45:23
Modified:src/main/org/jboss/ejb/plugins/local
BaseLocalContainerInvoker.java LocalHomeProxy.java
LocalProxy.java
Added: src/main/org/jboss/ejb/plugins/local EntityProxy.java
StatefulSessionProxy.java
StatelessSessionProxy.java
Log:
Make the local and local home interface handlers serializable to simplify
binding into jndi and passivation of references
Revision ChangesPath
1.22 +81 -297
jboss/src/main/org/jboss/ejb/plugins/local/BaseLocalContainerInvoker.java
Index: BaseLocalContainerInvoker.java
===
RCS file:
/cvsroot/jboss/jboss/src/main/org/jboss/ejb/plugins/local/BaseLocalContainerInvoker.java,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- BaseLocalContainerInvoker.java12 Apr 2002 19:30:44 - 1.21
+++ BaseLocalContainerInvoker.java18 Apr 2002 16:45:22 - 1.22
@@ -6,59 +6,44 @@
*/
package org.jboss.ejb.plugins.local;
-import java.awt.Component;
-import java.io.File;
-import java.io.IOException;
+import java.lang.reflect.InvocationHandler;
import java.lang.reflect.Method;
-import java.lang.reflect.Constructor;
+import java.lang.reflect.Proxy;
+import java.rmi.AccessException;
+import java.rmi.NoSuchObjectException;
import java.security.Principal;
import java.util.ArrayList;
import java.util.Collection;
+import java.util.Collections;
+import java.util.HashMap;
import java.util.Iterator;
import java.util.Map;
-import java.util.HashMap;
-import java.util.Properties;
-import java.lang.reflect.InvocationHandler;
-import java.lang.reflect.Proxy;
-
-import javax.ejb.EJBMetaData;
+import javax.ejb.AccessLocalException;
import javax.ejb.EJBLocalHome;
import javax.ejb.EJBLocalObject;
-import javax.ejb.AccessLocalException;
-import java.rmi.AccessException;
+import javax.ejb.EJBMetaData;
import javax.ejb.NoSuchObjectLocalException;
-import java.rmi.NoSuchObjectException;
import javax.ejb.TransactionRequiredLocalException;
-import javax.transaction.TransactionRequiredException;
import javax.ejb.TransactionRolledbackLocalException;
-import javax.transaction.TransactionRolledbackException;
-
-import javax.naming.Name;
-import javax.naming.InitialContext;
import javax.naming.Context;
-import javax.naming.NamingException;
+import javax.naming.InitialContext;
+import javax.naming.Name;
import javax.naming.NameNotFoundException;
-import javax.naming.Reference;
-import javax.naming.StringRefAddr;
-
+import javax.naming.NamingException;
import javax.transaction.Transaction;
import javax.transaction.TransactionManager;
+import javax.transaction.TransactionRequiredException;
+import javax.transaction.TransactionRolledbackException;
import org.jboss.ejb.Container;
import org.jboss.ejb.ContainerInvokerContainer;
-import org.jboss.ejb.Interceptor;
import org.jboss.ejb.LocalContainerInvoker;
-import org.jboss.ejb.LocalHomeObjectFactory;
-import org.jboss.deployment.DeploymentException;
import org.jboss.invocation.Invocation;
import org.jboss.invocation.MarshalledInvocation;
import org.jboss.logging.Logger;
-import org.jboss.metadata.MetaData;
-import org.jboss.metadata.EntityMetaData;
-import org.jboss.metadata.SessionMetaData;
+import org.jboss.metadata.BeanMetaData;
import org.jboss.naming.Util;
import org.jboss.security.SecurityAssociation;
-import org.jboss.tm.TransactionPropagationContextFactory;
/** The LocalContainerInvoker implementation that handles local ejb interface
@@ -71,31 +56,27 @@
{
// Attributes
protected static Logger log = Logger.getLogger(BaseLocalContainerInvoker.class);
+ /** A map of the BaseLocalContainerInvoker instances keyed by localJndiName */
+ protected static Map invokerMap = Collections.synchronizedMap(new HashMap());
+
protected Container container;
- protected String jndiName;
+ /** The JNDI name of the local home interface binding */
+ protected String localJndiName;
protected TransactionManager transactionManager;
// The home can be one.
protected EJBLocalHome home;
// The Stateless Object can be one.
protected EJBLocalObject statelessObject;
-
+
protected Map beanMethodInvokerMap;
protected Map homeMethodInvokerMap;
// Static
- private static TransactionPropagationContextFactory tpcFactory;
-
// Constructors --
// Public
-
- public
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/cts/keys AccountPK.java
User: starksm
Date: 02/04/18 09:55:37
Modified:src/main/org/jboss/test/cts/keys Tag: Branch_3_0
AccountPK.java
Log:
Add a local entity interface and testing of stateful session passivation
of a bean that includes a java:comp/env context and local interface
as instance session variables
Revision ChangesPath
No revision
No revision
1.3.2.1 +3 -8 jbosstest/src/main/org/jboss/test/cts/keys/AccountPK.java
Index: AccountPK.java
===
RCS file: /cvsroot/jboss/jbosstest/src/main/org/jboss/test/cts/keys/AccountPK.java,v
retrieving revision 1.3
retrieving revision 1.3.2.1
diff -u -r1.3 -r1.3.2.1
--- AccountPK.java9 Mar 2002 01:21:03 - 1.3
+++ AccountPK.java18 Apr 2002 16:55:37 - 1.3.2.1
@@ -1,18 +1,14 @@
package org.jboss.test.cts.keys;
-
-
-import java.io.*;
-
+import java.io.Serializable;
/**
* Class AccountPK
*
*
- * @author
- * @version %I%, %G%
+ * @author [EMAIL PROTECTED]
+ * @version $Revision: 1.3.2.1 $
*/
-
public class AccountPK
implements Serializable
{
@@ -69,6 +65,5 @@
}
}
-
/*-- Formatted by Jindent 3.23 Basic 1.0 --- http://www.jindent.de --*/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/cts/ejb CtsCmpBean.java StatefulSessionBean.java
User: starksm
Date: 02/04/18 09:55:36
Modified:src/main/org/jboss/test/cts/ejb Tag: Branch_3_0
CtsCmpBean.java StatefulSessionBean.java
Log:
Add a local entity interface and testing of stateful session passivation
of a bean that includes a java:comp/env context and local interface
as instance session variables
Revision ChangesPath
No revision
No revision
1.2.2.1 +8 -167jbosstest/src/main/org/jboss/test/cts/ejb/CtsCmpBean.java
Index: CtsCmpBean.java
===
RCS file: /cvsroot/jboss/jbosstest/src/main/org/jboss/test/cts/ejb/CtsCmpBean.java,v
retrieving revision 1.2
retrieving revision 1.2.2.1
diff -u -r1.2 -r1.2.2.1
--- CtsCmpBean.java 15 Feb 2002 06:15:51 - 1.2
+++ CtsCmpBean.java 18 Apr 2002 16:55:36 - 1.2.2.1
@@ -1,90 +1,32 @@
package org.jboss.test.cts.ejb;
-import org.jboss.test.cts.keys.*;
import java.rmi.RemoteException;
-import java.util.Vector;
-import java.util.Collection;
-import java.sql.*;
import javax.naming.*;
import javax.ejb.*;
-import javax.sql.DataSource;
+import org.jboss.test.cts.keys.AccountPK;
public class CtsCmpBean
implements EntityBean
{
org.apache.log4j.Category log =
org.apache.log4j.Category.getInstance(getClass());
- EntityContext ctx= null;
- DataSource ds = null;
+ EntityContext ctx = null;
// cmp fields
public AccountPK pk;
- public String accountNumber;
public String personsName;
- /**
-* Method ejbCreate
-*
-*
-* @param pk
-* @param personsName
-*
-* @return
-*
-* @throws CreateException
-* @throws DuplicateKeyException
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public AccountPK ejbCreate (AccountPK pk, String personsName)
throws CreateException, DuplicateKeyException, EJBException,
RemoteException
{
- log.debug(entry ejbCreate);
-
- return new AccountPK(accountNumber);
- }
-
- /**
-* Method ejbFindByPrimaryKey
-*
-*
-* @param pk
-*
-* @return
-*
-* @throws EJBException
-* @throws FinderException
-* @throws RemoteException
-*
-*/
-
- public AccountPK ejbFindByPrimaryKey (AccountPK pk)
- throws FinderException, EJBException, RemoteException
- {
- log.debug(entry ejbFindByPrimaryKey);
-
- return pk;
+ log.debug(entry ejbCreate, pk=+pk);
+ this.pk = pk;
+ this.personsName = personsName;
+ return null;
}
-
- /**
-* Method ejbPostCreate
-*
-*
-* @param pk
-* @param personsName
-*
-* @throws CreateException
-* @throws DuplicateKeyException
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public void ejbPostCreate (AccountPK pk, String personsName)
throws CreateException, DuplicateKeyException, EJBException,
RemoteException
@@ -92,15 +34,6 @@
log.debug(ejbPostCreate (AccountPK, String) called);
}
- /**
-* Method ejbLoad
-*
-*
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public void ejbLoad ()
throws EJBException, RemoteException
{
@@ -108,15 +41,6 @@
}
- /**
-* Method ejbStore
-*
-*
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public void ejbStore ()
throws EJBException, RemoteException
{
@@ -124,15 +48,6 @@
}
- /**
-* Method ejbRemove
-*
-*
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public void ejbRemove ()
throws EJBException, RemoteException
{
@@ -140,75 +55,24 @@
}
- /**
-* Method ejbActivate
-*
-*
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public void ejbActivate ()
throws EJBException, RemoteException
{
log.debug(ejbActivate () called);
}
- /**
-* Method ejbPassivate
-*
-*
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public void ejbPassivate ()
throws EJBException, RemoteException
{
log.debug(ejbPassivate () called);
}
- /**
-* Method setEntityContext
-*
-*
-* @param ctx
-*
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public void setEntityContext (EntityContext ctx)
throws
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/cts/test StatefulSessionUnitTestCase.java
User: starksm
Date: 02/04/18 09:55:38
Modified:src/main/org/jboss/test/cts/test Tag: Branch_3_0
StatefulSessionUnitTestCase.java
Log:
Add a local entity interface and testing of stateful session passivation
of a bean that includes a java:comp/env context and local interface
as instance session variables
Revision ChangesPath
No revision
No revision
1.3.2.1 +134 -323
jbosstest/src/main/org/jboss/test/cts/test/StatefulSessionUnitTestCase.java
Index: StatefulSessionUnitTestCase.java
===
RCS file:
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/cts/test/StatefulSessionUnitTestCase.java,v
retrieving revision 1.3
retrieving revision 1.3.2.1
diff -u -r1.3 -r1.3.2.1
--- StatefulSessionUnitTestCase.java 29 Jan 2002 22:00:01 - 1.3
+++ StatefulSessionUnitTestCase.java 18 Apr 2002 16:55:37 - 1.3.2.1
@@ -15,6 +15,7 @@
import java.rmi.ServerException;
import javax.ejb.Handle;
+import javax.ejb.RemoveException;
import javax.naming.InitialContext;
import javax.naming.Context;
import javax.rmi.PortableRemoteObject;
@@ -36,27 +37,51 @@
* @see related
* @author Author: kimptoc
* @author Author: d_jencks converted to JBossTestCase, added logging.
- * @version $Revision: 1.3 $
+ * @version $Revision: 1.3.2.1 $
*/
-
public class StatefulSessionUnitTestCase
extends JBossTestCase
{
- static boolean deployed = false;
-
- /**
-* Constructor Main
-*
-*
-* @param name
-*
-*/
-
public StatefulSessionUnitTestCase (String name)
{
super(name);
}
+ /** Create a StatefulSessionBean and then create a local interface to
+an entity in the session. This bean is then passivated by creating another
+session bean and then activated by invoking a business method. The
+purpose is to test that the session is passivated and that the local
+interface is restored.
+ */
+ public void testLocalInterfacePassivation() throws Exception
+ {
+ Context ctx = new InitialContext();
+ getLog().debug(+++ testLocalInterfacePassivation);
+ StatefulSessionHome sessionHome = ( StatefulSessionHome )
ctx.lookup(ejbcts/StatefulSessionBean);
+ StatefulSession sessionBean = sessionHome.create();
+
+ getLog().debug(Creating local home);
+ AccountPK pk = new AccountPK(123456789);
+ sessionBean.createLocalEntity(pk, jduke);
+
+ getLog().debug(Creating a second session bean, forcing the first one to be
passivated?);
+ // The pool size has been set to 1 in the container
+ // config, so creating another ASession here should
+ // cause the first one to be passivated.
+ StatefulSession anotherSession = sessionHome.create();
+ getLog().debug(OK);
+
+ getLog().debug(Checking for complete passivation/activation);
+ assertTrue(sessionBean.getWasPassivated() == true);
+ getLog().debug(OK);
+
+ // Some other checks
+ getLog().debug(Checking reactivation of session bean attributes);
+ String name = sessionBean.readAndRemoveEntity();
+ assertTrue(name.equals(jduke));
+ getLog().debug(OK);
+ }
+
/**
* EJB 1.1 (Page 40)
* The container is responsible for making the home interfaces
@@ -107,7 +132,6 @@
* @throws Exception
*
*/
-
public void testEJBHomeInterface ()
throws Exception
{
@@ -172,45 +196,27 @@
* method on a session results in the javax.ejb.RemoveException.
*
*/
-
public void testRemoveSessionObject ()
+ throws Exception
{
getLog().debug(
**);
getLog().debug( testRemoveSessionObject());
- StatefulSession sessionBean = null;
-
+ Context ctx = new InitialContext();
+ StatefulSessionHome home = ( StatefulSessionHome )
ctx.lookup(ejbcts/StatefulSessionBean);
+ StatefulSession bean = home.create();
+ getLog().debug(OK);
+ getLog().debug(Call remove using a primary key);
try
{
- Properties props = System.getProperties();
-
- getLog().debug(Obtain home interface);
-
- // Create a new session object
- Context ctx = new InitialContext(props);
- StatefulSessionHome home =
-( StatefulSessionHome ) ctx.lookup(ejbcts/StatefulSessionBean);
-
- sessionBean = home.create();
- getLog().debug(OK);
- getLog().debug(Call remove using a primary key);
home.remove(new AccountPK(pk));
-
+ fail([EJB 1.1, p42, section
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/cts/interfaces CtsCmpLocal.java CtsCmpLocalHome.java CtsCmpHome.java StatefulSession.java
User: starksm
Date: 02/04/18 09:55:37
Modified:src/main/org/jboss/test/cts/interfaces Tag: Branch_3_0
CtsCmpHome.java StatefulSession.java
Added: src/main/org/jboss/test/cts/interfaces Tag: Branch_3_0
CtsCmpLocal.java CtsCmpLocalHome.java
Log:
Add a local entity interface and testing of stateful session passivation
of a bean that includes a java:comp/env context and local interface
as instance session variables
Revision ChangesPath
No revision
No revision
1.1.6.1 +8 -46 jbosstest/src/main/org/jboss/test/cts/interfaces/CtsCmpHome.java
Index: CtsCmpHome.java
===
RCS file:
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/cts/interfaces/CtsCmpHome.java,v
retrieving revision 1.1
retrieving revision 1.1.6.1
diff -u -r1.1 -r1.1.6.1
--- CtsCmpHome.java 18 Feb 2001 16:04:45 - 1.1
+++ CtsCmpHome.java 18 Apr 2002 16:55:37 - 1.1.6.1
@@ -1,58 +1,20 @@
package org.jboss.test.cts.interfaces;
-
-
-import org.jboss.test.cts.keys.*;
import java.rmi.RemoteException;
-import java.util.Collection;
-import javax.ejb.*;
+import javax.ejb.CreateException;
+import javax.ejb.DuplicateKeyException;
+import javax.ejb.FinderException;
+
+import org.jboss.test.cts.keys.AccountPK;
public interface CtsCmpHome
- extends EJBHome
+ extends javax.ejb.EJBHome
{
-
- /**
-* Method create
-*
-*
-* @param pk
-* @param personsName
-*
-* @return
-*
-* @throws CreateException
-* @throws DuplicateKeyException
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public CtsCmp create (AccountPK pk, String personsName)
- throws CreateException, DuplicateKeyException, EJBException,
+ throws CreateException, DuplicateKeyException,
RemoteException;
- /**
-* Method findByPrimaryKey
-*
-*
-* @param pk
-*
-* @return
-*
-* @throws EJBException
-* @throws FinderException
-* @throws RemoteException
-*
-*/
-
public CtsCmp findByPrimaryKey (AccountPK pk)
- throws FinderException, EJBException, RemoteException;
+ throws FinderException, RemoteException;
}
-
-
-/*-- Formatted by Jindent 3.23 Basic 1.0 --- http://www.jindent.de --*/
-
-
-
-
1.7.6.1 +13 -7
jbosstest/src/main/org/jboss/test/cts/interfaces/StatefulSession.java
Index: StatefulSession.java
===
RCS file:
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/cts/interfaces/StatefulSession.java,v
retrieving revision 1.7
retrieving revision 1.7.6.1
diff -u -r1.7 -r1.7.6.1
--- StatefulSession.java 25 Jan 2001 02:45:36 - 1.7
+++ StatefulSession.java 18 Apr 2002 16:55:37 - 1.7.6.1
@@ -1,8 +1,6 @@
package org.jboss.test.cts.interfaces;
-
-
-import org.jboss.test.util.ejb.*;
+import org.jboss.test.cts.keys.AccountPK;
import javax.ejb.*;
@@ -10,10 +8,9 @@
* Interface StatefulSession
*
*
- * @author
- * @version %I%, %G%
+ * @author [EMAIL PROTECTED]
+ * @version $Revision: 1.7.6.1 $
*/
-
public interface StatefulSession
extends EJBObject
{
@@ -117,7 +114,16 @@
public void loopbackTest (EJBObject obj)
throws java.rmi.RemoteException;
-}
+
+ public boolean getWasPassivated()
+ throws java.rmi.RemoteException;
+
+ public void createLocalEntity(AccountPK pk, String personsName)
+ throws javax.ejb.CreateException, java.rmi.RemoteException;
+
+ public String readAndRemoveEntity()
+ throws javax.ejb.RemoveException, java.rmi.RemoteException;
+}
/*-- Formatted by Jindent 3.23 Basic 1.0 --- http://www.jindent.de --*/
No revision
No revision
1.1.2.1 +10 -0
jbosstest/src/main/org/jboss/test/cts/interfaces/Attic/CtsCmpLocal.java
1.1.2.1 +16 -0
jbosstest/src/main/org/jboss/test/cts/interfaces/Attic/CtsCmpLocalHome.java
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/cts/keys AccountPK.java
User: starksm
Date: 02/04/18 10:05:02
Modified:src/main/org/jboss/test/cts/keys AccountPK.java
Log:
Add a local entity interface and testing of stateful session passivation
of a bean that includes a java:comp/env context and local interface
as instance session variables
Revision ChangesPath
1.4 +3 -8 jbosstest/src/main/org/jboss/test/cts/keys/AccountPK.java
Index: AccountPK.java
===
RCS file: /cvsroot/jboss/jbosstest/src/main/org/jboss/test/cts/keys/AccountPK.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- AccountPK.java9 Mar 2002 01:21:03 - 1.3
+++ AccountPK.java18 Apr 2002 17:05:02 - 1.4
@@ -1,18 +1,14 @@
package org.jboss.test.cts.keys;
-
-
-import java.io.*;
-
+import java.io.Serializable;
/**
* Class AccountPK
*
*
- * @author
- * @version %I%, %G%
+ * @author [EMAIL PROTECTED]
+ * @version $Revision: 1.4 $
*/
-
public class AccountPK
implements Serializable
{
@@ -69,6 +65,5 @@
}
}
-
/*-- Formatted by Jindent 3.23 Basic 1.0 --- http://www.jindent.de --*/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/cts/interfaces CtsCmpLocal.java CtsCmpLocalHome.java CtsCmpHome.java StatefulSession.java
User: starksm
Date: 02/04/18 10:05:02
Modified:src/main/org/jboss/test/cts/interfaces CtsCmpHome.java
StatefulSession.java
Added: src/main/org/jboss/test/cts/interfaces CtsCmpLocal.java
CtsCmpLocalHome.java
Log:
Add a local entity interface and testing of stateful session passivation
of a bean that includes a java:comp/env context and local interface
as instance session variables
Revision ChangesPath
1.2 +8 -46 jbosstest/src/main/org/jboss/test/cts/interfaces/CtsCmpHome.java
Index: CtsCmpHome.java
===
RCS file:
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/cts/interfaces/CtsCmpHome.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- CtsCmpHome.java 18 Feb 2001 16:04:45 - 1.1
+++ CtsCmpHome.java 18 Apr 2002 17:05:02 - 1.2
@@ -1,58 +1,20 @@
package org.jboss.test.cts.interfaces;
-
-
-import org.jboss.test.cts.keys.*;
import java.rmi.RemoteException;
-import java.util.Collection;
-import javax.ejb.*;
+import javax.ejb.CreateException;
+import javax.ejb.DuplicateKeyException;
+import javax.ejb.FinderException;
+
+import org.jboss.test.cts.keys.AccountPK;
public interface CtsCmpHome
- extends EJBHome
+ extends javax.ejb.EJBHome
{
-
- /**
-* Method create
-*
-*
-* @param pk
-* @param personsName
-*
-* @return
-*
-* @throws CreateException
-* @throws DuplicateKeyException
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public CtsCmp create (AccountPK pk, String personsName)
- throws CreateException, DuplicateKeyException, EJBException,
+ throws CreateException, DuplicateKeyException,
RemoteException;
- /**
-* Method findByPrimaryKey
-*
-*
-* @param pk
-*
-* @return
-*
-* @throws EJBException
-* @throws FinderException
-* @throws RemoteException
-*
-*/
-
public CtsCmp findByPrimaryKey (AccountPK pk)
- throws FinderException, EJBException, RemoteException;
+ throws FinderException, RemoteException;
}
-
-
-/*-- Formatted by Jindent 3.23 Basic 1.0 --- http://www.jindent.de --*/
-
-
-
-
1.8 +13 -7
jbosstest/src/main/org/jboss/test/cts/interfaces/StatefulSession.java
Index: StatefulSession.java
===
RCS file:
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/cts/interfaces/StatefulSession.java,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- StatefulSession.java 25 Jan 2001 02:45:36 - 1.7
+++ StatefulSession.java 18 Apr 2002 17:05:02 - 1.8
@@ -1,8 +1,6 @@
package org.jboss.test.cts.interfaces;
-
-
-import org.jboss.test.util.ejb.*;
+import org.jboss.test.cts.keys.AccountPK;
import javax.ejb.*;
@@ -10,10 +8,9 @@
* Interface StatefulSession
*
*
- * @author
- * @version %I%, %G%
+ * @author [EMAIL PROTECTED]
+ * @version $Revision: 1.8 $
*/
-
public interface StatefulSession
extends EJBObject
{
@@ -117,7 +114,16 @@
public void loopbackTest (EJBObject obj)
throws java.rmi.RemoteException;
-}
+
+ public boolean getWasPassivated()
+ throws java.rmi.RemoteException;
+
+ public void createLocalEntity(AccountPK pk, String personsName)
+ throws javax.ejb.CreateException, java.rmi.RemoteException;
+
+ public String readAndRemoveEntity()
+ throws javax.ejb.RemoveException, java.rmi.RemoteException;
+}
/*-- Formatted by Jindent 3.23 Basic 1.0 --- http://www.jindent.de --*/
1.2 +10 -0
jbosstest/src/main/org/jboss/test/cts/interfaces/CtsCmpLocal.java
1.2 +16 -0
jbosstest/src/main/org/jboss/test/cts/interfaces/CtsCmpLocalHome.java
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/cts/ejb CtsCmpBean.java StatefulSessionBean.java
User: starksm
Date: 02/04/18 10:05:02
Modified:src/main/org/jboss/test/cts/ejb CtsCmpBean.java
StatefulSessionBean.java
Log:
Add a local entity interface and testing of stateful session passivation
of a bean that includes a java:comp/env context and local interface
as instance session variables
Revision ChangesPath
1.3 +8 -167jbosstest/src/main/org/jboss/test/cts/ejb/CtsCmpBean.java
Index: CtsCmpBean.java
===
RCS file: /cvsroot/jboss/jbosstest/src/main/org/jboss/test/cts/ejb/CtsCmpBean.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- CtsCmpBean.java 15 Feb 2002 06:15:51 - 1.2
+++ CtsCmpBean.java 18 Apr 2002 17:05:02 - 1.3
@@ -1,90 +1,32 @@
package org.jboss.test.cts.ejb;
-import org.jboss.test.cts.keys.*;
import java.rmi.RemoteException;
-import java.util.Vector;
-import java.util.Collection;
-import java.sql.*;
import javax.naming.*;
import javax.ejb.*;
-import javax.sql.DataSource;
+import org.jboss.test.cts.keys.AccountPK;
public class CtsCmpBean
implements EntityBean
{
org.apache.log4j.Category log =
org.apache.log4j.Category.getInstance(getClass());
- EntityContext ctx= null;
- DataSource ds = null;
+ EntityContext ctx = null;
// cmp fields
public AccountPK pk;
- public String accountNumber;
public String personsName;
- /**
-* Method ejbCreate
-*
-*
-* @param pk
-* @param personsName
-*
-* @return
-*
-* @throws CreateException
-* @throws DuplicateKeyException
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public AccountPK ejbCreate (AccountPK pk, String personsName)
throws CreateException, DuplicateKeyException, EJBException,
RemoteException
{
- log.debug(entry ejbCreate);
-
- return new AccountPK(accountNumber);
- }
-
- /**
-* Method ejbFindByPrimaryKey
-*
-*
-* @param pk
-*
-* @return
-*
-* @throws EJBException
-* @throws FinderException
-* @throws RemoteException
-*
-*/
-
- public AccountPK ejbFindByPrimaryKey (AccountPK pk)
- throws FinderException, EJBException, RemoteException
- {
- log.debug(entry ejbFindByPrimaryKey);
-
- return pk;
+ log.debug(entry ejbCreate, pk=+pk);
+ this.pk = pk;
+ this.personsName = personsName;
+ return null;
}
-
- /**
-* Method ejbPostCreate
-*
-*
-* @param pk
-* @param personsName
-*
-* @throws CreateException
-* @throws DuplicateKeyException
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public void ejbPostCreate (AccountPK pk, String personsName)
throws CreateException, DuplicateKeyException, EJBException,
RemoteException
@@ -92,15 +34,6 @@
log.debug(ejbPostCreate (AccountPK, String) called);
}
- /**
-* Method ejbLoad
-*
-*
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public void ejbLoad ()
throws EJBException, RemoteException
{
@@ -108,15 +41,6 @@
}
- /**
-* Method ejbStore
-*
-*
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public void ejbStore ()
throws EJBException, RemoteException
{
@@ -124,15 +48,6 @@
}
- /**
-* Method ejbRemove
-*
-*
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public void ejbRemove ()
throws EJBException, RemoteException
{
@@ -140,75 +55,24 @@
}
- /**
-* Method ejbActivate
-*
-*
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public void ejbActivate ()
throws EJBException, RemoteException
{
log.debug(ejbActivate () called);
}
- /**
-* Method ejbPassivate
-*
-*
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public void ejbPassivate ()
throws EJBException, RemoteException
{
log.debug(ejbPassivate () called);
}
- /**
-* Method setEntityContext
-*
-*
-* @param ctx
-*
-* @throws EJBException
-* @throws RemoteException
-*
-*/
-
public void setEntityContext (EntityContext ctx)
throws EJBException, RemoteException
{
- log.debug(setEntityContext (\ + ctx.getPrimaryKey()
-
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/cts/test StatefulSessionUnitTestCase.java
User: starksm
Date: 02/04/18 10:05:02
Modified:src/main/org/jboss/test/cts/test
StatefulSessionUnitTestCase.java
Log:
Add a local entity interface and testing of stateful session passivation
of a bean that includes a java:comp/env context and local interface
as instance session variables
Revision ChangesPath
1.4 +134 -323
jbosstest/src/main/org/jboss/test/cts/test/StatefulSessionUnitTestCase.java
Index: StatefulSessionUnitTestCase.java
===
RCS file:
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/cts/test/StatefulSessionUnitTestCase.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- StatefulSessionUnitTestCase.java 29 Jan 2002 22:00:01 - 1.3
+++ StatefulSessionUnitTestCase.java 18 Apr 2002 17:05:02 - 1.4
@@ -15,6 +15,7 @@
import java.rmi.ServerException;
import javax.ejb.Handle;
+import javax.ejb.RemoveException;
import javax.naming.InitialContext;
import javax.naming.Context;
import javax.rmi.PortableRemoteObject;
@@ -36,27 +37,51 @@
* @see related
* @author Author: kimptoc
* @author Author: d_jencks converted to JBossTestCase, added logging.
- * @version $Revision: 1.3 $
+ * @version $Revision: 1.4 $
*/
-
public class StatefulSessionUnitTestCase
extends JBossTestCase
{
- static boolean deployed = false;
-
- /**
-* Constructor Main
-*
-*
-* @param name
-*
-*/
-
public StatefulSessionUnitTestCase (String name)
{
super(name);
}
+ /** Create a StatefulSessionBean and then create a local interface to
+an entity in the session. This bean is then passivated by creating another
+session bean and then activated by invoking a business method. The
+purpose is to test that the session is passivated and that the local
+interface is restored.
+ */
+ public void testLocalInterfacePassivation() throws Exception
+ {
+ Context ctx = new InitialContext();
+ getLog().debug(+++ testLocalInterfacePassivation);
+ StatefulSessionHome sessionHome = ( StatefulSessionHome )
ctx.lookup(ejbcts/StatefulSessionBean);
+ StatefulSession sessionBean = sessionHome.create();
+
+ getLog().debug(Creating local home);
+ AccountPK pk = new AccountPK(123456789);
+ sessionBean.createLocalEntity(pk, jduke);
+
+ getLog().debug(Creating a second session bean, forcing the first one to be
passivated?);
+ // The pool size has been set to 1 in the container
+ // config, so creating another ASession here should
+ // cause the first one to be passivated.
+ StatefulSession anotherSession = sessionHome.create();
+ getLog().debug(OK);
+
+ getLog().debug(Checking for complete passivation/activation);
+ assertTrue(sessionBean.getWasPassivated() == true);
+ getLog().debug(OK);
+
+ // Some other checks
+ getLog().debug(Checking reactivation of session bean attributes);
+ String name = sessionBean.readAndRemoveEntity();
+ assertTrue(name.equals(jduke));
+ getLog().debug(OK);
+ }
+
/**
* EJB 1.1 (Page 40)
* The container is responsible for making the home interfaces
@@ -107,7 +132,6 @@
* @throws Exception
*
*/
-
public void testEJBHomeInterface ()
throws Exception
{
@@ -172,45 +196,27 @@
* method on a session results in the javax.ejb.RemoveException.
*
*/
-
public void testRemoveSessionObject ()
+ throws Exception
{
getLog().debug(
**);
getLog().debug( testRemoveSessionObject());
- StatefulSession sessionBean = null;
-
+ Context ctx = new InitialContext();
+ StatefulSessionHome home = ( StatefulSessionHome )
ctx.lookup(ejbcts/StatefulSessionBean);
+ StatefulSession bean = home.create();
+ getLog().debug(OK);
+ getLog().debug(Call remove using a primary key);
try
{
- Properties props = System.getProperties();
-
- getLog().debug(Obtain home interface);
-
- // Create a new session object
- Context ctx = new InitialContext(props);
- StatefulSessionHome home =
-( StatefulSessionHome ) ctx.lookup(ejbcts/StatefulSessionBean);
-
- sessionBean = home.create();
- getLog().debug(OK);
- getLog().debug(Call remove using a primary key);
home.remove(new AccountPK(pk));
-
+ fail([EJB 1.1, p42, section 5.3.2] Expected 'RemoveException' when
remove-ing a session object, got NO exception);
}
-
[JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb LocalHomeObjectFactory.java
User: starksm Date: 02/04/18 10:06:06 Removed: src/main/org/jboss/ejb LocalHomeObjectFactory.java Log: Remove obsolete jndi ObjectFactory ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/cts/META-INF ejb-jar.xml jboss.xml
User: starksm Date: 02/04/18 10:03:40 Modified:src/resources/cts/META-INF ejb-jar.xml jboss.xml Log: Add a local entity interface and set the stateful session container max cache size to 1 to force passivation for testing Revision ChangesPath 1.9 +73 -68jbosstest/src/resources/cts/META-INF/ejb-jar.xml Index: ejb-jar.xml === RCS file: /cvsroot/jboss/jbosstest/src/resources/cts/META-INF/ejb-jar.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- ejb-jar.xml 16 Feb 2002 05:37:35 - 1.8 +++ ejb-jar.xml 18 Apr 2002 17:03:40 - 1.9 @@ -1,74 +1,79 @@ ?xml version=1.0 encoding=UTF-8? ejb-jar - descriptionjBoss CTS application/description - display-namejBoss CTS/display-name - enterprise-beans - session - display-nameStateless Session/display-name - ejb-nameStatelessSessionBean/ejb-name - homeorg.jboss.test.cts.interfaces.StatelessSessionHome/home - remoteorg.jboss.test.cts.interfaces.StatelessSession/remote - ejb-classorg.jboss.test.cts.ejb.StatelessSessionBean/ejb-class - session-typeStateless/session-type - transaction-typeContainer/transaction-type - /session - session - display-nameStateful Session/display-name - ejb-nameStatefulSessionBean/ejb-name - homeorg.jboss.test.cts.interfaces.StatefulSessionHome/home - remoteorg.jboss.test.cts.interfaces.StatefulSession/remote - ejb-classorg.jboss.test.cts.ejb.StatefulSessionBean/ejb-class - session-typeStateful/session-type - transaction-typeContainer/transaction-type - security-role-ref -descriptionThis is to test the isCallerInRole( ) method on the SessionBean./description -role-namebean tester/role-name - /security-role-ref - /session - entity - descriptionTest for BEAN managed persistence/description - ejb-nameBMPBean/ejb-name - homeorg.jboss.test.cts.interfaces.CtsBmpHome/home - remoteorg.jboss.test.cts.interfaces.CtsBmp/remote - ejb-classorg.jboss.test.cts.ejb.CtsBmpBean/ejb-class - persistence-typeBean/persistence-type - prim-key-classorg.jboss.test.cts.keys.AccountPK/prim-key-class - reentrantTrue/reentrant - resource-ref -res-ref-namedatasource/res-ref-name -res-typejavax.sql.DataSource/res-type -res-authContainer/res-auth - /resource-ref - /entity - entity - descriptionTest for BEAN managed persistence (Callbacks)/description - ejb-nameBMPCallbackBean/ejb-name - homeorg.jboss.test.cts.interfaces.BmpCallbackHome/home - remoteorg.jboss.test.cts.interfaces.BmpCallback/remote - ejb-classorg.jboss.test.cts.ejb.BmpCallbackBean/ejb-class - persistence-typeBean/persistence-type - prim-key-classorg.jboss.test.cts.keys.AccountPK/prim-key-class - reentrantTrue/reentrant - resource-ref -res-ref-namedatasource/res-ref-name -res-typejavax.sql.DataSource/res-type -res-authContainer/res-auth - /resource-ref - /entity - entity - descriptionTest for CONTAINER managed persistence /description - ejb-nameCMPBean/ejb-name - homeorg.jboss.test.cts.interfaces.CtsCmpHome/home - remoteorg.jboss.test.cts.interfaces.CtsCmp/remote - ejb-classorg.jboss.test.cts.ejb.CtsCmpBean/ejb-class - persistence-typeContainer/persistence-type - prim-key-classorg.jboss.test.cts.keys.AccountPK/prim-key-class - reentrantTrue/reentrant + descriptionjBoss CTS application/description + display-namejBoss CTS/display-name + enterprise-beans + session + display-nameStateless Session/display-name + ejb-nameStatelessSessionBean/ejb-name + homeorg.jboss.test.cts.interfaces.StatelessSessionHome/home + remoteorg.jboss.test.cts.interfaces.StatelessSession/remote + ejb-classorg.jboss.test.cts.ejb.StatelessSessionBean/ejb-class + session-typeStateless/session-type + transaction-typeContainer/transaction-type + /session + session + display-nameStateful Session/display-name + ejb-nameStatefulSessionBean/ejb-name + homeorg.jboss.test.cts.interfaces.StatefulSessionHome/home + remoteorg.jboss.test.cts.interfaces.StatefulSession/remote + ejb-classorg.jboss.test.cts.ejb.StatefulSessionBean/ejb-class + session-typeStateful/session-type + transaction-typeContainer/transaction-type + ejb-local-ref +ejb-ref-nameejb/CMPBeanLocalHome/ejb-ref-name +ejb-ref-typeEntity/ejb-ref-type +local-homeorg.jboss.test.cts.interfaces.CtsCmpLocalHome/local-home +
[JBoss-dev] [ jboss-Bugs-543823 ] Unable to send Entity Beans as Msg
Bugs item #543823, was opened at 2002-04-14 13:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=543823group_id=22866 Category: JBossMQ Group: v2.4 (stable) Status: Closed Resolution: Invalid Priority: 5 Submitted By: Rico Kahnert (rkahnert) Assigned to: Nobody/Anonymous (nobody) Summary: Unable to send Entity Beans as Msg Initial Comment: Hi, I tried to send an EJB in an ObjectMessage and get the following Exception: javax.jms.MessageFormatException: ClassNotFoundException at org.jboss.mq.SpyObjectMessage.getObject (SpyObjectMessage.java:92) If I try it with a regular object it works fine. I'm absolutely sure that that the class (Remote Interface and Implementation) are in the classpath. Environment: Windows2000 SP2 / Debian Linux (not sure about the version) JDK/JRE 1.4 JBoss 2.4.4 (stable) I hope you can give me a hint of how to solve the problem/fix the problem pretty soon. THanks a lot Rico Kahnert -- Comment By: Rico Kahnert (rkahnert) Date: 2002-04-18 09:51 Message: Logged In: YES user_id=515280 Well ... I'm not sure if it is a scenario the is so far of the path ... What if I have two different applications running in one container using the same Entity Beans. I don't want to fool around with creating objects I only need to communicate with a MDB. I really think it's a valid scenario and would appreciate if you could have a look into it again. Thanks a lot Rico -- Comment By: Scott M Stark (starksm) Date: 2002-04-17 19:27 Message: Logged In: YES user_id=175228 You can't send the remote interface of an ejb as a serialized object. You would have to obtain the ejb handle and send that. Since the mdb is deployed with the target ejb it does not make sense for an external client to lookup the ejb and then pass a reference to it using jms. The jms message should simply describe which ejb the mdb should use. -- Comment By: Rico Kahnert (rkahnert) Date: 2002-04-14 14:26 Message: Logged In: YES user_id=515280 Here is a test case ... Just deploy the ear. The client is included in the jar/ear. It's testcase.MessageBeanClient and has main. -- Comment By: Scott M Stark (starksm) Date: 2002-04-14 13:23 Message: Logged In: YES user_id=175228 Provide a test case as there are too many variables to say why this should or should not work. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=543823group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-541855 ] Passivation of stateful sess beans fails
Bugs item #541855, was opened at 2002-04-09 22:21 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=541855group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 6 Submitted By: Stephen Coy (scoy) Assigned to: Scott M Stark (starksm) Summary: Passivation of stateful sess beans fails Initial Comment: Section 7.4.1 of the EJB2.0 spec says that EJBLocalHome and EJBLocalObject (amongst others) should be persisted during passivation. The code in org.jboss.ejb.plugins.SessionObjectOutputStream clearly doesn't do this yet. Someone needs to check and ifx this code for EJB2.0 conformance. -- Comment By: Scott M Stark (starksm) Date: 2002-04-18 09:58 Message: Logged In: YES user_id=175228 Fixed on head and the 3.0 branch -- Comment By: Stephen Coy (scoy) Date: 2002-04-17 01:10 Message: Logged In: YES user_id=463096 Doh! I figured out that I can set the cache size to 1. Creating a second session bean causes the first to be passivated. We now have a test that successfully fails. -- Comment By: Stephen Coy (scoy) Date: 2002-04-17 00:17 Message: Logged In: YES user_id=463096 The attached files incorporate test case stateful2 into the JBoss test suite. Please remove any .DS_Store files you find - they're an unfortunate side effect of using MacOS at present. I spent quite some time trrying to configure the container so that the session bean would passivate before the test completed, but failed miserably. However, you can still see the passivation failing when the EJB is undeployed. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=541855group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] testsuite jdk1.4 compilation
In order to compile the org.jboss.test.util.TestConnection.java class with jdk1.4, several methods must be uncommented (the JDBC 3.0 methods). It used to be that these methods caused this class to not compile with jdk1.3 due to the missing class, Savepoint. But this class is now included in the jboss-jca.jar archive, and now jdk1.3 compiles it correctly. Will there be a problem if I check TestConnection in with the JDBC 3.0 methods uncommented? -Larry * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=13360 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Java based web CMS
Open For Business in SourceForge claims to be a quite complete one. I have downloaded it, but still didn't try it. It is based on JBoss!!! =)) Out of this, Zope - CMF. Python based, IIRC. Quite complete. At personal level, Jason, pliz feedback your decision. I have to choose one next month :) On Thu, 2002-04-18 at 07:43, Jason Dillon wrote: Sorry, another off question... Do any of you know of any production quality content managment systems for Java? I have only found one, OpenCMS (http://www.opencms.org/opencms/opencms/index.html), which is currently being maintained. If you know of another system could you point me at it. If you have actually used one of these I would also appreciate any comments and insight you have on the matter. This is related to some pending changes to the JBoss website (so it sort of related)... but still sorry for the noise. Thanks, --jason * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=13303 ___ 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
Re: [JBoss-dev] [ jboss-Bugs-541855 ] Passivation of stateful sess beans fails
This change, serializing local proxies as well as remote ones, breaks the local ejb-link naming tests on my machine: previously only the remote ones were broken. In the nightly tests, the remote tests (not the local) also failed on jdk 1.4, a similar setup to mine. http://www.lubega.com/testarchive/sun_j2sdk140/org/jboss/test/naming/test/InternalNamingClassReplacementUnitTestCase.html As far as I can tell, the serialization code is keeping the first version of the class it sees, forever. I haven't dug into sun's code yet, however. (Is it available for 1.4 anyway?) I would think this change to serialized storage of local proxies would slow things down significantly compared to references. I was considering changing storage of remote proxies to references as well, on the argument that local access is expected to be more frequent than remote access, so the cost of serializing a referenced proxy for each remote call would be less than the cost of deserializing a serialized proxy for a local call. It would also fix these tests on more systems. Any comments? thanks david jencks On 2002.04.18 12:58:29 -0400 [EMAIL PROTECTED] wrote: Bugs item #541855, was opened at 2002-04-09 22:21 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=541855group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 6 Submitted By: Stephen Coy (scoy) Assigned to: Scott M Stark (starksm) Summary: Passivation of stateful sess beans fails Initial Comment: Section 7.4.1 of the EJB2.0 spec says that EJBLocalHome and EJBLocalObject (amongst others) should be persisted during passivation. The code in org.jboss.ejb.plugins.SessionObjectOutputStream clearly doesn't do this yet. Someone needs to check and ifx this code for EJB2.0 conformance. -- Comment By: Scott M Stark (starksm) Date: 2002-04-18 09:58 Message: Logged In: YES user_id=175228 Fixed on head and the 3.0 branch -- Comment By: Stephen Coy (scoy) Date: 2002-04-17 01:10 Message: Logged In: YES user_id=463096 Doh! I figured out that I can set the cache size to 1. Creating a second session bean causes the first to be passivated. We now have a test that successfully fails. -- Comment By: Stephen Coy (scoy) Date: 2002-04-17 00:17 Message: Logged In: YES user_id=463096 The attached files incorporate test case stateful2 into the JBoss test suite. Please remove any .DS_Store files you find - they're an unfortunate side effect of using MacOS at present. I spent quite some time trrying to configure the container so that the session bean would passivate before the test completed, but failed miserably. However, you can still see the passivation failing when the EJB is undeployed. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=541855group_id=22866 ___ 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
Re: [JBoss-dev] New connector postgresql-service
Does method boundary mean bean method boundary or any method boundary (helper classes used within a beans method) ? * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=12641 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] New connector postgresql-service
I have the same problem with oracle and the SEROPTO Type 4 JDBC driver. The code i use runs on the alpha and on the beta release of JBoss, but it doesn't run on the RC1. I open and close one connection within the boundary of one Bean method, but also use this connection in different helper methods (but always only within the method boundary of the bean). I also call methods on entity beans while the connection is open. But this all should be no problem is none in the alpha and beta release. So can anybody help me and tell me what has changed from beta to RC1 concerning this problem? Thanks Jörg * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=12641 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Oracle Configuration JBoss 3.0 RC1
I have installed the JBoss 3.0 RC1. I am not able configure the oracle. I have downloaded the oracle-service.xml from the cvs and made changes according to my site. The error I am getting is:- Class not found for mbean: DefautDomain:sevice=ConnectionFactoryLoader, name=OracleDS I know there is some class not loaded but not sure it is the JDBC driver class or some thing else. I have copied my classes12.zip (Ihave tried unzipping it and making a jar) in the JBOSS_HOME/lib dir. I have also tried copying the file in JBOSS_HOME/lib/ext. Can any one point me to the my mistkae please. thanks * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=13365 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/varia/src/main/org/jboss/varia/autonumber AutoNumberEJB2.java
User: dsundstrom
Date: 02/04/18 12:38:12
Modified:varia/src/main/org/jboss/varia/autonumber
AutoNumberEJB2.java
Log:
Fixed bug [ 543253 ] AutoNumberEJB2 ejbCreate init problem
Revision ChangesPath
1.3 +2 -1
contrib/varia/src/main/org/jboss/varia/autonumber/AutoNumberEJB2.java
Index: AutoNumberEJB2.java
===
RCS file:
/cvsroot/jboss/contrib/varia/src/main/org/jboss/varia/autonumber/AutoNumberEJB2.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- AutoNumberEJB2.java 3 Apr 2002 22:29:17 - 1.2
+++ AutoNumberEJB2.java 18 Apr 2002 19:38:12 - 1.3
@@ -13,7 +13,7 @@
/**
* The CMP 2 compatible version of AutoNumberEJB.
*
- * @version tt$Revision: 1.2 $/tt
+ * @version tt$Revision: 1.3 $/tt
* @author a href=mailto:[EMAIL PROTECTED];Michel de Groot/a
* @author a href=mailto:[EMAIL PROTECTED];Ignacio Coloma/a
*/
@@ -31,6 +31,7 @@
public String ejbCreate(String name)
{
setName(name);
+ setValue(new Integer(0));
return null;
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/etc/conf/default standardjbosscmp-jdbc.xml
User: dsundstrom Date: 02/04/18 12:22:37 Modified:src/etc/conf/default standardjbosscmp-jdbc.xml Log: Fixed bug [ 543255 ] SOLID DB and CONSTRAINT Solid DB doesn't use constraint name. Revision ChangesPath 1.24 +2 -2 jboss/src/etc/conf/default/standardjbosscmp-jdbc.xml Index: standardjbosscmp-jdbc.xml === RCS file: /cvsroot/jboss/jboss/src/etc/conf/default/standardjbosscmp-jdbc.xml,v retrieving revision 1.23 retrieving revision 1.24 diff -u -r1.23 -r1.24 --- standardjbosscmp-jdbc.xml 14 Apr 2002 17:35:31 - 1.23 +++ standardjbosscmp-jdbc.xml 18 Apr 2002 19:22:35 - 1.24 @@ -7,7 +7,7 @@ !-- -- !-- = -- -!-- $Id: standardjbosscmp-jdbc.xml,v 1.23 2002/04/14 17:35:31 dsundstrom Exp $ -- +!-- $Id: standardjbosscmp-jdbc.xml,v 1.24 2002/04/18 19:22:35 dsundstrom Exp $ -- jbosscmp-jdbc @@ -930,7 +930,7 @@ type-mapping nameSOLID/name row-locking-template/ - pk-constraint-templateCONSTRAINT ?1 PRIMARY KEY (?2)/pk-constraint-template + pk-constraint-templatePRIMARY KEY (?2)/pk-constraint-template fk-constraint-templateALTER TABLE ?1 ADD CONSTRAINT ?2 FOREIGN KEY (?3) REFERENCES ?4 (?5)/fk-constraint-template alias-header-prefixt/alias-header-prefix alias-header-suffix_/alias-header-suffix ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Are we logging the exception enough!!!
Title: RE: [JBoss-dev] Are we logging the exception enough!!! Well, IMHO, we should also find a way to remove all these redundant exceptions! Each level is printing the same exception, the same stack trace (with just a few line in less at each step...) When you *really* have more than one error, it is hard to differentiate them. -Message d'origine-De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Casey HaakensonEnvoyé: jeudi, 18 avril 2002 00:03À: 'Jason Dillon'Cc: [EMAIL PROTECTED]; 'marc fleury'; David Jencks; Scott M StarkObjet: RE: [JBoss-dev] Are we logging the exception enough!!! I attached before and after traces to the original message, but had mistakenly not saved the right after traces (was comparing initial startup and a redployment). Anyway, here are the right versions. I'm not trying to show less info, just the same info in a slightly more intuitive layout. In the case of the exception I was working on, "nested" only printed the name of the exception again "NullPointerException" which was already being printed by the stack trace. -Casey -Original Message- From: Jason Dillon [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 17, 2002 2:26 PM To: Casey Haakenson Cc: [EMAIL PROTECTED]; 'marc fleury'; David Jencks; Scott M Stark Subject: Re: [JBoss-dev] Are we logging the exception enough!!! The second set of patches is for reformatting of the exception printing. Dealing with it for a while, I just couldn't handle the way they were printed anymore so I changed it around a bit. I realize this is mainly a personal preference, but I thought I'd send it out for feedback. Outline of changes made: -Flipped the order NestedExceptions are printed in to be current exception first then sub-exception, and added a "Root Cause:" line above the sub-exception. This way, when a user is reading the log from bottom to top, they see the sub-exception first (probably where the real problem is) and it's seperated from the above exception to provide a visual break. -Changed NestedThrowable.Util.getMessage() to not use "nested" in constructing the message. It seemed to be only redundant info that was always printed out later on. This change does scare me a bit in that I'm not sure what other code paths rely on info being included by "nested". Any thoughts? Please show examples for what the exception output will look like... Looks like your patch to NestedThrowable only losses information... but it is hard to tell. Show me a before and after and why you think after is better please =) --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/ejb EJBDeployer.java
User: gropi
Date: 02/04/18 12:44:43
Modified:src/main/org/jboss/ejb EJBDeployer.java
Log:
typo
Revision ChangesPath
1.19 +2 -2 jboss/src/main/org/jboss/ejb/EJBDeployer.java
Index: EJBDeployer.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/ejb/EJBDeployer.java,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- EJBDeployer.java 14 Apr 2002 01:19:53 - 1.18
+++ EJBDeployer.java 18 Apr 2002 19:44:42 - 1.19
@@ -67,7 +67,7 @@
* @author a href=mailto:[EMAIL PROTECTED];Peter Antman/a.
* @author a href=mailto:[EMAIL PROTECTED];Scott Stark/a
* @author a href=mailto:[EMAIL PROTECTED];Sacha Labourey/a
- * @version $Revision: 1.18 $
+ * @version $Revision: 1.19 $
*/
public class EJBDeployer
extends SubDeployerSupport
@@ -346,7 +346,7 @@
}
catch( Throwable t )
{
- log.error(Verfiy failed, t );
+ log.error(Verify failed, t );
}
// unset verifier log
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/varia/src/main/org/jboss/varia/autonumber AutoNumberEJB2.java
User: dsundstrom
Date: 02/04/18 12:40:07
Modified:varia/src/main/org/jboss/varia/autonumber Tag: Branch_3_0
AutoNumberEJB2.java
Log:
Fixed bug [ 543253 ] AutoNumberEJB2 ejbCreate init problem.
Revision ChangesPath
No revision
No revision
1.2.2.1 +2 -1
contrib/varia/src/main/org/jboss/varia/autonumber/AutoNumberEJB2.java
Index: AutoNumberEJB2.java
===
RCS file:
/cvsroot/jboss/contrib/varia/src/main/org/jboss/varia/autonumber/AutoNumberEJB2.java,v
retrieving revision 1.2
retrieving revision 1.2.2.1
diff -u -r1.2 -r1.2.2.1
--- AutoNumberEJB2.java 3 Apr 2002 22:29:17 - 1.2
+++ AutoNumberEJB2.java 18 Apr 2002 19:40:07 - 1.2.2.1
@@ -31,6 +31,7 @@
public String ejbCreate(String name)
{
setName(name);
+ setValue(new Integer(0));
return null;
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: manual/src/examples/org/jboss/docs/interest build.xml web.xml
User: gropi
Date: 02/04/18 12:43:28
Modified:src/examples/org/jboss/docs/interest build.xml web.xml
Log:
Make interest example work again with these versions:
JBoss 2.4.5RC1, 2.4.5_Tomcat-4.0.3, 2.4.5_Jetty-4.0.0
JBoss 3.0.0RC1, 3.0.0RC1_Jetty
Revision ChangesPath
3.1 +2 -2 manual/src/examples/org/jboss/docs/interest/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/manual/src/examples/org/jboss/docs/interest/build.xml,v
retrieving revision 3.0
retrieving revision 3.1
diff -u -r3.0 -r3.1
--- build.xml 18 Nov 2001 20:10:50 - 3.0
+++ build.xml 18 Apr 2002 19:43:28 - 3.1
@@ -83,10 +83,10 @@
/target
target name=deploy-ejb-jar depends=ejb-jar
-copy file=${build.interest.dir}/interest.jar
todir=${jboss.dist}/deploy /
+copy file=${build.interest.dir}/interest.jar todir=${deploy.dir} /
/target
target name=deploy-ear depends=ear
-copy file=${build.interest.dir}/interest.ear
todir=${jboss.dist}/deploy /
+copy file=${build.interest.dir}/interest.ear todir=${deploy.dir} /
/target
target name=interest-client depends=compile
3.1 +3 -0 manual/src/examples/org/jboss/docs/interest/web.xml
Index: web.xml
===
RCS file: /cvsroot/jboss/manual/src/examples/org/jboss/docs/interest/web.xml,v
retrieving revision 3.0
retrieving revision 3.1
diff -u -r3.0 -r3.1
--- web.xml 18 Nov 2001 20:10:50 - 3.0
+++ web.xml 18 Apr 2002 19:43:28 - 3.1
@@ -1,5 +1,8 @@
?xml version=1.0 encoding=UTF-8?
+!DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application
+2.2//EN http://java.sun.com/j2ee/dtds/web-app_2_2.dtd;
+
web-app
!-- ### Servlets --
servlet
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] RC1 release branch occuring at 00:00
David Jencks wrote: cvs update -j HEAD myfile If you do this: cvs update -kk -j HEAD myfile The merge will work better, because it kills keyword expansion. Note, don't do this on a binary file, as binary files need -kb and -kk turns -kb off. -dain ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/resources/org/jboss/metadata jbosscmp-jdbc_3_0.dtd
User: dsundstrom Date: 02/04/18 12:51:53 Modified:src/resources/org/jboss/metadata jbosscmp-jdbc_3_0.dtd Log: Added missing other element to declared-sql. Revision ChangesPath 1.16 +8 -1 jboss/src/resources/org/jboss/metadata/jbosscmp-jdbc_3_0.dtd Index: jbosscmp-jdbc_3_0.dtd === RCS file: /cvsroot/jboss/jboss/src/resources/org/jboss/metadata/jbosscmp-jdbc_3_0.dtd,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- jbosscmp-jdbc_3_0.dtd 9 Apr 2002 15:31:51 - 1.15 +++ jbosscmp-jdbc_3_0.dtd 18 Apr 2002 19:51:53 - 1.16 @@ -326,7 +326,7 @@ !-- Explicitly declared sql fragments. -- -!ELEMENT declared-sql (select?, from?, where?, order?) +!ELEMENT declared-sql (select?, from?, where?, order?, other?) !-- @@ -365,6 +365,13 @@ -- !ELEMENT order (#PCDATA) + +!-- +Declares the other sql that is appended to the end of a query. + +Example: otherLIMIT 100 OFFSET 200/other +-- +!ELEMENT other (#PCDATA) !-- Declare the alias to use for the main select table. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [ jboss-Bugs-541855 ] Passivation of stateful sess beans fails
And these tests continue to run fine here. We need to be able to reproduce the issue you are seeing on my box. [junit] Running org.jboss.test.naming.test.InternalNamingClassReplacementUnitTestCase [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 9.109 sec Send me the server log of just the InternalNamingClassReplacementUnitTestCase run. This change does not serialize these proxies on every call, it only makes them Serializable. The only time a local home interface is serialized is when the home is obtained from JNDI. The local interfaces are only serialized when passivation occurs so this is not a performance issue. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: David Jencks [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Scott Stark [EMAIL PROTECTED] Sent: Thursday, April 18, 2002 11:25 AM Subject: Re: [JBoss-dev] [ jboss-Bugs-541855 ] Passivation of stateful sess beans fails This change, serializing local proxies as well as remote ones, breaks the local ejb-link naming tests on my machine: previously only the remote ones were broken. In the nightly tests, the remote tests (not the local) also failed on jdk 1.4, a similar setup to mine. http://www.lubega.com/testarchive/sun_j2sdk140/org/jboss/test/naming/test/In ternalNamingClassReplacementUnitTestCase.html As far as I can tell, the serialization code is keeping the first version of the class it sees, forever. I haven't dug into sun's code yet, however. (Is it available for 1.4 anyway?) I would think this change to serialized storage of local proxies would slow things down significantly compared to references. I was considering changing storage of remote proxies to references as well, on the argument that local access is expected to be more frequent than remote access, so the cost of serializing a referenced proxy for each remote call would be less than the cost of deserializing a serialized proxy for a local call. It would also fix these tests on more systems. Any comments? thanks david jencks ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: manual/src/examples/build build.xml
User: gropi
Date: 02/04/18 12:43:28
Modified:src/examples/build build.xml
Log:
Make interest example work again with these versions:
JBoss 2.4.5RC1, 2.4.5_Tomcat-4.0.3, 2.4.5_Jetty-4.0.0
JBoss 3.0.0RC1, 3.0.0RC1_Jetty
Revision ChangesPath
3.1 +27 -3 manual/src/examples/build/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/manual/src/examples/build/build.xml,v
retrieving revision 3.0
retrieving revision 3.1
diff -u -r3.0 -r3.1
--- build.xml 18 Nov 2001 20:10:42 - 3.0
+++ build.xml 18 Apr 2002 19:43:28 - 3.1
@@ -21,6 +21,15 @@
property name=src.resources value=${basedir}/resources/
property name=build.dir value=${basedir}/build-examples/
property name=dist.dir value=${basedir}/../../dist-examples/
+
+target name=validate-deploy
+!-- Look for the deployment dir. Differs between 2.x and 3.x
+ --
+!-- First look for JBoss 2.x --
+available property=deploy.dir value=${jboss.dist}/deploy
file=${jboss.dist}/deploy type=dir/
+!-- Then check for JBoss 3.x (will override previous one if found) --
+available property=deploy.dir
value=${jboss.dist}/server/default/deploy file=${jboss.dist}/server/default/deploy
type=dir/
+/target
target name=validate-servlet
!-- Override with your web server servlet jar location.
@@ -31,6 +40,8 @@
available property=servlet.jar
value=${env.JBOSS_DIST}/../jetty/lib/javax.servlet.jar
file=${env.JBOSS_DIST}/../jetty/lib/javax.servlet.jar/
available property=servlet.jar
value=${env.JBOSS_DIST}/../catalina/common/lib/servlet.jar
file=${env.JBOSS_DIST}/../catalina/common/lib/servlet.jar/
available property=servlet.jar
value=${env.JBOSS_DIST}/../catalina/common/lib/servlet.jar
file=${env.TOMCAT_HOME}/lib/servlet.jar/
+!-- JBoss 3.0.x --
+available property=servlet.jar
value=${env.JBOSS_DIST}/lib/javax.servlet.jar
file=${env.JBOSS_DIST}/lib/javax.servlet.jar/
property name=servlet.jar value=COULD_NOT_FIND_SERVLET_JAR/
path id=base.path_22
@@ -49,16 +60,29 @@
pathelement location=${jboss.dist}/client/jnp-client.jar/
pathelement location=${servlet.jar}/
/path
+path id=base.path_30
+pathelement location=${jboss.dist}/client/jboss-j2ee.jar/
+pathelement location=${jboss.dist}/client/jboss-common-client.jar/
+pathelement location=${jboss.dist}/client/log4j.jar/
+pathelement location=${jboss.dist}/client/jbosssx-client.jar/
+pathelement location=${jboss.dist}/client/jboss-client.jar/
+pathelement location=${jboss.dist}/client/jnp-client.jar/
+pathelement location=${servlet.jar}/
+/path
+
/target
-target name=validate-jboss depends=validate-servlet
+target name=validate-jboss depends=validate-servlet,validate-deploy
+!-- JBoss 2.2.x --
available property=classpath_id value=base.path_22
file=${jboss.dist}/client/ejb.jar /
+!-- JBoss 2.4.x --
available property=classpath_id value=base.path_24
file=${jboss.dist}/client/jboss-j2ee.jar /
-
+!-- JBoss 3.0.x --
+available property=classpath_id value=base.path_30
file=${jboss.dist}/client/jboss-common-client.jar /
/target
target name=fail_if_not_valid unless=classpath_id
-fail message=jboss.dist=${jboss.dist} is not a valid JBOSS_DIST
directory. If using a bundled JBoss version set JBOSS_DIST to the jboss/ subdir./
+fail message=jboss.dist=${jboss.dist} is not a valid JBOSS_DIST
directory. Please make sure the JBOSS_DIST environment variable is set properly. If
you are using a bundled JBoss 2.x version please set JBOSS_DIST to the jboss/
subdir./
/target
target name=init depends=validate-jboss,fail_if_not_valid
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [ jboss-Bugs-544848 ] EAR Deployments don't work
It doesn't seem to be fixed. I just (18-Apr-2002 21:00 MET) compiled the latest code from Branch_3_0 and ran into the same problems again. I, too, bundled struts.jar with my EAR. I could only make it work by copying struts.jar to JBoss' lib directory. tom * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=13076 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] testsuite jdk1.4 compilation
Will there be a problem if I check TestConnection in with the JDBC 3.0 methods uncommented? Only if it stops working under 1.3 ;) --jason - This mail sent through IMP: http://horde.org/imp/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-544437 ] FK not populated with CMR
Bugs item #544437, was opened at 2002-04-15 19:00 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=544437group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: frederik sauer (fredsa) Assigned to: Dain Sundstrom (dsundstrom) Summary: FK not populated with CMR Initial Comment: The below example worked in 3.0.0beta2 and no longer works in RC1. Steps to reproduce: 1. Create two entity beans, Parent and Child, each with a Long primary key (say parentId and childId) 2. Create bi-directional CMR parent-childeren using a Collection 3. Create a remotely accessible method in the Parent bean: public void addChildByPK(Long childPK) 3. Create a remotely accessible method in the Child bean: public void setParentByPK(Long parentPK) 4. In a test client show that this works as it should: a) create an instance of Parent b) create an instance of Child c) call parent.addChildByPK((Long) child.getPrimaryKey ()) d) select * from the child table and verify that the foreign key to the parent entity is populated 5. In a test client show that this is broken: a) create an instance of Parent b) create an instance of Child c) call child.setParentByPK((Long) parent.getPrimaryKey()) d) select * from the child table and verify that the foreign key to the parent entity is null I'm attaching a JAR file (includes source) which can be deployed. Included in the jar is a test client RelationshipTest.java. All files are in the java package dummy. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=544437group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] New Connection Adapter
I have just finished a new JCA adapter that allows mutliple EIS's to be used with a single JBoss instance. The adapter utilizes the security framework and the jca framework. It allows for a user to map themselves to an EIS at runtime without affecting other users running client sessions in the same jboss. The user then can have the ability to change to a different EIS at runtime depending on their public credentials. I modeled this adapter after the JBoss local RAR and enhanced it with a custom mapping login module. Is this something that JBoss wants? I would be willing to clean up the code and donate the new adapter to the project if people want it. Thanks Dan Bunker ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-544342 ] SQL table aliases also exceed db limits
Bugs item #544342, was opened at 2002-04-15 14:48 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=544342group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Closed Resolution: Invalid Priority: 5 Submitted By: frederik sauer (fredsa) Assigned to: Nobody/Anonymous (nobody) Summary: SQL table aliases also exceed db limits Initial Comment: Using custom Finder method (CMP2.0) JBoss can generate long table aliases which exceed datbase limitations. Also refer to these related bugs: 516835 pk constraint name too long 532262 relationship table names too long In the following JBoss generated example query the table alias t2_si_oDTSecurityGroups_RELATION exceeds Oracle's limitations causing an ORA-00972: identifier is too long: SELECT t0_secgrp.ODT_SECURITY_GROUP_ID FROM SYSTEM_IDENTITY t1_si, ODT_SECURITY_GROUP t0_secgrp, SYSTEM_ID_TO_SECURITY_GROUP t2_si_oDTSecurityGroups_RELATION WHERE t1_si.SYSTEM_ID = :1 AND (t1_si.SYSTEM_ID=t2_si_oDTSecurityGroups_RELATION.SYST EM_ID AND t0_secgrp.ODT_SECURITY_GROUP_ID=t2_si_oDTSecurityGroup s_RELATION.ODT_SECURITY_GROUP_ID) -- Comment By: Dain Sundstrom (dsundstrom) Date: 2002-04-18 15:35 Message: Logged In: YES user_id=251431 See alias-max-length element of type-mapping in standardjbosscmp-jdbc.xml for your database vendor. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=544342group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-545815 ] Failed WAR deployments leaves uncertain
Bugs item #545815, was opened at 2002-04-18 15:25 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=545815group_id=22866 Category: None Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Peter Luttrell (objec) Assigned to: Nobody/Anonymous (nobody) Summary: Failed WAR deployments leaves uncertain Initial Comment: JBoss3.0rc1+tomcat4.0.3 I deployed an ear file with a war file. The war file contained an ejb-local-ref in it that Jboss can't find. I then undeploy the ear file. I then redeploy the ear file and jboss complains that the context is not unique. When deployments fail, they should leave the appserver in the state prior to the failed deployment, especially when you consider that specifying an ejb- local-ref is stating that the war is going to use an resource and the app server is saying it can't find the ref. See below: 15:19:51,461 ERROR [EmbeddedCatalinaServiceSX] Error during deploy java.lang.IllegalArgumentException: addChild: Child name '/myContextName' is not unique at org.apache.catalina.core.ContainerBase.addChild (ContainerBase.java:779) at org.apache.catalina.core.StandardHost.addChild (StandardHost.java:454) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.create WebContext(EmbeddedCatalinaService SX.java:284) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.perfor mDeploy(EmbeddedCatalinaServiceSX. java:204) at org.jboss.web.AbstractWebContainer.start (AbstractWebContainer.java:405) at org.jboss.deployment.MainDeployer.start (MainDeployer.java:665) at org.jboss.deployment.MainDeployer.start (MainDeployer.java:658) at org.jboss.deployment.MainDeployer.deploy (MainDeployer.java:507) at org.jboss.deployment.MainDeployer.deploy (MainDeployer.java:470) at sun.reflect.GeneratedMethodAccessor6.invoke (Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke (Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke (ReflectedMBeanDispatcher.java:284 ) at org.jboss.mx.server.MBeanServerImpl.invoke (MBeanServerImpl.java:492) at org.jboss.util.jmx.MBeanProxy.invoke (MBeanProxy.java:174) at $Proxy4.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deplo y(URLDeploymentScanner.java:350) at org.jboss.deployment.scanner.URLDeploymentScanner.scanD irectory(URLDeploymentScanner.java :530) at org.jboss.deployment.scanner.URLDeploymentScanner.scan (URLDeploymentScanner.java:410) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ ScannerThread.loop(AbstractDeploym entScanner.java:202) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ ScannerThread.run(AbstractDeployme ntScanner.java:191) -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=545815group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-545821 ] web-app local-refs don't work
Bugs item #545821, was opened at 2002-04-18 15:47 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=545821group_id=22866 Category: None Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Peter Luttrell (objec) Assigned to: Nobody/Anonymous (nobody) Summary: web-app local-refs don't work Initial Comment: jboss3.0rc1+tomcat4.0.3 I attempted to lookup an ejb via local interface in a web app. As I read the spec you need to specify the refernce in the web.xml as such: ejb-local-ref ejb-ref-namejndiLookupName/ejb-ref-name ejb-ref-typeEntity/ejb-ref-type local-homemyLocalHome/local-home localmyLocal/local ejb-linkejb-name/ejb-link /ejb-local-ref The problem is the ejb-name. Jboss can't seam to locate the ejb and thus can't build the ENC. My war is located in the root of an ear, named test.war. My ejb-jar (with the ejb I need) is located in the root of the ear, named test-ejbs.jar. The spec states (from web-app_2_3.dtd): !-- The ejb-link element is used in the ejb-ref or ejb- local-ref elements to specify that an EJB reference is linked to an enterprise bean. The name in the ejb-link element is composed of a path name specifying the ejb-jar containing the referenced enterprise bean with the ejb-name of the target bean appended and separated from the path name by #. The path name is relative to the war file containing the web application that is referencing the enterprise bean. This allows multiple enterprise beans with the same ejb-name to be uniquely identified. Used in: ejb-local-ref, ejb-ref Examples: ejb-linkEmployeeRecord/ejb-link ejb- link../products/product.jar#ProductEJB/ejb-link -- Thus I've tried these values for ejb-link: myEjbName test-ejbs.jar#myEjbName But neither work. Two additional things that I tried are: adding a reference to the test-ejbs.jar in the Manifest.mf file for the war. adding the test-ejbs.jar file to the WEB-INF\lib dir in my war. Here's the exception: 15:29:02,961 ERROR [EmbeddedCatalinaServiceSX] Failed to setup web application ENC javax.naming.NamingException: ejb-local-ref: jndiLookupName, target not found, add valid ejb-link at org.jboss.web.AbstractWebContainer.linkEjbLocalRefs (AbstractWebContainer.java:757) at org.jboss.web.AbstractWebContainer.parseWebAppDescripto rs(AbstractWebContainer.java:567) at org.jboss.web.AbstractWebContainer$DescriptorParser.par seWebAppDescriptors(AbstractWebCon tainer.java:1050) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.contex tInit(EmbeddedCatalinaServiceSX.ja va:334) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.access $000(EmbeddedCatalinaServiceSX.jav a:74) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX$1.life cycleEvent(EmbeddedCatalinaService SX.java:276) at org.apache.catalina.util.LifecycleSupport.fireLifecycle Event(LifecycleSupport.java:155) at org.apache.catalina.core.ContainerBase.start (ContainerBase.java:1131) at org.apache.catalina.core.StandardContext.start (StandardContext.java:3345) at org.apache.catalina.core.ContainerBase.addChild (ContainerBase.java:785) at org.apache.catalina.core.StandardHost.addChild (StandardHost.java:454) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.create WebContext(EmbeddedCatalinaService SX.java:284) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.perfor mDeploy(EmbeddedCatalinaServiceSX. java:204) at org.jboss.web.AbstractWebContainer.start (AbstractWebContainer.java:405) at org.jboss.deployment.MainDeployer.start (MainDeployer.java:665) at org.jboss.deployment.MainDeployer.start (MainDeployer.java:658) at org.jboss.deployment.MainDeployer.deploy (MainDeployer.java:507) at org.jboss.deployment.MainDeployer.deploy (MainDeployer.java:470) at sun.reflect.GeneratedMethodAccessor6.invoke (Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke (Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke (ReflectedMBeanDispatcher.java:284 ) at org.jboss.mx.server.MBeanServerImpl.invoke (MBeanServerImpl.java:492) at org.jboss.util.jmx.MBeanProxy.invoke (MBeanProxy.java:174) at $Proxy4.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deplo y(URLDeploymentScanner.java:350) at org.jboss.deployment.scanner.URLDeploymentScanner.scanD irectory(URLDeploymentScanner.java :530) at org.jboss.deployment.scanner.URLDeploymentScanner.scan (URLDeploymentScanner.java:410) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ ScannerThread.loop(AbstractDeploym entScanner.java:202) at org.jboss.deployment.scanner.AbstractDeploymentScanner$
Re: [JBoss-dev] [ jboss-Bugs-544848 ] EAR Deployments don't work
Applications within an ear file will only get deployed if: 1) They are referenced from an application.xml module tag (rars,ejbs,wars, and client jars) 2) They are spcified in a META-INF / Class-Path entry of one of the the deployed applications from step 1. (See http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#JAR%20Manifest) Have you tried step 2 above? If so, let me know and I will try to reproduce it. -Larry It doesn't seem to be fixed. I just (18-Apr-2002 21:00 MET) compiled the latest code from Branch_3_0 and ran into the same problems again. I, too, bundled struts.jar with my EAR. I could only make it work by copying struts.jar to JBoss' lib directory. tom * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=13076 ___ 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
Re: [JBoss-dev] tomcat4 log dir in jboss3-rc1
Its our service configuration file. Is property transformation supported
automatically? If not, it can be done at the service when the attribute
is set.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, April 18, 2002 1:48 PM
Subject: Re: [JBoss-dev] tomcat4 log dir in jboss3-rc1
Is there a way to access properties from the tomcat config? If so it
should
set the log dir in ${jboss.server.home.dir}/log
--jason
Quoting David Ward [EMAIL PROTECTED]:
I don't know the ins-and-outs of creating a change request, but was
wondering if for the next rc of jboss3-tomcat4 the tomcat4-service.xml
file could be changed in this way:
From this:
Valve className = org.apache.catalina.valves.AccessLogValve
prefix = localhost_access suffix = .log
pattern = common directory = ../jboss/log /
To this:
Valve className = org.apache.catalina.valves.AccessLogValve
prefix = localhost_access suffix = .log
pattern = common directory = ../server/default/log /
Currently it assumes the old JBoss-2.4.x-Tomcat-x.x.x dir structure
where jboss and tomcat/catalina were next to eachother as subdirs, which
isn't the case anymore.
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] tomcat4 log dir in jboss3-rc1
Is there a way to access properties from the tomcat config? If so it should
set the log dir in ${jboss.server.home.dir}/log
--jason
Quoting David Ward [EMAIL PROTECTED]:
I don't know the ins-and-outs of creating a change request, but was
wondering if for the next rc of jboss3-tomcat4 the tomcat4-service.xml
file could be changed in this way:
From this:
Valve className = org.apache.catalina.valves.AccessLogValve
prefix = localhost_access suffix = .log
pattern = common directory = ../jboss/log /
To this:
Valve className = org.apache.catalina.valves.AccessLogValve
prefix = localhost_access suffix = .log
pattern = common directory = ../server/default/log /
Currently it assumes the old JBoss-2.4.x-Tomcat-x.x.x dir structure
where jboss and tomcat/catalina were next to eachother as subdirs, which
isn't the case anymore.
Thanks,
David
As an aside, I like how the Ajp13 connector example is included in the
XML, but personally I think it would be cool to (leave it in there) but
comment it out by default. Maybe also include (but leave commented out)
Warp - and maybe the new Coyote
(http://cvs.apache.org/viewcvs/jakarta-tomcat-connectors/coyote/)? -
Connector lines.
Thanks again.
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
-
This mail sent through IMP: http://horde.org/imp/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] tomcat4 log dir in jboss3-rc1
ic. Then no (currently).
--jason
Scott M Stark wrote:
Its our service configuration file. Is property transformation supported
automatically? If not, it can be done at the service when the attribute
is set.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, April 18, 2002 1:48 PM
Subject: Re: [JBoss-dev] tomcat4 log dir in jboss3-rc1
Is there a way to access properties from the tomcat config? If so it
should
set the log dir in ${jboss.server.home.dir}/log
--jason
Quoting David Ward [EMAIL PROTECTED]:
I don't know the ins-and-outs of creating a change request, but was
wondering if for the next rc of jboss3-tomcat4 the tomcat4-service.xml
file could be changed in this way:
From this:
Valve className = org.apache.catalina.valves.AccessLogValve
prefix = localhost_access suffix = .log
pattern = common directory = ../jboss/log /
To this:
Valve className = org.apache.catalina.valves.AccessLogValve
prefix = localhost_access suffix = .log
pattern = common directory = ../server/default/log /
Currently it assumes the old JBoss-2.4.x-Tomcat-x.x.x dir structure
where jboss and tomcat/catalina were next to eachother as subdirs, which
isn't the case anymore.
___
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
Re: [JBoss-dev] Oracle Configuration JBoss 3.0 RC1
Try putting the classes12.jar in the deply directory. On Fri, 2002-04-19 at 05:05, Raj Saini wrote: I have installed the JBoss 3.0 RC1. I am not able configure the oracle. I have downloaded the oracle-service.xml from the cvs and made changes according to my site. The error I am getting is:- Class not found for mbean: DefautDomain:sevice=ConnectionFactoryLoader, name=OracleDS I know there is some class not loaded but not sure it is the JDBC driver class or some thing else. I have copied my classes12.zip (Ihave tried unzipping it and making a jar) in the JBOSS_HOME/lib dir. I have also tried copying the file in JBOSS_HOME/lib/ext. Can any one point me to the my mistkae please. thanks * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=13365 ___ 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] CVS update: jboss/src/resources/org/jboss/metadata jbosscmp-jdbc_3_0.dtd
User: dsundstrom Date: 02/04/18 12:55:52 Modified:src/resources/org/jboss/metadata Tag: Branch_3_0 jbosscmp-jdbc_3_0.dtd Log: Added missing other element to declared-sql. Revision ChangesPath No revision No revision 1.15.2.1 +8 -1 jboss/src/resources/org/jboss/metadata/jbosscmp-jdbc_3_0.dtd Index: jbosscmp-jdbc_3_0.dtd === RCS file: /cvsroot/jboss/jboss/src/resources/org/jboss/metadata/jbosscmp-jdbc_3_0.dtd,v retrieving revision 1.15 retrieving revision 1.15.2.1 diff -u -r1.15 -r1.15.2.1 --- jbosscmp-jdbc_3_0.dtd 9 Apr 2002 15:31:51 - 1.15 +++ jbosscmp-jdbc_3_0.dtd 18 Apr 2002 19:55:52 - 1.15.2.1 @@ -326,7 +326,7 @@ !-- Explicitly declared sql fragments. -- -!ELEMENT declared-sql (select?, from?, where?, order?) +!ELEMENT declared-sql (select?, from?, where?, order?, other?) !-- @@ -365,6 +365,13 @@ -- !ELEMENT order (#PCDATA) + +!-- +Declares the other sql that is appended to the end of a query. + +Example: otherLIMIT 100 OFFSET 200/other +-- +!ELEMENT other (#PCDATA) !-- Declare the alias to use for the main select table. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: mysql-service.xml
Hi Claus, Thank you for you help but now give the following error: java.io.IOException: Properties file users.properties not found Thanks, João * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=13151 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Are we logging the exception enough!!!
Title: RE: [JBoss-dev] Are we logging the exception enough!!! Here are the results of your code snippet below in a clean build of jboss. It looks like it's printed in a, b, c order if I go by the line in ApplicationBean that caused each stack trace. And unless I'm doing something else wrong, my patch does something odd with 3-level deep exceptions, so I think it is broken too. -Casey 15:30:33,708 ERROR [STDERR] org.jboss.deployment.DeploymentException: c; - nested throwable is: org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a 15:30:33,709 ERROR [STDERR] + nested throwable: 15:30:33,709 ERROR [STDERR] org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a 15:30:33,709 ERROR [STDERR] + nested throwable: 15:30:33,710 ERROR [STDERR] org.jboss.deployment.DeploymentException: a 15:30:33,710 ERROR [STDERR] at f5.ApplicationBean.ejbPostCreate(ApplicationBean.java:67) 15:30:33,711 ERROR [STDERR] at java.lang.reflect.Method.invoke(Native Method) 15:30:33,711 ERROR [STDERR] at org.jboss.ejb.plugins.CMPPersistenceManager.postCreateEntity(CMPPersistenceManager.java:284) 15:30:33,756 ERROR [STDERR] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.postCreateEntity(CachedConnectionInterceptor.java:239) 15:30:33,757 ERROR [STDERR] at org.jboss.ejb.EntityContainer.postCreateHome(EntityContainer.java:716) 15:30:33,757 ERROR [STDERR] at java.lang.reflect.Method.invoke(Native Method) 15:30:33,758 ERROR [STDERR] at org.jboss.ejb.EntityContainer$ContainerInterceptor.invoke(EntityContainer.java:1164) 15:30:33,758 ERROR [STDERR] at org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor.invoke(JDBCRelationInterceptor.java:190) 15:30:33,758 ERROR [STDERR] at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynchronizationInterceptor.java:313) 15:30:33,759 ERROR [STDERR] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:147) 15:30:33,759 ERROR [STDERR] at org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:193) 15:30:33,759 ERROR [STDERR] at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:107) 15:30:33,760 ERROR [STDERR] at org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationInterceptor.java:59) 15:30:33,760 ERROR [STDERR] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:98) 15:30:33,761 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:167) 15:30:33,761 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:52) 15:30:33,761 ERROR [STDERR] at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:104) 15:30:33,762 ERROR [STDERR] at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:109) 15:30:33,762 ERROR [STDERR] at org.jboss.ejb.EntityContainer.invokeHome(EntityContainer.java:487) 15:30:33,762 ERROR [STDERR] at org.jboss.ejb.Container.invoke(Container.java:727) 15:30:33,763 ERROR [STDERR] at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1055) 15:30:33,763 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:492) 15:30:33,763 ERROR [STDERR] at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:364) 15:30:33,764 ERROR [STDERR] at java.lang.reflect.Method.invoke(Native Method) 15:30:33,764 ERROR [STDERR] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:241) 15:30:33,765 ERROR [STDERR] at sun.rmi.transport.Transport$1.run(Transport.java:152) 15:30:33,765 ERROR [STDERR] at java.security.AccessController.doPrivileged(Native Method) 15:30:33,765 ERROR [STDERR] at sun.rmi.transport.Transport.serviceCall(Transport.java:148) 15:30:33,766 ERROR [STDERR] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:465) 15:30:33,766 ERROR [STDERR] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:706) 15:30:33,766 ERROR [STDERR] at java.lang.Thread.run(Thread.java:484) 15:30:33,767 ERROR [STDERR] + throwable: 15:30:33,767 ERROR [STDERR] org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a 15:30:33,767 ERROR [STDERR] at f5.ApplicationBean.ejbPostCreate(ApplicationBean.java:68) 15:30:33,768 ERROR [STDERR] at java.lang.reflect.Method.invoke(Native Method) 15:30:33,768 ERROR [STDERR] at org.jboss.ejb.plugins.CMPPersistenceManager.postCreateEntity(CMPPersistenceManager.java:284) 15:30:33,768 ERROR [STDERR] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.postCreateEntity(CachedConnectionInterceptor.java:239) 15:30:33,769 ERROR [STDERR] at org.jboss.ejb.EntityContainer.postCreateHome(EntityContainer.java:716) 15:30:33,769 ERROR [STDERR] at java.lang.reflect.Method.invoke(Native
Re: [JBoss-dev] Are we logging the exception enough!!!
I was hoping you would do this outside of the container... so we can see clearly (with out the other mess) what is going on... =| --jason Casey Haakenson wrote: Here are the results of your code snippet below in a clean build of jboss. It looks like it's printed in a, b, c order if I go by the line in ApplicationBean that caused each stack trace. And unless I'm doing something else wrong, my patch does something odd with 3-level deep exceptions, so I think it is broken too. -Casey 15:30:33,708 ERROR [STDERR] org.jboss.deployment.DeploymentException: c; - nested throwable is: org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a 15:30:33,709 ERROR [STDERR] + nested throwable: 15:30:33,709 ERROR [STDERR] org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a 15:30:33,709 ERROR [STDERR] + nested throwable: 15:30:33,710 ERROR [STDERR] org.jboss.deployment.DeploymentException: a 15:30:33,710 ERROR [STDERR] at f5.ApplicationBean.ejbPostCreate(ApplicationBean.java:67) 15:30:33,711 ERROR [STDERR] at java.lang.reflect.Method.invoke(Native Method) 15:30:33,711 ERROR [STDERR] at org.jboss.ejb.plugins.CMPPersistenceManager.postCreateEntity(CMPPersistenceManager.java:284) 15:30:33,756 ERROR [STDERR] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.postCreateEntity(CachedConnectionInterceptor.java:239) 15:30:33,757 ERROR [STDERR] at org.jboss.ejb.EntityContainer.postCreateHome(EntityContainer.java:716) 15:30:33,757 ERROR [STDERR] at java.lang.reflect.Method.invoke(Native Method) 15:30:33,758 ERROR [STDERR] at org.jboss.ejb.EntityContainer$ContainerInterceptor.invoke(EntityContainer.java:1164) 15:30:33,758 ERROR [STDERR] at org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor.invoke(JDBCRelationInterceptor.java:190) 15:30:33,758 ERROR [STDERR] at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynchronizationInterceptor.java:313) 15:30:33,759 ERROR [STDERR] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:147) 15:30:33,759 ERROR [STDERR] at org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:193) 15:30:33,759 ERROR [STDERR] at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:107) 15:30:33,760 ERROR [STDERR] at org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationInterceptor.java:59) 15:30:33,760 ERROR [STDERR] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:98) 15:30:33,761 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:167) 15:30:33,761 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:52) 15:30:33,761 ERROR [STDERR] at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:104) 15:30:33,762 ERROR [STDERR] at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:109) 15:30:33,762 ERROR [STDERR] at org.jboss.ejb.EntityContainer.invokeHome(EntityContainer.java:487) 15:30:33,762 ERROR [STDERR] at org.jboss.ejb.Container.invoke(Container.java:727) 15:30:33,763 ERROR [STDERR] at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1055) 15:30:33,763 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:492) 15:30:33,763 ERROR [STDERR] at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:364) 15:30:33,764 ERROR [STDERR] at java.lang.reflect.Method.invoke(Native Method) 15:30:33,764 ERROR [STDERR] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:241) 15:30:33,765 ERROR [STDERR] at sun.rmi.transport.Transport$1.run(Transport.java:152) 15:30:33,765 ERROR [STDERR] at java.security.AccessController.doPrivileged(Native Method) 15:30:33,765 ERROR [STDERR] at sun.rmi.transport.Transport.serviceCall(Transport.java:148) 15:30:33,766 ERROR [STDERR] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:465) 15:30:33,766 ERROR [STDERR] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:706) 15:30:33,766 ERROR [STDERR] at java.lang.Thread.run(Thread.java:484) 15:30:33,767 ERROR [STDERR] + throwable: 15:30:33,767 ERROR [STDERR] org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a 15:30:33,767 ERROR [STDERR] at f5.ApplicationBean.ejbPostCreate(ApplicationBean.java:68) 15:30:33,768 ERROR [STDERR] at java.lang.reflect.Method.invoke(Native Method) 15:30:33,768 ERROR [STDERR] at
[JBoss-dev] [ jboss-Bugs-542801 ] 2.4.5 RC1: NoClassDefFoundError (crypto)
Bugs item #542801, was opened at 2002-04-11 22:01 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=542801group_id=22866 Category: JBossSX Group: v2.4 (stable) Status: Open Resolution: Accepted Priority: 5 Submitted By: Jeffrey Wescott (binaryfeed) Assigned to: Scott M Stark (starksm) Summary: 2.4.5 RC1: NoClassDefFoundError (crypto) Initial Comment: Using the JBoss-2.4.5_Tomcat-4.0.3 RC1 (04/11) bundle, trying to login using ProxyLoginModule -- DatabaseServerLoginModule gives: java.lang.NoClassDefFoundError: org/jboss/crypto/JBossXSProvider My _guess_ is that this class needs to be added to whatever jar file is seen by the ProxyLoginModule. -- Comment By: Brian Coyner (coyner_b) Date: 2002-04-18 17:24 Message: Logged In: YES user_id=513857 Is the version tag 2.4? If not what is the exact version tag that will merge correctly with the 2.4.5RC1 bundle? If you do not mind, will you please list the changes you made so that I can be sure that I have retrieved the correct files? Thanks. -- Comment By: Scott M Stark (starksm) Date: 2002-04-17 21:06 Message: Logged In: YES user_id=175228 Changes that should fix this issue have been checked into the 2.4 branch, but I until I can reproduce the exception I'm not sure the test cases are complete. -- Comment By: Brian Coyner (coyner_b) Date: 2002-04-17 21:05 Message: Logged In: YES user_id=513857 Here is the stack trace that is produced by another classpath issue. The stack trace for the original exception/ bug was the same as this stack trace. I hope this helps. Let me know if you need more information. I am more than happy to help! [INFO,SRPService] Starting [ERROR,ConfigurationService] Unexpected error java.lang.NoClassDefFoundError: org/jboss/security/srp/SRPParameters at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods (Class.java:1613) at java.lang.Class.privateGetPublicMethods (Class.java:1641) at java.lang.Class.getMethod0(Class.java:1730) at java.lang.Class.getMethod(Class.java:951) at org.jboss.security.srp.SRPRemoteServer_Stub.clinit (Unknown Source) at sun.reflect.NativeConstructorAccessorImpl.newInstance0 (Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance (NativeConstruct orAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance (DelegatingC onstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance (Constructor.java:274) at sun.rmi.server.RemoteProxy.getStub (RemoteProxy.java:95) at sun.rmi.server.RemoteProxy.getStub (RemoteProxy.java:55) at sun.rmi.server.UnicastServerRef.setSkeleton (UnicastServerRef.java:179 ) at sun.rmi.server.UnicastServerRef.exportObject (UnicastServerRef.java:14 2) at sun.rmi.server.UnicastServerRef.exportObject (UnicastServerRef.java:12 9) at java.rmi.server.UnicastRemoteObject.exportObject (UnicastRemoteObject. java:275) at java.rmi.server.UnicastRemoteObject.exportObject (UnicastRemoteObject. java:206) at java.rmi.server.UnicastRemoteObject.init (UnicastRemoteObject.java:9 7) at org.jboss.security.srp.SRPRemoteServer.init (SRPRemoteServer.java:63 ) at org.jboss.security.srp.SRPService.startService (SRPService.java:238) at org.jboss.util.ServiceMBeanSupport.start (ServiceMBeanSupport.java:103 ) at sun.reflect.GeneratedMethodAccessor9.invoke (Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sun.management.jmx.MBeanServerImpl.invoke (MBeanServerImpl.java:16 28) at com.sun.management.jmx.MBeanServerImpl.invoke (MBeanServerImpl.java:15 23) at org.jboss.configuration.ConfigurationService$ServiceProxy.in voke(Conf igurationService.java:967) at $Proxy0.start(Unknown Source) at org.jboss.util.ServiceControl.start (ServiceControl.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sun.management.jmx.MBeanServerImpl.invoke (MBeanServerImpl.java:16 28) at com.sun.management.jmx.MBeanServerImpl.invoke (MBeanServerImpl.java:15 23) at org.jboss.Main.init(Main.java:208) at org.jboss.Main$1.run(Main.java:110) at java.security.AccessController.doPrivileged (Native Method) at
[JBoss-dev] [ jboss-Bugs-545821 ] web-app local-refs don't work
Bugs item #545821, was opened at 2002-04-18 15:47 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=545821group_id=22866 Category: None Group: v3.0 Rabbit Hole Status: Deleted Resolution: None Priority: 5 Submitted By: Peter Luttrell (objec) Assigned to: Nobody/Anonymous (nobody) Summary: web-app local-refs don't work Initial Comment: jboss3.0rc1+tomcat4.0.3 I attempted to lookup an ejb via local interface in a web app. As I read the spec you need to specify the refernce in the web.xml as such: ejb-local-ref ejb-ref-namejndiLookupName/ejb-ref-name ejb-ref-typeEntity/ejb-ref-type local-homemyLocalHome/local-home localmyLocal/local ejb-linkejb-name/ejb-link /ejb-local-ref The problem is the ejb-name. Jboss can't seam to locate the ejb and thus can't build the ENC. My war is located in the root of an ear, named test.war. My ejb-jar (with the ejb I need) is located in the root of the ear, named test-ejbs.jar. The spec states (from web-app_2_3.dtd): !-- The ejb-link element is used in the ejb-ref or ejb- local-ref elements to specify that an EJB reference is linked to an enterprise bean. The name in the ejb-link element is composed of a path name specifying the ejb-jar containing the referenced enterprise bean with the ejb-name of the target bean appended and separated from the path name by #. The path name is relative to the war file containing the web application that is referencing the enterprise bean. This allows multiple enterprise beans with the same ejb-name to be uniquely identified. Used in: ejb-local-ref, ejb-ref Examples: ejb-linkEmployeeRecord/ejb-link ejb- link../products/product.jar#ProductEJB/ejb-link -- Thus I've tried these values for ejb-link: myEjbName test-ejbs.jar#myEjbName But neither work. Two additional things that I tried are: adding a reference to the test-ejbs.jar in the Manifest.mf file for the war. adding the test-ejbs.jar file to the WEB-INF\lib dir in my war. Here's the exception: 15:29:02,961 ERROR [EmbeddedCatalinaServiceSX] Failed to setup web application ENC javax.naming.NamingException: ejb-local-ref: jndiLookupName, target not found, add valid ejb-link at org.jboss.web.AbstractWebContainer.linkEjbLocalRefs (AbstractWebContainer.java:757) at org.jboss.web.AbstractWebContainer.parseWebAppDescripto rs(AbstractWebContainer.java:567) at org.jboss.web.AbstractWebContainer$DescriptorParser.par seWebAppDescriptors(AbstractWebCon tainer.java:1050) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.contex tInit(EmbeddedCatalinaServiceSX.ja va:334) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.access $000(EmbeddedCatalinaServiceSX.jav a:74) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX$1.life cycleEvent(EmbeddedCatalinaService SX.java:276) at org.apache.catalina.util.LifecycleSupport.fireLifecycle Event(LifecycleSupport.java:155) at org.apache.catalina.core.ContainerBase.start (ContainerBase.java:1131) at org.apache.catalina.core.StandardContext.start (StandardContext.java:3345) at org.apache.catalina.core.ContainerBase.addChild (ContainerBase.java:785) at org.apache.catalina.core.StandardHost.addChild (StandardHost.java:454) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.create WebContext(EmbeddedCatalinaService SX.java:284) at org.jboss.web.catalina.EmbeddedCatalinaServiceSX.perfor mDeploy(EmbeddedCatalinaServiceSX. java:204) at org.jboss.web.AbstractWebContainer.start (AbstractWebContainer.java:405) at org.jboss.deployment.MainDeployer.start (MainDeployer.java:665) at org.jboss.deployment.MainDeployer.start (MainDeployer.java:658) at org.jboss.deployment.MainDeployer.deploy (MainDeployer.java:507) at org.jboss.deployment.MainDeployer.deploy (MainDeployer.java:470) at sun.reflect.GeneratedMethodAccessor6.invoke (Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke (Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke (ReflectedMBeanDispatcher.java:284 ) at org.jboss.mx.server.MBeanServerImpl.invoke (MBeanServerImpl.java:492) at org.jboss.util.jmx.MBeanProxy.invoke (MBeanProxy.java:174) at $Proxy4.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deplo y(URLDeploymentScanner.java:350) at org.jboss.deployment.scanner.URLDeploymentScanner.scanD irectory(URLDeploymentScanner.java :530) at org.jboss.deployment.scanner.URLDeploymentScanner.scan (URLDeploymentScanner.java:410) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ ScannerThread.loop(AbstractDeploym entScanner.java:202) at org.jboss.deployment.scanner.AbstractDeploymentScanner$
RE: [JBoss-dev] Are we logging the exception enough!!!
Title: RE: [JBoss-dev] Are we logging the exception enough!!! I figured I would run it in container to compare apples to apples, but here it is outside of the container. Source file attached. -Casey org.jboss.deployment.DeploymentException: c; - nested throwable is: org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a + nested throwable: org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a + nested throwable: org.jboss.deployment.DeploymentException: a at ExceptionClass.main(ExceptionClass.java:18) + throwable: org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a at ExceptionClass.main(ExceptionClass.java:19) + throwable: org.jboss.deployment.DeploymentException: c; - nested throwable is: org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a at ExceptionClass.main(ExceptionClass.java:20) -Original Message- From: Jason Dillon [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 3:45 PM To: Casey Haakenson Cc: [EMAIL PROTECTED]; 'marc fleury'; David Jencks; Scott M Stark Subject: Re: [JBoss-dev] Are we logging the exception enough!!! I was hoping you would do this outside of the container... so we can see clearly (with out the other mess) what is going on... =| --jason Casey Haakenson wrote: Here are the results of your code snippet below in a clean build of jboss. It looks like it's printed in a, b, c order if I go by the line in ApplicationBean that caused each stack trace. And unless I'm doing something else wrong, my patch does something odd with 3-level deep exceptions, so I think it is broken too. -Casey 15:30:33,708 ERROR [STDERR] org.jboss.deployment.DeploymentException: c; - nested throwable is: org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a 15:30:33,709 ERROR [STDERR] + nested throwable: 15:30:33,709 ERROR [STDERR] org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a 15:30:33,709 ERROR [STDERR] + nested throwable: 15:30:33,710 ERROR [STDERR] org.jboss.deployment.DeploymentException: a 15:30:33,710 ERROR [STDERR] at f5.ApplicationBean.ejbPostCreate(ApplicationBean.java:67) 15:30:33,711 ERROR [STDERR] at java.lang.reflect.Method.invoke(Native Method) 15:30:33,711 ERROR [STDERR] at org.jboss.ejb.plugins.CMPPersistenceManager.postCreateEntity(CMPPersistenceManager.java:284) 15:30:33,756 ERROR [STDERR] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.postCreateEntity(CachedConnectionInterceptor.java:239) 15:30:33,757 ERROR [STDERR] at org.jboss.ejb.EntityContainer.postCreateHome(EntityContainer.java:716) 15:30:33,757 ERROR [STDERR] at java.lang.reflect.Method.invoke(Native Method) 15:30:33,758 ERROR [STDERR] at org.jboss.ejb.EntityContainer$ContainerInterceptor.invoke(EntityContainer.java:1164) 15:30:33,758 ERROR [STDERR] at org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor.invoke(JDBCRelationInterceptor.java:190) 15:30:33,758 ERROR [STDERR] at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynchronizationInterceptor.java:313) 15:30:33,759 ERROR [STDERR] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:147) 15:30:33,759 ERROR [STDERR] at org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:193) 15:30:33,759 ERROR [STDERR] at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:107) 15:30:33,760 ERROR [STDERR] at org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationInterceptor.java:59) 15:30:33,760 ERROR [STDERR] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:98) 15:30:33,761 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:167) 15:30:33,761 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:52) 15:30:33,761 ERROR [STDERR] at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:104) 15:30:33,762 ERROR [STDERR] at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:109) 15:30:33,762 ERROR [STDERR] at org.jboss.ejb.EntityContainer.invokeHome(EntityContainer.java:487) 15:30:33,762 ERROR [STDERR] at org.jboss.ejb.Container.invoke(Container.java:727) 15:30:33,763 ERROR [STDERR] at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1055) 15:30:33,763 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:492) 15:30:33,763 ERROR [STDERR] at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:364) 15:30:33,764 ERROR
[JBoss-dev] CVS update: jbosstest build.xml
User: starksm
Date: 02/04/18 16:16:56
Modified:.Tag: Branch_3_0 build.xml
Log:
Add the org.jboss.test.util.Debug class to the naming test jars
Revision ChangesPath
No revision
No revision
1.106.2.3 +5 -1 jbosstest/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jbosstest/build.xml,v
retrieving revision 1.106.2.2
retrieving revision 1.106.2.3
diff -u -r1.106.2.2 -r1.106.2.3
--- build.xml 17 Apr 2002 13:57:14 - 1.106.2.2
+++ build.xml 18 Apr 2002 23:16:56 - 1.106.2.3
@@ -13,7 +13,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.106.2.2 2002/04/17 13:57:14 d_jencks Exp $ --
+!-- $Id: build.xml,v 1.106.2.3 2002/04/18 23:16:56 starksm Exp $ --
project default=main name=JBoss/Testsuite
@@ -1418,6 +1418,7 @@
patternset refid=common.test.application.classes/
include name=org/jboss/test/naming/ejb/**/
include name=org/jboss/test/naming/interfaces/**/
+include name=org/jboss/test/util/Debug.class/
/fileset
fileset dir=${build.resources}/naming/jar
include name=META-INF/*.xml/
@@ -1430,6 +1431,7 @@
patternset refid=common.test.application.classes/
include name=org/jboss/test/naming/ejb/**/
include name=org/jboss/test/naming/interfaces/**/
+include name=org/jboss/test/util/Debug.class/
/fileset
fileset dir=${build.resources}/remote-naming
include name=**/*.xml/
@@ -1442,6 +1444,7 @@
patternset refid=common.test.application.classes/
include name=org/jboss/test/naming/ejb/**/
include name=org/jboss/test/naming/interfaces/**/
+include name=org/jboss/test/util/Debug.class/
/fileset
fileset dir=${build.resources}/naming/ear/a
include name=META-INF/*.xml/
@@ -1454,6 +1457,7 @@
patternset refid=common.test.application.classes/
include name=org/jboss/test/naming/ejb/**/
include name=org/jboss/test/naming/interfaces/**/
+include name=org/jboss/test/util/Debug.class/
/fileset
fileset dir=${build.resources}/naming/ear/b
include name=META-INF/*.xml/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/naming/ejb TestEjbLinkBean.java
User: starksm
Date: 02/04/18 16:15:02
Modified:src/main/org/jboss/test/naming/ejb Tag: Branch_3_0
TestEjbLinkBean.java
Log:
Report the full details of the JNDI proxy implementing TestEjbLinkLocalHome
as well as the details on the static reference to TestEjbLinkLocalHome.
Revision ChangesPath
No revision
No revision
1.2.2.1 +25 -1
jbosstest/src/main/org/jboss/test/naming/ejb/TestEjbLinkBean.java
Index: TestEjbLinkBean.java
===
RCS file:
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/naming/ejb/TestEjbLinkBean.java,v
retrieving revision 1.2
retrieving revision 1.2.2.1
diff -u -r1.2 -r1.2.2.1
--- TestEjbLinkBean.java 23 Mar 2002 01:55:54 - 1.2
+++ TestEjbLinkBean.java 18 Apr 2002 23:15:02 - 1.2.2.1
@@ -13,11 +13,12 @@
import org.jboss.test.naming.interfaces.TestEjbLink;
import org.jboss.test.naming.interfaces.TestEjbLinkLocalHome;
import org.jboss.test.naming.interfaces.TestEjbLinkLocal;
+import org.jboss.test.util.Debug;
/** A bean that tests ejb-link works
@author a href=mailto:[EMAIL PROTECTED];Adrian.Brock/a
-@version $Revision: 1.2 $
+@version $Revision: 1.2.2.1 $
*/
public class TestEjbLinkBean implements SessionBean
{
@@ -50,6 +51,17 @@
{
InitialContext initial = new InitialContext();
Object object = initial.lookup(jndiName);
+ log.debug(jndiName=+jndiName);
+
+ StringBuffer results = new StringBuffer(testEjbLinkCaller Proxy info\n);
+ Debug.displayClassInfo(object.getClass(), results);
+ log.debug(results.toString());
+
+ results.setLength(0);
+ results.append(testEjbLinkCaller TestEjbLinkLocalHome.class info\n);
+ Debug.displayClassInfo(TestEjbLinkLocalHome.class, results);
+ log.debug(results.toString());
+
TestEjbLinkHome home =
(TestEjbLinkHome) PortableRemoteObject.narrow(object,
TestEjbLinkHome.class);
TestEjbLink bean = home.create();
@@ -68,6 +80,17 @@
{
InitialContext initial = new InitialContext();
Object object = initial.lookup(jndiName);
+ log.debug(jndiName=+jndiName);
+
+ StringBuffer results = new StringBuffer(testEjbLinkCallerLocal Proxy
info\n);
+ Debug.displayClassInfo(object.getClass(), results);
+ log.debug(results.toString());
+
+ results.setLength(0);
+ results.append(testEjbLinkCallerLocal TestEjbLinkLocalHome.class
info\n);
+ Debug.displayClassInfo(TestEjbLinkLocalHome.class, results);
+ log.debug(results.toString());
+
TestEjbLinkLocalHome home =
(TestEjbLinkLocalHome) PortableRemoteObject.narrow(object,
TestEjbLinkLocalHome.class);
TestEjbLinkLocal bean = home.create();
@@ -84,4 +107,5 @@
{
return Works;
}
+
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/util Debug.java
User: starksm Date: 02/04/18 16:15:45 Added: src/main/org/jboss/test/util Tag: Branch_3_0 Debug.java Log: Various debugging utility methods available for use in unit tests Revision ChangesPath No revision No revision 1.1.2.1 +83 -0 jbosstest/src/main/org/jboss/test/util/Attic/Debug.java ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/util Debug.java
User: starksm Date: 02/04/18 16:22:45 Added: src/main/org/jboss/test/util Debug.java Log: Various debugging utility methods available for use in unit tests Revision ChangesPath 1.2 +83 -0 jbosstest/src/main/org/jboss/test/util/Debug.java ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest build.xml
User: starksm
Date: 02/04/18 16:22:00
Modified:.build.xml
Log:
Add the org.jboss.test.util.Debug class to the naming test jars
Revision ChangesPath
1.109 +5 -1 jbosstest/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jbosstest/build.xml,v
retrieving revision 1.108
retrieving revision 1.109
diff -u -r1.108 -r1.109
--- build.xml 17 Apr 2002 14:06:46 - 1.108
+++ build.xml 18 Apr 2002 23:21:57 - 1.109
@@ -13,7 +13,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.108 2002/04/17 14:06:46 d_jencks Exp $ --
+!-- $Id: build.xml,v 1.109 2002/04/18 23:21:57 starksm Exp $ --
project default=main name=JBoss/Testsuite
@@ -1418,6 +1418,7 @@
patternset refid=common.test.application.classes/
include name=org/jboss/test/naming/ejb/**/
include name=org/jboss/test/naming/interfaces/**/
+include name=org/jboss/test/util/Debug.class/
/fileset
fileset dir=${build.resources}/naming/jar
include name=META-INF/*.xml/
@@ -1430,6 +1431,7 @@
patternset refid=common.test.application.classes/
include name=org/jboss/test/naming/ejb/**/
include name=org/jboss/test/naming/interfaces/**/
+include name=org/jboss/test/util/Debug.class/
/fileset
fileset dir=${build.resources}/remote-naming
include name=**/*.xml/
@@ -1442,6 +1444,7 @@
patternset refid=common.test.application.classes/
include name=org/jboss/test/naming/ejb/**/
include name=org/jboss/test/naming/interfaces/**/
+include name=org/jboss/test/util/Debug.class/
/fileset
fileset dir=${build.resources}/naming/ear/a
include name=META-INF/*.xml/
@@ -1454,6 +1457,7 @@
patternset refid=common.test.application.classes/
include name=org/jboss/test/naming/ejb/**/
include name=org/jboss/test/naming/interfaces/**/
+include name=org/jboss/test/util/Debug.class/
/fileset
fileset dir=${build.resources}/naming/ear/b
include name=META-INF/*.xml/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/main/org/jboss/test/naming/ejb TestEjbLinkBean.java
User: starksm
Date: 02/04/18 16:23:37
Modified:src/main/org/jboss/test/naming/ejb TestEjbLinkBean.java
Log:
Report the full details of the JNDI proxy implementing TestEjbLinkLocalHome
as well as the details on the static reference to TestEjbLinkLocalHome.
Revision ChangesPath
1.3 +25 -1
jbosstest/src/main/org/jboss/test/naming/ejb/TestEjbLinkBean.java
Index: TestEjbLinkBean.java
===
RCS file:
/cvsroot/jboss/jbosstest/src/main/org/jboss/test/naming/ejb/TestEjbLinkBean.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- TestEjbLinkBean.java 23 Mar 2002 01:55:54 - 1.2
+++ TestEjbLinkBean.java 18 Apr 2002 23:23:37 - 1.3
@@ -13,11 +13,12 @@
import org.jboss.test.naming.interfaces.TestEjbLink;
import org.jboss.test.naming.interfaces.TestEjbLinkLocalHome;
import org.jboss.test.naming.interfaces.TestEjbLinkLocal;
+import org.jboss.test.util.Debug;
/** A bean that tests ejb-link works
@author a href=mailto:[EMAIL PROTECTED];Adrian.Brock/a
-@version $Revision: 1.2 $
+@version $Revision: 1.3 $
*/
public class TestEjbLinkBean implements SessionBean
{
@@ -50,6 +51,17 @@
{
InitialContext initial = new InitialContext();
Object object = initial.lookup(jndiName);
+ log.debug(jndiName=+jndiName);
+
+ StringBuffer results = new StringBuffer(testEjbLinkCaller Proxy info\n);
+ Debug.displayClassInfo(object.getClass(), results);
+ log.debug(results.toString());
+
+ results.setLength(0);
+ results.append(testEjbLinkCaller TestEjbLinkLocalHome.class info\n);
+ Debug.displayClassInfo(TestEjbLinkLocalHome.class, results);
+ log.debug(results.toString());
+
TestEjbLinkHome home =
(TestEjbLinkHome) PortableRemoteObject.narrow(object,
TestEjbLinkHome.class);
TestEjbLink bean = home.create();
@@ -68,6 +80,17 @@
{
InitialContext initial = new InitialContext();
Object object = initial.lookup(jndiName);
+ log.debug(jndiName=+jndiName);
+
+ StringBuffer results = new StringBuffer(testEjbLinkCallerLocal Proxy
info\n);
+ Debug.displayClassInfo(object.getClass(), results);
+ log.debug(results.toString());
+
+ results.setLength(0);
+ results.append(testEjbLinkCallerLocal TestEjbLinkLocalHome.class
info\n);
+ Debug.displayClassInfo(TestEjbLinkLocalHome.class, results);
+ log.debug(results.toString());
+
TestEjbLinkLocalHome home =
(TestEjbLinkLocalHome) PortableRemoteObject.narrow(object,
TestEjbLinkLocalHome.class);
TestEjbLinkLocal bean = home.create();
@@ -84,4 +107,5 @@
{
return Works;
}
+
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Oracle Configuration JBoss 3.0 RC1
i got an oracle datasource by hacking the hsqldb service. can you send me the oracle-service.xml to have a look at? c Raj Saini wrote: I have installed the JBoss 3.0 RC1. I am not able configure the oracle. I have downloaded the oracle-service.xml from the cvs and made changes according to my site. The error I am getting is:- Class not found for mbean: DefautDomain:sevice=ConnectionFactoryLoader, name=OracleDS I know there is some class not loaded but not sure it is the JDBC driver class or some thing else. I have copied my classes12.zip (Ihave tried unzipping it and making a jar) in the JBOSS_HOME/lib dir. I have also tried copying the file in JBOSS_HOME/lib/ext. Can any one point me to the my mistkae please. thanks * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=13365 ___ 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] Automated JBoss Testsuite Results: 19-April-2002
Number of tests run: 570 Successful tests: 539 Errors:15 Failures: 16 [time of test: 19 April 2002 0:38 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] See http://lubega.com/testarchive/ibm_jdk13_20010626 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! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/iiop/src/main/org/jboss/iiop CorbaORBService.java
User: reverbel Date: 02/04/18 16:51:09 Modified:iiop/src/main/org/jboss/iiop CorbaORBService.java Log: If verbosity is zero then do not let JacORB send its version to stdout. Revision ChangesPath 1.13 +2 -2 contrib/iiop/src/main/org/jboss/iiop/CorbaORBService.java Index: CorbaORBService.java === RCS file: /cvsroot/jboss/contrib/iiop/src/main/org/jboss/iiop/CorbaORBService.java,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- CorbaORBService.java 17 Apr 2002 13:21:57 - 1.12 +++ CorbaORBService.java 18 Apr 2002 23:51:08 - 1.13 @@ -45,7 +45,7 @@ * for JBoss to use. * * @author a href=mailto:[EMAIL PROTECTED];Ole Husgaard/a - * @version $Revision: 1.12 $ + * @version $Revision: 1.13 $ */ public class CorbaORBService extends ServiceMBeanSupport @@ -120,7 +120,7 @@ props.put(org.omg.PortableInterceptor.ORBInitializerClass.standard_init, org.jacorb.orb.standardInterceptors.IORInterceptorInitializer); props.put(jacorb.verbosity, Integer.toString(verbosity)); - props.put(jacorb.orb.print_version, on); + props.put(jacorb.orb.print_version, ((verbosity == 0) ? off : on)); orb = ORB.init(new String[0], props); bind(ORB_NAME, org.omg.CORBA.ORB); ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Are we logging the exception enough!!!
Yes, it looks like this could be improved... can you submit a bug and assign it to me. --jason Casey Haakenson wrote: I figured I would run it in container to compare apples to apples, but here it is outside of the container. Source file attached. -Casey org.jboss.deployment.DeploymentException: c; - nested throwable is: org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a + nested throwable: org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a + nested throwable: org.jboss.deployment.DeploymentException: a at ExceptionClass.main(ExceptionClass.java:18) + throwable: org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a at ExceptionClass.main(ExceptionClass.java:19) + throwable: org.jboss.deployment.DeploymentException: c; - nested throwable is: org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a at ExceptionClass.main(ExceptionClass.java:20) -Original Message- From: Jason Dillon [ mailto:[EMAIL PROTECTED] ] Sent: Thursday, April 18, 2002 3:45 PM To: Casey Haakenson Cc: [EMAIL PROTECTED]; 'marc fleury'; David Jencks; Scott M Stark Subject: Re: [JBoss-dev] Are we logging the exception enough!!! I was hoping you would do this outside of the container... so we can see clearly (with out the other mess) what is going on... =| --jason Casey Haakenson wrote: Here are the results of your code snippet below in a clean build of jboss. It looks like it's printed in a, b, c order if I go by the line in ApplicationBean that caused each stack trace. And unless I'm doing something else wrong, my patch does something odd with 3-level deep exceptions, so I think it is broken too. -Casey 15:30:33,708 ERROR [STDERR] org.jboss.deployment.DeploymentException: c; - nested throwable is: org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a 15:30:33,709 ERROR [STDERR] + nested throwable: 15:30:33,709 ERROR [STDERR] org.jboss.deployment.DeploymentException: b; - nested throwable is: org.jboss.deployment.DeploymentException: a 15:30:33,709 ERROR [STDERR] + nested throwable: 15:30:33,710 ERROR [STDERR] org.jboss.deployment.DeploymentException: a 15:30:33,710 ERROR [STDERR] at f5.ApplicationBean.ejbPostCreate(ApplicationBean.java:67) 15:30:33,711 ERROR [STDERR] at java.lang.reflect.Method.invoke(Native Method) 15:30:33,711 ERROR [STDERR] at org.jboss.ejb.plugins.CMPPersistenceManager.postCreateEntity(CMPPersistenceManager.java:284) 15:30:33,756 ERROR [STDERR] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.postCreateEntity(CachedConnectionInterceptor.java:239) 15:30:33,757 ERROR [STDERR] at org.jboss.ejb.EntityContainer.postCreateHome(EntityContainer.java:716) 15:30:33,757 ERROR [STDERR] at java.lang.reflect.Method.invoke(Native Method) 15:30:33,758 ERROR [STDERR] at org.jboss.ejb.EntityContainer$ContainerInterceptor.invoke(EntityContainer.java:1164) 15:30:33,758 ERROR [STDERR] at org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor.invoke(JDBCRelationInterceptor.java:190) 15:30:33,758 ERROR [STDERR] at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynchronizationInterceptor.java:313) 15:30:33,759 ERROR [STDERR] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:147) 15:30:33,759 ERROR [STDERR] at org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:193) 15:30:33,759 ERROR [STDERR] at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:107) 15:30:33,760 ERROR [STDERR] at org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationInterceptor.java:59) 15:30:33,760 ERROR [STDERR] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:98) 15:30:33,761 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:167) 15:30:33,761 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:52) 15:30:33,761 ERROR [STDERR] at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:104) 15:30:33,762 ERROR [STDERR] at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:109) 15:30:33,762 ERROR [STDERR] at org.jboss.ejb.EntityContainer.invokeHome(EntityContainer.java:487) 15:30:33,762 ERROR [STDERR] at org.jboss.ejb.Container.invoke(Container.java:727) 15:30:33,763 ERROR [STDERR] at
Re: [JBoss-dev] RC1 release branch occuring at 00:00
On Wed, 17 Apr 2002, Jason Dillon wrote: Just noticed that the iiop stuff from jacorb dumps useless crap to stderr stdout... perhaps we should import and manage these sources locally (like we do with Jetty), so we can turn these into logs... or something. Would it worth the trouble? You can tell JacORB to shut up by changing iiop-service.xml and setting to 0 the Verbosity attribute of the CorbaOrbService MBean. Maybe I should change the default verbosity to 0... Right now it is 1 just to help me with debugging. Cheers, Francisco ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Oracle Configuration JBoss 3.0 RC1
Here: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/jbosscx/src/etc/example-config/ - Original Message - From: Craig Day [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 18, 2002 6:36 PM Subject: Re: [JBoss-dev] Oracle Configuration JBoss 3.0 RC1 i got an oracle datasource by hacking the hsqldb service. can you send me the oracle-service.xml to have a look at? c Raj Saini wrote: I have installed the JBoss 3.0 RC1. I am not able configure the oracle. I have downloaded the oracle-service.xml from the cvs and made changes according to my site. The error I am getting is:- Class not found for mbean: DefautDomain:sevice=ConnectionFactoryLoader, name=OracleDS I know there is some class not loaded but not sure it is the JDBC driver class or some thing else. I have copied my classes12.zip (Ihave tried unzipping it and making a jar) in the JBOSS_HOME/lib dir. I have also tried copying the file in JBOSS_HOME/lib/ext. Can any one point me to the my mistkae please. thanks * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=13365 ___ 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-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: mysql-service.xml
Check the example files here: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/jbosscx/src/etc/example-config/ Follow the instructions in the XML comments. Ricardo - Original Message - From: John Mello [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 18, 2002 5:40 PM Subject: Re: [JBoss-dev] Re: mysql-service.xml Hi Claus, Thank you for you help but now give the following error: java.io.IOException: Properties file users.properties not found Thanks, João * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=13151 ___ 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
Re: [JBoss-dev] RC1 release branch occuring at 00:0
On Wed, 17 Apr 2002, Jason Dillon wrote:
Basically what happens is that a parameterless ORB.init() call is
performed within a call to ORB.init(args, props).
Class org.jacorb.orb.ORB handles the call to ORB.init(args, props) and
indirectly performs the parameterless ORB.init() call, which should
be relayed to class org.jacorb.orb.ORBSingleton, per specified by a
system property. It appears that this class is not found... How come?
It is in the same jar as the class org.jacorb.orb.ORB...
How does it find ORBSingleton? Might need to use TCL...
Don't know. ORB.init() is in class org.omg.ORB, which is provided by the
JDK. I don't have the source.
ic... based on the context above I was assuming ORB.init() was
org.jacorb.orb.ORB()... as I know nothing about how iiop/corba works in
Java.
ORB.init is a static method of class org.omg.CORBA.ORB. This class is a
standard one and both jacorb and the jdk have implementations if it.
The ORB.init() method should load an ORB-specific implementation class
specified by a sysprop. In jacorb's case, it should load the class
org.jacorb.orb.ORBSingleton.
Setting the context classloader might help... Looks like a hack, but is
worth a try.
JBoss should have already set the TCL, if not then it won't hurt to set
it... though it really depends on how the org.omb.ORB class finds the
target orb class... if that method does not look at the TCL when loading
the class then it will never work.
Yes, JBoss already set the TCL. This is why things work with Sun VMs
and not with IBM VMs. See below.
The problem might be very similar to URL problem protocol handlers,
since URL is on the system classpath does not use the TCL when looking
for handler classes, its default mechanism to search for handlers by
setting a property can not be used to load JBoss handlers, as they do
not (and probably will never) live on the system classpath.
You are right. See below.
Must disconnect now... Tomorrow I´ll let you know if TCL worked.
I bet you can find the source for org.omb.ORB somewhere...
Yes I did. And guess what is the difference between the Sun version and
the IBM version of org.omg.CORBA.ORB...
Sun's ORB.init:
ClassLoader cl = Thread.currentThread().getContextClassLoader();
if (cl == null)
cl = ClassLoader.getSystemClassLoader();
try {
return (ORB) Class.forName(className, true, cl).newInstance();
}
...
IBM's ORB.init:
// Dont use the ContextClassLoader because it would potentially
// allow an untrusted applet to install the shared singleton ORB.
// ClassLoader cl = Thread.currentThread().getContextClassLoader();
ClassLoader cl = ClassLoader.getSystemClassLoader();
singleton = create_impl(className, cl);
where create_impl(className, cl) does a
return (ORB) Class.forName(className, true, cl).newInstance();
(The IBM guys commented out the TCL stuff on purpose.)
What now? I cannot see no other way out... Either we require IBM users
to say
export JBOSS_CLASSPATH=$JBOSS_HOME/lib/jacorb.jar
or we hack run.sh to do it for them.
Cheers,
Francisco
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] testsuite jdk1.4 compilation
The TestConnection and TestDBDriver classes weren't being used for anything so I removed them a couple of days ago. Is your cvs up to date? Did I miss a branch? david jencks On 2002.04.18 14:01:58 -0400 Larry Sanderson wrote: In order to compile the org.jboss.test.util.TestConnection.java class with jdk1.4, several methods must be uncommented (the JDBC 3.0 methods). It used to be that these methods caused this class to not compile with jdk1.3 due to the missing class, Savepoint. But this class is now included in the jboss-jca.jar archive, and now jdk1.3 compiles it correctly. Will there be a problem if I check TestConnection in with the JDBC 3.0 methods uncommented? -Larry * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=13360 ___ 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] Re: XDoclet in /tools has BUGSSSSSS
Hi David 1. tag your website builds You mean according to the jboss-all tags ? 2. Include the website in the testsuite. No idea what you mean ? From checking out jboss-all, I get the idea that it is all of jboss I have to worry about when I change things, and I think running build/build.sh clean main and testsuite/build.sh clean tests is all the testing available. If you want something else to work, you need to make it obvious when it is broken. My question is how to we solve this problem right now because we shouldn't use software in beta when there is a production release out there, shouldn't we ? What do you think about having two XDoclet version around: - xdoclet.jar which is the lastest stable production release - xdoclet.beta.jar which is a beta version when necessary like in your case you want to use the XMBean stuff Have fun - Andy ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 19-April-2002
Number of tests run: 568 Successful tests: 537 Errors:16 Failures: 15 [time of test: 19 April 2002 1:45 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] See http://lubega.com/testarchive/ibm_jdk13_20020124 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! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] RC1 release branch occuring at 00:00
I guess it depends on if we have more issues based on the JacORB impl or not. We are already working off a patched copy right? --jason Francisco Reverbel wrote: On Wed, 17 Apr 2002, Jason Dillon wrote: Just noticed that the iiop stuff from jacorb dumps useless crap to stderr stdout... perhaps we should import and manage these sources locally (like we do with Jetty), so we can turn these into logs... or something. Would it worth the trouble? You can tell JacORB to shut up by changing iiop-service.xml and setting to 0 the Verbosity attribute of the CorbaOrbService MBean. Maybe I should change the default verbosity to 0... Right now it is 1 just to help me with debugging. Cheers, Francisco ___ 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
Re: [JBoss-dev] Re: XDoclet in /tools has BUGSSSSSS
I would like to avoid having this namespace setup... can't we just get xdoclet fixed? Or stop using beta features. --jason Andreas Schaefer wrote: Hi David 1. tag your website builds You mean according to the jboss-all tags ? 2. Include the website in the testsuite. No idea what you mean ? From checking out jboss-all, I get the idea that it is all of jboss I have to worry about when I change things, and I think running build/build.sh clean main and testsuite/build.sh clean tests is all the testing available. If you want something else to work, you need to make it obvious when it is broken. My question is how to we solve this problem right now because we shouldn't use software in beta when there is a production release out there, shouldn't we ? What do you think about having two XDoclet version around: - xdoclet.jar which is the lastest stable production release - xdoclet.beta.jar which is a beta version when necessary like in your case you want to use the XMBean stuff Have fun - Andy ___ 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
Re: [JBoss-dev] Re: mysql-service.xml
Hi Ricardo, Thank you for you help, but that was the configuration that I had, but now I have the following error when I try to deploy. 2002-04-18 20:57:46,657 DEBUG [org.jboss.system.ServiceController] stopping service: jboss.j2ee:service=EjbModule,url=file%/C%/jboss-3.0.0beta/server/default/deploy/jbmserveejb.jar 2002-04-18 20:57:46,657 DEBUG [org.jboss.system.ServiceController] service context has 0 depending services 2002-04-18 20:57:46,657 DEBUG [org.jboss.system.ServiceController] destroying service: jboss.j2ee:service=EjbModule,url=file%/C%/jboss-3.0.0beta/server/default/deploy/jbmserveejb.jar 2002-04-18 20:57:46,667 INFO [org.jboss.ejb.EjbModule] Destroying 2002-04-18 20:57:46,697 INFO [org.jboss.ejb.EjbModule] Remove JSR-77 EJB Module: jboss.management.single:J2EEApplication= ,J2EEServer=Single,j2eeType=EJBModule,name=jbmserveejb.jar 2002-04-18 20:57:46,707 INFO [org.jboss.ejb.EjbModule] Destroyed 2002-04-18 20:57:46,707 DEBUG [org.jboss.system.ServiceController] removing service: jboss.j2ee:service=EjbModule,url=file%/C%/jboss-3.0.0beta/server/default/deploy/jbmserveejb.jar 2002-04-18 20:57:46,707 DEBUG [org.jboss.system.ServiceController] removing jboss.j2ee:service=EjbModule,url=file%/C%/jboss-3.0.0beta/server/default/deploy/jbmserveejb.jar from server 2002-04-18 20:57:46,707 INFO [org.jboss.deployment.MainDeployer] could not delete directory file:/C:/jboss-3.0.0beta/server/default/tmp/deploy/C/jboss-3.0.0beta/server/default/deploy/jbmserveejb.jar/79.jbmserveejb.jar restart will delete it 2002-04-18 20:57:46,717 INFO [org.jboss.deployment.MainDeployer] Undeployed file:/C:/jboss-3.0.0beta/server/default/deploy/jbmserveejb.jar 2002-04-18 20:57:46,717 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.0beta/server/default/deploy/jbmserveejb.jar 2002-04-18 20:57:46,727 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/C:/jboss-3.0.0beta/server/default/deploy/jbmserveejb.jar 2002-04-18 20:57:46,777 DEBUG [org.jboss.deployment.MainDeployer] using deployer org.jboss.ejb.EJBDeployer@52fc36 2002-04-18 20:57:46,787 DEBUG [org.jboss.deployment.MainDeployer] found 0 subpackages of file:/C:/jboss-3.0.0beta/server/default/deploy/jbmserveejb.jar 2002-04-18 20:57:46,787 DEBUG [org.jboss.deployment.MainDeployer] Watching new file: file:/C:/jboss-3.0.0beta/server/default/deploy/jbmserveejb.jar 2002-04-18 20:57:46,787 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/C:/jboss-3.0.0beta/server/default/deploy/jbmserveejb.jar 2002-04-18 20:57:46,927 DEBUG [org.jboss.ejb.EJBDeployer] Verifying file:/C:/jboss-3.0.0beta/server/default/deploy/jbmserveejb.jar 2002-04-18 20:57:46,987 DEBUG [org.jboss.ejb.EJBDeployer] User: Verified. 2002-04-18 20:57:47,007 DEBUG [org.jboss.ejb.EJBDeployer] UserManager: Verified. 2002-04-18 20:57:47,007 DEBUG [org.jboss.ejb.EJBDeployer] Deploying: file:/C:/jboss-3.0.0beta/server/default/deploy/jbmserveejb.jar 2002-04-18 20:57:47,007 INFO [org.jboss.ejb.EjbModule] Creating 2002-04-18 20:57:47,027 DEBUG [org.jboss.ejb.EjbModule] Application.start(), begin 2002-04-18 20:57:47,027 DEBUG [org.jboss.management.j2ee.EJBModule] EJBModule.create(), server name: J2EEServer=Single 2002-04-18 20:57:47,027 DEBUG [org.jboss.management.j2ee.J2EEDeployedObject] File: file:/C:/jboss-3.0.0beta/server/default/tmp/deploy/C/jboss-3.0.0beta/server/default/deploy/jbmserveejb.jar/80.jbmserveejb.jar, descriptor: META-INF/ejb-jar.xml 2002-04-18 20:57:47,037 DEBUG [org.jboss.management.j2ee.EJBModule] Create EJB-Module, name: jbmserveejb.jar, application: jboss.management.single:J2EEServer=Single,name= , dd: ?xml version=1.0 encoding=UTF-8? !DOCTYPE ejb-jar PUBLIC -//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN http://java.sun.com/dtd/ejb-jar_2_0.dtd; ejb-jar enterprise-beans session display-nameUserManager/display-name ejb-nameUserManager/ejb-name homejbmserve.ejb.usermanager.UserManagerHome/home remotejbmserve.ejb.usermanager.UserManager/remote ejb-classjbmserve.ejb.usermanager.UserManagerBean/ejb-class session-typeStateless/session-type transaction-typeContainer/transaction-type ejb-local-ref description / ejb-ref-nameejb/User/ejb-ref-name ejb-ref-typeEntity/ejb-ref-type local-homejbmserve.ejb.user.UserHome/local-home localjbmserve.ejb.user.User/local ejb-linkUser/ejb-link /ejb-local-ref /session entity display-nameUser/display-name ejb-nameUser/ejb-name local-homejbmserve.ejb.user.UserHome/local-home localjbmserve.ejb.user.User/local ejb-classjbmserve.ejb.user.UserBean/ejb-class persistence-typeContainer/persistence-type
[JBoss-dev] Automated JBoss Testsuite Results: 19-April-2002
Number of tests run: 570 Successful tests: 549 Errors:15 Failures: 6 [time of test: 19 April 2002 2:31 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1_02a-FCS] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com/testarchive/blackdown_jdk131_02_native 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! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] RC1 release branch occuring at 00:0
I bet you can find the source for org.omb.ORB somewhere...
Yes I did. And guess what is the difference between the Sun version and
the IBM version of org.omg.CORBA.ORB...
Sun's ORB.init:
ClassLoader cl = Thread.currentThread().getContextClassLoader();
if (cl == null)
cl = ClassLoader.getSystemClassLoader();
try {
return (ORB) Class.forName(className, true, cl).newInstance();
}
...
IBM's ORB.init:
// Dont use the ContextClassLoader because it would potentially
// allow an untrusted applet to install the shared singleton ORB.
// ClassLoader cl = Thread.currentThread().getContextClassLoader();
ClassLoader cl = ClassLoader.getSystemClassLoader();
singleton = create_impl(className, cl);
where create_impl(className, cl) does a
return (ORB) Class.forName(className, true, cl).newInstance();
Fuck... love java... love jvm vendors... write once, pray it works
everywhere... bastards.
*sigh*
(The IBM guys commented out the TCL stuff on purpose.)
What now? I cannot see no other way out... Either we require IBM users
to say
export JBOSS_CLASSPATH=$JBOSS_HOME/lib/jacorb.jar
or we hack run.sh to do it for them.
I would say file a bug on the IBM vm, then document for those users that
because IBM changed there impl that they need to do some special work.
And perhaps show them a link to the bug report so they can bitch too.
This way we don't complicate the system for everyone else... only those
using IBM.
I really wish these classes (among others) were not in the core JRE, so
we could simply insist that they use a version that works. Is it
possible that a different version of these classes could be put on the
jboss classpath (in lib/*) for this to work...
One day, the JRE will contain every possible buggy version of every
possible api and every different jvm vendor will fix the bugs in
non-standard ways and the entire java movement will fall flat on its
face... thanks SUN... =[
--jason
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: mysql-service.xml
I just found the problem. I did not define 'MySqlDbRealm' in login-config.xml. To all o you that help me, thank you. This is the price that all the newcomers have to pay. Thank you, João * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66thread=13151 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
