[JBoss-dev] NullPointerException deploying org.jboss.resource.ConnectionFactoryLoader MBean
Hi JBoss developers! I have a quick question. I just need some pointers... The following worked fine with the RH CVS code as of Nov, 7th. Since I updated today from the CVS and rebuilt I get the following error (see attached exception.txt) when the service XML file (see attached sybase-service.xml) is being deployed. Has something changed in the meantime that breaks the syntax/semantics of my file? Regards, Peter [09:50:49,960,AutoDeployer] Auto deploy of file:/net/stsrv_vol1/homes/peter/J2EE/jboss-3.0.0alpha/deploy/sybase-service.xml [09:50:50,100,Default] Libraries adding URLClassLoader -1325046644 key URL file:/net/stsrv_vol1/homes/peter/J2EE/jboss-3.0.0alpha/lib/ext/jconn2.jar [09:50:50,105,ServiceCreator] About to create the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Sybase_J2EETEST [09:50:50,109,ServiceCreator] Created the beanJBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Sybase_J2EETEST [09:50:50,578,ServiceController] Could not configure MBean: JBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Sybase_J2EETEST java.lang.NullPointerException at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:225) at org.jboss.system.ServiceController.deploy(ServiceController.java:215) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.deployment.ServiceDeployer.invoke(ServiceDeployer.java:732) at org.jboss.deployment.ServiceDeployer.addMBeans(ServiceDeployer.java:668) at org.jboss.deployment.ServiceDeployer.deploy(ServiceDeployer.java:215) at org.jboss.deployment.DeployerMBeanSupport.deploy(DeployerMBeanSupport.java:107) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.deployment.AutoDeployer.deploy(AutoDeployer.java:654) at org.jboss.deployment.AutoDeployer.run(AutoDeployer.java:327) at org.jboss.deployment.AutoDeployer.startService(AutoDeployer.java:509) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:117) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:775) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:479) at org.jboss.system.ServiceController.registerAndStartService(ServiceController.java:273) at org.jboss.system.ServiceController.deploy(ServiceController.java:257) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.deployment.ServiceDeployer.invoke(ServiceDeployer.java:732) at org.jboss.deployment.ServiceDeployer.addMBeans(ServiceDeployer.java:668) at org.jboss.deployment.ServiceDeployer.deploy(ServiceDeployer.java:215) at org.jboss.deployment.DeployerMBeanSupport.deploy(DeployerMBeanSupport.java:107) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.Main.init(Main.java:199) at org.jboss.Main$1.run(Main.java:411) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.Main.main(Main.java:406) ?xml version=1.0 encoding=UTF-8? server dependsJBOSS-SYSTEM:service=Naming/depends dependsJBOSS-SYSTEM:service=TransactionManager/depends dependsJCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory/depends dependsJCA:service=RARDeployer/depends classpath archives=jconn2.jar/ mbean code=org.jboss.resource.ConnectionFactoryLoader name=JBOSS-SYSTEM:service=ConnectionFactoryLoader,name=Sybase_J2EETEST attribute name=ManagedConnectionFactoryPropertiesConnectionURL=jdbc:sybase:Tds:vino:4100 DriverClass=com.sybase.jdbc2.jdbc.SybDriver UserName=j2eetest Password=j2eetest/attribute attribute name=JndiNameSybase_J2EETEST/attribute attribute name=TransactionManagerNamejava:/TransactionManager/attribute attribute name=ResourceAdapterNameMinerva JDBC LocalTransaction ResourceAdapter/attribute attribute name=RARDeployerNameJCA:service=RARDeployer/attribute attribute name=ConnectionManagerFactoryNameMinervaSharedLocalCMFactory/attribute
Re: [JBoss-dev] JBoss3/Jetty4 JBossSX integration...
H... I've given this a little more thought and The Servlet API should probably be part of JBoss and not the WebContainer implementation since it comprises part of the Specification of the Application Server. This prevents e.g hotswapping between e.g. 2.2 and 2.3 WebContainers, but rather enforces the fact that JBoss x.x MUST contain an implementation of Servlets y.y. Any comments ? Jasper being an implementation, should be in the jetty.sar. Javac/Tools is problematic. We can't ship it by default, since we don't own the Source/Copyright. So it must be : Either: 1. Used from $JAVA_HOME/lib (I guess this means put on the JBOSS_CLASSPATH)). Or: 2. linked/copied into the tree at JBoss install time, probably into lib/ or lib/ext - There is a dependency here as the Jetty jboss-service.xml needs to be updated to show Jetty's requirement. (What happens if you want to use a different JAVA_HOME post-install?) Or: 3. copied into the jetty.sar before sar-deployment. This avoids the need to update jetty's jboss-service.xml (I think). (What happens if you want to use a different JAVA_HOME post re-sar-ring of Jetty?). I may have missed possible problems arising from ClassLoader organisation within these three possibilities What does everyone think ? Looking at this my preference is to get it onto the JBOSS_CLASSPATH, since then Jetty gets to see the tools.jar belonging to the current $JAVA_HOME everytime. I have not experimented to see what I need in my jboss-service.xml, but this may require I enter a dependency on tools.jar - If it does, this is again problematic, since I will get a nasty exception at deployment time if we are only running on a JRE (not a JDK) and the tools.jar is not available. It is not mandatory since people may precompile their JSPs in which case Jasper does not need the compiler Any suggestions... Thanks for your input... Jules --- Julian Gosnell [EMAIL PROTECTED] wrote: David Jencks wrote: Julian, I spent a little time this weekend making jars in sars work, with Jetty as an example. If no one objects, I might check it in later tonight. I look forward to playing with it - thanks. What I've done/ found that works is: jetty-plugin.sar contains -previous contents (classes for the plugin) -org.mortbay.jetty.jar -org.mortbay.ftp.jar -org.mortbay.jetty.nbio.jar -org.mortbay.jetty.jmx.jar -org.mortbay.jetty.sasl.jar -org.mortbay.tools.jar -cryptix-sasl-jetty.jar I find that I need in lib/ext to make jasper work: tools.jar (not provided) for on-the-fly JSP compilation javax.servlet.jar The Servlet API - implemented by Jetty org.apache.jasper.jar JASPER JSP engine - consumed by Jetty Any idea why? See above. Since Servlet-API and Jasper versions vary with Jetty versions (3/2.2/1.1 or 4/2.3/1.2) I will probably roll these two jars into the same sar as well, then I can choose to drop in a version of Jetty3 or 4 (or later 5!) depending on which version of these I require. Does anyone object ? What do you think of this much repackaging? I think it's fine. Think of it like this. If I drop a Jetty sar into one node of a farm, I may want it up an running on every node - therefore it needs to contain everything that Jetty needs to run. Assuming that Jetty does not share Servlet-API Jasper components with any other JBoss module, these should probably be included as well. Does anyone feel strongly either way as to whether the tools/javac.jar should go in the jetty.sar or in lib/ext ? Does anyone else do on-the-fly compilation ? I suppose I may want to remove the jetty.sar and drop in an equivalent web-container that would - So I shall leave it in lib/ext - that makes it easier to write a script that copies it from JAVA_HOME as well. In addition, I am considering using the local-directory feature of sars to install the jetty.properties, jetty.xml, and webdefault.xml files into db/jetty-config/. Is this a good idea? I'll give this one some thought - we need to be careful not to replicate our efforts here (going into a subdirectory of db may not be the best place, but it is where the local-directory feature currently puts things) Thanks david jencks Thanks for all the help, David, Jules On 2001.11.18 20:37:20 -0500 Julian Gosnell wrote: Scott, Due to various changes in Jetty I am having to rework the Security integration. My authenticate() is not working and I'm afraid that I have a few simple questions ; 1. Is JBossSX working in RH yet, or am I wasting my time trying to get the testsuite's WebIntegrationUnitTestCase to run ? I look up the JBossSX Security Context once for each WebApp 2. I look up the securityMgr on EVERY authenticate() - could I do this ONCE on WebApp creation ? 3. I look up the realmMapping EVERY time I need
AW: [JBoss-dev] Bug #482875: Out of Memory
Does the Java VM consistently garbage-collect classloaders and classes? Having observed the behaviour of various IDE´s and other Java programs that deal with the issue of dynamically loading byte code, I´m not sure about this at all. If yes, the OOM-situation caused by hot-deployment is indeed a bug. CGJ -Ursprüngliche Nachricht- Von: Scott M Stark [mailto:[EMAIL PROTECTED]] Gesendet: Sonntag, 18. November 2001 00:41 An: [EMAIL PROTECTED] Betreff: Re: [JBoss-dev] Bug #482875: Out of Memory It is a bug, its just a question of its priority. The deployment code is getting old and crusty and needs to be redone. However, since it works well enough in the absence of multiple redeploys its not high on my priority list. The implicit assumption that hot deployment should not be used in production environments is really a criticism of the state of the hot deployment facility. It should be up to the user to make the decision as to whether hot deployment is enabled for a production environment. If I'm running an ASP environment where users can create stores and dynamically update their content then I am going to want some hot deploy feature. Right now were saying don't use ours. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Andreas Schaefer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, November 17, 2001 1:58 PM Subject: [JBoss-dev] Bug #482875: Out of Memory Hi Geeks Recently this bug was reported on JBoss 2.4 stating that JBoss server runs out of memory when to many hot- deployment with big archives. IMO this is not a bug because when people start to deploy big archives then they have to deal with it. - In Production this should not become a problem and when then a restart of JBoss is necessary - In Development this should not be a big problem to bounce the server. What do you think ? Bugs item #482875, was opened at 2001-11-17 12:12 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=482875group_id= 22866 Category: JBossServer Group: v2.4 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Joel Boehland (jolby) Assigned to: Nobody/Anonymous (nobody) Summary: OutOfMemory after many Deploy cycles Initial Comment: I have been seeing OutOfMemoryErrors in my server after doing several deploy/redeploy cycles of my application .ear file (which is around 3 megs in size) Basic info: *Hardware: AMD-K2-400MHz, 196MB RAM *OS: linux 2.2.14 *jdk: Blackdown-1.3.0-FCS, mixed mode *Server: JBoss-2.4.3_Jetty-3.1.3-1 *ServerTrace: I don't have one now, but I can provide one later if needed. *Steps to reproduce: Deploy/Redeploy .ear file many times. My .ear is around 3 megs, so it may be necessary to use a large one to trigger this effect. Other info *I have had this happen using native threads mode, and green threads mode. *Jozsa Kristof [EMAIL PROTECTED] has also reported this error on the jboss-user list. He was using IBM jdk 1.3.0 on linux, so this doesn't appear to be tied to any particular version of the jdk. --Joel --- 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-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] MBean ordering guarantee?
Ok, I'll make the dependencies more explicit. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury Sent: Sunday, November 18, 2001 12:09 PM To: David Jencks; [EMAIL PROTECTED] Subject: RE: [JBoss-dev] MBean ordering guarantee? Bill, knowledge by packaging is weak... it is lost in the packaging. e.g. if you have bean dependencies and visibility is scoped by packaging you have a problem (our scoped deployment fixes that), if you have mbean dependencies you have a problem (our rh cl and dependency deployer fixes that). Both come from the same problem, that packaging is a temporary thing. The particular case we are talking about and why I write is I was thinking, ok so units in a page can be init and start together, but then you can deploy independent xml snippets etc etc. We need to be consistent otherwise our admin UI gets confusing. What if you had to operate your VCR based on whether it was in this packaging box or the other... tracking the jar a given app came from is redundant. We are better off treating all these as independently deployed units and then be specific. I know you think the packaging is better than what was in Iona, Bill, but it still sucks in J2EE (war/jar/ear/sar p!). The new XML only (RH only) with explicit dependencies does away with this madness, madness be gone! marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of David |Jencks |Sent: Sunday, November 18, 2001 10:32 AM |To: [EMAIL PROTECTED] |Subject: Re: [JBoss-dev] MBean ordering guarantee? | | |On 2001.11.18 09:38:07 -0500 Bill Burke wrote: | If 2 mbeans are defined in the same xml file, are you guaranteed that one | will be started before the other? | |The only guarantees are if one has an mbean-ref to the other: then it will |wait till the other is started. However, in the absence of mbean-refs, the |order of the file will be followed: | |create mbeana |configure mbeana |startmbeana | |create mbeanb |configure mbeanb |startmbeanb | | |david jencks | |___ |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] CVS update: build/jboss build.xml
User: d_jencks
Date: 01/11/19 07:34:04
Modified:jbossbuild.xml
Log:
Repackaged jetty to use jar-in-sar
Revision ChangesPath
1.49 +10 -15build/jboss/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/build/jboss/build.xml,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- build.xml 2001/11/17 04:13:58 1.48
+++ build.xml 2001/11/19 15:34:04 1.49
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.48 2001/11/17 04:13:58 user57 Exp $ --
+!-- $Id: build.xml,v 1.49 2001/11/19 15:34:04 d_jencks Exp $ --
project default=main name=JBoss/Build
@@ -680,12 +680,7 @@
/fileset
/copy--
-!-- Copy the jetty service xml snippet (deploy) - -
-copy todir=${install.deploy} filtering=no
- fileset dir=${_module.output}/etc/conf/default
- include name=jetty-service.xml/
- /fileset
-/copy--
+!-- Copy the jetty service xml snippet (deploy) NOW IN A SAR --
!-- Copy the jms service xml snippet (deploy) --
copy todir=${install.deploy} filtering=no
@@ -1171,15 +1166,10 @@
/fileset
/copy
-!-- Copy the generated libraries (lib/ext)- now jetty-plugin.sar already
copied - -
-mkdir dir=${install.lib.ext}/
-copy todir=${install.lib.ext} filtering=no
- fileset dir=${_module.output}/lib
- include name=**/*/
- /fileset
-/copy--
!-- Copy the default configuration files (conf/default) --
+!-- These could perhaps be repackaged into jetty-plugin.sar
+ using the local directory feature --
mkdir dir=${install.conf.default}/
copy todir=${install.conf.default} filtering=no
fileset dir=${_module.output}/etc
@@ -1333,12 +1323,17 @@
fileset dir=${exolab.tyrex.lib}
include name=tyrex.jar/
/fileset
+ !--now in jetty.sar--
fileset dir=${mortbay.jetty.lib}
+include name=**/javax.servlet.jar/
+include name=**/org.apache.jasper.jar/
+ /fileset
+ !--fileset dir=${mortbay.jetty.lib}
include name=**/*.jar/
/fileset
fileset dir=${mortbay.jetty3extra.jmx.lib}
include name=**/*.jar/
- /fileset
+ /fileset--
/copy
mkdir dir=${install.client}/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/jetty build.xml
User: d_jencks
Date: 01/11/19 07:34:04
Modified:jettybuild.xml
Log:
Repackaged jetty to use jar-in-sar
Revision ChangesPath
1.10 +18 -0 contrib/jetty/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/contrib/jetty/build.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- build.xml 2001/09/26 21:47:03 1.9
+++ build.xml 2001/11/19 15:34:04 1.10
@@ -365,12 +365,30 @@
mkdir dir=${build.lib}/
jar jarfile=${build.lib}/${module.name}.sar
+ !-- Jetty plugin classes --
fileset dir=${build.classes}
include name=**/
/fileset
+ !-- jboss-service.xml for jetty plugin --
fileset dir=${build.resources}/jetty-plugin
include name=**/*/
/fileset
+ !--include jars in sar--
+ fileset dir=${mortbay.jetty.lib}
+!-- For some reason jasper doesn't work if servlet and jasper are in the
sar --
+!--include name=javax.servlet.jar/
+include name=org.apache.jasper.jar/--
+include name=org.mortbay.jetty.jar/
+ /fileset
+ fileset dir=${mortbay.jetty3extra.jmx.lib}
+include name=org.mortbay.ftp.jar/
+include name=org.mortbay.jetty.nbio.jar/
+include name=org.mortbay.jetty.jmx.jar/
+include name=org.mortbay.jetty.sasl.jar/
+include name=org.mortbay.tools.jar/
+include name=cryptix-sasl-jetty.jar/
+ /fileset
+
/jar
/target
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/jetty/src/resources/jetty-plugin/META-INF jboss-service.xml
User: d_jencks Date: 01/11/19 07:34:04 Modified:jetty/src/resources/jetty-plugin/META-INF jboss-service.xml Log: Repackaged jetty to use jar-in-sar Revision ChangesPath 1.2 +1 -11 contrib/jetty/src/resources/jetty-plugin/META-INF/jboss-service.xml Index: jboss-service.xml === RCS file: /cvsroot/jboss/contrib/jetty/src/resources/jetty-plugin/META-INF/jboss-service.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- jboss-service.xml 2001/09/28 12:51:19 1.1 +++ jboss-service.xml 2001/11/19 15:34:04 1.2 @@ -2,18 +2,8 @@ server - dependsJBOSS-SYSTEM:service=Naming/depends - classpath archives= - org.mortbay.ftp.jar, - org.mortbay.jetty.nbio.jar, - org.mortbay.jetty.jmx.jar, - org.mortbay.jetty.sasl.jar, - org.mortbay.tools.jar, - cryptix-sasl-jetty.jar, - javax.servlet.jar, - org.apache.jasper.jar, - org.mortbay.jetty.jar/ + classpath archives=tools.jar, javax.servlet.jar, org.apache.jasper.jar/ !-- -- !-- Web Container-- ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] 1 to Many Relations
Ok, you are not getting it. I am it's just that the moon is gone ;) Although JBossCMP does not generate the column names you would like, the system still runs. Is that correct? (i.e., this is still a suggestion) If I use the jbosscmp-jdbc.xml file I can get it to work. Ok now that we agree on that. How would you like the column names generated? Be very very specific and take into consideraton the above problems. I do no want jboss to generate any column names. It's not necessary. Either the class field is the database column name or in jbosscmp-jdbc.xml you specify that class field x maps to database column y. If there is a name space collision then it is a database setup problem not JBOSS's and we should not be coding for it. As for my comment easy to code, that is perfectly valid, as we are shooting for CMP 2.0 compliance. CMP 2.0 is a huge spec, so everything can not be perfect in the first pass. Some of the implementation details get implemnted the easy way. There have to be priorities. Yup, it's just this one looks like something that will fill the mailing lists. If you pulled togther your test cases then I could probably have a look, you do not have to do this whole thing by yourself. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] 1 to Many Relations
Hi guys, I've just been skimming this thread, but it strikes me as possible that it is based on a misunderstanding. Dave, do you know that you should not define a cmp field for a foreign key column? So changing the naming convention wouldn't be necessary to get it to work by default. Sorry if this is not the problem, and I have missed the point. If so, please just ignore me. -Dan On 19 Nov 01, at 11:05, Dave Smith wrote: Ok, you are not getting it. I am it's just that the moon is gone ;) Although JBossCMP does not generate the column names you would like, the system still runs. Is that correct? (i.e., this is still a suggestion) If I use the jbosscmp-jdbc.xml file I can get it to work. Ok now that we agree on that. How would you like the column names generated? Be very very specific and take into consideraton the above problems. I do no want jboss to generate any column names. It's not necessary. Either the class field is the database column name or in jbosscmp-jdbc.xml you specify that class field x maps to database column y. If there is a name space collision then it is a database setup problem not JBOSS's and we should not be coding for it. As for my comment easy to code, that is perfectly valid, as we are shooting for CMP 2.0 compliance. CMP 2.0 is a huge spec, so everything can not be perfect in the first pass. Some of the implementation details get implemnted the easy way. There have to be priorities. Yup, it's just this one looks like something that will fill the mailing lists. If you pulled togther your test cases then I could probably have a look, you do not have to do this whole thing by yourself. ___ 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] Extending CMP 2 to support CCI resource adapters
As if your life isn't hard enough...;-) I'm going to start looking at extending the CMP 2 code to work with CCI resource adapters as well as jca-jdbc drivers. (the aim is to use EJB 2 with an object database, for which there is a CCI connector.) My initial impression is that I will have to implement all the classes in ejb/plugins/cmp/jdbc/** in a new ejb/plugins/cmp/cci/** (for starters). Is this anywhere near the right track? Any clues about what else I will need? [I am hoping that the results of this work will be donated to JBoss, but cannot guarantee this] Also, would it be OK if I converted the sample app and tests you sent me to fit in the jboss testsuite and committed them? Thanks! David Jencks ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: contrib/jetty build.xml
Thanks, David,
I'll try this tonight.
Jules
--- David Jencks [EMAIL PROTECTED]
wrote:User: d_jencks
Date: 01/11/19 07:34:04
Modified:jettybuild.xml
Log:
Repackaged jetty to use jar-in-sar
Revision ChangesPath
1.10 +18 -0 contrib/jetty/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/contrib/jetty/build.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- build.xml 2001/09/26 21:47:03 1.9
+++ build.xml 2001/11/19 15:34:04 1.10
@@ -365,12 +365,30 @@
mkdir dir=${build.lib}/
jar
jarfile=${build.lib}/${module.name}.sar
+ !-- Jetty plugin classes --
fileset dir=${build.classes}
include name=**/
/fileset
+ !-- jboss-service.xml for jetty plugin --
fileset
dir=${build.resources}/jetty-plugin
include name=**/*/
/fileset
+ !--include jars in sar--
+ fileset dir=${mortbay.jetty.lib}
+!-- For some reason jasper doesn't work
if servlet and jasper are in the sar --
+!--include name=javax.servlet.jar/
+include name=org.apache.jasper.jar/--
+include name=org.mortbay.jetty.jar/
+ /fileset
+ fileset
dir=${mortbay.jetty3extra.jmx.lib}
+include name=org.mortbay.ftp.jar/
+include
name=org.mortbay.jetty.nbio.jar/
+include
name=org.mortbay.jetty.jmx.jar/
+include
name=org.mortbay.jetty.sasl.jar/
+include name=org.mortbay.tools.jar/
+include name=cryptix-sasl-jetty.jar/
+ /fileset
+
/jar
/target
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
__
Do You Yahoo!?
Everything you'll ever need on one web page from News and Sport to Email and Music
Charts
http://uk.my.yahoo.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Extending CMP 2 to support CCI resource adapters
|[I am hoping that the results of this work will be donated to JBoss, but |cannot guarantee this] You have done more free work than many people here, don't worry about free. Whatever keeps you dedicated to JBoss is what I want. marcf | |Also, would it be OK if I converted the sample app and tests you sent me to |fit in the jboss testsuite and committed them? | |Thanks! | |David Jencks | |___ |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] Is there a dtd for jbosscmp-jdbc.xml files?
If so, where? If not, OK if I write one? (based on what?) Thanks david jencks ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] 1 to Many Relations
Don't be sorry, be happy ;) the problem is that the name specified in the cmr-field-name is not the database column. Jboss assumes that the database column name is the cmr_field_name (left side) +_ + cmr_field_name right side. What I think makes more sense is for the cmr_field_name by default to match the database column name the same way it does in CMP. Dan OConnor wrote: Hi guys, I've just been skimming this thread, but it strikes me as possible that it is based on a misunderstanding. Dave, do you know that you should not define a cmp field for a foreign key column? So changing the naming convention wouldn't be necessary to get it to work by default. Sorry if this is not the problem, and I have missed the point. If so, please just ignore me. -Dan On 19 Nov 01, at 11:05, Dave Smith wrote: e.net 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] 1 to Many Relations
Ok, you are not getting it. I am it's just that the moon is gone ;) Although JBossCMP does not generate the column names you would like, the system still runs. Is that correct? (i.e., this is still a suggestion) If I use the jbosscmp-jdbc.xml file I can get it to work. Do you have to use the jbosscmp-jdbc.xml file? If you don't, what happens? Does the system generate two columns with the same name? Ok now that we agree on that. How would you like the column names generated? Be very very specific and take into consideraton the above problems. I do no want jboss to generate any column names. It's not necessary. Either the class field is the database column name or in jbosscmp-jdbc.xml you specify that class field x maps to database column y. If there is a name space collision then it is a database setup problem not JBOSS's and we should not be coding for it. All column names are either generated, or specified in the jbosscmp-jdbc.xml file. Your opinion is that when jboss generates the column name for a relationship fk it should first attempt to the name of the cmr-field abstract accessors. Problems occur when the entity does not have an accessor for the relationship, and when the primary key related entity maps to more then one db column. What is your complete proposal for fk column generation and relation-table column generation? Be specific. As for my comment easy to code, that is perfectly valid, as we are shooting for CMP 2.0 compliance. CMP 2.0 is a huge spec, so everything can not be perfect in the first pass. Some of the implementation details get implemnted the easy way. There have to be priorities. Yup, it's just this one looks like something that will fill the mailing lists. If you pulled together your test cases then I could probably have a look, you do not have to do this whole thing by yourself. I know. I am working on the todo list right now (which will be posted to sf), and after that I will be adding my test cases. For now, what is your proposal? -dain ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Extending CMP 2 to support CCI resource adapters
As if your life isn't hard enough...;-) :) I'm going to start looking at extending the CMP 2 code to work with CCI resource adapters as well as jca-jdbc drivers. (the aim is to use EJB 2 with an object database, for which there is a CCI connector.) I have been thinking about a new cmp 2 extension that maps to stored procedures. Would that be similar? My initial impression is that I will have to implement all the classes in ejb/plugins/cmp/jdbc/** in a new ejb/plugins/cmp/cci/** (for starters). Is this anywhere near the right track? Any clues about what else I will need? Well, not exactly. ejb/plugins/cmp/jdbc/** is an implementation of ejb/plugins/cmp/**, but may be a good stating place. One issue I see, is that I plan on changing this somewhat to support database INSERT/DELETE/SYNC timing and ordering. The most important packages to investigate are the bridge packages. The bridge packages implements the bridge pattern. The bridge is between entity implementation accessors and cmp-field/cmr-field/query objects. [I am hoping that the results of this work will be donated to JBoss, but cannot guarantee this] Also, would it be OK if I converted the sample app and tests you sent me to fit in the jboss testsuite and committed them? I have a much more detailed set of test cases, that I would like to add. I'm not really sure how the test system works, so maybe you can send me some pointers. It is good to see s much interest today :) -dain ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: Is there a dtd for jbosscmp-jdbc.xml files?
Funny, that is on the todo list also. I have a fairly complete xml. Can we reverse generate a DTD? -dain -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 11:05 AM To: Dain Sundstrom; jboss-dev Subject: Is there a dtd for jbosscmp-jdbc.xml files? If so, where? If not, OK if I write one? (based on what?) Thanks david jencks ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Extending CMP 2 to support CCI resource adapters
On 2001.11.19 12:28:58 -0500 Dain Sundstrom wrote:
As if your life isn't hard enough...;-)
:)
I'm going to start looking at extending the CMP 2 code to
work with CCI
resource adapters as well as jca-jdbc drivers. (the aim is to
use EJB 2
with an object database, for which there is a CCI connector.)
I have been thinking about a new cmp 2 extension that maps to stored
procedures. Would that be similar?
I think a case could be made for using something like the CCI - jdbc -
blackbox jca wrapper for this, where basically the sp's are kept in the
InteractionSpecs. In other words I'd suggest using the CCI interface I am
proposing for sps as well.
My initial impression is that I will have to implement all
the classes in
ejb/plugins/cmp/jdbc/** in a new ejb/plugins/cmp/cci/** (for
starters). Is
this anywhere near the right track? Any clues about what else
I will need?
Well, not exactly. ejb/plugins/cmp/jdbc/** is an implementation of
ejb/plugins/cmp/**, but may be a good stating place. One issue I see, is
that I plan on changing this somewhat to support database
INSERT/DELETE/SYNC
timing and ordering.
The most important packages to investigate are the bridge packages. The
bridge packages implements the bridge pattern. The bridge is between
entity
implementation accessors and cmp-field/cmr-field/query objects.
So this would be in .../cmp/cci/bridge? Don't I need the cmp/cci analogues
of cmp/jdbc also?
[I am hoping that the results of this work will be donated to
JBoss, but
cannot guarantee this]
Also, would it be OK if I converted the sample app and tests
you sent me to
fit in the jboss testsuite and committed them?
I have a much more detailed set of test cases, that I would like to add.
I'm not really sure how the test system works, so maybe you can send me
some
pointers.
If you'd like I would be happy to do this to get more oriented. If you
want to...
Lets say you put it in .../test/cmp2/.
Test cases go in .../test/cmp2/test. They should be named
*UnitTestCase.java or *StressTestCase.java. They should descend from
JBossTestCase.
Typically you will have an application to test, say Example.ear. Assuming
you want to deploy it for a whole TestCase class worth of tests (rather
than un/redeploy it between tests), use a JBossTestSetup like this in your
testcase:
public static Test suite() throws Exception
{
return getJ2eeSetup(MyCMP2UnitTestCase.class, Example.ear);
}
This will deploy Example.ear once before any tests from MyCMP2UnitTestCase
and undeploy it after all are complete.
Put the bean classes in .../test/cmp2/bean (or .../ejb), interfaces (if not
xdoclet-generated) in .../test/cmp2/interfaces
Put ejb-jar.xml and other config files in .../src/resources/cmp2/
Put instructions for building the ears in the build.xml, it should end up
in output/lib. As far as I am concerned you don't need to package the
*/test/*TestCase code, although it may be getting jarred up anyway.
Personally I am only interested in running tests from ant, where the test
class files work fine.
Tests named *UnitTestCase will be run from the tests-unit target. You can
run all cmp2 tests with -Dtest=cmp2 test or one test class with
-Dtest=MyCMP2UnitTestCase one-test.
Thanks!
david jencks
It is good to see s much interest today :)
-dain
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: Is there a dtd for jbosscmp-jdbc.xml files?
From: David Jencks [EMAIL PROTECTED] To: Dain Sundstrom [EMAIL PROTECTED] CC: jboss-dev [EMAIL PROTECTED] Subject: [JBoss-dev] Re: Is there a dtd for jbosscmp-jdbc.xml files? Date: Mon, 19 Nov 2001 13:03:03 -0500 On 2001.11.19 12:30:45 -0500 Dain Sundstrom wrote: Funny, that is on the todo list also. I have a fairly complete xml. Can we reverse generate a DTD? I think XML spy can do this. Send me the XML and I'll try tonight. Regards, Hiram I'll try if you send me the xml. I don't know about automatically. david jencks -dain -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 11:05 AM To: Dain Sundstrom; jboss-dev Subject: Is there a dtd for jbosscmp-jdbc.xml files? If so, where? If not, OK if I write one? (based on what?) Thanks david jencks ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] mbean-ref
On 2001.11.19 14:24:27 -0500 Bill Burke wrote: Does this mark a dependency? Yes. Sequence of events: mbean created mbean configured, returning a list of mbean references from mbean-ref and mbean-ref-list-element elements (the values must be object names) ServiceController looks to see if all the referenced mbeans are started yet. If so, it starts (and remembers that it is started) the mbean. If not, it waits, and every time an mbean is started, checks to see if all the dependencies are satisfied yet. As soon as they are, the newly OK mbean is started. Essentially the reverse happens when you undeploy a referenced mbean. Note that mbean-refs can correspond to ObjectName valued properties of the referencing mbean, in which case they need a valid name attribute, or can be anonymous, with no name attribute. An example of the use of the latter is in the DefaultDS mbean, which requires the hsqldb to be started, but has no use for a direct mbean reference to it. It uses an anonymous mbean-ref to wait until the hsqldb is started. I think its a good idea to use the ObjectNames you get from these mbean-refs to perform operations on the referenced mbean, rather than e.g. using a singleton with a static get method or binding in jndi and needing also a jndi name. I have sometimes implemented a getInstance method in the mbean interface to return the actual object so you don't need every operation and its brother in the mbean interface. I'm not certain this is the best design idea, but it sure was convenient;-). David Jencks ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-483464 ] Additional Info via MBean (part 2)
Patches item #483464, was opened at 2001-11-19 07:41 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=483464group_id=22866 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jason Vasquez (jpvasquez) Assigned to: Nobody/Anonymous (nobody) Summary: Additional Info via MBean (part 2) Initial Comment: Follow up to patch #483459 -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376687aid=483464group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-482875 ] OutOfMemory after many Deploy cycles
Bugs item #482875, was opened at 2001-11-17 12:12
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=482875group_id=22866
Category: JBossServer
Group: v2.4 (stable)
Status: Open
Resolution: None
Priority: 7
Submitted By: Joel Boehland (jolby)
Assigned to: Nobody/Anonymous (nobody)
Summary: OutOfMemory after many Deploy cycles
Initial Comment:
I have been seeing OutOfMemoryErrors in my server after
doing several deploy/redeploy cycles of my application
.ear file (which is around 3 megs in size)
Basic info:
*Hardware: AMD-K2-400MHz, 196MB RAM
*OS: linux 2.2.14
*jdk: Blackdown-1.3.0-FCS, mixed mode
*Server: JBoss-2.4.3_Jetty-3.1.3-1
*ServerTrace: I don't have one now, but I can provide
one later if needed.
*Steps to reproduce: Deploy/Redeploy .ear file many
times. My .ear is around 3 megs, so it may be necessary
to use a large one to trigger this effect.
Other info
*I have had this happen using native threads mode, and
green threads mode.
*Jozsa Kristof [EMAIL PROTECTED] has also reported
this error on the jboss-user list. He was using IBM jdk
1.3.0 on linux, so this doesn't appear to be tied to
any particular version of the jdk.
--Joel
--
Comment By: Adrian Brock (ejort)
Date: 2001-11-19 07:55
Message:
Logged In: YES
user_id=9459
I can reproduce this with a 4k HelloWorld.jar using the
-Xmx parameter to constrain the heap size of the JVM.
It seems the classloaders created by J2EEDeployer are not
being garbage collected.
Here's a hack to monitor garbage collection from
org.jboss.Main.
You call org.jboss.Main.monitorGarbage(Object,String) to
request monitoring and the list of uncollected stuff gets
printed once a second.
System.out.println(JBoss +versionIdentifier+ Started
in +minutes+m:+seconds+s);
hack
try
{
while (true)
{
// Wait for garbage collection
java.lang.ref.Reference collected =
garbageQueue.remove(1000);
while (collected !=null)
{
// Remove all available garbage
garbage.remove(collected);
collected = garbageQueue.remove(1);
}
// List uncollected garbage
Iterator uncollected = garbage.values().iterator();
System.out.println(Uncollected items: +
garbage.size());
while (uncollected.hasNext())
System.out.println(uncollected.next());
System.gc();
}
}catch (InterruptedException ignored){};
/hack
}
resume-hack
// Request garbage collection monitoring
public static void monitorGarbage(Object object,
String info)
{
garbage.put(
new java.lang.ref.WeakReference(object,garbageQueue),
info);
System.out.println(MonitorGarbage: + info);
}
// Garbage to monitor
public static HashMap garbage = new HashMap();
// Garbage collected queue
public static java.lang.ref.ReferenceQueue garbageQueue =
new java.lang.ref.ReferenceQueue();
/resume-hack
Then I changed org.jboss.deployment.J2EEDeployer
to monitor the garbage collection of the classloader
// set the context classloader for this application
createContextClassLoader(_d);
// save the application classloader for later
ClassLoader appCl =
Thread.currentThread().getContextClassLoader();
new-code
org.jboss.Main.monitorGarbage(appCl, ClassLoader +
_d.getName());
/new-code
If you go through the cycle of deploying and undeploying a
few times you'll notice the the classloaders are never
garbage collected.
There must be a class lying around somewhere that needs the
classloader?
--
Comment By: Jim Cook (oravecz)
Date: 2001-11-17 14:42
Message:
Logged In: YES
user_id=6215
Ditto, on Windows 2000 as well. Redeploy of a 700K WAR file
causes an Out of Memory after 15-20 redeploys.
Would there be any clues as to whether the WAR file
contents are actually guilty of some kind of memory leak?
Using WebWork and Velocity in the WAR...
-jim
--
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=482875group_id=22866
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Ignorance
You need to create the declaration to include with the source using the serialver tool, or your IDE if it supports it(Netbeans does). To use serialver, you run it much as you would the java command and it will print out the serialVersionUID statement you must copy and place into source code: examples 1983serialver -classpath build/classes org.jboss.chap11.model.AccountInfo org.jboss.chap11.model.AccountInfo:static final long serialVersionUID = -5888058120666796953L; - Original Message - From: marc fleury [EMAIL PROTECTED] To: Bill Burke [EMAIL PROTECTED]; Jboss-Development@Lists. Sourceforge. Net [EMAIL PROTECTED] Sent: Monday, November 19, 2001 11:17 AM Subject: RE: [JBoss-dev] Ignorance and I don't need to write anything in the source then do I ? marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Bill |Burke |Sent: Monday, November 19, 2001 1:43 PM |To: marc fleury; Jboss-Development@Lists. Sourceforge. Net |Subject: RE: [JBoss-dev] Ignorance | | |serialver executable? | | -Original Message- | From: [EMAIL PROTECTED] | [mailto:[EMAIL PROTECTED]]On Behalf Of marc | fleury | Sent: Monday, November 19, 2001 12:30 PM | To: Jboss-Development@Lists. Sourceforge. Net | Subject: [JBoss-dev] Ignorance | | | So how does the serialVersionUID get generated in classes that are | Externalizable? | | I am a bit fuzzy, in fact I plain would like the beginner version | on that... | | thanks, he he | | :) | | ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Ignorance
merci :) marcf |-Original Message- |From: Scott M Stark [mailto:[EMAIL PROTECTED]] |Sent: Monday, November 19, 2001 3:31 PM |To: marc fleury; Jboss-Development@Lists. Sourceforge. Net |Subject: Re: [JBoss-dev] Ignorance | | |You need to create the declaration to include with the source using the |serialver |tool, or your IDE if it supports it(Netbeans does). To use serialver, you |run |it much as you would the java command and it will print out the |serialVersionUID |statement you must copy and place into source code: | |examples 1983serialver -classpath build/classes |org.jboss.chap11.model.AccountInfo |org.jboss.chap11.model.AccountInfo:static final long serialVersionUID |= -5888058120666796953L; | |- Original Message - |From: marc fleury [EMAIL PROTECTED] |To: Bill Burke [EMAIL PROTECTED]; Jboss-Development@Lists. |Sourceforge. Net [EMAIL PROTECTED] |Sent: Monday, November 19, 2001 11:17 AM |Subject: RE: [JBoss-dev] Ignorance | | | and I don't need to write anything in the source then do I ? | | marcf | | |-Original Message- | |From: [EMAIL PROTECTED] | |[mailto:[EMAIL PROTECTED]]On Behalf Of Bill | |Burke | |Sent: Monday, November 19, 2001 1:43 PM | |To: marc fleury; Jboss-Development@Lists. Sourceforge. Net | |Subject: RE: [JBoss-dev] Ignorance | | | | | |serialver executable? | | | | -Original Message- | | From: [EMAIL PROTECTED] | | [mailto:[EMAIL PROTECTED]]On |Behalf Of marc | | fleury | | Sent: Monday, November 19, 2001 12:30 PM | | To: Jboss-Development@Lists. Sourceforge. Net | | Subject: [JBoss-dev] Ignorance | | | | | | So how does the serialVersionUID get generated in classes that are | | Externalizable? | | | | I am a bit fuzzy, in fact I plain would like the beginner version | | on that... | | | | thanks, he he | | | | :) | | | | | | ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/docs news082000.htm news122000.html
User: user57 Date: 01/11/19 12:40:12 Removed: src/docs news082000.htm news122000.html Log: o these are quite old and do not seem to be linked from anywhere ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/docs main.css
User: user57
Date: 01/11/19 12:33:32
Modified:src/docs main.css
Log:
o added code, command and output class styles
o updated quickstart to use them
Revision ChangesPath
1.6 +39 -15newsite/src/docs/main.css
Index: main.css
===
RCS file: /cvsroot/jboss/newsite/src/docs/main.css,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- main.css 2001/11/17 04:19:12 1.5
+++ main.css 2001/11/19 20:33:31 1.6
@@ -2,40 +2,66 @@
* Style Sheet document for the new JBoss website.
*/
-/* $Id: main.css,v 1.5 2001/11/17 04:19:12 user57 Exp $ */
+/* $Id: main.css,v 1.6 2001/11/19 20:33:31 user57 Exp $ */
.linkhead {
- font-family: Arial;
+ font-family: Arial,serif;
font-size: 12px;
color: #ff;
font-weight: bold;
}
.linkmenu {
- font-family: Arial;
+ font-family: Arial,serif;
font-size: 12px;
color: #0a0a0a;
font-weight: bold;
text-decoration: none;
}
+.linkmenu:hover {
+ color: #40;
+ text-decoration: underline;
+}
+
.head {
- font-family: Arial;
+ font-family: Arial,serif;
font-size: 14px;
color: #336633;
font-weight: bold;
}
+
.slogan {
- font-family: Arial;
+ font-family: Arial,serif;
font-size: 15px;
color: #338833;
font-weight: bold;
}
+
.text {
- font-family: Arial;
+ font-family: Arial,serif;
+ font-size: 13px;
+ color: #00;
+}
+
+.code {
+ font-family: monospace;
+ font-size: 10px;
+ color: #00;
+}
+
+.command {
+ font-family: monospace;
font-size: 13px;
color: #00;
}
+
+.output {
+ font-family: monospace;
+ font-size: 10px;
+ color: #00;
+}
+
.link {
- font-family: Arial;
+ font-family: Arial,serif;
font-size: 13px;
color: #003399;
font-weight: bold;
@@ -43,18 +69,16 @@
.link:hover {
color: #336633;
}
+
.copy {
- font-family: Arial;
+ font-family: Arial,serif;
font-size: 11px;
color: #808080;
}
-.linkmenu:hover {
- color: #40;
- text-decoration: underline;
-}
.copy:hover {
color: #00;
}
+
.label {
font-weight: bold
}
@@ -66,9 +90,9 @@
td.black { background-color: #00 }
td.dark { background-color: #276561 }
td.light { background-color: #307d77 }
-td.link { font-family: Arial; font-size: 13px; color: #404040; font-weight: bold; }
-td.newsbody { font-family: Arial; font-size: 13px; color: #00}
-td.newsheader {font-family: Arial; font-size: 14px; color: #336633; font-weight:
bold; }
+td.link { font-family: Arial,serif; font-size: 13px; color: #404040; font-weight:
bold; }
+td.newsbody { font-family: Arial,serif; font-size: 13px; color: #00}
+td.newsheader {font-family: Arial,serif; font-size: 14px; color: #336633;
font-weight: bold; }
/*td.newsheader { color: black; background-color: #C1E0B2 }*/
td.pageheader { color: white; font-weight: bold; font-size: 14pt; background-color:
#99 }
td.yellow { background-color: #f4c641 }
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/docs/developers quickstart.jsp
User: user57 Date: 01/11/19 12:33:32 Modified:src/docs/developers quickstart.jsp Log: o added code, command and output class styles o updated quickstart to use them Revision ChangesPath 1.2 +17 -18newsite/src/docs/developers/quickstart.jsp Index: quickstart.jsp === RCS file: /cvsroot/jboss/newsite/src/docs/developers/quickstart.jsp,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- quickstart.jsp2001/11/17 04:19:12 1.1 +++ quickstart.jsp2001/11/19 20:33:32 1.2 @@ -1,5 +1,5 @@ jsp:include page=head.jsp flush=true/ -!-- $Id: quickstart.jsp,v 1.1 2001/11/17 04:19:12 user57 Exp $ -- +!-- $Id: quickstart.jsp,v 1.2 2001/11/19 20:33:32 user57 Exp $ -- jsp:include page=slogan.jsp flush=true jsp:param name=SLOGAN value=QUICK START GUIDE/ /jsp:include @@ -28,8 +28,8 @@ Unless specified otherwise, all examples given are formated for UNIX users and assume that the current working directory (CWD) is the project directory which contains the ttbuild//tt sub-directory. Windows - users can emprobably/em substitute tt//tt for tt\/tt, - tt.sh/tt for tt.bat/tt and omit any preceding tt./tt to + users can emprobably/em omit any preceding tt.//tt, substitute + tt//tt for tt\/tt and change tt.sh/tt for tt.bat/tt to create runnable command examples. p class=text @@ -149,12 +149,12 @@ a href=cvs.jspCVS/a page to get and setup your CVS client. Once you have done that you can check out the module: blockquote - codecvs -z3 checkout jboss-all/codebr + code class=commandcvs -z3 checkout jboss-all/codebr /blockquote p class=text You should see output similar to: - font size=-1pre + font size=-1pre class=output U tools/bin/ant U tools/bin/ant.bat U tools/bin/antRun @@ -185,7 +185,6 @@ should have a ttjboss-all//tt directory with a sub-directory layout similarsup*/sup to this: blockquote - ttCVS//ttbr tttools//ttbr ttthirdparty//ttbr ttbuild//ttbr @@ -274,7 +273,7 @@ can empre-initialize/em the build system and define or set some user local properties, which can alter the behavior of the build: blockquote - code./build/build.sh init/codebr + code class=command./build/build.sh init/codebr /blockquote p class=text @@ -301,7 +300,7 @@ standard components which are included in a production release, so all we have todo is tell the build system to start: blockquote - code./build/build.sh/codebr + code class=command./build/build.sh/codebr /blockquote p class=text @@ -312,7 +311,7 @@ p class=text The output of the build should be slightly verbose and look something like this: - font size=-1pre + font size=-1pre class=output Searching for build.xml ... Buildfile: /home/jason/ws/jboss-all/build/build.xml @@ -383,12 +382,12 @@ most common targets and a brief description, re-run the build and specify the tthelp/tt target: blockquote - code./build/build.sh help/codebr + code class=command./build/build.sh help/codebr /blockquote p class=text This command should output something like this: - font size=-1pre + font size=-1pre class=output Searching for build.xml ... Buildfile: /nfs/home/jason/ws/jboss/tmp/jboss-all/build/build.xml @@ -411,10 +410,10 @@ [help] testcase Run a test case. [help] tests Execute all tests. [help] - [help] -Dgroups=group[(,group)*] Specify the module groups. - [help] -Dmodules=module[(,module)*] Specify the modules. + [help] -Dgroups=lt;groupgt;[(,lt;groupgt;)*] Specify the module groups. + [help] -Dmodules=lt;modulegt;[(,lt;modulegt;)*] Specify the modules. [help](overrides groups). - [help] -Dtest=testcase Specify the testcase to run. + [help] -Dtest=lt;testcasegt; Specify the testcase to run. [help] -projecthelp for all targets [help] -help for full options [help] @@ -494,7 +493,7 @@ start the server by hand from the project root directory you run (change release directory according to the version you are using): blockquote - code./build/output/jboss-3.0.0alpha/bin/run.sh/codebr + code class=command./build/output/jboss-3.0.0alpha/bin/run.sh/codebr /blockquote !-- picateam block --tabletrtdjsp:include page=/common/picateam.jsp flush=true//tdtd @@ -504,7 +503,7 @@ action and takes care of using the correct release directory based on the current version
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/pm/rollinglogged SpyTxLog.java
User: dmaplesden
Date: 01/11/19 12:41:19
Modified:src/main/org/jboss/mq/pm/rollinglogged SpyTxLog.java
Log:
fixing my bad formatting
Revision ChangesPath
1.6 +100 -100 jbossmq/src/main/org/jboss/mq/pm/rollinglogged/SpyTxLog.java
Index: SpyTxLog.java
===
RCS file:
/cvsroot/jboss/jbossmq/src/main/org/jboss/mq/pm/rollinglogged/SpyTxLog.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- SpyTxLog.java 2001/11/19 04:06:04 1.5
+++ SpyTxLog.java 2001/11/19 20:41:19 1.6
@@ -18,107 +18,107 @@
*
* @createdAugust 16, 2001
* @author:Hiram Chirino ([EMAIL PROTECTED])
- * @version$Revision: 1.5 $
+ * @version$Revision: 1.6 $
*/
public class SpyTxLog {
- /
- // Attributes
- /
- private IntegrityLog transactionLog;
- private int liveTransactionCount = 0;
- private Object counterLock = new Object();
-
- /
- // Constructors
- /
- SpyTxLog( File file )
- throws JMSException {
- try {
- transactionLog = new IntegrityLog( file );
- } catch ( IOException e ) {
- throwJMSException( Could not open the queue's
tranaction log: + file.getAbsolutePath(), e );
- }
- System.out.println(created SpyTxLog: + this);
- //new Exception().printStackTrace();
- }
-
- /
- // Public Methods
- /
- public synchronized void close()
- throws JMSException {
- try {
- transactionLog.close();
- } catch ( IOException e ) {
- throwJMSException( Could not close the queue's
tranaction log., e );
- }
- }
-
- public synchronized void delete()
- throws JMSException {
- try {
- transactionLog.delete();
- } catch ( IOException e ) {
- throwJMSException( Could not delete the queue's
tranaction log., e );
- }
- }
-
-
- public void createTx()
- throws JMSException {
- synchronized ( counterLock ) {
- ++liveTransactionCount;
- }
- }
-
- public boolean completed()
- throws JMSException {
- synchronized ( counterLock ) {
- return ( liveTransactionCount == 0 );
- }
- }
-
-
- public synchronized void restore( java.util.TreeSet result )
- throws JMSException {
- try {
- result.addAll( transactionLog.toTreeSet() );
- } catch ( Exception e ) {
- throwJMSException( Could not restore the transaction
log., e );
- }
- }
-
- public synchronized void commitTx( org.jboss.mq.pm.Tx id )
- throws JMSException {
-
- try {
- transactionLog.addTx( id );
- transactionLog.commit();
- synchronized ( counterLock ) {
- --liveTransactionCount;
- }
- } catch ( IOException e ) {
- throwJMSException( Could not create a new
transaction., e );
- }
-
- }
-
- public void rollbackTx( org.jboss.mq.pm.Tx txId )
- throws JMSException {
- synchronized ( counterLock ) {
- --liveTransactionCount;
- }
- }
-
-
- /
- // Private Methods
- /
- private void throwJMSException( String message, Exception e )
- throws JMSException {
- JMSException newE = new
[JBoss-dev] Bug #426048 NoClassDefFoundError on Cloudscape
Hi Geeks I don't know Cloudscape therefore I was wondering if someone could tell me if this bug is one, still exists or if I can close the bug. Thanx 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] Removing safeguard on cl check in invocation
OK, Just a quicky. I am rewriting most of the invocation format and reusing as much as I can as I go, I am lazy. I notice that in JRMPContainerInvoker in invoke(O,M,T,P,O) at line 479 there is a safeguard that checks whether the class is really of the right type, by comparing the classloader stuff implicitely. It is a very smart hack btw, but I am going to remove it. If I remember correctly its main purpose in life was to make sure that tomcat integration was correctly done and not fail if it wasn't, while that was again a nice ease of use line, I think it is deprecated. While I am changing many more things I just want to send a FYI that if we start getting classcast exceptions from users it means a faulty CL integration and we want to know about it. Not serialize and bring JBoss to a crawling halt on serialization. Which is why I remove this in the first place. If we are going to be the standard monopoly as I say in the vision, we better start making sure people play nice with the CL stuff otherwise everyone is floating. And that means playing by the rules in CL, our rules. Do the right thing on contextCL or else... it will also mean people will be using the microkernel loaders without knowing about it, and that is good, that is good, removes a lot of the packaging headaches... I will stop going down the ramifications of this, you get the idea. So the engine will bomb if the CL integration is fucked up, which it shouldn't nowadays marcf Marc Fleury President JBoss Group, LLC ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Test cases
Comments below (changed subject to reflect new discussion thread)
Lets say you put it in .../test/cmp2/.
Test cases go in .../test/cmp2/test. They should be named
*UnitTestCase.java or *StressTestCase.java. They should descend from
JBossTestCase.
Typically you will have an application to test, say
Example.ear. Assuming
you want to deploy it for a whole TestCase class worth of
tests (rather
than un/redeploy it between tests), use a JBossTestSetup like
this in your
testcase:
public static Test suite() throws Exception
{
return getJ2eeSetup(MyCMP2UnitTestCase.class, Example.ear);
}
This will deploy Example.ear once before any tests from
MyCMP2UnitTestCase
and undeploy it after all are complete.
Put the bean classes in .../test/cmp2/bean (or .../ejb),
interfaces (if not
xdoclet-generated) in .../test/cmp2/interfaces
Put ejb-jar.xml and other config files in .../src/resources/cmp2/
Put instructions for building the ears in the build.xml, it
should end up
in output/lib. As far as I am concerned you don't need to package the
*/test/*TestCase code, although it may be getting jarred up anyway.
Personally I am only interested in running tests from ant,
where the test
class files work fine.
Tests named *UnitTestCase will be run from the tests-unit
target. You can
run all cmp2 tests with -Dtest=cmp2 test or one test class with
-Dtest=MyCMP2UnitTestCase one-test.
Thanks!
david jencks
Is this structure imposed by the build system or is it just a convention? I
have a set of test that are based on the cmp 2 section 10.3.7 Assignment
rules for relationships of the ejb 2.0 spec. There are test for each
relation type (1-n bi, 1-n uni, n-1 uni ...) and mapping style (fk, fk with
back pointers, and relation-table). That is about 14 unit tests. Anyway I
have these organized into sub-packages under the org.jboss.test.relationship
package. I can't merge them all into package as each type has it's own set
of 'A' / 'B' interfaces. Should I leave them organized into sub packages or
should I eliminate the top level relationship package?
The other issue I have is my tests use a, yet to be completed, extension to
JUnit which runs the tests on the serverside (I wrote this). This is
required for testing local interfaces which by definition are not accessible
remotely. Anyway, how do I go about adding the code to the build system.
It is in the package net.sourceforge.junitejb.*
-dain
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] 1 to Many Relations
If I use the jbosscmp-jdbc.xml file I can get it to work. Do you have to use the jbosscmp-jdbc.xml file? If you don't, what happens? Does the system generate two columns with the same name? The database table already exsists. Basically I have to use foreign-key-fields and set field-name and column-name attributes the same. Ok now that we agree on that. How would you like the column names generated? Be very very specific and take into consideraton the above problems. I do no want jboss to generate any column names. It's not necessary. Either the class field is the database column name or in jbosscmp-jdbc.xml you specify that class field x maps to database column y. If there is a name space collision then it is a database setup problem not JBOSS's and we should not be coding for it. All column names are either generated, or specified in the jbosscmp-jdbc.xml file. Your opinion is that when jboss generates the column name for a relationship fk it should first attempt to the name of the cmr-field abstract accessors. Problems occur when the entity does not have an accessor for the relationship, and when the primary key related entity maps to more then one db column. What is your complete proposal for fk column generation and relation-table column generation? Be specific. Not quite I suggest you use the name of the cmr-field-name in the ejb-relationship. therefore when creating the column the field always has to be there. Now after great thought how do you keep the columns straight in a multi column pk? So if table1 has a primary key of a,b,c and the foregin key in the table2 is e,f,g and then to find the key a=g,b=f and c=e how do you specify this now? There is no guarantee on the order the fields are pulled out of the primary key. Is the order we specify them in the cmp-fieldfield-name have to be the same on both sides of the relation? Once you answer this I can pull the rest of the proposal together. As for my comment easy to code, that is perfectly valid, as we are shooting for CMP 2.0 compliance. CMP 2.0 is a huge spec, so everything can not be perfect in the first pass. Some of the implementation details get implemnted the easy way. There have to be priorities. Yup, it's just this one looks like something that will fill the mailing lists. If you pulled together your test cases then I could probably have a look, you do not have to do this whole thing by yourself. I know. I am working on the todo list right now (which will be posted to sf), and after that I will be adding my test cases. For now, what is your proposal? -dain ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Test cases
- Original Message - From: Dain Sundstrom [EMAIL PROTECTED] Cc: jboss-dev [EMAIL PROTECTED] Sent: Monday, November 19, 2001 1:35 PM Subject: [JBoss-dev] Test cases Is this structure imposed by the build system or is it just a convention? I have a set of test that are based on the cmp 2 section 10.3.7 Assignment rules for relationships of the ejb 2.0 spec. There are test for each relation type (1-n bi, 1-n uni, n-1 uni ...) and mapping style (fk, fk with back pointers, and relation-table). That is about 14 unit tests. Anyway I have these organized into sub-packages under the org.jboss.test.relationship package. I can't merge them all into package as each type has it's own set of 'A' / 'B' interfaces. Should I leave them organized into sub packages or should I eliminate the top level relationship package? That unit tests must be in a org/jboss/test/*/test subpacakge is imposed by the build system as this is the only place it looks for tests. Only the JUnit testcase classes need to be here. You can have as many supporting packages as you want. The unit tests just need to import the supporting packages. The other issue I have is my tests use a, yet to be completed, extension to JUnit which runs the tests on the serverside (I wrote this). This is required for testing local interfaces which by definition are not accessible remotely. Anyway, how do I go about adding the code to the build system. It is in the package net.sourceforge.junitejb.* If this is a seperate project your maintaing it needs to be treated as a thirdparty library. If its not move into the JBossTest module under org.jboss.test.util ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: Test cases
On 2001.11.19 16:35:48 -0500 Dain Sundstrom wrote: Comments below (changed subject to reflect new discussion thread) snip Is this structure imposed by the build system or is it just a convention? Looking more closely, anything named *UnitTestCase and not specifically excluded will be run in tests-unit. Put as many directories as you want in. I have a set of test that are based on the cmp 2 section 10.3.7 Assignment rules for relationships of the ejb 2.0 spec. There are test for each relation type (1-n bi, 1-n uni, n-1 uni ...) and mapping style (fk, fk with back pointers, and relation-table). That is about 14 unit tests. Anyway I have these organized into sub-packages under the org.jboss.test.relationship package. I can't merge them all into package as each type has it's own set of 'A' / 'B' interfaces. Should I leave them organized into sub packages or should I eliminate the top level relationship package? The other issue I have is my tests use a, yet to be completed, extension to JUnit which runs the tests on the serverside (I wrote this). This is required for testing local interfaces which by definition are not accessible remotely. Anyway, how do I go about adding the code to the build system. It is in the package net.sourceforge.junitejb.* This is on sourceforge in its most recent state? I'd add the jar into thirdparty/junitejb/junitejb/lib/junitejb.jar with a readme saying what version it is. I'd think tagging cvs when you make the jar would be a very good idea. You might want to ask Jason first. david -dain ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/docs/developers/guide - New directory
User: user57 Date: 01/11/19 14:10:45 newsite/src/docs/developers/guide - New directory ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] RE: Test cases
The other issue I have is my tests use a, yet to be completed, extension to JUnit which runs the tests on the serverside (I wrote this). This is required for testing local interfaces which by definition are not accessible remotely. Anyway, how do I go about adding the code to the build system. It is in the package net.sourceforge.junitejb.* This is on sourceforge in its most recent state? I'd add the jar into thirdparty/junitejb/junitejb/lib/junitejb.jar with a readme saying what version it is. I'd think tagging cvs when you make the jar would be a very good idea. You might want to ask Jason first. I have to update the cvs for my project. I just changed it with the cmp2 doc example code. The I'll package and post the package. I'll also tag the cvs version. If Jason is listening, do you have any comments on this? -dain ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: Test cases
snip Is this structure imposed by the build system or is it just a convention? Looking more closely, anything named *UnitTestCase and not specifically excluded will be run in tests-unit. Put as many directories as you want in. This is a change in main then. I think we should keep the previous convention of having a single directory per suite of tests that contain all the unit test classes. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] 1 to Many Relations
If I use the jbosscmp-jdbc.xml file I can get it to work. Do you have to use the jbosscmp-jdbc.xml file? If you don't, what happens? Does the system generate two columns with the same name? The database table already exsists. Basically I have to use foreign-key-fields and set field-name and column-name attributes the same. Ok, now we are getting somewhere. If you want to use an existing database structure you must tell JBossCMP about it. JAWS had the same requirement. If your database happens to work by default, well you were lucky. We make no gaurentees that JBossCMP will map by default the way you want. We may decide that a default name was stupid and change it. Let make this very very very very clear. All column names are either generated, or specified in the jbosscmp-jdbc.xml file. All column names are either generated, or specified in the jbosscmp-jdbc.xml file. Your opinion is that when jboss generates the column name for a relationship fk it should first attempt to the name of the cmr-field abstract accessors. Problems occur when the entity does not have an accessor for the relationship, and when the primary key related entity maps to more then one db column. What is your complete proposal for fk column generation and relation-table column generation? Be specific. Not quite I suggest you use the name of the cmr-field-name in the ejb-relationship. therefore when creating the column the field always has to be there. What about many-to-one unidirectiona relationships that wish to use a fk? Now after great thought how do you keep the columns straight in a multi column pk? So if table1 has a primary key of a,b,c and the foregin key in the table2 is e,f,g and then to find the key a=g,b=f and c=e how do you specify this now? There is no guarantee on the order the fields are pulled out of the primary key. Is the order we specify them in the cmp-fieldfield-name have to be the same on both sides of the relation? Once you answer this I can pull the rest of the proposal together. Order has nothing to do with this. Each pk field is mapped by name in the foreign-key-fields element or the table-fields element. foreign-key-fields foreign-key-field field-namea/field-name column-namee/column-name /foreign-key-field foreign-key-field field-nameb/field-name column-namef/column-name /foreign-key-field foreign-key-field field-namec/field-name column-nameg/column-name /foreign-key-field /foreign-key-fields All of this information is mainatined in the field objects (see the bridge package). -dain ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/docs main.css navigation.jsp
User: user57
Date: 01/11/19 15:00:22
Modified:src/docs main.css navigation.jsp
Log:
o found out there was a developers/main.css, copied the styles over
from /main.css (with the appropriate color changes)
o moved buildsystem* and quickstart guides to /developers/guide
o added logging system guide (based on the recent emails from scott)
o moved the guidelines.jsp to guide/codestyle.jsp
o changed navigation pages to use a New suffix (in superscript) for
items marked as new.
o changed CVS to Source Code on develoeprs nav include
o added guides link to resources section
o moved SF Project info to Resources section @SourceForge
* leaving quick start under source code to help new users find it faster
Revision ChangesPath
1.7 +2 -2 newsite/src/docs/main.css
Index: main.css
===
RCS file: /cvsroot/jboss/newsite/src/docs/main.css,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- main.css 2001/11/19 20:33:31 1.6
+++ main.css 2001/11/19 23:00:22 1.7
@@ -1,8 +1,8 @@
/**
- * Style Sheet document for the new JBoss website.
+ * Style Sheet for the JBoss Users website.
*/
-/* $Id: main.css,v 1.6 2001/11/19 20:33:31 user57 Exp $ */
+/* $Id: main.css,v 1.7 2001/11/19 23:00:22 user57 Exp $ */
.linkhead {
font-family: Arial,serif;
1.14 +10 -10newsite/src/docs/navigation.jsp
Index: navigation.jsp
===
RCS file: /cvsroot/jboss/newsite/src/docs/navigation.jsp,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- navigation.jsp2001/11/16 02:12:24 1.13
+++ navigation.jsp2001/11/19 23:00:22 1.14
@@ -55,9 +55,9 @@
trtd width=110 height=16 bgcolor=#c6b80bp class=linkhead
HOME
/td/tr/table
- a class=linkmenu href=/vision.jspfont color=red(new)/font Our
vision/abr
- a class=linkmenu href=/developers/index.jspFor developers/abr
- a class=linkmenu href=/index.jspFor users/abr
+ a class=linkmenu href=/vision.jspOurnbsp;Visionsupfont
color=red New/font/sup/abr
+ a class=linkmenu
href=/developers/index.jspFornbsp;Developers/abr
+ a class=linkmenu href=/index.jspFornbsp;Users/abr
/td
td bgcolor=#ffcc00 valign=topimg src=/pictures/tb5.gif/td
@@ -76,13 +76,13 @@
td bgcolor=#ffcc00
table cellspacing=0 cellpadding=0 border=0
trtd width=110 height=16 bgcolor=#c6b80bp class=linkhead
- FREE PRODUCTS
+ FREEnbsp;PRODUCTS
/td/tr/table
a class=linkmenu href=/jboss-overview.jspOverview/abr
a class=linkmenu href=/doco.jspDocumentation/abr
a class=linkmenu href=/binary.jspDownload JBoss/abr
- a class=linkmenu href=/spread.jspfont color=red(new)/font
Presentation/abr
+ a class=linkmenu href=/spread.jspPresentationsupfont color=red
New/font/sup/abr
/td
td bgcolor=#ffcc00 valign=topimg src=/pictures/tb5.gif/td
@@ -101,7 +101,7 @@
td bgcolor=#ffcc00
table cellspacing=0 cellpadding=0 border=0
trtd width=110 height=16 bgcolor=#c6b80bp class=linkhead
- $ OFFERINGS $
+ $nbsp;OFFERINGSnbsp;$
/td/tr/table
a class=linkmenu href=/jbossgroup/partners.jspPartners/abr
a class=linkmenu href=/jbossgroup/services.jspSupport /abr
@@ -128,10 +128,10 @@
p class=linkhead RESOURCES
/td/tr/table
- a class=linkmenu href=/testimonials.jspReferences/abr
- a class=linkmenu href=/forums/index.jspUser Forums/abr
- a class=linkmenu href=/survey/index.jspUser Survey/abr
- a class=linkmenu href=/team.jspThe Team/abr
+ a class=linkmenu href=/testimonials.jspReferences/abr
+ a class=linkmenu href=/forums/index.jspUsernbsp;Forums/abr
+ a class=linkmenu href=/survey/index.jspUsernbsp;Survey/abr
+ a class=linkmenu href=/team.jspThenbsp;Team/abr
/td
td bgcolor=#ffcc00 valign=topimg src=/pictures/tb5.gif/td
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/docs/developers contrib.jsp cvs.jsp head.jsp main.css navigation.jsp buildsystem-faq.jsp buildsystem.jsp guidelines.jsp quickstart.jsp
User: user57 Date: 01/11/19 15:00:23 Modified:src/docs/developers contrib.jsp cvs.jsp head.jsp main.css navigation.jsp Removed: src/docs/developers buildsystem-faq.jsp buildsystem.jsp guidelines.jsp quickstart.jsp Log: o found out there was a developers/main.css, copied the styles over from /main.css (with the appropriate color changes) o moved buildsystem* and quickstart guides to /developers/guide o added logging system guide (based on the recent emails from scott) o moved the guidelines.jsp to guide/codestyle.jsp o changed navigation pages to use a New suffix (in superscript) for items marked as new. o changed CVS to Source Code on develoeprs nav include o added guides link to resources section o moved SF Project info to Resources section @SourceForge * leaving quick start under source code to help new users find it faster Revision ChangesPath 1.4 +9 -6 newsite/src/docs/developers/contrib.jsp Index: contrib.jsp === RCS file: /cvsroot/jboss/newsite/src/docs/developers/contrib.jsp,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- contrib.jsp 2001/11/07 19:55:37 1.3 +++ contrib.jsp 2001/11/19 23:00:22 1.4 @@ -87,15 +87,15 @@ p class=text When submitting a bug, please include the following information: - ul + ul class=text liYour Operating System (WindowsNT, Linux, ...) /li liJDK Version (1.2.2, 1.3, ...) /li liServer trace from the console (JDK version is at the beginning..) /li liSteps to reproduce the bug/li /ul +p class=text Your bug report will be automatically sent to the developer list. -p/p p a class=link href=http://sourceforge.net/tracker/?func=addgroup_id=22866atid=376685;Submit Bug Report/a @@ -113,11 +113,14 @@ a class=link href=http://sourceforge.net/tracker/?func=addgroup_id=22866atid=376688;Submit Feature Request/a /p -p class=headStyle Guides (DEVELOPERS)/p +p class=headGUIDES (DEVELOPERS)/p p class=text - Please have a look at the a class=link href=guidelines.jspGuidelines/a to make - JBoss code more readable, thanx. + Please have a look at the various developer + a class=link href=/developers/guide/guides/a. + Be sure to understand and follow the + a class=link href=/developers/guide/codestyle.jspStyle Guide/a + to help keep JBoss code readable. /p p class=headCHANGE NOTES (DEVELOPERS)/p @@ -129,7 +132,7 @@ form group to indicate which version your change applies to. /p -p +p class=text a class=link href=http://sourceforge.net/tracker/?func=addgroup_id=22866atid=381174;Submit Change Note/a (Requires login) /p 1.10 +61 -25newsite/src/docs/developers/cvs.jsp Index: cvs.jsp === RCS file: /cvsroot/jboss/newsite/src/docs/developers/cvs.jsp,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- cvs.jsp 2001/11/17 04:19:12 1.9 +++ cvs.jsp 2001/11/19 23:00:22 1.10 @@ -18,26 +18,51 @@ !-- end picateam block --/td/tr/table + p class=headSOURCE CODE/p + p class=text - Our CVS repository (amoung other things) is hosted by our friends at - a class=link href=http://sourceforge.net; - img src=http://sourceforge.net/sflogo.php?group_id=22866; border=0 alt=SourceForge align=absmiddle/a - /ul - /p + Source code is available from a href=#CVSCVS/a or + a nightly updated CVS a href=#NIGHTLY_SNAPSHOTSsnapshot/a. - p class=headSOURCE CODE/p - + p class=head + a name=NIGHTLY_SNAPSHOTSNIGHTLY SNAPSHOTS/a + + p class=text + Snapshots are only made for the latest development branches, so if you + need a specific branch you will need to use CVS to get at it. + + p class=text + Browse the available a class=link href=/snapshotssnapshots/a + or select one of the following: + ul class=text + lijboss-all + [a class=link href=/snapshots/jboss-all.zipzip/a] + [a class=link href=/snapshots/jboss-all.tgztgz/a] + lijboss-mq + [a class=link href=/snapshots/jboss-mq.zipzip/a] + [a class=link href=/snapshots/jboss-mq.tgztgz/a] + lijboss-plugins + [a class=link href=/snapshots/jboss-plugins.zipzip/a] + [a class=link href=/snapshots/jboss-plugins.tgztgz/a] + /ul + + p class=head + a name=CVSCVS/a + p class=text - a class=link
[JBoss-dev] CVS update: jbossmx/src/main/org/jboss/ha/framework/server ClusterPartitionMBean.java ClusterPartition.java
User: patriot1burke
Date: 01/11/19 15:13:49
Modified:src/main/org/jboss/ha/framework/server
ClusterPartitionMBean.java ClusterPartition.java
Log:
implemented 2-phase initialization under new mbean code (removal of init())
Revision ChangesPath
1.3 +34 -30
jbossmx/src/main/org/jboss/ha/framework/server/ClusterPartitionMBean.java
Index: ClusterPartitionMBean.java
===
RCS file:
/cvsroot/jboss/jbossmx/src/main/org/jboss/ha/framework/server/ClusterPartitionMBean.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- ClusterPartitionMBean.java2001/11/11 19:04:25 1.2
+++ ClusterPartitionMBean.java2001/11/19 23:13:49 1.3
@@ -1,30 +1,34 @@
-package org.jboss.ha.framework.server;
-
-import org.jboss.ha.framework.interfaces.HAPartition;
-
-public interface ClusterPartitionMBean
- extends org.jboss.system.ServiceMBean
-{
- // Constants -
- public static final String OBJECT_NAME = :service=HANaming;
-
- public String getPartitionName();
- public void setPartitionName(String newName);
-
- public String getPartitionProperties(); // i.e. JavaGroups properties
- public void setPartitionProperties(String newProps);
-
- public boolean getDeadlockDetection();
- public void setDeadlockDetection(boolean doit);
-
- // Access to the underlying HAPartition without going through JNDI
- //
- public HAPartition getHAPartition ();
-}
-
-
-
-
-
-
-
+package org.jboss.ha.framework.server;
+
+import java.util.Collection;
+import org.jboss.ha.framework.interfaces.HAPartition;
+
+public interface ClusterPartitionMBean
+ extends org.jboss.system.ServiceMBean
+{
+ // Constants -
+ static final String OBJECT_NAME = :service=ClusterPartition;
+
+ String getPartitionName();
+ void setPartitionName(String newName);
+
+ String getPartitionProperties(); // i.e. JavaGroups properties
+ void setPartitionProperties(String newProps);
+
+ boolean getDeadlockDetection();
+ void setDeadlockDetection(boolean doit);
+
+ Collection getSynchronizedMBeans();
+ void setSynchronizedMBeans(Collection syncMBeans);
+
+ // Access to the underlying HAPartition without going through JNDI
+ //
+ HAPartition getHAPartition ();
+}
+
+
+
+
+
+
+
1.7 +63 -3
jbossmx/src/main/org/jboss/ha/framework/server/ClusterPartition.java
Index: ClusterPartition.java
===
RCS file:
/cvsroot/jboss/jbossmx/src/main/org/jboss/ha/framework/server/ClusterPartition.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- ClusterPartition.java 2001/11/12 19:59:17 1.6
+++ ClusterPartition.java 2001/11/19 23:13:49 1.7
@@ -10,6 +10,9 @@
import javax.management.MBeanServer;
import javax.management.ObjectName;
import javax.management.MalformedObjectNameException;
+import java.util.ArrayList;
+import java.util.Collection;
+import java.util.Iterator;
import org.jboss.metadata.ClusterConfigMetaData;
@@ -24,12 +27,13 @@
*
* @author [EMAIL PROTECTED]
* @author [EMAIL PROTECTED]
- * @version $Revision: 1.6 $
+ * @version $Revision: 1.7 $
*
* pbRevisions:/bbr
*/
public class ClusterPartition extends ServiceMBeanSupport implements
ClusterPartitionMBean
{
+ protected final Collection syncMBeans = new ArrayList();
protected String partitionName = ClusterConfigMetaData.DEFAULT_PARTITION;
protected String jgProps =
/*
@@ -58,7 +62,7 @@
GMS: +
STATE_TRANSFER(trace=true): +
QUEUE;
-protected HAPartitionImpl partition;
+ protected HAPartitionImpl partition;
protected boolean deadlock_detection = false;
protected JChannel channel;
@@ -103,6 +107,23 @@
return new ObjectName(OBJECT_NAME);
}
+ public Collection getSynchronizedMBeans()
+ {
+ synchronized (syncMBeans)
+ {
+ return new ArrayList(syncMBeans);
+ }
+ }
+
+ public synchronized void setSynchronizedMBeans(Collection syncMBeans)
+ {
+ log.info(SynchronizedMBeans set to + syncMBeans);
+ synchronized (this.syncMBeans)
+ {
+ this.syncMBeans.clear();
+ this.syncMBeans.addAll(syncMBeans);
+ }
+ }
public HAPartition getHAPartition ()
{
return this.partition;
@@ -124,6 +145,20 @@
partition.init();
log.info(...HAPartition initialized.);
+ synchronized (syncMBeans) //noone should be
[JBoss-dev] CVS update: jbossmx/src/main/org/jboss/ha/jndi HANamingServiceMBean.java HANamingService.java
User: patriot1burke
Date: 01/11/19 15:16:57
Modified:src/main/org/jboss/ha/jndi HANamingServiceMBean.java
HANamingService.java
Log:
implemented 2-phase initialization under new mbean code (removal of init())
also added stop method to AutomaticDiscovery so that sockets would be
cleaned up
Revision ChangesPath
1.4 +3 -3 jbossmx/src/main/org/jboss/ha/jndi/HANamingServiceMBean.java
Index: HANamingServiceMBean.java
===
RCS file:
/cvsroot/jboss/jbossmx/src/main/org/jboss/ha/jndi/HANamingServiceMBean.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- HANamingServiceMBean.java 2001/10/10 20:02:05 1.3
+++ HANamingServiceMBean.java 2001/11/19 23:16:57 1.4
@@ -1,17 +1,17 @@
package org.jboss.ha.jndi;
import java.net.UnknownHostException;
-
+import org.jboss.ha.framework.server.PartitionServiceMBean;
/**
*
* @author [EMAIL PROTECTED]
* @author [EMAIL PROTECTED]
- * @version $Revision: 1.3 $
+ * @version $Revision: 1.4 $
*
* pbRevisions:/bbr
*/
public interface HANamingServiceMBean
- extends org.jboss.system.ServiceMBean
+ extends PartitionServiceMBean
{
// Constants -
public static final String OBJECT_NAME = :service=HANaming;
1.14 +50 -16jbossmx/src/main/org/jboss/ha/jndi/HANamingService.java
Index: HANamingService.java
===
RCS file: /cvsroot/jboss/jbossmx/src/main/org/jboss/ha/jndi/HANamingService.java,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- HANamingService.java 2001/11/18 12:40:42 1.13
+++ HANamingService.java 2001/11/19 23:16:57 1.14
@@ -61,9 +61,14 @@
* Management Bean for HA-JNDI service.
*
* @author [EMAIL PROTECTED]
- * @version $Revision: 1.13 $
+ * @version $Revision: 1.14 $
*
* pbRevisions:/bbr
+ * pb2001/11/19 bill burke:/b
+ * ul
+ * li implemented PartitionServiceMBean interface for new 2-phase initilization
+ * li added stop method to AutomaticDiscovery so that it could be cleaned up.
+ * /ul
*/
public class HANamingService extends ServiceMBeanSupport implements Runnable,
HANamingServiceMBean
{
@@ -202,19 +207,11 @@
}
- protected void startService()
+ public void startPartitionService(HAPartition haPartition)
throws Exception
{
- log.info(Initializing HAJNDI server);
- partition = (HAPartition)new InitialContext().lookup(/HAPartition/ +
partitionName);
- replicantManager = partition.getDistributedReplicantManager();
- log.info(Create remote object);
- theServer = new HAJNDI(partition);
- log.info(initialize HAJNDI);
- theServer.init();
log.info(Starting HAJNDI server);
-
- log.info(Register with replicantManager as listener for HAJNDI replicants);
+ log.info(Create HARMIServer proxy);
this.rmiserver = new HARMIServerImpl(partition, HAJNDI, Naming.class,
theServer);
this.stub = (Naming)rmiserver.createHAStub(new RoundRobin());
@@ -240,19 +237,41 @@
autoDiscovery.listen ();
}
- protected void stopService()
+ protected void startService()
+ throws Exception
{
+ }
+
+ public void partitionInitializationPhase(HAPartition haPartition)
+ throws Exception
+ {
+ log.info(Initializing HAJNDI server);
+ log.info(jndi lookup of + /HAPartition/ + partitionName);
+ partition = (HAPartition)new InitialContext().lookup(/HAPartition/ +
partitionName);
+ replicantManager = partition.getDistributedReplicantManager();
+ log.info(Create remote object);
+ theServer = new HAJNDI(partition);
+ log.info(initialize HAJNDI);
+ theServer.init();
+ }
+
+ public void stopPartitionService() throws Exception
+ {
try
{
- log.info(Stopping);
+ log.info(HA-JNDI is stopping);
// Unexport server
+ log.info(destroy ha rmiserver);
this.rmiserver.destroy ();
// Stop listener
ServerSocket s = serverSocket;
serverSocket = null;
+ log.info(closing socket);
s.close();
+ log.info(Stopping AutomaticDiscovery);
+ autoDiscovery.stop();
log.info(Stopped);
} catch (Exception e)
{
@@ -327,12 +346,13 @@
{
protected MulticastSocket socket = null;
protected byte[] ipAddress = null;
+ protected InetAddress group = null;
+ protected boolean stopping = false;
-
public
[JBoss-dev] CVS update: jbossmx/src/main/org/jboss/ha/hasessionstate/server HASessionStateServiceMBean.java HASessionStateService.java
User: patriot1burke
Date: 01/11/19 15:17:34
Modified:src/main/org/jboss/ha/hasessionstate/server
HASessionStateServiceMBean.java
HASessionStateService.java
Log:
implemented 2-phase initialization under new mbean code (removal of init())
THis means implementing PartitionServiceMBean interface
Revision ChangesPath
1.2 +3 -2
jbossmx/src/main/org/jboss/ha/hasessionstate/server/HASessionStateServiceMBean.java
Index: HASessionStateServiceMBean.java
===
RCS file:
/cvsroot/jboss/jbossmx/src/main/org/jboss/ha/hasessionstate/server/HASessionStateServiceMBean.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- HASessionStateServiceMBean.java 2001/11/09 22:49:56 1.1
+++ HASessionStateServiceMBean.java 2001/11/19 23:17:34 1.2
@@ -6,18 +6,19 @@
*/
package org.jboss.ha.hasessionstate.server;
+import org.jboss.ha.framework.server.PartitionServiceMBean;
/**
* MBEAN interface for HASessionState service
*
* @see HASessionState
* @author [EMAIL PROTECTED]
- * @version $Revision: 1.1 $
+ * @version $Revision: 1.2 $
*
* pbRevisions:/bbr
*/
-public interface HASessionStateServiceMBean extends org.jboss.system.ServiceMBean
+public interface HASessionStateServiceMBean extends PartitionServiceMBean
{
// Constants -
public static final String OBJECT_NAME = JBOSS-SYSTEM:service=HASessionState;
1.3 +16 -4
jbossmx/src/main/org/jboss/ha/hasessionstate/server/HASessionStateService.java
Index: HASessionStateService.java
===
RCS file:
/cvsroot/jboss/jbossmx/src/main/org/jboss/ha/hasessionstate/server/HASessionStateService.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- HASessionStateService.java2001/11/12 06:36:49 1.2
+++ HASessionStateService.java2001/11/19 23:17:34 1.3
@@ -17,13 +17,14 @@
import org.jboss.metadata.ClusterConfigMetaData;
import org.jboss.ha.hasessionstate.server.HASessionStateImpl;
+import org.jboss.ha.framework.interfaces.HAPartition;
/**
* Service class for HASessionState
*
* @see HASessionState
* @author [EMAIL PROTECTED]
- * @version $Revision: 1.2 $
+ * @version $Revision: 1.3 $
*
* pbRevisions:/bbr
*/
@@ -144,15 +145,26 @@
// **
- protected void startService () throws Exception
+ public void startPartitionService(HAPartition haPartition)
+ throws Exception
+ {
+ this.sessionState.start ();
+ }
+
+ public void partitionInitializationPhase(HAPartition haPartition)
+ throws Exception
{
this.sessionState = new HASessionStateImpl (this.jndiName,
this.subPartitionProps, this.haPartitionName, this.topologyComputerClass,
this.subPartitionSize,
this.subPartitionCreationWaitTime, this.beanCleaningDelay);
this.sessionState.init ();
- this.sessionState.start ();
+ }
+
+ protected void startService () throws Exception
+ {
+ // Complete.
}
- protected void stopService ()
+ public void stopPartitionService ()
{
try
{
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] RE: Test cases
I haven't been following this thread at all... just happened to see my name at the bottom on this one. What is the issue? The short version please =) --jason On Mon, 19 Nov 2001, Dain Sundstrom wrote: The other issue I have is my tests use a, yet to be completed, extension to JUnit which runs the tests on the serverside (I wrote this). This is required for testing local interfaces which by definition are not accessible remotely. Anyway, how do I go about adding the code to the build system. It is in the package net.sourceforge.junitejb.* This is on sourceforge in its most recent state? I'd add the jar into thirdparty/junitejb/junitejb/lib/junitejb.jar with a readme saying what version it is. I'd think tagging cvs when you make the jar would be a very good idea. You might want to ask Jason first. I have to update the cvs for my project. I just changed it with the cmp2 doc example code. The I'll package and post the package. I'll also tag the cvs version. If Jason is listening, do you have any comments on this? -dain ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmx/etc cluster-service.xml
User: patriot1burke Date: 01/11/19 15:21:41 Modified:etc cluster-service.xml Log: new xml Revision ChangesPath 1.3 +41 -37jbossmx/etc/cluster-service.xml Index: cluster-service.xml === RCS file: /cvsroot/jboss/jbossmx/etc/cluster-service.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- cluster-service.xml 2001/11/09 23:54:39 1.2 +++ cluster-service.xml 2001/11/19 23:21:41 1.3 @@ -1,37 +1,41 @@ -?xml version=1.0 encoding=UTF-8? - - -!-- = -- -!-- -- -!-- Sample Clustering Service Configuration -- -!-- -- -!-- = -- - -server - - classpath archives=jbossha.jar/ - - dependsJBOSS-SYSTEM:service=Naming/depends - - !-- -- - !-- Cluster Partition: defines cluster -- - !-- -- - - mbean code=org.jboss.ha.framework.server.ClusterPartition name=JBOSS-SYSTEM:service=DefaultPartition - /mbean - - !-- -- - !-- HA Session State Service for SFSB-- - !-- -- - - mbean code=org.jboss.ha.hasessionstate.server.HASessionStateService name=JBOSS-SYSTEM:service=HASessionState - /mbean - - !-- -- - !-- HA JNDI -- - !-- -- - - mbean code=org.jboss.ha.jndi.HANamingService name=JBOSS-SYSTEM:service=HAJNDI - /mbean - -/server +?xml version=1.0 encoding=UTF-8? + + +!-- = -- +!-- -- +!-- Sample Clustering Service Configuration -- +!-- -- +!-- = -- + +server + + classpath archives=jbossha.jar/ + + dependsJBOSS-SYSTEM:service=Naming/depends + + !-- -- + !-- Cluster Partition: defines cluster -- + !-- -- + + mbean code=org.jboss.ha.framework.server.ClusterPartition name=JBOSS-SYSTEM:service=DefaultPartition +mbean-ref-list name=SynchronizedMBeans + mbean-ref-list-elementJBOSS-SYSTEM:service=HASessionState/mbean-ref-list-element + mbean-ref-list-elementJBOSS-SYSTEM:service=HAJNDI/mbean-ref-list-element +/mbean-ref-list + /mbean + + !-- -- + !-- HA Session State Service for SFSB-- + !-- -- + + mbean code=org.jboss.ha.hasessionstate.server.HASessionStateService name=JBOSS-SYSTEM:service=HASessionState + /mbean + + !-- -- + !-- HA JNDI -- + !-- -- + + mbean code=org.jboss.ha.jndi.HANamingService name=JBOSS-SYSTEM:service=HAJNDI + /mbean + +/server ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] new developers guide section
I just finished some initial work on a guide section for the developers site. I moved the build system stuff and the quick start guide in here. I also added the start of a logging guide, based off of the emails from Scott. This should be ready for viewing tomorrow, unless the autodeployer on jboss.org has an issue. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] clustering mbeans fixed
FYI Bill
[JBoss-dev] CVS update: website-snapshots - Imported sources
User: user57 Date: 01/11/19 16:42:20 Log: o import of a seperated website/snapshots module Status: Vendor Tag: jboss Release Tags: start N website-snapshots/build.bat N website-snapshots/build.sh N website-snapshots/build.xml N website-snapshots/src/metadata/snapshots-web.xml N website-snapshots/src/metadata/snapshots-application.xml No conflicts created by this import ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: CVSROOT modules
User: user57 Date: 01/11/19 16:50:01 Modified:.modules Log: o oops =| Revision ChangesPath 1.72 +1 -1 CVSROOT/modules Index: modules === RCS file: /cvsroot/jboss/CVSROOT/modules,v retrieving revision 1.71 retrieving revision 1.72 diff -u -r1.71 -r1.72 --- modules 2001/11/20 00:46:41 1.71 +++ modules 2001/11/20 00:50:01 1.72 @@ -123,7 +123,7 @@ _jboss_website_build -d buildbuild/website _jboss_website_forums-d forums website-forums _jboss_website_survey-d survey website-survey -_jboss_website_snapshots -d survey website-snapshots +_jboss_website_snapshots -d snapshotswebsite-snapshots _jboss_website_website -d website newsite ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: CVSROOT modules
User: user57 Date: 01/11/19 16:46:41 Modified:.modules Log: o added snapshots module to jboss-website Revision ChangesPath 1.71 +5 -3 CVSROOT/modules Index: modules === RCS file: /cvsroot/jboss/CVSROOT/modules,v retrieving revision 1.70 retrieving revision 1.71 diff -u -r1.70 -r1.71 --- modules 2001/10/23 21:14:04 1.70 +++ modules 2001/11/20 00:46:41 1.71 @@ -114,15 +114,17 @@ jboss-website-modules-a \ _jboss_website_build \ _jboss_website_forums \ - _jboss_j2ee \ _jboss_website_survey \ - _jboss_website \ + _jboss_website_snapshots \ + _jboss_website_website \ + _jboss_j2ee \ _jboss_manual _jboss_website_build -d buildbuild/website _jboss_website_forums-d forums website-forums _jboss_website_survey-d survey website-survey -_jboss_website -d website newsite +_jboss_website_snapshots -d survey website-snapshots +_jboss_website_website -d website newsite ## ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] split up snapshot generation into module
CVS snapshots are now generated in the jboss-website/snapshots module. This allows folks to build the website content seperatly (and effectivly) from the snapshotting. You WILL need to checkout the jboss-website module again to get these changes. Once you have a fresh project workspace, simply specify the modules you want to build. For most ui testing stuff you will just want to use the website content module: ./build/build.sh -Dmodules=website This will build a 'website/output/website.ear', which you can deploy into a JBoss instance and get the jist of what the site looks like. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/metadata website-application.xml snapshots-web.xml website-application-nosnaps.xml
User: user57 Date: 01/11/19 17:13:09 Modified:src/metadata website-application.xml Removed: src/metadata snapshots-web.xml website-application-nosnaps.xml Log: o removed snapshot configuration metadata files (moved to snapshots module) o removed indexPET.jsp, has old data, looks like it is not ref'd anywhere o updated cvs.jsp, added direct link to the latest CVSROOT/modules documented that the when browsing the structure is different than when checking out Revision ChangesPath 1.4 +1 -8 newsite/src/metadata/website-application.xml Index: website-application.xml === RCS file: /cvsroot/jboss/newsite/src/metadata/website-application.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- website-application.xml 2001/11/02 17:29:54 1.3 +++ website-application.xml 2001/11/20 01:13:09 1.4 @@ -1,7 +1,7 @@ ?xml version=1.0 encoding=UTF-8? !DOCTYPE application -!-- $Id: website-application.xml,v 1.3 2001/11/02 17:29:54 mnf999 Exp $ -- +!-- $Id: website-application.xml,v 1.4 2001/11/20 01:13:09 user57 Exp $ -- application display-nameJBoss Website/display-name @@ -10,13 +10,6 @@ web web-uriwebsite.war/web-uri context-root//context-root - /web - /module - - module - web - web-urisnapshots.war/web-uri - context-root/snapshots/context-root /web /module ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite build.xml
User: user57
Date: 01/11/19 17:13:07
Modified:.build.xml
Log:
o removed snapshot configuration metadata files (moved to snapshots
module)
o removed indexPET.jsp, has old data, looks like it is not ref'd anywhere
o updated cvs.jsp, added direct link to the latest CVSROOT/modules
documented that the when browsing the structure is different than when
checking out
Revision ChangesPath
1.25 +3 -145newsite/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/newsite/build.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- build.xml 2001/11/13 23:44:42 1.24
+++ build.xml 2001/11/20 01:13:07 1.25
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.24 2001/11/13 23:44:42 tmcsys Exp $ --
+!-- $Id: build.xml,v 1.25 2001/11/20 01:13:07 user57 Exp $ --
project default=main name=JBoss Website/Website
@@ -184,8 +184,6 @@
!-- Where build generated files will go --
property name=build.bin value=${module.output}/bin/
property name=build.metadata value=${module.output}/metadata/
-property name=build.snapshots value=${module.output}/snapshots/
-property name=build.snapshots.tmp value=${build.snapshots}/tmp/
property name=build.docs value=${module.output}/docs/
property name=build.xdocs value=${module.output}/xdocs/
property name=build.stylesheets value=${module.output}/stylesheets/
@@ -233,13 +231,6 @@
property name=junit.timeout value=24/ !-- 4 minutes --
property name=junit.batchtest.todir value=${build.reports}/
property name=junit.jvm.options value=-Ddummy/
-
-!-- Controls for the compile-snapshot target --
-property name=snapshot.cvsroot
- value=:pserver:[EMAIL PROTECTED]:/cvsroot/jboss/
-
-property name=snapshot.modules
- value=jboss-all jboss-mq jboss-plugins/
/target
@@ -259,8 +250,7 @@
depends=init,
compile-docs,
compile-metadata,
- compile-bin,
- compile-snapshots/
+ compile-bin/
!-- Compile doc sources support files --
target name=compile-docs depends=init
@@ -306,106 +296,6 @@
/chmod
/target
- !-- Export the cvs modules for snapshots --
-
- target name=_compile-snapshots-export-cvs
- depends=init
- unless=snapshot-export-cvs.disable
-mkdir dir=${build.snapshots.tmp}/
-echoExporting CVS modules for snaphots.../echo
-
-
-!-- Make sure there is an entry for this cvsroot --
-
- cvspass cvsroot=${snapshot.cvsroot} password=/
-cvs cvsroot=${snapshot.cvsroot}
- command=-Q -r -f -z3 export
- date=TODAY
- package=${snapshot.modules}
- dest=${build.snapshots.tmp}/
- /target
-
- !-- Compile cvs source snapshots --
-
- target name=compile-snapshots
- unless=snapshot.disable
- depends=init, _compile-snapshots-export-cvs
-mkdir dir=${build.snapshots}/
-
-
-!-- build jboss-all.zip --
-
- zip zipfile=${build.snapshots}/jboss-all.zip
- fileset dir=${build.snapshots.tmp}
-include name=jboss-all/**/
- /fileset
-/zip
-
-
-!-- build jboss-all.tgz --
-
-tar tarfile=${build.snapshots}/jboss-all.tar
- longfile=gnu
- basedir=${build.snapshots.tmp}
- includes=jboss-all/**
-/tar
-gzip src=${build.snapshots}/jboss-all.tar
- zipfile=${build.snapshots}/jboss-all.tgz/
-
-
-!-- build jboss-mq.zip --
-
- zip zipfile=${build.snapshots}/jboss-mq.zip
- fileset dir=${build.snapshots.tmp}
-include name=jboss-mq/**/
- /fileset
-/zip
-
-!-- build jboss-mq.tgz --
-
-tar tarfile=${build.snapshots}/jboss-mq.tar
- longfile=gnu
- basedir=${build.snapshots.tmp}
- includes=jboss-mq/**
-/tar
-gzip src=${build.snapshots}/jboss-mq.tar
- zipfile=${build.snapshots}/jboss-mq.tgz/
-
-!-- build jboss-plugins.zip --
-
- zip zipfile=${build.snapshots}/jboss-plugins.zip
- fileset dir=${build.snapshots.tmp}
-include name=jboss-plugins/**/
- /fileset
-/zip
-
-!-- build jboss-plugins.tgz --
- tar tarfile=${build.snapshots}/jboss-plugins.tar
- longfile=gnu
- basedir=${build.snapshots.tmp}
- includes=jboss-plugins/**
-/tar
-gzip src=${build.snapshots}/jboss-plugins.tar
- zipfile=${build.snapshots}/jboss-plugins.tgz/
-
-!-- =
[JBoss-dev] CVS update: newsite/src/docs/developers cvs.jsp indexPET.jsp
User: user57 Date: 01/11/19 17:13:09 Modified:src/docs/developers cvs.jsp Removed: src/docs/developers indexPET.jsp Log: o removed snapshot configuration metadata files (moved to snapshots module) o removed indexPET.jsp, has old data, looks like it is not ref'd anywhere o updated cvs.jsp, added direct link to the latest CVSROOT/modules documented that the when browsing the structure is different than when checking out Revision ChangesPath 1.11 +13 -11newsite/src/docs/developers/cvs.jsp Index: cvs.jsp === RCS file: /cvsroot/jboss/newsite/src/docs/developers/cvs.jsp,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- cvs.jsp 2001/11/19 23:00:22 1.10 +++ cvs.jsp 2001/11/20 01:13:08 1.11 @@ -36,14 +36,14 @@ or select one of the following: ul class=text lijboss-all - [a class=link href=/snapshots/jboss-all.zipzip/a] - [a class=link href=/snapshots/jboss-all.tgztgz/a] + a class=link href=/snapshots/jboss-all.zip[zip]/a + a class=link href=/snapshots/jboss-all.tgz[tgz]/a lijboss-mq - [a class=link href=/snapshots/jboss-mq.zipzip/a] - [a class=link href=/snapshots/jboss-mq.tgztgz/a] + a class=link href=/snapshots/jboss-mq.zip[zip]/a + a class=link href=/snapshots/jboss-mq.tgz[tgz]/a lijboss-plugins - [a class=link href=/snapshots/jboss-plugins.zipzip/a] - [a class=link href=/snapshots/jboss-plugins.tgztgz/a] + a class=link href=/snapshots/jboss-plugins.zip[zip]/a + a class=link href=/snapshots/jboss-plugins.tgz[tgz]/a /ul p class=head @@ -55,8 +55,10 @@ img src=http://sourceforge.net/sflogo.php?group_id=22866; border=0 alt=SourceForge align=absmiddle/a. p class=text - This repository is available for online - a class=link href=http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/;browsing/a. + The repository is available for online + a class=link href=http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/; browsing/a. + Please note that the structure of the actual repository is + bdifferent/b than the project layout of a checked out CVS module. p class=head a name=CVS_ENVIRONMENTCVS ENVIRONMENT/a @@ -79,7 +81,7 @@ tt:pserver:[EMAIL PROTECTED]:/cvsroot/jboss/ttbr /blockquote p class=text - The password is blank (press enter)./p + The password is emblank/em (just press enter)./p p class=text bSettings for developer access:/b @@ -104,8 +106,8 @@ p class=text Below is a list of the currently supported modules. These modules are - created via ttCVSROOT/modules/tt, so look there for more information - about how they work. + created via tta href=http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/~checkout~/jboss/CVSROOT/modules?rev=1.72;CVSROOT/modules/a/tt, + so look there for more information about how they work. blockquote dl class=text ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: build/website build.xml
User: user57
Date: 01/11/19 17:14:45
Modified:website build.xml
Log:
o added 'snapshots' module config
Revision ChangesPath
1.16 +29 -4 build/website/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/build/website/build.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- build.xml 2001/11/02 00:12:56 1.15
+++ build.xml 2001/11/20 01:14:45 1.16
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.15 2001/11/02 00:12:56 schaefera Exp $ --
+!-- $Id: build.xml,v 1.16 2001/11/20 01:14:45 user57 Exp $ --
project default=main name=JBoss Website/Build
@@ -176,15 +176,20 @@
module name=manual/
module name=forums/
module name=survey/
+ module name=snapshots/
!-- Support modules --
module name=j2ee/
!-- Module groups --
group name=standard
-include modules=website, manual, forums, survey/
+include modules=website, manual, forums, survey, snapshots/
/group
+ group name=quick
+include modules=website/
+ /group
+
group name=support
include modules=j2ee/
/group
@@ -377,6 +382,26 @@
!-- Nothing --
/target
+ !-- = --
+ !-- Snapshots --
+ !-- = --
+
+ target name=_module-snapshots-most
+property name=_module.name value=snapshots override=true/
+property name=_module.output override=true
+ value=${project.root}/${_module.name}/output/
+mkdir dir=${install.deploy}/
+copy todir=${install.deploy}
+ fileset dir=${_module.output}/lib
+include name=snapshots.ear/
+ /fileset
+/copy
+ /target
+
+ target name=_module-snapshots-all depends=_module-snapshots-most
+!-- Nothing --
+ /target
+
!-- == --
!-- Forums --
!-- == --
@@ -588,7 +613,7 @@
/copy
!-- copy the SURVEY deployables but first wait 30 seconds --
-sleep seconds=30 /
+sleep seconds=30/
copy todir=${jboss.deploy.root}
fileset dir=${install.deploy}
include name=survey.ear/
@@ -596,7 +621,7 @@
/copy
!-- copy the SURVEY-HELPER deployables but first wait 30 seconds --
-sleep seconds=30 /
+sleep seconds=30/
copy todir=${jboss.deploy.root}
fileset dir=${install.deploy}
include name=survey-helper.ear/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss3/Jetty4: Optimized call had serialized argument;....
I have now plumbed in, thanks to David Jencks, a working copy of jetty4 (Servlet2.3, JSP 1.2). I am running the WebIntegrationUnitTestCase from the testsuite and all is going well. A quick question: Is this exception something someone is aware of - or is it more likely that I have made a mistake? I figure optimised calls are made if the current thread's ContextClassLoader is correctly set - so they either happen or don't - howcome then we are in an inconsistant state here, where we prepare to make a serialised call and then it turns out to be optimised ? Thanks for your time, Jules [01:10:08,484,Default] StatelessSessionBean2.ejbCreate() called [01:10:08,497,Default] StatelessSessionBean2.noop, test.wasSerialized=true, optimized=true [01:10:08,510,StatelessSessionContainer] invoke returned an exception java.rmi.ServerException: Optimized call had serialized argument; nested exception is: javax.ejb.EJBException: Optimized call had serialized argument javax.ejb.EJBException: Optimized call had serialized argument at org.jboss.test.web.ejb.StatelessSessionBean2.noop(StatelessSessionBean2.java:77) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:569) at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:67) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:98) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:156) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:65) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:131) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166) at org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.java:280) at org.jboss.ejb.Container.invoke(Container.java:528) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerInvoker.java:411) at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerInvoker.java:493) at org.jboss.ejb.plugins.jrmp.interfaces.GenericProxy.invokeContainer(GenericProxy.java:346) at org.jboss.ejb.plugins.jrmp.interfaces.StatelessSessionProxy.invoke(StatelessSessionProxy.java:123) at $Proxy95.noop(Unknown Source) at org.jboss.test.web.servlets.EJBOnStartupServlet.processRequest(EJBOnStartupServlet.java:84) at org.jboss.test.web.servlets.EJBOnStartupServlet.doGet(EJBOnStartupServlet.java:104) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:289) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:526) at org.mortbay.http.HttpContext.handle(HttpContext.java:1132) at org.mortbay.http.HttpContext.handle(HttpContext.java:1086) at org.mortbay.http.HttpServer.service(HttpServer.java:723) at org.mortbay.http.HttpConnection.service(HttpConnection.java:745) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:918) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:760) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:138) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) at org.mortbay.util.ThreadPool$JobRunner.run(ThreadPool.java:715) at java.lang.Thread.run(Thread.java:484) [01:10:08,597,Jetty] WARNING: GET /jbosstest/EJBOnStartupServlet HTTP/1.1 java.rmi.ServerException: Optimized call had serialized argument; nested exception is: javax.ejb.EJBException: Optimized call had serialized argument javax.ejb.EJBException: Optimized call had serialized argument no stack trace available [01:10:08,617,Jetty] ENCServlet: init _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBoss3/Jetty4: Optimized call had serialized argument;....
This means the class loader is not set correctly or that the class loader is more nested than the check performed by the JRMPContainerInvoker is making can handle. This is the check that Marc mentioned earlier that he was going to remove. When this is done this test will either succeed or fail with a ClassCastException. - Original Message - From: Julian Gosnell [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, November 19, 2001 5:17 PM Subject: [JBoss-dev] JBoss3/Jetty4: Optimized call had serialized argument; I have now plumbed in, thanks to David Jencks, a working copy of jetty4 (Servlet2.3, JSP 1.2). I am running the WebIntegrationUnitTestCase from the testsuite and all is going well. A quick question: Is this exception something someone is aware of - or is it more likely that I have made a mistake? I figure optimised calls are made if the current thread's ContextClassLoader is correctly set - so they either happen or don't - howcome then we are in an inconsistant state here, where we prepare to make a serialised call and then it turns out to be optimised ? Thanks for your time, Jules [01:10:08,484,Default] StatelessSessionBean2.ejbCreate() called [01:10:08,497,Default] StatelessSessionBean2.noop, test.wasSerialized=true, optimized=true [01:10:08,510,StatelessSessionContainer] invoke returned an exception java.rmi.ServerException: Optimized call had serialized argument; nested exception is: javax.ejb.EJBException: Optimized call had serialized argument javax.ejb.EJBException: Optimized call had serialized argument at org.jboss.test.web.ejb.StatelessSessionBean2.noop(StatelessSessionBean2.java :77) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(Stateles sSessionContainer.java:569) at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSe ssionInstanceInterceptor.java:67) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor .java:98) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT. java:156) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:65) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:13 1) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166) at org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.jav a:280) at org.jboss.ejb.Container.invoke(Container.java:528) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerI nvoker.java:411) at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerI nvoker.java:493) at org.jboss.ejb.plugins.jrmp.interfaces.GenericProxy.invokeContainer(GenericPr oxy.java:346) at org.jboss.ejb.plugins.jrmp.interfaces.StatelessSessionProxy.invoke(Stateless SessionProxy.java:123) at $Proxy95.noop(Unknown Source) at org.jboss.test.web.servlets.EJBOnStartupServlet.processRequest(EJBOnStartupS ervlet.java:84) at org.jboss.test.web.servlets.EJBOnStartupServlet.doGet(EJBOnStartupServlet.ja va:104) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:289) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:526) at org.mortbay.http.HttpContext.handle(HttpContext.java:1132) at org.mortbay.http.HttpContext.handle(HttpContext.java:1086) at org.mortbay.http.HttpServer.service(HttpServer.java:723) at org.mortbay.http.HttpConnection.service(HttpConnection.java:745) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:918) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:760) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:138) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) at org.mortbay.util.ThreadPool$JobRunner.run(ThreadPool.java:715) at java.lang.Thread.run(Thread.java:484) [01:10:08,597,Jetty] WARNING: GET /jbosstest/EJBOnStartupServlet HTTP/1.1 java.rmi.ServerException: Optimized call had serialized argument; nested exception is: javax.ejb.EJBException: Optimized call had serialized argument javax.ejb.EJBException: Optimized call had serialized argument no stack trace available [01:10:08,617,Jetty] ENCServlet: init _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 188 Successful tests: 150 Errors:25 Failures: 13 [time of test: 20 November 2001 3:12 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-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite. Its easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 188 Successful tests: 152 Errors:24 Failures: 12 [time of test: 20 November 2001 3:59 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-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-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite. Its easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-426048 ] NoClassDefFoundError on Cloudscape
Bugs item #426048, was opened at 2001-05-21 13:32 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=426048group_id=22866 Category: JBossServer Group: v2.2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Andreas Schaefer (schaefera) Summary: NoClassDefFoundError on Cloudscape Initial Comment: Hi, I was trying to deploy EJB beans on the Jboss Server. The beans get deployed fine on both Cloudscape and Oracle databases. However, when I access the beans using Cloudscape database, I am getting this error. It works fine with the Oracle Database. [] TRANSACTION ROLLBACK EXCEPTION:null; nested exception is: javax.ejb.EJBException [] java.lang.ClassCastException: java.lang.NoClassDefFoundError [] at org.jboss.ejb.plugins.BMPPersistenceManager.callFinderM ethod(BMPPersi stenceManager.java:503) [] at org.jboss.ejb.plugins.BMPPersistenceManager.findEntity (BMPPersistence Manager.java:218) [] at org.jboss.ejb.EntityContainer.find (EntityContainer.java:419) [] at java.lang.reflect.Method.invoke(Native Method) [] at org.jboss.ejb.EntityContainer$ContainerInterceptor.invo keHome(EntityC ontainer.java:639) [] at org.jboss.ejb.plugins.EntitySynchronizationInterceptor. invokeHome(Ent itySynchronizationInterceptor.java:160) [] at org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeH ome(EntityInst anceInterceptor.java:87) [] at org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext (TxInterceptorCMT.ja va:135) [] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti ons(TxIntercep torCMT.java:263) [] at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome (TxInterceptorCMT.ja va:86) -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=426048group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JBoss3/Jetty4: Optimized call had serialized argument;....
|This means the class loader is not set correctly or that the class loader |is more nested than the check performed by the JRMPContainerInvoker |is making can handle. This is the check that Marc mentioned earlier that he |was going to remove. When this is done this test will either succeed or |fail with a ClassCastException. right, marcf | |- Original Message - |From: Julian Gosnell [EMAIL PROTECTED] |To: [EMAIL PROTECTED] |Sent: Monday, November 19, 2001 5:17 PM |Subject: [JBoss-dev] JBoss3/Jetty4: Optimized call had serialized |argument; | | | | I have now plumbed in, thanks to David Jencks, a working copy of jetty4 | (Servlet2.3, JSP 1.2). | | I am running the WebIntegrationUnitTestCase from the testsuite and all | is going well. | | A quick question: | | Is this exception something someone is aware of - or is it more likely | that I have made a mistake? | | I figure optimised calls are made if the current thread's | ContextClassLoader is correctly set - so they either happen or don't - | howcome then we are in an inconsistant state here, where we prepare to | make a serialised call and then it turns out to be optimised ? | | Thanks for your time, | | | Jules | | | [01:10:08,484,Default] StatelessSessionBean2.ejbCreate() called | [01:10:08,497,Default] StatelessSessionBean2.noop, | test.wasSerialized=true, optimized=true | [01:10:08,510,StatelessSessionContainer] invoke returned an exception | java.rmi.ServerException: Optimized call had serialized argument; nested | exception is: | javax.ejb.EJBException: Optimized call had serialized argument | javax.ejb.EJBException: Optimized call had serialized argument | at | |org.jboss.test.web.ejb.StatelessSessionBean2.noop(StatelessSessionB |ean2.java |:77) | | at java.lang.reflect.Method.invoke(Native Method) | at | |org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke |(Stateles |sSessionContainer.java:569) | | at | |org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(St |atelessSe |ssionInstanceInterceptor.java:67) | | at | |org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxIn |terceptor |.java:98) | | at | |org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterc |eptorCMT. |java:156) | | at | org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:65) | at | |org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityIntercepto |r.java:13 |1) | | at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166) | | at | |org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionCont |ainer.jav |a:280) | | at org.jboss.ejb.Container.invoke(Container.java:528) | at | com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555) | | at | com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) | | at | |org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPC |ontainerI |nvoker.java:411) | | at | |org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPC |ontainerI |nvoker.java:493) | | at | |org.jboss.ejb.plugins.jrmp.interfaces.GenericProxy.invokeContainer( |GenericPr |oxy.java:346) | | at | |org.jboss.ejb.plugins.jrmp.interfaces.StatelessSessionProxy.invoke( |Stateless |SessionProxy.java:123) | | at $Proxy95.noop(Unknown Source) | at | |org.jboss.test.web.servlets.EJBOnStartupServlet.processRequest(EJBO |nStartupS |ervlet.java:84) | | at | |org.jboss.test.web.servlets.EJBOnStartupServlet.doGet(EJBOnStartupS |ervlet.ja |va:104) | | at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) | at | org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:289) | at | org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:526) | | at org.mortbay.http.HttpContext.handle(HttpContext.java:1132) | at org.mortbay.http.HttpContext.handle(HttpContext.java:1086) | at org.mortbay.http.HttpServer.service(HttpServer.java:723) | at org.mortbay.http.HttpConnection.service(HttpConnection.java:745) | at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:918) | at org.mortbay.http.HttpConnection.handle(HttpConnection.java:760) | at | org.mortbay.http.SocketListener.handleConnection(SocketListener.java:138) | | at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) | at org.mortbay.util.ThreadPool$JobRunner.run(ThreadPool.java:715) | at java.lang.Thread.run(Thread.java:484) | [01:10:08,597,Jetty] WARNING: GET /jbosstest/EJBOnStartupServlet | HTTP/1.1 | java.rmi.ServerException: Optimized call had serialized argument; nested | exception is: | javax.ejb.EJBException: Optimized call had serialized argument | javax.ejb.EJBException: Optimized call had serialized argument | no stack trace available | | [01:10:08,617,Jetty] ENCServlet: init | | | | | | _ | Do You Yahoo!? | Get your free @yahoo.com address at http://mail.yahoo.com | | |
Re: [JBoss-dev] RE: Test cases
On 2001.11.19 18:22:59 -0500 Jason Dillon wrote: I haven't been following this thread at all... just happened to see my name at the bottom on this one. What is the issue? The short version please =) --jason Dain has en external project (on sourceforge) in sort of an alpha state that he is using to test cmp 2 stuff. What is the best way to get these tests + external stuff in? I suggest -tag other project -build jar, including some kind of info about the checkout tag. -put copy of jar in jboss thirdparty/junitejb/junitejb/lib/junitejb.jar Is this ok? What is the best way to indicate what version (tag in this case) the external project is at? What are we doing for the other external files? thanks david jencks On Mon, 19 Nov 2001, Dain Sundstrom wrote: The other issue I have is my tests use a, yet to be completed, extension to JUnit which runs the tests on the serverside (I wrote this). This is required for testing local interfaces which by definition are not accessible remotely. Anyway, how do I go about adding the code to the build system. It is in the package net.sourceforge.junitejb.* This is on sourceforge in its most recent state? I'd add the jar into thirdparty/junitejb/junitejb/lib/junitejb.jar with a readme saying what version it is. I'd think tagging cvs when you make the jar would be a very good idea. You might want to ask Jason first. I have to update the cvs for my project. I just changed it with the cmp2 doc example code. The I'll package and post the package. I'll also tag the cvs version. If Jason is listening, do you have any comments on this? -dain ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 173 Successful tests: 139 Errors:22 Failures: 12 [time of test: 20 November 2001 5:24 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-FCS] [java.vm.name: Classic VM] [java.vm.info: green threads, nojit] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite. Its easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] RE: Test cases
Dain has en external project (on sourceforge) in sort of an alpha state that he is using to test cmp 2 stuff. What is the best way to get these tests + external stuff in? I suggest -tag other project -build jar, including some kind of info about the checkout tag. -put copy of jar in jboss thirdparty/junitejb/junitejb/lib/junitejb.jar A public release would be best, which would indicate that the source module should be tagged, though that is up to the cvs admin policy for that project. Otherwise sounds good. Is the group owner called 'junitejb'? If not then that name should be used as the vendor. Is this ok? Sure. What is the best way to indicate what version (tag in this case) the external project is at? What are we doing for the other external files? Tag the imported files with a label which indicates the version. For example the junit.jar file has a junit_3_7 tag (amoung others) which shows what version that it is: snip jason(2)reason:...thirdparty/junit/junit/libcvs status -v junit.jar === File: junit.jar Status: Up-to-date Working revision:1.1.1.1 Repository revision: 1.1.1.1 /cvsroot/jboss/thirdparty/junit/junit/lib/junit.jar,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: -kb Existing Tags: Rel_2_4_4_15(revision: 1.1.1.1) Rel_3_0_0_1 (revision: 1.1.1.1) RelMQ_1_0_0_2 (revision: 1.1.1.1) RelMQ_1_0_0_1 (revision: 1.1.1.1) RelMQ_1_0_0_0_0 (revision: 1.1.1.1) Rel_2_5_0_4 (revision: 1.1.1.1) jboss_buildmagic(branch: 1.1.1.1.4) junit_3_7 (revision: 1.1.1.1) junit (branch: 1.1.1) /snip I would suggest setting up the proper directory structre then entering the base dir (containing the lib dir and such) and doing: cvs import thirdparty/junitejb/junitejb junitejb junitejb_M_m_r Where M_m_r is the Major.minor.release or whatever the vendor (dain) descides to use as a convetion for release numbers. This will setup the correct tags. Be sure to inclde a LICENSE file as a peer to lib/ to indicate its distribution licensing too. * * * Tagging is the only way I have found with CVS to tack this version information. If someone else has an idea on how todo it better please let me know. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 188 Successful tests: 152 Errors:24 Failures: 12 [time of test: 20 November 2001 6:22 GMT] [java.version: 1.3.1] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1-b24] [java.vm.name: Java HotSpot(TM) Server VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite. Its easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: thirdparty/sun/jsr77/lib jsr77.jar
User: schaefera Date: 01/11/19 23:01:40 Modified:sun/jsr77/lib jsr77.jar Log: Adjustment of JBossMGT to the changes in JSR-77 and a first real implementation of JSR-77 (managmeent domain and single JBoss server). Revision ChangesPath 1.3 +67 -66thirdparty/sun/jsr77/lib/jsr77.jar Binary file ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/management/mejb MEJBBean.java
User: schaefera
Date: 01/11/19 23:01:40
Modified:src/main/org/jboss/management/mejb MEJBBean.java
Log:
Adjustment of JBossMGT to the changes in JSR-77 and a first real implementation
of JSR-77 (managmeent domain and single JBoss server).
Revision ChangesPath
1.2 +9 -9 jboss/src/main/org/jboss/management/mejb/MEJBBean.java
Index: MEJBBean.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/management/mejb/MEJBBean.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- MEJBBean.java 2001/11/12 04:24:18 1.1
+++ MEJBBean.java 2001/11/20 07:01:40 1.2
@@ -11,6 +11,7 @@
import javax.ejb.RemoveException;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
+import javax.management.ObjectName;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
@@ -18,7 +19,6 @@
import javax.management.j2ee.MEJBServer;
import javax.management.j2ee.Attribute;
import javax.management.j2ee.AttributeList;
-import javax.management.j2ee.J2EEObjectName;
/*
import javax.management.j2ee.;
import javax.management.j2ee.;
@@ -34,7 +34,7 @@
*
* @author a href=mailto:[EMAIL PROTECTED];Marc Fleury/a
* @author a href=mailto:[EMAIL PROTECTED];Andreas Schaefer/a
-* @version $Revision: 1.1 $
+* @version $Revision: 1.2 $
*
* @ejb:bean name=MEJB
* display-name=JBoss Management EJB (MEJB)
@@ -66,7 +66,7 @@
*
* @ejb:interface-method view-type=remote
**/
- public Object getAttribute( J2EEObjectName pName, String pAttribute )
+ public Object getAttribute( ObjectName pName, String pAttribute )
throws RemoteException
{
return null;
@@ -77,7 +77,7 @@
*
* @ejb:interface-method view-type=remote
**/
- public AttributeList getAttributes( J2EEObjectName pName, String pAttributes )
+ public AttributeList getAttributes( ObjectName pName, String pAttributes )
throws RemoteException
{
return null;
@@ -110,7 +110,7 @@
*
* @ejb:interface-method view-type=remote
**/
- public Object invoke( J2EEObjectName pName, String pOperationName, Object[]
pParams, String[] pSignature )
+ public Object invoke( ObjectName pName, String pOperationName, Object[] pParams,
String[] pSignature )
throws RemoteException
{
return null;
@@ -121,7 +121,7 @@
*
* @ejb:interface-method view-type=remote
**/
- public boolean isRegistered( J2EEObjectName pName )
+ public boolean isRegistered( ObjectName pName )
throws RemoteException
{
return false;
@@ -132,7 +132,7 @@
*
* @ejb:interface-method view-type=remote
**/
- public Set queryNames( J2EEObjectName pName )
+ public Set queryNames( ObjectName pName )
throws RemoteException
{
return null;
@@ -143,7 +143,7 @@
*
* @ejb:interface-method view-type=remote
**/
- public Attribute setAttribute( J2EEObjectName pName, Attribute pAttribute )
+ public Attribute setAttribute( ObjectName pName, Attribute pAttribute )
throws RemoteException
{
return null;
@@ -154,7 +154,7 @@
*
* @ejb:interface-method view-type=remote
**/
- public AttributeList setAttributes( J2EEObjectName pName, AttributeList
pAttributes )
+ public AttributeList setAttributes( ObjectName pName, AttributeList pAttributes )
throws RemoteException
{
return null;
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/management/j2ee InvalidParentException.java J2EEApplicationMBean.java J2EEManagedObjectMBean.java J2EEManagement.java J2EEManagementMBean.java J2EEServer.java J2EEServerMBean.java SingleJBossServerManagement.java WrapperException.java ConnectorModule.java EjbModule.java EntityBean.java IpAddress.java J2EEApplication.java J2EEDeployedObject.java J2EEManagedObject.java J2EEModule.java J2EEResource.java JDBC.java JDBCConnection.java JDBCConnectionPool.java JDBCDataSource.java JNDI.java JVM.java JavaMail.java MessageDrivenBean.java Node.java Port.java StatefulSessionBean.java StatelessSessionBean.java WebModule.java
User: schaefera
Date: 01/11/19 23:01:39
Modified:src/main/org/jboss/management/j2ee ConnectorModule.java
EjbModule.java EntityBean.java IpAddress.java
J2EEApplication.java J2EEDeployedObject.java
J2EEManagedObject.java J2EEModule.java
J2EEResource.java JDBC.java JDBCConnection.java
JDBCConnectionPool.java JDBCDataSource.java
JNDI.java JVM.java JavaMail.java
MessageDrivenBean.java Node.java Port.java
StatefulSessionBean.java StatelessSessionBean.java
WebModule.java
Added: src/main/org/jboss/management/j2ee
InvalidParentException.java
J2EEApplicationMBean.java
J2EEManagedObjectMBean.java J2EEManagement.java
J2EEManagementMBean.java J2EEServer.java
J2EEServerMBean.java
SingleJBossServerManagement.java
WrapperException.java
Log:
Adjustment of JBossMGT to the changes in JSR-77 and a first real implementation
of JSR-77 (managmeent domain and single JBoss server).
Revision ChangesPath
1.2 +12 -3 jboss/src/main/org/jboss/management/j2ee/ConnectorModule.java
Index: ConnectorModule.java
===
RCS file:
/cvsroot/jboss/jboss/src/main/org/jboss/management/j2ee/ConnectorModule.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ConnectorModule.java 2001/08/09 06:30:58 1.1
+++ ConnectorModule.java 2001/11/20 07:01:39 1.2
@@ -10,6 +10,9 @@
import java.util.ArrayList;
import java.util.List;
+import javax.management.MalformedObjectNameException;
+import javax.management.ObjectName;
+
import javax.management.j2ee.J2EEApplication;
import javax.management.j2ee.J2EEServer;
import javax.management.j2ee.JVM;
@@ -22,7 +25,7 @@
* JBoss specific implementation.
*
* @author a href=mailto:[EMAIL PROTECTED];Marc Fleury/a
-* @version $Revision: 1.1 $
+* @version $Revision: 1.2 $
*/
public class ConnectorModule
extends J2EEModule
@@ -46,12 +49,18 @@
*
* @throws InvalidParameterException If the given Name is null
**/
- public ConnectorModule( String pName, String pDeploymentDescriptor,
J2EEApplication[] pApplications, J2EEServer[] pServer, JVM pJVM, ResourceAdapter[]
pAdapters ) {
- super( pName, pDeploymentDescriptor, pApplications, pServer, pJVM );
+ public ConnectorModule( String pName, ObjectName pApplication, String
pDeploymentDescriptor )
+ throws
+ MalformedObjectNameException,
+ InvalidParentException
+ {
+ super( ConnectorModule, pName, pApplication, pDeploymentDescriptor );
+/*
if( pAdapters == null || pAdapters.length == 0 ) {
throw new InvalidParameterException( Resource Adapters may not be null or
empty );
}
mResourceAdapters = new ArrayList( Arrays.asList( pAdapters ) );
+*/
}
// -
1.2 +12 -3 jboss/src/main/org/jboss/management/j2ee/EjbModule.java
Index: EjbModule.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/management/j2ee/EjbModule.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- EjbModule.java2001/08/09 06:30:58 1.1
+++ EjbModule.java2001/11/20 07:01:39 1.2
@@ -10,6 +10,9 @@
import java.util.ArrayList;
import java.util.List;
+import javax.management.MalformedObjectNameException;
+import javax.management.ObjectName;
+
import javax.management.j2ee.EJB;
import javax.management.j2ee.J2EEApplication;
import javax.management.j2ee.J2EEServer;
@@ -22,7 +25,7 @@
* JBoss specific implementation.
*
* @author a href=mailto:[EMAIL PROTECTED];Marc Fleury/a
-* @version $Revision: 1.1 $
+* @version $Revision: 1.2 $
*/
public class EjbModule
extends J2EEModule
@@ -46,12 +49,18 @@
*
* @throws InvalidParameterException If the given Name is null
**/
- public EjbModule( String pName, String pDeploymentDescriptor, J2EEApplication[]
pApplications, J2EEServer[] pServer, JVM pJVM, EJB[] pEJBs ) {
- super( pName, pDeploymentDescriptor, pApplications, pServer, pJVM );
+ public EjbModule( String pName, ObjectName pApplication, String
pDeploymentDescriptor )
+ throws
+ MalformedObjectNameException,
+ InvalidParentException
+ {
+ super( EjbModule, pName, pApplication, pDeploymentDescriptor );
+/*
if( pEJBs == null || pEJBs.length == 0 ) {
[JBoss-dev] request for jboss description blurb
I was wondering if there was a short and sweet, 3-5 line, by 80 char, description of jboss? I can find things longer, but nothing that describes it in short and simple terms. I need just such a description for making jboss debs. I thought who better to ask, than those who write it. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
I haven't dug around in the source yet. If you can give me a pointer where to look, I'll check it out... If I remove DefaultDS (remove the Hypersonic service XML file), my beans don't deploy at all, complaining that DefaultDS is missing... So it's definitely not picking up my request for a different datasource to be used. Hunter From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 15:40:42 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Looks right to me. Did you try tracking this down in the source? I'll look at it later but I'm a little busy right now. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 1:48 PM To: JBoss Dev Subject: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I am deploying a 2.0EJB jar into RH3. Here's my jbosscmp-jdbc.xml file: ?xml version=1.0 encoding=UTF-8? !DOCTYPE jbosscmp-jdbc jbosscmp-jdbc defaults datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-key/preferred-relation-mapping /defaults /jbosscmp-jdbc No matter what, the jar tries to run against DefaultDS when I want it to run against 'Groundswell' as the datasource. What am I doing wrong? Hunter ___ 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] Rabbit Hole with PostgreSQL
I am starting to test my app on RH/3.0alpha so I need to get it running against Postgres 7.1. It looks like the config for datasources has changed/moved quite a bit. What files do I need to generate and where do I need to put them to get Rabbit Hole running against PostgreSQL? ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Rabbit Hole with PostgreSQL
Here is my postgresql-default-service.xml that is in the deploy directory Hunter Hillegas wrote: I am starting to test my app on RH/3.0alpha so I need to get it running against Postgres 7.1. It looks like the config for datasources has changed/moved quite a bit. What files do I need to generate and where do I need to put them to get Rabbit Hole running against PostgreSQL? ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ?xml version=1.0 encoding=UTF-8? server classpath archives=postgresql.jar/ mbean code=org.jboss.resource.ConnectionFactoryLoader name=JBOSS-SYSTEM:service=ConnectionFactoryLoader,name=DefaultDS attribute name=ManagedConnectionFactoryProperties ConnectionURL=jdbc:postgresql://localhost/Import DriverClass=org.postgresql.Driver UserName=dave Password= /attribute attribute name=JndiNameDefaultDS/attribute attribute name=TransactionManagerNamejava:/TransactionManager/attribute mbean-ref name=ResourceAdapterNameJCA:service=RARDeployment,name=Minerva JDBC LocalTransaction ResourceAdapter/mbean-ref mbean-ref name=ConnectionManagerFactoryLoaderNameJCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFactory/mbean-ref attribute name=ConnectionManagerProperties InvalidateOnError=false Blocking=true IdleTimeoutMillis=180 MaxSize=10 TimestampUsed=false IdleTimeoutEnabled=false GCIntervalMillis=12 MinSize=0 GCMinIdleMillis=120 GCEnabled=false MaxIdleTimeoutPercent=1.0 /attribute attribute name=PrincipalMappingClass org.jboss.resource.security.ManyToOnePrincipalMapping /attribute attribute name=PrincipalMappingProperties UserName=dave /attribute /mbean /server
Re: [JBoss-dev] Rabbit Hole with PostgreSQL
Here is a sample. Have fun - Andy - Original Message - From: Hunter Hillegas [EMAIL PROTECTED] To: JBoss Dev [EMAIL PROTECTED] Sent: Monday, November 19, 2001 10:18 AM Subject: [JBoss-dev] Rabbit Hole with PostgreSQL I am starting to test my app on RH/3.0alpha so I need to get it running against Postgres 7.1. It looks like the config for datasources has changed/moved quite a bit. What files do I need to generate and where do I need to put them to get Rabbit Hole running against PostgreSQL? ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ?xml version=1.0 encoding=UTF-8? !-- = -- !-- -- !-- foo App DataSource -- !-- -- !-- = -- !-- $Id: foo-postgres-service.xml,v 1.0 2001/09/20 20:00:05 icoloma Exp $ -- server dependsJBOSS-SYSTEM:service=Naming/depends dependsJBOSS-SYSTEM:service=TransactionManager/depends classpath archives= jdbc7.0-1.2.jar, jbosscx.sar/ !-- -- !-- JDBC - Initialize the databases -- !-- to ConnectionFactoryLoader -- !-- -- mbean code=org.jboss.resource.ConnectionFactoryLoader name=DefaultDomain:service=ConnectionFactoryLoader,name=FooPostgresDS attribute name=ManagedConnectionFactoryPropertiesConnectionURL=jdbc:postgresql://192.168.0.4:5432/foo DriverClass=org.postgresql.Driver UserName=postgres Password=postgres/attribute attribute name=JndiNameFooPostgresDS/attribute attribute name=TransactionManagerNamejava:/TransactionManager/attribute attribute name=ResourceAdapterNameMinerva JDBC LocalTransaction ResourceAdapter/attribute attribute name=RARDeployerNameJCA:service=RARDeployer/attribute attribute name=ConnectionManagerFactoryNameMinervaSharedLocalCMFactory/attribute attribute name=ConnectionManagerProperties# #Wed Aug 15 16:17:29 EDT 2001 InvalidateOnError=false BlockingTimeoutMillis=50 IdleTimeoutMillis=180 MaxSize=10 TimestampUsed=false IdleTimeoutEnabled=false CleanupIntervalMillis=12 MinSize=0 GCMinIdleMillis=120 GCEnabled=false MaxIdleTimeoutPercent=1.0 /attribute attribute name=PrincipalMappingClass org.jboss.resource.security.ManyToOnePrincipalMapping /attribute attribute name=PrincipalMappingPropertiesUserName=/attribute /mbean /server
[JBoss-dev] 2.0 jar Really Likes DefaultDS?
I am deploying a 2.0EJB jar into RH3. Here's my jbosscmp-jdbc.xml file: ?xml version=1.0 encoding=UTF-8? !DOCTYPE jbosscmp-jdbc jbosscmp-jdbc defaults datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-key/preferred-relation-mapping /defaults /jbosscmp-jdbc No matter what, the jar tries to run against DefaultDS when I want it to run against 'Groundswell' as the datasource. What am I doing wrong? Hunter ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
Looks right to me. Did you try tracking this down in the source? I'll look at it later but I'm a little busy right now. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 1:48 PM To: JBoss Dev Subject: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I am deploying a 2.0EJB jar into RH3. Here's my jbosscmp-jdbc.xml file: ?xml version=1.0 encoding=UTF-8? !DOCTYPE jbosscmp-jdbc jbosscmp-jdbc defaults datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-key/preferred-relation-mapping /defaults /jbosscmp-jdbc No matter what, the jar tries to run against DefaultDS when I want it to run against 'Groundswell' as the datasource. What am I doing wrong? Hunter ___ 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] 2.0 jar Really Likes DefaultDS?
Jaws.xml is used in 2.0 persistence? From: Andreas Schaefer [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 13:53:59 -0800 To: Hunter Hillegas [EMAIL PROTECTED] Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Hi I am not quite sure with 2.0 but check jaws.xml file therefore you should have the datasource specified. Andy - Original Message - From: Hunter Hillegas [EMAIL PROTECTED] To: Dain Sundstrom [EMAIL PROTECTED]; JBoss Dev [EMAIL PROTECTED] Sent: Monday, November 19, 2001 1:50 PM Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I haven't dug around in the source yet. If you can give me a pointer where to look, I'll check it out... If I remove DefaultDS (remove the Hypersonic service XML file), my beans don't deploy at all, complaining that DefaultDS is missing... So it's definitely not picking up my request for a different datasource to be used. Hunter From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 15:40:42 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Looks right to me. Did you try tracking this down in the source? I'll look at it later but I'm a little busy right now. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 1:48 PM To: JBoss Dev Subject: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I am deploying a 2.0EJB jar into RH3. Here's my jbosscmp-jdbc.xml file: ?xml version=1.0 encoding=UTF-8? !DOCTYPE jbosscmp-jdbc jbosscmp-jdbc defaults datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-key/preferred-relation-mapping /defaults /jbosscmp-jdbc No matter what, the jar tries to run against DefaultDS when I want it to run against 'Groundswell' as the datasource. What am I doing wrong? Hunter ___ 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] 2.0 jar Really Likes DefaultDS?
The ds jndi name is loaded in the metadata object of entities in the ...plulgin.cmp.jdbc.metadata package. Then the ds is looked up in the JDBCStoreManager init method. Finally it is used in the JDBCCommand object. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 3:50 PM To: Dain Sundstrom; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I haven't dug around in the source yet. If you can give me a pointer where to look, I'll check it out... If I remove DefaultDS (remove the Hypersonic service XML file), my beans don't deploy at all, complaining that DefaultDS is missing... So it's definitely not picking up my request for a different datasource to be used. Hunter From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 15:40:42 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Looks right to me. Did you try tracking this down in the source? I'll look at it later but I'm a little busy right now. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 1:48 PM To: JBoss Dev Subject: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I am deploying a 2.0EJB jar into RH3. Here's my jbosscmp-jdbc.xml file: ?xml version=1.0 encoding=UTF-8? !DOCTYPE jbosscmp-jdbc jbosscmp-jdbc defaults datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-key/preferred-relation-mapping /defaults /jbosscmp-jdbc No matter what, the jar tries to run against DefaultDS when I want it to run against 'Groundswell' as the datasource. What am I doing wrong? Hunter ___ 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] 2.0 jar Really Likes DefaultDS?
In your postgresql-default-service.xml what do you have as the JnDIname and the name of the Mbean? Hunter Hillegas wrote: I am deploying a 2.0EJB jar into RH3. Here's my jbosscmp-jdbc.xml file: ?xml version=1.0 encoding=UTF-8? !DOCTYPE jbosscmp-jdbc jbosscmp-jdbc defaults datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-key/preferred-relation-mapping /defaults /jbosscmp-jdbc No matter what, the jar tries to run against DefaultDS when I want it to run against 'Groundswell' as the datasource. What am I doing wrong? Hunter ___ 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] 2.0 jar Really Likes DefaultDS?
No. -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 3:57 PM To: JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Jaws.xml is used in 2.0 persistence? From: Andreas Schaefer [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 13:53:59 -0800 To: Hunter Hillegas [EMAIL PROTECTED] Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Hi I am not quite sure with 2.0 but check jaws.xml file therefore you should have the datasource specified. Andy - Original Message - From: Hunter Hillegas [EMAIL PROTECTED] To: Dain Sundstrom [EMAIL PROTECTED]; JBoss Dev [EMAIL PROTECTED] Sent: Monday, November 19, 2001 1:50 PM Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I haven't dug around in the source yet. If you can give me a pointer where to look, I'll check it out... If I remove DefaultDS (remove the Hypersonic service XML file), my beans don't deploy at all, complaining that DefaultDS is missing... So it's definitely not picking up my request for a different datasource to be used. Hunter From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 15:40:42 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Looks right to me. Did you try tracking this down in the source? I'll look at it later but I'm a little busy right now. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 1:48 PM To: JBoss Dev Subject: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I am deploying a 2.0EJB jar into RH3. Here's my jbosscmp-jdbc.xml file: ?xml version=1.0 encoding=UTF-8? !DOCTYPE jbosscmp-jdbc jbosscmp-jdbc defaults datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-key/preferred-relation-mapping /defaults /jbosscmp-jdbc No matter what, the jar tries to run against DefaultDS when I want it to run against 'Groundswell' as the datasource. What am I doing wrong? Hunter ___ 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-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS?
Groundswell From: Dave Smith [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 17:21:54 -0500 To: Hunter Hillegas [EMAIL PROTECTED] Cc: JBoss Dev [EMAIL PROTECTED] Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? In your postgresql-default-service.xml what do you have as the JnDIname and the name of the Mbean? Hunter Hillegas wrote: I am deploying a 2.0EJB jar into RH3. Here's my jbosscmp-jdbc.xml file: ?xml version=1.0 encoding=UTF-8? !DOCTYPE jbosscmp-jdbc jbosscmp-jdbc defaults datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-key/preferred-relation-mapping /defaults /jbosscmp-jdbc No matter what, the jar tries to run against DefaultDS when I want it to run against 'Groundswell' as the datasource. What am I doing wrong? Hunter ___ 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] 2.0 jar Really Likes DefaultDS?
So far nothing from this end. If you get a chance to look at or if anyone else has any ideas, please chime in? Is no one else running Rabbit Hole with PostgreSQL and 2.0 EJB? From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 16:14:21 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], Dain Sundstrom [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? The ds jndi name is loaded in the metadata object of entities in the ...plulgin.cmp.jdbc.metadata package. Then the ds is looked up in the JDBCStoreManager init method. Finally it is used in the JDBCCommand object. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 3:50 PM To: Dain Sundstrom; JBoss Dev Subject: Re: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I haven't dug around in the source yet. If you can give me a pointer where to look, I'll check it out... If I remove DefaultDS (remove the Hypersonic service XML file), my beans don't deploy at all, complaining that DefaultDS is missing... So it's definitely not picking up my request for a different datasource to be used. Hunter From: Dain Sundstrom [EMAIL PROTECTED] Date: Mon, 19 Nov 2001 15:40:42 -0600 To: 'Hunter Hillegas' [EMAIL PROTECTED], JBoss Dev [EMAIL PROTECTED] Subject: RE: [JBoss-dev] 2.0 jar Really Likes DefaultDS? Looks right to me. Did you try tracking this down in the source? I'll look at it later but I'm a little busy right now. -dain -Original Message- From: Hunter Hillegas [mailto:[EMAIL PROTECTED]] Sent: Monday, November 19, 2001 1:48 PM To: JBoss Dev Subject: [JBoss-dev] 2.0 jar Really Likes DefaultDS? I am deploying a 2.0EJB jar into RH3. Here's my jbosscmp-jdbc.xml file: ?xml version=1.0 encoding=UTF-8? !DOCTYPE jbosscmp-jdbc jbosscmp-jdbc defaults datasourcejava:/Groundswell/datasource type-mappingPostgreSQL/type-mapping debugtrue/debug create-tabletrue/create-table remove-tablefalse/remove-table read-onlyfalse/read-only time-out300/time-out select-for-updatefalse/select-for-update preferred-relation-mappingforeign-key/preferred-relation-mapping /defaults /jbosscmp-jdbc No matter what, the jar tries to run against DefaultDS when I want it to run against 'Groundswell' as the datasource. What am I doing wrong? Hunter ___ 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
