[JBoss-dev] deploying testsuite into jboss
I was just reading about some extentions to junit on junit.org and now think that it would be a good idea to deploy the entire testsuite into jboss, then start it up via jmx or html. This would make it really easy to take a set of distributed tests, and give each node in the network a part of the test to run. For us, we will eventually want to run a night test on how 2 or more JBoss servers interact with each other. Each of these types of testsuites could be given a set of .ear's which would be deployed on to a running jboss. Currently we only have one testsuite, but we will probably end up with a few more. o One that is quick to run, covers the basics o One that can take hours which will be run overnight, o One that can take hours and requires 2 or more jvms which will be run overnight too. The last two could be condensed into just the later or not. Who knows. Any ways, the concept just started making sence today, so I thought I would share. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/etc/conf/boot-server jboss-service.xml jetty.properties jetty.xml log4j.properties webdefault.xml
User: chirino Date: 01/08/30 21:26:39 Added: src/etc/conf/boot-server jboss-service.xml jetty.properties jetty.xml log4j.properties webdefault.xml Log: Ceating a configuration which starts jetty configured to web server the current distribution off the http://localhost:8090 address. Good for testing the new 'run --net-install' option Revision ChangesPath 1.1 jboss/src/etc/conf/boot-server/jboss-service.xml Index: jboss-service.xml === ?xml version=1.0 encoding=UTF-8? !-- = -- !-- -- !-- JBoss Server Configuration -- !-- -- !-- = -- !-- $Id: jboss-service.xml,v 1.1 2001/08/31 04:26:39 chirino Exp $ -- !-- | This is where you can add and configure your MBeans. | | *ATTENTION* | | The order of the listing here is the same order as | the MBeans are loaded. Therefore if a MBean depends on another | MBean to be loaded and started it has to be listed after all | the MBeans it depends on. -- server !-- The Classpath element is needed for http based installations we need to list all the archives that the server needs at boot if the installation is local and the configuration is from file then there is no need to list the files and it should commented -- classpath archives= castor.jar, castor-jdo-plugin.jar, com.mortbay.ftp.jar, com.mortbay.jetty.jar, com.mortbay.jetty.jmx.jar, com.mortbay.jetty.sasl.jar, com.mortbay.tools.jar, concurrent.jar, crimson.jar, cryptix-sasl-jetty.jar, gnu-regexp.jar, hsql.jar, hsql-plugin.jar, jaas.jar, JavaGroups.jar, javax-sasl.jar, jaxp.jar, jbosscx.jar, jbossha.jar, jboss-j2ee.jar, jboss.jar, jbossmq.jar, jbossmx.jar, jbosspool.jar, jbosssx.jar, jcert.jar, javax.servlet.jar, jetty-plugin.jar, jmxtools.jar, jndi.jar, jnet.jar, jnpserver.jar, jpl-pattern.jar, jpl-util.jar, jsr77.jar, jsse.jar, jts.jar, mail.jar, org.apache.jasper.jar, tyrex.jar, tyrex-tm-plugin.jar, xalan.jar/ !-- -- !-- Web Container-- !-- -- mbean code=org.jboss.jetty.JettyService name=:service=Jetty attribute name=JettyHome..//attribute attribute name=Configuration../conf/boot-server/jetty.xml/attribute attribute name=WebDefault../conf/boot-server/webdefault.xml/attribute attribute name=UnpackWarstrue/attribute attribute name=PublishMBeanstrue/attribute /mbean /server 1.1 jboss/src/etc/conf/boot-server/jetty.properties Index: jetty.properties === ### == ### ## ## ## Jetty Properties## ## ## ### == ### ### $Id: jetty.properties,v 1.1 2001/08/31 04:26:39 chirino Exp $ ### # Use sun's parser org.xml.sax.parser=com.sun.xml.parser.Parser 1.1 jboss/src/etc/conf/boot-server/jetty.xml Index: jetty.xml === ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE Configure PUBLIC -//Mort Bay Consulting//DTD Configure 1.1//EN http://jetty.mortbay.com/configure_1_1.dtd; Configure class=com.mortbay.HTTP.HttpServer Call name=addListener Arg New class=com.mortbay.HTTP.SocketListener Set name=Port8090/Set Set name=MinThreads1/Set Set name=MaxThreads25/Set Set name=MaxIdleTimeMs6/Set Set name=MaxReadTimeMs6/Set /New /Arg /Call !-- Uncomment this to add an SSL listener. Call name=addListener Arg New
Re: [JBoss-dev] EJB 2.0 CMP
Dain Sundstrom wrote:
Dave,
After reviewing these comments I think we are making this way more
complicated than it has to be. As far as I am concerned we should only
need the relationship stuff in jbosscmp-jdbc.xml for relationships that
use a relation table (ex. self relation employee/manager, just to
control the name and fields ) or for primary keys that are composite.
Relax. The only reason you need the jbosscmp-jdbc.xml file is that you are
tiring to exactly specify the foreign key field. If you just let the system
define the foreign key field for you, you would not have any problems. I
have a test case that closely matches what you have coded except my case
uses a general oid for the line item and the order fk is auto generated.
Ahh... lights on.
Is this how the majority of end users are going to use this? It would
seem within a larger shop the people doing the data modeling are not the
people building the J2EE apps. I would think that the data modeling or
db's would say here are the tables build your objects. I know it's not
*object oriented* but we should code for the masses.
Time Passes
So let me understand the order case above. Would the database schemas
look like this?
create table order (
objectid int default nextval('some sequence') primary key,
other fields ...
);
create table order_detail (
objectid int default nextval('some sequence') primary key,
order_oid int references order,
line_numint
other fields ...
);
Still having a hard time why you have to auto generate fk fields for
this case. It would seem this is what a dba would give you ... and if
the order/order_detail objects had all of the fields above nothing to
generate?
I think that your code is handling all of the difficult cases and is
ramming the easy ones into it. We really should have a waterfall type
style where we assume that it is the simple case and then have the
program add what's missing or have the user define it.
We should avoid creating tables if all possible. I would see only 3
cases where you need a third table
Many to Many
1 to Many (unidirectional. I can not come up with an example but it
would be valid)
Self referencing entry
A relation table is only required for a many-to-many relationship. A
unidirectional many-to-one relationship can always use foreign keys. The
trick is that the database mapping of the relationship does not have to
match the object level navigability. A self-referencing entity can also use
a foreign key to itself.
Time passes ...
I'm am really trying hard to not have to use this jboss-jdbc.xml ... For
composite foreign keys would could also the jdbc method
getImportedKeys() to figure out composite keys. This would mean the jdbc
driver would have to support the DatabaseMetaData method and the dba
would have to use the references in their table definition. We could
always fall back to the xml file if it did not exsist. So with a good
jdbc driver we really would only have to create an xml entry if we had a
specfic relation table we had already predefined.
This is a good idea but, would only work if there were only a single
relationship between the two entities. The problem is that it is very
common for entities to have multiple relationships. For example, order has
a shipping address and a billing address.
So what. There are two foriegn keys on a table. Could be hundreds ..
still do not see the problem. Let me check out getImportedKeys , I'll
get back to you ..
Maybe I'm foaming at the mouth, but I feel this is a HUGE feature for
people writing business apps and it should be as simple as possible. I
really think this could be simpler for the developers and users.
I agree. It think the configuration is very complicated. I was thinking of
writing a took that could generate the jbosscmp-jdbc.xml file based on the
system defaults. Then the user could modify the default configuration. This
utility could also read in the current config and fill in the unspecified
options. Something like this or a gui could make configuration very easy.
Have I missed something? Do you have a counter point or suggestion?
As a side note, I am happy to see someone challenging my design decisions.
I have been known to be full of it (and my self). Please keep the criticism
up, and don't worry about ticking me off (it takes a lot).
Thanks a lot,
-dain
I think a database schema of your case would help my understanding. I still believe
there is overkill for the simple cases
which will be the majority of cases. This is something that many
business aps will use and I in my day have written tons of this
collection handling shit and it would be nice to get it right once and
for all.
Writting is not my strong point , so I'm not trying to be cruft just
trying to make JBOSS better. Tear in my eye ... beatles songs running
[JBoss-dev] CVS update: jboss/src/build build.xml
User: chirino
Date: 01/08/30 22:38:58
Modified:src/build Tag: Branch_2_4 build.xml
Log:
The zip distribution was not creating the db/jbossmq directory because it was empty.
We now add a text file to directory so that it is not empty
Revision ChangesPath
No revision
No revision
1.77.2.5 +1 -0 jboss/src/build/Attic/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jboss/src/build/Attic/build.xml,v
retrieving revision 1.77.2.4
retrieving revision 1.77.2.5
diff -u -r1.77.2.4 -r1.77.2.5
--- build.xml 2001/08/21 01:33:41 1.77.2.4
+++ build.xml 2001/08/31 05:38:58 1.77.2.5
@@ -294,6 +294,7 @@
copy file=${etc.dir}/deploy.txt tofile=${dist.dir}/deploy/deploy.txt/
copy file=${etc.dir}/hypersonic.txt
tofile=${dist.dir}/db/hypersonic/hypersonic.txt/
+ copy file=${etc.dir}/jbossmq.txt
tofile=${dist.dir}/db/jbossmq/jbossmq.txt/
copy file=${lib.dir}/jmxri.jar tofile=${dist.dir}/lib/jmxri.jar/
copy file=${etc.dir}/log.properties
tofile=${dist.dir}/log/log.properties/
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/etc jbossmq.txt
User: chirino Date: 01/08/30 22:38:59 Added: src/etc Tag: Branch_2_4 jbossmq.txt Log: The zip distribution was not creating the db/jbossmq directory because it was empty. We now add a text file to directory so that it is not empty Revision ChangesPath No revision No revision 1.1.2.1 +1 -0 jboss/src/etc/Attic/jbossmq.txt ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/etc/conf/boot-server - New directory
User: chirino Date: 01/08/30 21:23:16 jboss/src/etc/conf/boot-server - New directory ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss daily test failed
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
Searching for build.xml ...
Buildfile: /home/lubega/jbossro/jboss-all/build/build.xml
init-buildlog:
init:
[echo] user.home = /home/lubega
[echo] build.compiler = ${build.compiler}
[echo] java.home = /opt/jdk1.3_ibm_20010723/jre
[echo] java.class.path =
/home/lubega/jbossro/jboss-all/tools/lib/xerces.jar:/home/lubega/jbossro/jboss-all/tools/lib/xalan.jar:/home/lubega/jbossro/jboss-all/tools/lib/stylebook.jar:/home/lubega/jbossro/jboss-all/tools/lib/saxon.jar:/home/lubega/jbossro/jboss-all/tools/lib/pretty.jar:/home/lubega/jbossro/jboss-all/tools/lib/optional.jar:/home/lubega/jbossro/jboss-all/tools/lib/junit.jar:/home/lubega/jbossro/jboss-all/tools/lib/jaxp.jar:/home/lubega/jbossro/jboss-all/tools/lib/JavaStyle.jar:/home/lubega/jbossro/jboss-all/tools/lib/javac.jar:/home/lubega/jbossro/jboss-all/tools/lib/fop.jar:/home/lubega/jbossro/jboss-all/tools/lib/ejbdoclet.jar:/home/lubega/jbossro/jboss-all/tools/lib/crimson.jar:/home/lubega/jbossro/jboss-all/tools/lib/buildmagic-tasks.jar:/home/lubega/jbossro/jboss-all/tools/lib/bsf.jar:/home/lubega/jbossro/jboss-all/tools/lib/batik.jar:/home/lubega/jbossro/jboss-all/tools/lib/ant.jar:/opt/jdk1.3_ibm_20010723/lib/tools.jar
[echo] java.version = 1.3.0
[echo] java.vendor = IBM Corporation
[echo] java.vm.version = 1.3.0
[echo] java.vm.name = Classic VM
[echo] java.vm.info = J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)
[echo] os.name = Linux
[echo] os.arch = Linux
[echo] os.version = Linux
[echo]
configure:
[projectinfo] Project root: /home/lubega/jbossro/jboss-all
[projectinfo] Modules:
j2ee,naming,server,security,messaging,connector,pool,cluster,admin,testsuite,plugins/varia,plugins/jetty
run-testsuite:
[execmodules]
==
== Executing 'tests' in module 'testsuite'...
==
init-buildlog:
init:
[moduleinfo] Project root: /home/lubega/jbossro/jboss-all
[moduleinfo] Module root: /home/lubega/jbossro/jboss-all/testsuite
compile-classes:
[mkdir] Created dir: /home/lubega/jbossro/jboss-all/testsuite/output/classes
[javac] Compiling 274 source files to
/home/lubega/jbossro/jboss-all/testsuite/output/classes
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:8:
cannot resolve symbol
[execmodules] symbol : class Identifier
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.Identifier;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:9:
cannot resolve symbol
[execmodules] symbol : class Operator
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.Operator;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:10:
cannot resolve symbol
[execmodules] symbol : class SelectorParser
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.SelectorParser;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:11:
cannot resolve symbol
[execmodules] symbol : class ISelectorParser
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.ISelectorParser;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:21:
cannot resolve symbol
[execmodules] symbol : class ISelectorParser
[execmodules] location: class org.jboss.test.jbossmq.test.TestSelectorParser
[execmodules] static ISelectorParser parser;
[execmodules]^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:140:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert(!clct.isEmpty());
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:148:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert(bean.getPersonsName().trim().equals(BEAN_NAME));
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:270:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert( this.gotRefOkay(bean, BEAN_NAME) );
[execmodules] ^
[execmodules]
[JBoss-dev] [ jboss-Bugs-457149 ] ant for example cmp does not work
Bugs item #457149, was opened at 2001-08-31 01:47
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=457149group_id=22866
Category: JBossDoc
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: ant for example cmp does not work
Initial Comment:
the problem come up with the version i downloaded
today document-examples.tar.gz from 2001-aug-30
the ant-script for the client part of cmp example does
not work, since the variable ${client} is nowhere set.
i changed the ant-script as follows to make it
running: (basically i added some prperty name=client
value=blabla/
)
olaf
!--
***
--
!-- Chapter 4 - CMP --
target name=cmp-cd-compile depends=init
ant
antfile=org/jboss/docs/cmp/cd/build/build-cmp-cd-
compile.xml target=main /
/target
target name=cmp-cd-dist depends=cmp-cd-
compile
!-- Nothing special here --
/target
target name=cmp-cd-list depends=init
property name=client value=List/
ant
antfile=org/jboss/docs/cmp/cd/build/build-client.xml
target=main /
/target
target name=cmp-cd-upload depends=init
property name=client value=Upload/
ant
antfile=org/jboss/docs/cmp/cd/build/build-client.xml
target=main /
/target
target name=cmp-cd-remove depends=init
property name=client value=Remove/
ant
antfile=org/jboss/docs/cmp/cd/build/build-client.xml
target=main /
/target
--
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376685aid=457149group_id=22866
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Rabbit hole
SUN is a dead company, head is in the clouds but the emperor is naked. Naked? What does that say about Java? --jason ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite build.xml
User: user57
Date: 01/08/30 22:30:31
Modified:.build.xml
Log:
o finished initial module level work to automate the website build via
ant/buildmagic.
! still needs project control, to pull files to release.
Revision ChangesPath
1.2 +68 -28newsite/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/newsite/build.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- build.xml 2001/08/30 22:34:32 1.1
+++ build.xml 2001/08/31 05:30:31 1.2
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.1 2001/08/30 22:34:32 user57 Exp $ --
+!-- $Id: build.xml,v 1.2 2001/08/31 05:30:31 user57 Exp $ --
project default=main name=JBoss/Website
@@ -145,6 +145,7 @@
!-- Where build generated files will go --
property name=build.metadata value=${module.build}/metadata/
+ property name=build.snapshots value=${module.build}/snapshots/
property name=build.docs value=${module.build}/docs/
property name=build.xdocs value=${module.build}/xdocs/
property name=build.stylesheets value=${module.build}/stylesheets/
@@ -191,9 +192,19 @@
| different type of compile that needs to be performed, short of
| documentation compiles.
--
- target name=compile depends=init, compile-docs, compile-metadata
+ target name=compile depends=init, compile-docs, compile-metadata,
compile-snapshots
description=Compile all source files./
+ !-- Compile doc sources support files --
+ target name=compile-docs depends=init
+mkdir dir=${build.docs}/
+copy todir=${build.docs} filtering=no
+ fileset dir=${source.docs}
+ include name=**/*/
+ /fileset
+/copy
+ /target
+
!-- Compile metadata --
target name=compile-metadata depends=init
mkdir dir=${build.metadata}/
@@ -204,14 +215,23 @@
/copy
/target
- !-- Compile doc sources support files --
- target name=compile-docs depends=init
-mkdir dir=${build.docs}/
-copy todir=${build.docs} filtering=no
- fileset dir=${source.docs}
- include name=**/*/
- /fileset
-/copy
+ property name=snapshot.cvsroot
+ value=:pserver:[EMAIL PROTECTED]:/cvsroot/jboss/
+
+ property name=snapshot.modules value=jboss-all/
+
+ !-- Compile cvs source snapshots --
+ target name=compile-snapshots depends=init
+mkdir dir=${build.snapshots}/
+
+!-- Make sure there is an entry for this cvsroot --
+cvspass cvsroot=${snapshot.cvsroot} password=/
+
+cvs cvsroot=${snapshot.cvsroot}
+ command=export
+ date=TODAY
+ package=jboss-all
+ dest=${build.snapshots}/
/target
@@ -223,16 +243,47 @@
target name=jars depends=compile description=Builds all jar files.
mkdir dir=${build.jars}/
-!-- build the website wars
-war warfile=${build.jars}/manual.war
- webxml=${build.metadata}/manual-web.xml
- zipfileset prefix=HTML/fancy dir=${build.html.fancy}/
- zipfileset prefix=HTML/printable dir=${build.html.printable}/
+war warfile=${build.jars}/website.war
+ webxml=${build.metadata}/website-web.xml
+ fileset dir=${build.docs}
+include name=**/*/
+exclude name=jbossgroup/
+ /fileset
/war
---
- /target
+war warfile=${build.jars}/jbossgroup.war
+ webxml=${build.metadata}/jbossgroup-web.xml
+ fileset dir=${build.docs}/jbossgroup
+include name=**/*/
+ /fileset
+/war
+
+zip zipfile=${build.jars}/jboss-all-${build.number}.zip
+ fileset dir=${build.snapshots}/jboss-all
+include name=**/*/
+ /fileset
+/zip
+war warfile=${build.jars}/snapshots.war
+ webxml=${build.metadata}/snapshots-web.xml
+ fileset dir=${build.jars}
+include name=jboss-all-${build.number}.zip/
+ /fileset
+/war
+
+ear earfile=${build.jars}/website.ear
+ appxml=${build.metadata}/website-application.xml
+ fileset dir=${build.jars}
+include name=website.war/
+include name=jbossgroup.war/
+include name=snapshots.war/
+!-- the manual is currently added by another ear --
+ /fileset
+/ear
+
+ /target
+
+
!-- == --
!-- Build documents--
!-- == --
@@ -253,14 +304,6 @@
target name=release depends=all
description=Builds a release
[JBoss-dev] CVS update: newsite/src/metadata jbossgroup-web.xml snapshots-web.xml website-application.xml website-web.xml
User: user57 Date: 01/08/30 22:30:32 Added: src/metadata jbossgroup-web.xml snapshots-web.xml website-application.xml website-web.xml Log: o finished initial module level work to automate the website build via ant/buildmagic. ! still needs project control, to pull files to release. Revision ChangesPath 1.1 newsite/src/metadata/jbossgroup-web.xml Index: jbossgroup-web.xml === ?xml version=1.0 encoding=UTF-8? !DOCTYPE web-app !-- $Id: jbossgroup-web.xml,v 1.1 2001/08/31 05:30:32 user57 Exp $ -- web-app /web-app 1.1 newsite/src/metadata/snapshots-web.xml Index: snapshots-web.xml === ?xml version=1.0 encoding=UTF-8? !DOCTYPE web-app !-- $Id: snapshots-web.xml,v 1.1 2001/08/31 05:30:32 user57 Exp $ -- web-app /web-app 1.1 newsite/src/metadata/website-application.xml Index: website-application.xml === ?xml version=1.0 encoding=UTF-8? !DOCTYPE application !-- $Id: website-application.xml,v 1.1 2001/08/31 05:30:32 user57 Exp $ -- application display-nameJBoss Website/display-name module web web-uriwebsite.war/web-uri context-root//context-root /web /module module web web-urijbossgroup.war/web-uri context-rootJBG/context-root /web /module module web web-urisnapshots.war/web-uri context-rootzip_archives/context-root /web /module /application 1.1 newsite/src/metadata/website-web.xml Index: website-web.xml === ?xml version=1.0 encoding=UTF-8? !DOCTYPE web-app !-- $Id: website-web.xml,v 1.1 2001/08/31 05:30:32 user57 Exp $ -- web-app /web-app ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] requirements for build
Well, I downloaded and compiled the Rabbit Hole release of JBoss today. It's the first time I've built JBoss from scratch in about 6 months. At any rate, I thought I'd reflect a little on a couple of things, so that I can save people the 30 minutes I spent figuring it out. -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. Once that's done, you can cd into your_jboss_dir/build and type build. I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond. -dan -- Dan Kirkpatrick, Software Architect Blue Lotus Software+44 (0) 1224 575 985 [EMAIL PROTECTED] http://www.bluelotussoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/etc/conf/default webdefault.xml jboss-service.xml
User: chirino Date: 01/08/30 21:28:48 Modified:src/etc/conf/default jboss-service.xml Added: src/etc/conf/default webdefault.xml Log: Since the jetty plugin and jetty jars are being included in the dist, we might as well enable the jetty servlet container. Revision ChangesPath 1.3 +7 -6 jboss/src/etc/conf/default/jboss-service.xml Index: jboss-service.xml === RCS file: /cvsroot/jboss/jboss/src/etc/conf/default/jboss-service.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- jboss-service.xml 2001/08/30 20:43:04 1.2 +++ jboss-service.xml 2001/08/31 04:28:48 1.3 @@ -7,7 +7,7 @@ !-- -- !-- = -- -!-- $Id: jboss-service.xml,v 1.2 2001/08/30 20:43:04 pra Exp $ -- +!-- $Id: jboss-service.xml,v 1.3 2001/08/31 04:28:48 chirino Exp $ -- !-- | This is where you can add and configure your MBeans. @@ -48,6 +48,7 @@ hsql-plugin.jar, jaas.jar, JavaGroups.jar, + javax.servlet.jar, javax-sasl.jar, jaxp.jar, jbosscx.jar, @@ -412,15 +413,15 @@ | Besure to check that the configuration values are valid for your | environment. | + -- mbean code=org.jboss.jetty.JettyService name=:service=Jetty -attribute name=JettyHome../../jetty/attribute -attribute name=Configurationjetty.xml/attribute -attribute name=WebDefault../../jetty/etc/webdefault.xml/attribute +attribute name=JettyHome..//attribute +attribute name=Configuration../conf/default/jetty.xml/attribute +attribute name=WebDefault../conf/default/webdefault.xml/attribute attribute name=UnpackWarstrue/attribute attribute name=PublishMBeanstrue/attribute /mbean - -- !-- -- !-- JBossMQ -- @@ -695,4 +696,4 @@ !-- Add your custom MBeans here -- !-- -- -/server \ No newline at end of file +/server 1.1 jboss/src/etc/conf/default/webdefault.xml Index: webdefault.xml === !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN http://java.sun.com/j2ee/dtds/web-app_2_2.dtd; !-- This file contains the default settings for webapplications -- web-app welcome-file-list welcome-fileindex.jsp/welcome-file welcome-fileindex.html/welcome-file /welcome-file-list servlet servlet-nameJSP/servlet-name servlet-classorg.apache.jasper.servlet.JspServlet/servlet-class load-on-startup0/load-on-startup /servlet servlet-mapping servlet-nameJSP/servlet-name url-pattern*.jsp,*.jsP,*.jSp,*.jSP,*.Jsp,*.JsP,*.JSp,*.JSP/url-pattern /servlet-mapping session-config session-timeout60/session-timeout /session-config security-constraint web-resource-collection web-resource-nameRead Only/web-resource-name url-pattern//url-pattern http-methodDELETE/http-method http-methodPUT/http-method /web-resource-collection /security-constraint !-- security-role role-nameroleName/role-name /security-role -- /web-app ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] requirements for build
On Fri, 31 Aug 2001, Dan - Blue Lotus Software wrote: I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond. I didn't need to install anything... worked fine for me. -- Juha ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/pm/jdbc PersistenceManager.java MessageLog.java
User: chirino
Date: 01/08/30 21:39:08
Modified:src/main/org/jboss/mq/pm/jdbc PersistenceManager.java
MessageLog.java
Log:
This PM was trying to get JNDI to a DataSource too soon. Moved to when the PM is
started.
Still need to test.
Revision ChangesPath
1.4 +269 -301 jbossmq/src/main/org/jboss/mq/pm/jdbc/PersistenceManager.java
Index: PersistenceManager.java
===
RCS file:
/cvsroot/jboss/jbossmq/src/main/org/jboss/mq/pm/jdbc/PersistenceManager.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- PersistenceManager.java 2001/08/30 02:35:55 1.3
+++ PersistenceManager.java 2001/08/31 04:39:08 1.4
@@ -5,341 +5,309 @@
* See terms of license at gnu.org.
*/
package org.jboss.mq.pm.jdbc;
-import java.io.*;
+
+import javax.rmi.PortableRemoteObject;
+import javax.jms.JMSException;
+import javax.sql.*;
+import javax.naming.*;
+import javax.management.*;
+import javax.naming.InitialContext;
import java.net.URL;
-import java.sql.*;
import java.util.HashMap;
+import java.util.TreeSet;
import java.util.Iterator;
import java.util.LinkedList;
import java.util.Properties;
-import java.util.TreeSet;
-import javax.jms.JMSException;
-
-import javax.management.*;
-import javax.naming.*;
-
-import javax.naming.InitialContext;
-
-import javax.rmi.PortableRemoteObject;
-import javax.sql.*;
-import org.jboss.mq.ConnectionToken;
+import java.sql.*;
+import java.io.*;
+import org.jboss.util.ServiceMBeanSupport;
import org.jboss.mq.SpyDestination;
-import org.jboss.mq.SpyJMSException;
-import org.jboss.mq.SpyMessage;
-import org.jboss.mq.pm.TxManager;
+import org.jboss.mq.xml.XElement;
+import org.jboss.mq.ConnectionToken;
import org.jboss.mq.server.JMSDestination;
import org.jboss.mq.server.JMSServer;
-import org.jboss.mq.xml.XElement;
-
-import org.jboss.system.ServiceMBeanSupport;
+import org.jboss.mq.pm.TxManager;
+import org.jboss.mq.SpyMessage;
+import org.jboss.mq.SpyJMSException;
/**
* This class manages all persistence related services for file based
* persistence.
*
- * @createdAugust 16, 2001
- * @author:Jayesh Parayali ([EMAIL PROTECTED])
- * @version$Revision: 1.3 $
+ * @author: Jayesh Parayali ([EMAIL PROTECTED])
+ *
+ * @version $Revision: 1.4 $
*/
-public class PersistenceManager extends org.jboss.system.ServiceMBeanSupport
implements PersistenceManagerMBean, org.jboss.mq.pm.PersistenceManager {
+public class PersistenceManager extends org.jboss.util.ServiceMBeanSupport
implements PersistenceManagerMBean, org.jboss.mq.pm.PersistenceManager {
+
+ protected static DataSource datasource;
// Log file used to store commited transactions.
- TxLogtxLog;
+ TxLog txLog;
// Maps SpyDestinations to SpyMessageLogs
- HashMap messageLogs = new HashMap();
+ HashMap messageLogs= new HashMap();
// Maps (Long)txIds to LinkedList of AddFile tasks
- HashMap transactedTasks = new HashMap();
- TxManagertxManager;
+ HashMap transactedTasks= new HashMap();
- private String jmsDBPoolName;
-
- protected static DataSource datasource;
-
+ static class LogInfo {
+ MessageLog log;
+ SpyDestination destination;
- /**
-* Insert the method's description here. Creation date: (6/27/2001 1:07:07
-* AM)
-*
-* @param newJmsDBPoolName java.lang.String
-*/
- public void setJmsDBPoolName( java.lang.String newJmsDBPoolName ) {
- jmsDBPoolName = newJmsDBPoolName;
+ LogInfo(MessageLog log, SpyDestination destination) {
+ this.log= log;
+ this.destination= destination;
+ }
}
- /**
-* Insert the method's description here. Creation date: (6/27/2001 1:07:07
-* AM)
-*
-* @returnjava.lang.String
-*/
- public java.lang.String getJmsDBPoolName() {
- return jmsDBPoolName;
+ class Transaction {
+ private LogInfo logInfo;
+ private SpyMessage message;
+ private org.jboss.mq.pm.Tx txId;
+ private boolean add;
+ public Transaction(boolean add, LogInfo logInfo, SpyMessage message,
org.jboss.mq.pm.Tx txId) {
+ this.add= add;
+ this.logInfo= logInfo;
+ this.message= message;
+ this.txId= txId;
+ }
+ public void commit() throws JMSException {
+ if (!add)
+ logInfo.log.remove(message, txId);
+ }
+ public void rollback() throws JMSException {
+ if (add)
+ logInfo.log.remove(message, txId);
+ }
}
- public String
[JBoss-dev] jboss daily test failed
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
Searching for build.xml ...
Buildfile: /home/lubega/jbossro/jboss-all/build/build.xml
init-buildlog:
init:
[echo] user.home = /home/lubega
[echo] build.compiler = ${build.compiler}
[echo] java.home = /opt/jdk1.3.1_blackdown/jre
[echo] java.class.path =
/home/lubega/jbossro/jboss-all/tools/lib/xerces.jar:/home/lubega/jbossro/jboss-all/tools/lib/xalan.jar:/home/lubega/jbossro/jboss-all/tools/lib/stylebook.jar:/home/lubega/jbossro/jboss-all/tools/lib/saxon.jar:/home/lubega/jbossro/jboss-all/tools/lib/pretty.jar:/home/lubega/jbossro/jboss-all/tools/lib/optional.jar:/home/lubega/jbossro/jboss-all/tools/lib/junit.jar:/home/lubega/jbossro/jboss-all/tools/lib/jaxp.jar:/home/lubega/jbossro/jboss-all/tools/lib/JavaStyle.jar:/home/lubega/jbossro/jboss-all/tools/lib/javac.jar:/home/lubega/jbossro/jboss-all/tools/lib/fop.jar:/home/lubega/jbossro/jboss-all/tools/lib/ejbdoclet.jar:/home/lubega/jbossro/jboss-all/tools/lib/crimson.jar:/home/lubega/jbossro/jboss-all/tools/lib/buildmagic-tasks.jar:/home/lubega/jbossro/jboss-all/tools/lib/bsf.jar:/home/lubega/jbossro/jboss-all/tools/lib/batik.jar:/home/lubega/jbossro/jboss-all/tools/lib/ant.jar:/opt/jdk1.3.1_blackdown/lib/tools.jar
[echo] java.version = 1.3.1
[echo] java.vendor = Blackdown Java-Linux Team
[echo] java.vm.version = Blackdown-1.3.1-FCS
[echo] java.vm.name = Classic VM
[echo] java.vm.info = green threads, nojit
[echo] os.name = Linux
[echo] os.arch = Linux
[echo] os.version = Linux
[echo]
configure:
[projectinfo] Project root: /home/lubega/jbossro/jboss-all
[projectinfo] Modules:
j2ee,naming,server,security,messaging,connector,pool,cluster,admin,testsuite,plugins/varia,plugins/jetty
run-testsuite:
[execmodules]
==
== Executing 'tests' in module 'testsuite'...
==
init-buildlog:
init:
[moduleinfo] Project root: /home/lubega/jbossro/jboss-all
[moduleinfo] Module root: /home/lubega/jbossro/jboss-all/testsuite
compile-classes:
[mkdir] Created dir: /home/lubega/jbossro/jboss-all/testsuite/output/classes
[javac] Compiling 274 source files to
/home/lubega/jbossro/jboss-all/testsuite/output/classes
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:8:
cannot resolve symbol
[execmodules] symbol : class Identifier
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.Identifier;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:9:
cannot resolve symbol
[execmodules] symbol : class Operator
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.Operator;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:10:
cannot resolve symbol
[execmodules] symbol : class SelectorParser
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.SelectorParser;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:11:
cannot resolve symbol
[execmodules] symbol : class ISelectorParser
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.ISelectorParser;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:21:
cannot resolve symbol
[execmodules] symbol : class ISelectorParser
[execmodules] location: class org.jboss.test.jbossmq.test.TestSelectorParser
[execmodules] static ISelectorParser parser;
[execmodules]^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:140:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert(!clct.isEmpty());
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:148:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert(bean.getPersonsName().trim().equals(BEAN_NAME));
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:270:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert( this.gotRefOkay(bean, BEAN_NAME) );
[execmodules] ^
[execmodules]
[JBoss-dev] CVS update: manual build.xml
User: user57
Date: 01/08/30 22:30:31
Modified:.build.xml
Log:
o finished initial module level work to automate the website build via
ant/buildmagic.
! still needs project control, to pull files to release.
Revision ChangesPath
1.15 +8 -11 manual/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/manual/build.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- build.xml 2001/08/29 22:45:06 1.14
+++ build.xml 2001/08/31 05:30:31 1.15
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.14 2001/08/29 22:45:06 user57 Exp $ --
+!-- $Id: build.xml,v 1.15 2001/08/31 05:30:31 user57 Exp $ --
project default=main
@@ -197,7 +197,7 @@
| different type of compile that needs to be performed, short of
| documentation compiles.
--
- target name=compile depends=init, compile-stylesheets, compile-docs,
compile-etc
+ target name=compile depends=init, compile-stylesheets, compile-docs,
compile-metadata
description=Compile all source files./
!-- Compile stylesheets --
@@ -210,8 +210,8 @@
/copy
/target
- !-- Compile etc --
- target name=compile-etc depends=init
+ !-- Compile metadata --
+ target name=compile-metadata depends=init
mkdir dir=${build.metadata}/
copy todir=${build.metadata} filtering=yes
fileset dir=${source.metadata}
@@ -256,8 +256,8 @@
war warfile=${build.jars}/manual.war
webxml=${build.metadata}/manual-web.xml
- zipfileset prefix=HTML/fancy dir=${build.html.fancy}/
- zipfileset prefix=HTML/printable dir=${build.html.printable}/
+ zipfileset prefix=HTML dir=${build.html.fancy}/
+ zipfileset prefix=printable dir=${build.html.printable}/
/war
ear earfile=${build.jars}/manual.ear
@@ -483,14 +483,11 @@
target name=main depends=most
description=Executes the default target (most)./
- target name=all depends=docs
+ target name=all depends=jars
description=Builds everything./
- target name=most depends=docs
+ target name=most depends=jars
description=Builds almost everything./
-
- target name=min depends=compile
- description=Builds a minimal subset./
target name=tests depends=init
description=Execute all tests./
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: build/jboss build.xml
User: user57
Date: 01/08/30 22:25:55
Modified:jbossbuild.xml
Log:
o changed [EMAIL PROTECTED] to [EMAIL PROTECTED]
Revision ChangesPath
1.12 +2 -2 build/jboss/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/build/jboss/build.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- build.xml 2001/08/30 06:40:09 1.11
+++ build.xml 2001/08/31 05:25:55 1.12
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.11 2001/08/30 06:40:09 user57 Exp $ --
+!-- $Id: build.xml,v 1.12 2001/08/31 05:25:55 user57 Exp $ --
project default=main
@@ -577,7 +577,7 @@
mimemail tolist=[EMAIL PROTECTED]
subject=Automated JBoss Testsuite
message=Automated JBoss Testsuite
- from=[EMAIL PROTECTED]
+ from=[EMAIL PROTECTED]
fileset dir=${project.root}/testsuite/output/reports
include name=text/**/
/fileset
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: manual/src/metadata manual-application.xml
User: user57 Date: 01/08/30 22:30:31 Modified:src/metadata manual-application.xml Log: o finished initial module level work to automate the website build via ant/buildmagic. ! still needs project control, to pull files to release. Revision ChangesPath 1.2 +4 -2 manual/src/metadata/manual-application.xml Index: manual-application.xml === RCS file: /cvsroot/jboss/manual/src/metadata/manual-application.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- manual-application.xml2001/08/29 22:45:06 1.1 +++ manual-application.xml2001/08/31 05:30:31 1.2 @@ -1,14 +1,16 @@ ?xml version=1.0 encoding=UTF-8? !DOCTYPE application -!-- $Id: manual-application.xml,v 1.1 2001/08/29 22:45:06 user57 Exp $ -- +!-- $Id: manual-application.xml,v 1.2 2001/08/31 05:30:31 user57 Exp $ -- application - display-nameJBO/display-name + display-nameJBoss Manual/display-name + module web web-urimanual.war/web-uri context-rootdocumentation/context-root /web /module + /application ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss 3.0 and Jetty
Marc, I'm trying to gauge requirements for Jetty within a JBoss-3 context. This is what I have figured so far: 1. JettyService needs to be delivered as a self contained SAR. So it can be hot-deployed onto a JBoss node. My major concern here is whether the SAR is run packed/unpacked. Unpacked is probably not much work. Packed will probably require changes to Jetty itself (need to investigate). 2. Clustered Session support - if an incoming http request can be routed to any one of a number of nodes, then HttpSession objects need to be transparently distributed, in order that conversational state may be maintained between client and webapp. I was thinking that the simplest HttpSession implementation might be a CMP Bean ? Is this how clustering is expected to work in 3.0? Is this the sort of approach that you would expect ? Do you have any further primary issues that need attention ? Once we have something working we can address secondary issues such as tighter integration with shared thread pools etc Jules Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: thirdparty/mortbay/jetty/lib com.mortbay.jetty.jar org.apache.jasper.jar
User: chirino Date: 01/08/30 21:22:48 Modified:mortbay/jetty/lib com.mortbay.jetty.jar org.apache.jasper.jar Log: Upgrading to Jetty 3.1 RC 8 and Jetty 3 Extra 0.0.6 Revision ChangesPath 1.2 +1054 -1050thirdparty/mortbay/jetty/lib/com.mortbay.jetty.jar Binary file 1.2 +318 -318 thirdparty/mortbay/jetty/lib/org.apache.jasper.jar Binary file ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] EJB playing with finders
I am trying a simple home method with a query Home method public java.util.Collection findByInQueue() throws java.rmi.RemoteException,javax.ejb.FinderException; ejb-jar.xml snippit query ejb-qlselect object(t) from transferhead t where status=' '/ejb-ql query-method method-namefindByInQueue/method-name method-params /method-params /query-method result-type-mappingRemote/result-type-mapping /query Now there are two problems 1) [CMP,DEBUG] Finder: inQueue [CMP,DEBUG] Could not create the finder findByInQueue, because no matching CMP field was found. there are no arguments, just run it. 2) Now actually call the homemethod and I get findByInQueue command executing: SELECT t1_t.objectid FROM Transferhead t1_t Which politly returns all of them. Should it not throw an error or at least not return anything? ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] EJB 2.0 CMP
Sorry if this is posted twice!
Dain Sundstrom wrote:
Dave,
After reviewing these comments I think we are making this way more
complicated than it has to be. As far as I am concerned we should only
need the relationship stuff in jbosscmp-jdbc.xml for relationships that
use a relation table (ex. self relation employee/manager, just to
control the name and fields ) or for primary keys that are composite.
Relax. The only reason you need the jbosscmp-jdbc.xml file is that
you are
tiring to exactly specify the foreign key field. If you just let the
system
define the foreign key field for you, you would not have any problems. I
have a test case that closely matches what you have coded except my case
uses a general oid for the line item and the order fk is auto generated.
Ahh... lights on.
Is this how the majority of end users are going to use this? It would
seem within a larger shop the people doing the data modeling are not the
people building the J2EE apps. I would think that the data modeling or
db's would say here are the tables build your objects. I know it's not
*object oriented* but we should code for the masses.
Time Passes
So let me understand the order case above. Would the database schemas
look like this?
create table order (
objectid int default nextval('some sequence') primary key,
other fields ...
);
create table order_detail (
objectid int default nextval('some sequence') primary key,
order_oid int references order,
line_numint
other fields ...
);
Still having a hard time why you have to auto generate fk fields for
this case. It would seem this is what a dba would give you ... and if
the order/order_detail objects had all of the fields above nothing to
generate?
I think that your code is handling all of the difficult cases and is
ramming the easy ones into it. We really should have a waterfall type
style where we assume that it is the simple case and then have the
program add what's missing or have the user define it.
We should avoid creating tables if all possible. I would see only 3
cases where you need a third table
Many to Many
1 to Many (unidirectional. I can not come up with an example but it
would be valid)
Self referencing entry
A relation table is only required for a many-to-many relationship. A
unidirectional many-to-one relationship can always use foreign keys. The
trick is that the database mapping of the relationship does not have to
match the object level navigability. A self-referencing entity can
also use
a foreign key to itself.
Time passes ...
I'm am really trying hard to not have to use this jboss-jdbc.xml ... For
composite foreign keys would could also the jdbc method
getImportedKeys() to figure out composite keys. This would mean the jdbc
driver would have to support the DatabaseMetaData method and the dba
would have to use the references in their table definition. We could
always fall back to the xml file if it did not exsist. So with a good
jdbc driver we really would only have to create an xml entry if we had a
specfic relation table we had already predefined.
This is a good idea but, would only work if there were only a single
relationship between the two entities. The problem is that it is very
common for entities to have multiple relationships. For example,
order has
a shipping address and a billing address.
So what. There are two foriegn keys on a table. Could be hundreds ..
still do not see the problem. Let me check out getImportedKeys , I'll
get back to you ..
Maybe I'm foaming at the mouth, but I feel this is a HUGE feature for
people writing business apps and it should be as simple as possible. I
really think this could be simpler for the developers and users.
I agree. It think the configuration is very complicated. I was
thinking of
writing a took that could generate the jbosscmp-jdbc.xml file based
on the
system defaults. Then the user could modify the default
configuration. This
utility could also read in the current config and fill in the unspecified
options. Something like this or a gui could make configuration very
easy.
Have I missed something? Do you have a counter point or suggestion?
As a side note, I am happy to see someone challenging my design
decisions.
I have been known to be full of it (and my self). Please keep the
criticism
up, and don't worry about ticking me off (it takes a lot).
Thanks a lot,
-dain
I think a database schema of your case would help my understanding. I
still believe there is overkill for the simple cases
which will be the majority of cases. This is something that many
business aps will use and I in my day have written tons of this
collection handling shit and it would be nice to get it right once and
for all.
Writting is not my strong point , so I'm not trying to be cruft just
[JBoss-dev] CVS update: jboss build.xml
User: user57
Date: 01/08/30 22:39:08
Modified:.build.xml
Log:
o cleaned up tabs
Revision ChangesPath
1.20 +31 -29jboss/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jboss/build.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- build.xml 2001/08/30 07:03:58 1.19
+++ build.xml 2001/08/31 05:39:08 1.20
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.19 2001/08/30 07:03:58 rickardoberg Exp $ --
+!-- $Id: build.xml,v 1.20 2001/08/31 05:39:08 user57 Exp $ --
project name=JBoss default=main
@@ -463,39 +463,41 @@
/fileset
/jar
- !-- Build the boot and spine.jar --
- jar jarfile=${build.jars}/jboss-boot.jar
- basedir=${build.classes}
+!-- Build jboss-boot.jar --
+jar jarfile=${build.jars}/jboss-boot.jar
+ fileset dir=${build.classes}
include name=org/jboss/system/URLClassLoader.class/
- include name=org/jboss/system/URLClassLoaderMBean.class/
+include name=org/jboss/system/URLClassLoaderMBean.class/
include name=org/jboss/system/MBeanClassLoader.class/
include name=org/jboss/system/MBeanClassLoaderMBean.class/
- include name=org/jboss/system/ServiceLibraries.class/
- include name=org/jboss/system/ServiceLibrariesMBean.class/
- include name=org/jboss/deployment/DeploymentException.class/
+include name=org/jboss/system/ServiceLibraries.class/
+include name=org/jboss/system/ServiceLibrariesMBean.class/
+include name=org/jboss/deployment/DeploymentException.class/
+ /fileset
/jar
- jar jarfile=${build.jars}/jboss-spine.jar
- basedir=${build.classes}
- include name=org/jboss/logging/**/
- include name=org/jboss/system/Service.class/
- include name=org/jboss/system/ServiceMBean.class/
- include name=org/jboss/system/ServiceMBeanSupport.class/
- include name=org/jboss/system/ServiceController**.class/
- include name=org/jboss/system/ServiceCreator**.class/
- include name=org/jboss/system/ServiceConfigurator.class/
- include name=org/jboss/system/ServiceControllerMBean.class/
- include name=org/jboss/system/ConfigurationException.class/
- include name=org/jboss/system/Info.class/
- include name=org/jboss/system/InfoMBean.class/
- include name=org/jboss/system/Shutdown*.class/
-
- include name=org/jboss/deployment/ServiceDeployer.class/
- include name=org/jboss/deployment/ServiceDeployerMBean.class/
- include name=org/jboss/deployment/ServiceDeployer**.class/
- include name=org/jboss/deployment/DeployerMBean.class/
- include name=org/jboss/deployment/DeploymentException.class/
+
+!-- Build jboss-spine.jar --
+jar jarfile=${build.jars}/jboss-spine.jar
+ fileset dir=${build.classes}
+include name=org/jboss/logging/**/
+include name=org/jboss/system/Service.class/
+include name=org/jboss/system/ServiceMBean.class/
+include name=org/jboss/system/ServiceMBeanSupport.class/
+include name=org/jboss/system/ServiceController**.class/
+include name=org/jboss/system/ServiceCreator**.class/
+include name=org/jboss/system/ServiceConfigurator.class/
+include name=org/jboss/system/ServiceControllerMBean.class/
+include name=org/jboss/system/ConfigurationException.class/
+include name=org/jboss/system/Info.class/
+include name=org/jboss/system/InfoMBean.class/
+include name=org/jboss/system/Shutdown*.class/
+include name=org/jboss/deployment/ServiceDeployer.class/
+include name=org/jboss/deployment/ServiceDeployerMBean.class/
+include name=org/jboss/deployment/ServiceDeployer**.class/
+include name=org/jboss/deployment/DeployerMBean.class/
+include name=org/jboss/deployment/DeploymentException.class/
+ /fileset
/jar
-
!-- Build jboss-client.jar --
jar jarfile=${build.jars}/jboss-client.jar
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: manual/src/xdocs/howto howtopetstore.xml
User: tmcsys Date: 01/08/31 12:00:20 Modified:src/xdocs/howto howtopetstore.xml Log: give prominence to comment on the application's 'Table Madness' Revision ChangesPath 1.2 +3 -1 manual/src/xdocs/howto/howtopetstore.xml Index: howtopetstore.xml === RCS file: /cvsroot/jboss/manual/src/xdocs/howto/howtopetstore.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- howtopetstore.xml 2001/08/29 09:19:37 1.1 +++ howtopetstore.xml 2001/08/31 19:00:20 1.2 @@ -19,6 +19,9 @@ titleOutstanding Deployment Issues/title paraPlease post your experiences with deploying the Pet Store in JBoss to the jboss-user mailing list./para formalpara + titleInitializing the Database/title + paraThe current Pet Store application should automatically build required database tables the first time the Pet Store application is started. Apparently the latest database schema is slightly different from the earlier release, so you may encounter problems if you have an existing Pet Store database from a previous installation. When tring to determine the initial status of the database, this conflict may cause one of the drop commands to fail, and the application will not create the required tables. If this is the case, you may need to manually drop all existing tables before deploying the Pet Store for the first time./para +/formalpara titleThe Admin Client/title paraThe Admin application apparently needs some work on the deployment descriptors. Please post your experences with the Admin application to the mailing list./para /formalpara @@ -96,7 +99,6 @@ paraModify the Cloudscape startup command to use port 1098./para paraYou do this by adding -port port_number. For example:/para programlistingjava ... RmiJdbc.RJJdbcServer -port 1098 COM.cloudscape.core.JDBCDriver/programlisting - paraThe current Pet Store application should automatically build required databases the first time the application is started. Apparently, the schema is slightly different from the earlier release, so you may encounter problems if you have an existing Pet Store database from a previous installation. If this is the case, you may need to manually drop all existing tables./para paraStart Cloudscape./para /listitem listitem ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] EJB playing with finders
Right now there is no error handling in the ejb-ql parser. The problem with your ejb-ql is you have status when you should have t.status. It should work then, -dain -Original Message- From: Dave Smith [mailto:[EMAIL PROTECTED]] Sent: Friday, August 31, 2001 8:12 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] EJB playing with finders I am trying a simple home method with a query Home method public java.util.Collection findByInQueue() throws java.rmi.RemoteException,javax.ejb.FinderException; ejb-jar.xml snippit query ejb-qlselect object(t) from transferhead t where status=' '/ejb-ql query-method method-namefindByInQueue/method-name method-params /method-params /query-method result-type-mappingRemote/result-type-mapping /query Now there are two problems 1) [CMP,DEBUG] Finder: inQueue [CMP,DEBUG] Could not create the finder findByInQueue, because no matching CMP field was found. there are no arguments, just run it. 2) Now actually call the homemethod and I get findByInQueue command executing: SELECT t1_t.objectid FROM Transferhead t1_t Which politly returns all of them. Should it not throw an error or at least not return anything? ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] requirements for build
Dan - Blue Lotus Software wrote: -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. It should work OK out of the box. I was in the same position last night - I hadn't done a build since 2.* and I spent ages messing about doing all sorts of unnecessary stuff trying to get it working - installing ant, hacking about with scripts, modifying paths in cygwin etc. etc. However, after a quick check through recent mails in the list (should've done that first, obviously :-), I worked out that ant is actually still included in the build - just do a cvs get jboss-all and run build/build.sh (use Cygwin on Windows as suggested). It's included in the tools package and the scripts find it OK, even with Cygwin. So I was able to delete my draft why isn't there a self-contained build anymore mails. I reckon the build.bat file will still have to work though, to avoid lots of user queries. Seems pretty impressive so far Luke. -- Luke Taylor. PGP Key ID: 0x57E9523C ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] requirements for build
I didn't need to install anything... worked fine for me. As it should be. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] requirements for build
What os are you using? What module did you checkout? --jason On Fri, 31 Aug 2001, Dan - Blue Lotus Software wrote: Well, I downloaded and compiled the Rabbit Hole release of JBoss today. It's the first time I've built JBoss from scratch in about 6 months. At any rate, I thought I'd reflect a little on a couple of things, so that I can save people the 30 minutes I spent figuring it out. -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. Once that's done, you can cd into your_jboss_dir/build and type build. I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond. -dan -- Dan Kirkpatrick, Software Architect Blue Lotus Software+44 (0) 1224 575 985 [EMAIL PROTECTED] http://www.bluelotussoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss daily test failed
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
Searching for build.xml ...
Buildfile: /home/lubega/jbossro/jboss-all/build/build.xml
init-buildlog:
init:
[echo] user.home = /home/lubega
[echo] build.compiler = ${build.compiler}
[echo] java.home = /opt/jdk1.3.1_sun/jre
[echo] java.class.path =
/home/lubega/jbossro/jboss-all/tools/lib/xerces.jar:/home/lubega/jbossro/jboss-all/tools/lib/xalan.jar:/home/lubega/jbossro/jboss-all/tools/lib/stylebook.jar:/home/lubega/jbossro/jboss-all/tools/lib/saxon.jar:/home/lubega/jbossro/jboss-all/tools/lib/pretty.jar:/home/lubega/jbossro/jboss-all/tools/lib/optional.jar:/home/lubega/jbossro/jboss-all/tools/lib/junit.jar:/home/lubega/jbossro/jboss-all/tools/lib/jaxp.jar:/home/lubega/jbossro/jboss-all/tools/lib/JavaStyle.jar:/home/lubega/jbossro/jboss-all/tools/lib/javac.jar:/home/lubega/jbossro/jboss-all/tools/lib/fop.jar:/home/lubega/jbossro/jboss-all/tools/lib/ejbdoclet.jar:/home/lubega/jbossro/jboss-all/tools/lib/crimson.jar:/home/lubega/jbossro/jboss-all/tools/lib/buildmagic-tasks.jar:/home/lubega/jbossro/jboss-all/tools/lib/bsf.jar:/home/lubega/jbossro/jboss-all/tools/lib/batik.jar:/home/lubega/jbossro/jboss-all/tools/lib/ant.jar:/opt/jdk1.3.1_sun/lib/tools.jar
[echo] java.version = 1.3.1
[echo] java.vendor = Sun Microsystems Inc.
[echo] java.vm.version = 1.3.1-b24
[echo] java.vm.name = Java HotSpot(TM) Client VM
[echo] java.vm.info = mixed mode
[echo] os.name = Linux
[echo] os.arch = Linux
[echo] os.version = Linux
[echo]
configure:
[projectinfo] Project root: /home/lubega/jbossro/jboss-all
[projectinfo] Modules:
j2ee,naming,server,security,messaging,connector,pool,cluster,admin,testsuite,plugins/varia,plugins/jetty
run-testsuite:
[execmodules]
==
== Executing 'tests' in module 'testsuite'...
==
init-buildlog:
init:
[moduleinfo] Project root: /home/lubega/jbossro/jboss-all
[moduleinfo] Module root: /home/lubega/jbossro/jboss-all/testsuite
compile-classes:
[mkdir] Created dir: /home/lubega/jbossro/jboss-all/testsuite/output/classes
[javac] Compiling 274 source files to
/home/lubega/jbossro/jboss-all/testsuite/output/classes
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:8:
cannot resolve symbol
[execmodules] symbol : class Identifier
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.Identifier;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:9:
cannot resolve symbol
[execmodules] symbol : class Operator
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.Operator;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:10:
cannot resolve symbol
[execmodules] symbol : class SelectorParser
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.SelectorParser;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:11:
cannot resolve symbol
[execmodules] symbol : class ISelectorParser
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.ISelectorParser;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:21:
cannot resolve symbol
[execmodules] symbol : class ISelectorParser
[execmodules] location: class org.jboss.test.jbossmq.test.TestSelectorParser
[execmodules] static ISelectorParser parser;
[execmodules]^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:140:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert(!clct.isEmpty());
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:148:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert(bean.getPersonsName().trim().equals(BEAN_NAME));
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:270:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert( this.gotRefOkay(bean, BEAN_NAME) );
[execmodules] ^
[execmodules]
[JBoss-dev] CVS update: manual/src/xdocs jbossjms.xml
User: chirino Date: 01/08/30 22:02:22 Modified:src/xdocs jbossjms.xml Log: A few ajustments to the PM JMS section Revision ChangesPath 1.2 +129 -129 manual/src/xdocs/jbossjms.xml Index: jbossjms.xml === RCS file: /cvsroot/jboss/manual/src/xdocs/jbossjms.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- jbossjms.xml 2001/08/29 09:19:36 1.1 +++ jbossjms.xml 2001/08/31 05:02:22 1.2 @@ -2,7 +2,7 @@ !-- edited with XML Spy v3.5 NT (http://www.xmlspy.com) by na (na) -- !--DOCTYPE chapter PUBLIC -//OASIS//DTD DocBook XML V4.1.2//EN docbookx/docbookx.dtd/-- !--for standalone validation uncomment the DOCTYPE declaration-- -!-- Version: $Revision: 1.1 $ -- +!-- Version: $Revision: 1.2 $ -- chapter id=jms titleJBoss and JMS/title subtitleJava Messaging Service in JBoss/subtitle @@ -495,13 +495,13 @@ /row row entryrollinglogged/entry - entryFast/entry - entryVery new. Needs more testing/entry + entryVery Fast/entry + entryVery new/entry /row row entryjdbc/entry - entryHas jdbc overhead/entry entryShould provide better stability/scaleability/entry + entryHas JDBC overhead/entry /row row entrylogged/entry @@ -512,137 +512,137 @@ /tgroup /table paraPlease note that you must have one and only one PM configured for one instance of the JMS server./para - section id=jms-jms-adv-config-pm-file - titleSetting up the file PM/title - paraThe file PM uses the concept of one file per persisted message. This method of message persistence is not the most effective performance wise, but it is very stable./para - paraThe file PM is the default PM that comes enabled with the a JBoss distribution. If you look at the jboss.jcml you should see a XML section that looks like:/para - figure - titleDefining the file PM in jbossmq.xml/title - programlisting![CDATA[ + /section + !--jms-jms-adv-config-pm-- + section id=jms-jms-adv-config-pm-file + titleSetting up the file PM/title + paraThe file PM uses the concept of one file per persisted message. This method of message persistence is not the most effective performance wise, but it is very stable./para + paraThe file PM is the default PM that comes enabled with the a JBoss distribution. If you look at the jboss.jcml you should see a XML section that looks like:/para + figure + titleDefining the file PM in jbossmq.xml/title + programlisting![CDATA[ mbean code=org.jboss.mq.pm.file.PersistenceManager name=JBossMQ:service=PersistenceManager attribute name=DataDirectory../../db/jbossmq//attribute /mbean ]]/programlisting - /figure - paraThe file PM allows you to set the following attributes when setting up the MBean configuration:/para - table - titleSettable MBean attributes of the file PM/title - tgroup cols=2 - thead - row - entryAttribute/entry -
[JBoss-dev] CVS update: build/jboss build.xml
User: kimptoc
Date: 01/08/31 03:01:18
Modified:jbossbuild.xml
Log:
added some echo info to let you know what you are using - just in case you think its
different
Revision ChangesPath
1.13 +16 -1 build/jboss/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/build/jboss/build.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- build.xml 2001/08/31 05:25:55 1.12
+++ build.xml 2001/08/31 10:01:18 1.13
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.12 2001/08/31 05:25:55 user57 Exp $ --
+!-- $Id: build.xml,v 1.13 2001/08/31 10:01:18 kimptoc Exp $ --
project default=main
@@ -42,6 +42,21 @@
!-- Initialize the build system. --
target name=init unless=project-initialized-already
depends=init-buildlog
+
+echo message=user.home = ${user.home}/
+echo message=build.compiler = ${build.compiler}/
+echo message=java.home = ${java.home}/
+echo message=java.class.path = ${java.class.path}/
+echo message=java.version = ${java.version}/
+echo message=java.vendor = ${java.vendor}/
+echo message=java.vm.version = ${java.vm.version}/
+echo message=java.vm.name = ${java.vm.name}/
+echo message=java.vm.info = ${java.vm.info}/
+echo message=os.name = ${os.name}/
+echo message=os.arch = ${os.name}/
+echo message=os.version = ${os.name}/
+echo message=/
+
tstamp
format property=build.number pattern=MMddHHmm/
/tstamp
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] EJB 2.0 CMP
Dave, We still don't see eye-to-eye, and I think I made the problem worse with my example. I think the most common type of relationship will be something like 'a cd has an artist' or 'a cd has a publisher.' In this cases, the foreign key for the artist or publisher would be just another column in the cd table. So we would have something like: String idbn pk String title ... Oid cd_artist fk Oid cd_publisher fk The oid is a place holder for what ever the pk for cd and artist (don't let it confuse you). I will argue that this is the most common relationship type and is auto created by the system. Now your mapping is very different from what we have above. Your mapping mapps a foreign key to one of the pk columns (multi-key). This is a very difficult mapping because of the way the cmp engine is architected. The CMP engine is field oriented as apposed to column oriented. A field can map to multiple columns (a feature that existed in jaws). Follow so far? Now each entity is composed of a collection of cmp field field objects and a collection of foreign key fields (or relation table key fields). I'm only going to address foreign key fields here. When the system starts it initializes the cmp fields for every entity. After that is complete it initializes the relationships. For each cmr field in an entity, it locates the related entity and creates a set of foreign-keys that are a copy of the related entitie's pk field(s). Still with me? The problem you mapping presents is you want to use a field for both an entity cmp and a relation foreign key field. In the current code these fields are different object. The caching code is also field oriented, so you would end up with two distinct caches of the code. Which could be a big problem. Ok let's take a step back and examine the mapping from the spec perspecitve. Using a pk field as a relationship foreign key presents a problem because the spec requres that a pk never change after ejbCreate but also requires that a relationship can not be set until ejbPostCreate. This leads to the question, how exactly are you going to set the relationship? Any way, I don't think any of the above text is that important. Although I think what you ask will make your code not spec compliant, I also think this type of mapping is important. I will look into adding support for this type of mapping, but it won't happen soon. I am focusing on the features required for spec compliance. Then I am going to add performance enhancements. And finally additional features. Ok that was a lot of babble. I need to stop writting emails before I get my first cup of coffee. -dain ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-457245 ] Passivation Error in BaseLocalContainerI
Bugs item #457245, was opened at 2001-08-31 07:25 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=457245group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Passivation Error in BaseLocalContainerI Initial Comment: This exception is thrown after a while if I do not remove my stateful session bean with ejbRemove. A reference to an other bean is stored in the bean. I am using this JBoss 2.4 final JDK 1.3.0_02 Win2000 [Container factory] java.rmi.ServerException: Could not passivate; nested exception is: [Container factory] java.io.NotSerializableException: org.jboss.ejb.plugins.local.BaseLocalContainerInvoker$H omeProxy [Container factory] java.io.NotSerializableException: org.jboss.ejb.plugins.local.BaseLocalContainer Invoker$HomeProxy [Container factory] at java.io.ObjectOutputStream.outputObject (ObjectOutputStream.java:1148) [Container factory] at java.io.ObjectOutputStream.writeObject (ObjectOutputStream.java:366) [Container factory] at java.io.ObjectOutputStream.outputClassFields (ObjectOutputStream.java:1841 ) [Container factory] at java.io.ObjectOutputStream.defaultWriteObject (ObjectOutputStream.java:480 ) [Container factory] at java.io.ObjectOutputStream.outputObject (ObjectOutputStream.java:1214) [Container factory] at java.io.ObjectOutputStream.writeObject (ObjectOutputStream.java:366) [Container factory] at java.io.ObjectOutputStream.outputClassFields (ObjectOutputStream.java:1841 ) [Container factory] at java.io.ObjectOutputStream.defaultWriteObject (ObjectOutputStream.java:480 ) [Container factory] at java.io.ObjectOutputStream.outputObject (ObjectOutputStream.java:1214) [Container factory] at java.io.ObjectOutputStream.writeObject (ObjectOutputStream.java:366) [Container factory] at org.jboss.ejb.plugins.StatefulSessionFilePersistenceMan ager.passivateSess ion(StatefulSessionFilePersistenceManager.java:285) [Container factory] at org.jboss.ejb.plugins.StatefulSessionInstanceCache.pass ivate(StatefulSess ionInstanceCache.java:67) [Container factory] at org.jboss.ejb.plugins.AbstractInstanceCache$1.execute (AbstractInstanceCac he.java:688) [Container factory] at org.jboss.util.WorkerQueue$QueueLoop.run (WorkerQueue.java:199) [Container factory] at java.lang.Thread.run (Thread.java:484) [Container factory] java.rmi.ServerException: Could not passivate; nested exception is: [Container factory] java.io.NotSerializableException: org.jboss.ejb.plugins.local.BaseLocalConta inerInvoker$HomeProxy [Container factory] java.io.NotSerializableException: org.jboss.ejb.plugins.local.BaseLocalContainer Invoker$HomeProxy [Container factory] at java.io.ObjectOutputStream.outputObject (ObjectOutputStream.java:1148) [Container factory] at java.io.ObjectOutputStream.writeObject (ObjectOutputStream.java:366) [Container factory] at java.io.ObjectOutputStream.outputClassFields (ObjectOutputStream.java:1841 ) [Container factory] at java.io.ObjectOutputStream.defaultWriteObject (ObjectOutputStream.java:480 ) [Container factory] at java.io.ObjectOutputStream.outputObject (ObjectOutputStream.java:1214) [Container factory] at java.io.ObjectOutputStream.writeObject (ObjectOutputStream.java:366) [Container factory] at java.io.ObjectOutputStream.outputClassFields (ObjectOutputStream.java:1841 ) [Container factory] at java.io.ObjectOutputStream.defaultWriteObject (ObjectOutputStream.java:480 ) [Container factory] at java.io.ObjectOutputStream.outputObject (ObjectOutputStream.java:1214) [Container factory] at java.io.ObjectOutputStream.writeObject (ObjectOutputStream.java:366) [Container factory] at org.jboss.ejb.plugins.StatefulSessionFilePersistenceMan ager.passivateSess ion(StatefulSessionFilePersistenceManager.java:285) [Container factory] at org.jboss.ejb.plugins.StatefulSessionInstanceCache.pass ivate(StatefulSess ionInstanceCache.java:67) [Container factory] at org.jboss.ejb.plugins.AbstractInstanceCache$1.execute (AbstractInstanceCac he.java:688) [Container factory] at org.jboss.util.WorkerQueue$QueueLoop.run (WorkerQueue.java:199) [Container factory] at java.lang.Thread.run (Thread.java:484) -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=457245group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] EJB 2.0 CMP
|I still believe there is overkill for the simple cases | |which will be the majority of cases. This is something that many hmmm I am a cretin when it comes to db stuff but anything that makes the lives of *most* people better as opposed to the lives of everyone blah is a good thing. Never design for everyone, that is what kills design, design for the majority. | beatles songs running |through my head Trumpets raising in the background, heroic music helping men marching to the front, crazed up frenchman playing the fiddle in the back...yes... deja-vu all over again... is there a glitch in the matrix? There was a black rabbit a second ago and then a second one *just* like it! regards marcf | | | | | | | | | | | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] remote debugging from IDEA
Looks like port 5000 from your command, but check the how-to for debugging jboss with netbeans and there should be some info there on the setup of the jvm... Cheers -Original Message- From: Colin Daly To: [EMAIL PROTECTED] Sent: 8/30/01 8:47 PM Subject: [JBoss-dev] remote debugging from IDEA hi, i'm trying to get remote debugging with IntelliJ IDEA and JBoss 2.4 Beta / Jetty distribution. IDEA says that the remote VM must be run in debug mode with the following settings. -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5000 ok. then it asks for the host (localhost) and the port. what is the port number I should use? Colin. ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: tools/bin ant
Hi, --- Jason Dillon [EMAIL PROTECTED] wrote: User: user57 Date: 01/08/30 15:37:31 Modified:bin ant Log: o only showing ANT_OPTS and running jvm for help message if $ANT_DEBUG is set. Thanks - I only meant to have that in for my testing ;-) I'll look at the junitreport stuff - I just about have the tests running - just got to add a step to copy aside each set of results for the various environments. Does the javadoc generation work - I tried setting the local.properties/javadoc generated property to false, but I still don't seem to have any docs... Chris = Need somewhere to Live in London - http://freeflats.com __ Do You Yahoo!? Get email alerts NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
Hi, Is ANT_HOME env property set ? Unset it and it will run by finding ant from tools/ Vincent. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Dan - Blue Lotus Software Envoyé : vendredi 31 août 2001 11:21 À : JBoss Dev Objet : [JBoss-dev] requirements for build Well, I downloaded and compiled the Rabbit Hole release of JBoss today. It's the first time I've built JBoss from scratch in about 6 months. At any rate, I thought I'd reflect a little on a couple of things, so that I can save people the 30 minutes I spent figuring it out. -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. Once that's done, you can cd into your_jboss_dir/build and type build. I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond. -dan -- Dan Kirkpatrick, Software Architect Blue Lotus Software+44 (0) 1224 575 985 [EMAIL PROTECTED] http://www.bluelotussoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] JBoss 3.0 and Jetty
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Julian Gosnell Sent: Friday, August 31, 2001 7:18 AM To: marc fleury Cc: Greg Wilkins; [EMAIL PROTECTED] Subject: [JBoss-dev] JBoss 3.0 and Jetty Marc, I'm trying to gauge requirements for Jetty within a JBoss-3 context. This is what I have figured so far: 1. JettyService needs to be delivered as a self contained SAR. So it can be hot-deployed onto a JBoss node. My major concern here is whether the SAR is run packed/unpacked. Unpacked is probably not much work. Packed will probably require changes to Jetty itself (need to investigate). 2. Clustered Session support - if an incoming http request can be routed to any one of a number of nodes, then HttpSession objects need to be transparently distributed, in order that conversational state may be maintained between client and webapp. I was thinking that the simplest HttpSession implementation might be a CMP Bean ? Is this how clustering is expected to work in 3.0? Is this the sort of approach that you would expect ? Julian, take a look at http://www.javagroups.com especially the DistributedHashtable. Putting the HttpSession in a CMP Bean is a bad idea. You don't want to be hitting the database on every click to your site. When Sacha and I get the HA SFSBs going, I was thinking of making the HttpSession a SFSB. Just an idea though. Regards, Bill ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] requirements for build
on 1-08-31 22.35, Jason Dillon at [EMAIL PROTECTED] wrote: I didn't need to install anything... worked fine for me As it should be. Yes - on my post of success tagged True Build and Rabbit Magic was on 7.1 red Hat distro, BlackDown.com JVM. cvs get jboss-all ... and it just works ... sorry for being sloppy on the details there ... /peter_f ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
Win2k jboss-all One thing. I first tried it with Ant v1.3. It crashed and burned quickly, due to a missing buildmagic class. So I copied the Jar file into the lib directory of Ant. This got me past the classpath problem, but exposed the record problem. So when I installed Ant v1.4beta2, I dropped the buildmagic jar file into its lib directory, too. That may not have been necessary. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jason Dillon Sent: Friday, August 31, 2001 9:35 PM To: JBoss Dev Subject: Re: [JBoss-dev] requirements for build What os are you using? What module did you checkout? --jason On Fri, 31 Aug 2001, Dan - Blue Lotus Software wrote: Well, I downloaded and compiled the Rabbit Hole release of JBoss today. It's the first time I've built JBoss from scratch in about 6 months. At any rate, I thought I'd reflect a little on a couple of things, so that I can save people the 30 minutes I spent figuring it out. -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. Once that's done, you can cd into your_jboss_dir/build and type build. I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond. -dan -- Dan Kirkpatrick, Software Architect Blue Lotus Software+44 (0) 1224 575 985 [EMAIL PROTECTED] http://www.bluelotussoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] requirements for build
However, after a quick check through recent mails in the list (should've done that first, obviously :-), I worked out that ant is actually still included in the build - just do a cvs get jboss-all and run build/build.sh (use Cygwin on Windows as suggested). It's included in the tools package and the scripts find it OK, even with Cygwin. So I was able to delete my draft why isn't there a self-contained build anymore mails. ;) I reckon the build.bat file will still have to work though, to avoid lots of user queries. build.bat will always have issues, since we can not give it all of the features that build.sh has (like chaning the JAXP impl and such). I highly recommended that every windows user install cygwin. It will be worth the effort, believe me. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
Yes, this was it. I suggest we unset ANT_HOME in the build script. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Vincent Harcq Sent: Friday, August 31, 2001 7:50 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] requirements for build Hi, Is ANT_HOME env property set ? Unset it and it will run by finding ant from tools/ Vincent. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Dan - Blue Lotus Software Envoyé : vendredi 31 août 2001 11:21 À : JBoss Dev Objet : [JBoss-dev] requirements for build Well, I downloaded and compiled the Rabbit Hole release of JBoss today. It's the first time I've built JBoss from scratch in about 6 months. At any rate, I thought I'd reflect a little on a couple of things, so that I can save people the 30 minutes I spent figuring it out. -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. Once that's done, you can cd into your_jboss_dir/build and type build. I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond. -dan -- Dan Kirkpatrick, Software Architect Blue Lotus Software+44 (0) 1224 575 985 [EMAIL PROTECTED] http://www.bluelotussoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: tools/bin ant
Does the javadoc generation work - I tried setting the local.properties/javadoc generated property to false, but I still don't seem to have any docs... You have to comment it, ant if/unless attributes only check for the existence of the property. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
|build.bat will always have issues, since we can not give it all of the |features that build.sh has (like chaning the JAXP impl and such). | |I highly recommended that every windows user install cygwin. It will be |worth the effort, believe me. no, we have been down this road before and the result is not pretty. 95% will NOT install cygwin and will NOT be able to build. |--jason Jason I am serious now, I am working on linux these days so I don't notice these thing but if your stuff is dependent in any way on cygwin stuff it goes right out the door. The build wars of early EJBoss still send shivers down my spine and I won't let *anyone* monkey with this. ANT brought us Linux/windows tools acgnosticism, anything that touches that is a regression. You must have SIMILAR builds on both. Kill features that break this. I am dead serious jason, tell me it is not the case. marcf | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: build/jboss build.xml
Can you make the info a dependency (or call target), which will only run if
a property is set, so those who don't really want to see this do not have
to.
--jason
On Fri, 31 Aug 2001, Chris Kimpton wrote:
User: kimptoc
Date: 01/08/31 03:01:18
Modified:jbossbuild.xml
Log:
added some echo info to let you know what you are using - just in case you think
its different
Revision ChangesPath
1.13 +16 -1 build/jboss/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/build/jboss/build.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- build.xml 2001/08/31 05:25:55 1.12
+++ build.xml 2001/08/31 10:01:18 1.13
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.12 2001/08/31 05:25:55 user57 Exp $ --
+!-- $Id: build.xml,v 1.13 2001/08/31 10:01:18 kimptoc Exp $ --
project default=main
@@ -42,6 +42,21 @@
!-- Initialize the build system. --
target name=init unless=project-initialized-already
depends=init-buildlog
+
+echo message=user.home = ${user.home}/
+echo message=build.compiler = ${build.compiler}/
+echo message=java.home = ${java.home}/
+echo message=java.class.path = ${java.class.path}/
+echo message=java.version = ${java.version}/
+echo message=java.vendor = ${java.vendor}/
+echo message=java.vm.version = ${java.vm.version}/
+echo message=java.vm.name = ${java.vm.name}/
+echo message=java.vm.info = ${java.vm.info}/
+echo message=os.name = ${os.name}/
+echo message=os.arch = ${os.name}/
+echo message=os.version = ${os.name}/
+echo message=/
+
tstamp
format property=build.number pattern=MMddHHmm/
/tstamp
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
Did you try the build.bat script? It should use the correct version of Ant with all of the correct support jars. --jason On Fri, 31 Aug 2001, Dan - Blue Lotus Software wrote: Win2k jboss-all One thing. I first tried it with Ant v1.3. It crashed and burned quickly, due to a missing buildmagic class. So I copied the Jar file into the lib directory of Ant. This got me past the classpath problem, but exposed the record problem. So when I installed Ant v1.4beta2, I dropped the buildmagic jar file into its lib directory, too. That may not have been necessary. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jason Dillon Sent: Friday, August 31, 2001 9:35 PM To: JBoss Dev Subject: Re: [JBoss-dev] requirements for build What os are you using? What module did you checkout? --jason On Fri, 31 Aug 2001, Dan - Blue Lotus Software wrote: Well, I downloaded and compiled the Rabbit Hole release of JBoss today. It's the first time I've built JBoss from scratch in about 6 months. At any rate, I thought I'd reflect a little on a couple of things, so that I can save people the 30 minutes I spent figuring it out. -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. Once that's done, you can cd into your_jboss_dir/build and type build. I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond. -dan -- Dan Kirkpatrick, Software Architect Blue Lotus Software+44 (0) 1224 575 985 [EMAIL PROTECTED] http://www.bluelotussoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
You should not need ANT_HOME set at all. --jason On Fri, 31 Aug 2001, Dan - Blue Lotus Software wrote: This makes sense. I have the ANT_HOME environment variable set to a separate install of Ant. It probably just used that instead of the one included with jboss-all. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Luke Taylor Sent: Friday, August 31, 2001 8:48 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] requirements for build Dan - Blue Lotus Software wrote: -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. It should work OK out of the box. I was in the same position last night - I hadn't done a build since 2.* and I spent ages messing about doing all sorts of unnecessary stuff trying to get it working - installing ant, hacking about with scripts, modifying paths in cygwin etc. etc. However, after a quick check through recent mails in the list (should've done that first, obviously :-), I worked out that ant is actually still included in the build - just do a cvs get jboss-all and run build/build.sh (use Cygwin on Windows as suggested). It's included in the tools package and the scripts find it OK, even with Cygwin. So I was able to delete my draft why isn't there a self-contained build anymore mails. I reckon the build.bat file will still have to work though, to avoid lots of user queries. Seems pretty impressive so far Luke. -- Luke Taylor. PGP Key ID: 0x57E9523C ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
Perhaps we should ignore any user set ANT_HOME, or warn the user if it is set. --jason On Fri, 31 Aug 2001, Dan - Blue Lotus Software wrote: Yes, this was it. I suggest we unset ANT_HOME in the build script. -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Vincent Harcq Sent: Friday, August 31, 2001 7:50 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] requirements for build Hi, Is ANT_HOME env property set ? Unset it and it will run by finding ant from tools/ Vincent. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Dan - Blue Lotus Software Envoyé : vendredi 31 août 2001 11:21 À : JBoss Dev Objet : [JBoss-dev] requirements for build Well, I downloaded and compiled the Rabbit Hole release of JBoss today. It's the first time I've built JBoss from scratch in about 6 months. At any rate, I thought I'd reflect a little on a couple of things, so that I can save people the 30 minutes I spent figuring it out. -You need v1.4beta of Ant. The current release is v1.4beta2. -Copy the jar file from your_jboss_dir/tools/buildmagic-tasks.jar into the lib directory under Ant. Once that's done, you can cd into your_jboss_dir/build and type build. I'm sorry if this is obvious to everyone on this list. It wasn't for me, though. The directions for buildmagic say nothing about how to *install* it. And the build script contains the record tag, which is only supported in v1.4beta1 and beyond. -dan -- Dan Kirkpatrick, Software Architect Blue Lotus Software+44 (0) 1224 575 985 [EMAIL PROTECTED] http://www.bluelotussoftware.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
|I highly recommended that every windows user install cygwin. It will be |worth the effort, believe me. no, we have been down this road before and the result is not pretty. 95% will NOT install cygwin and will NOT be able to build. Notice I said recommend. Jason I am serious now, I am working on linux these days so I don't notice these thing but if your stuff is dependent in any way on cygwin stuff it goes right out the door. No worries, nothing is dependent on cygwin. But I don't have the patience to deal with maintaining a batch script. I would rather write it in basic than have to deal with the frustrations of the different versions of batch. The build wars of early EJBoss still send shivers down my spine and I won't let *anyone* monkey with this. ANT brought us Linux/windows tools acgnosticism, anything that touches that is a regression. You must have SIMILAR builds on both. Kill features that break this. There are not features that break this, short of letting users run any old version of ant that they have installed, that is what breaks things. The scripts probably need to be tuned a little more to complain when the running env is not correct, but other wise everything is compatible with all java enabled os's. I am dead serious jason, tell me it is not the case. It is not the case. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/bin - New directory
User: user57 Date: 01/08/31 15:50:47 newsite/src/bin - New directory ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: build/website build.xml
User: user57 Date: 01/08/31 16:22:13 Modified:website build.xml Log: o adding website, website-install website-run-once to help automate updating the website. Revision ChangesPath 1.3 +15 -1 build/website/build.xml Index: build.xml === RCS file: /cvsroot/jboss/build/website/build.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- build.xml 2001/08/30 22:07:30 1.2 +++ build.xml 2001/08/31 23:22:13 1.3 @@ -10,7 +10,7 @@ !---- !-- == -- -!-- $Id: build.xml,v 1.2 2001/08/30 22:07:30 user57 Exp $ -- +!-- $Id: build.xml,v 1.3 2001/08/31 23:22:13 user57 Exp $ -- project default=main name=JBoss Website/Build @@ -411,5 +411,19 @@ target name=tests depends=all-tests description=Execute all tests./ + + + !-- == -- + !-- Generate the Website -- + !-- == -- + + target name=website-run-once depends=init + /target + + target name=website depends=init + /target + + target name=website-install depends=init + /target /project ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/bin catchlog.sh nightly-website.sh update-website.sh
User: user57
Date: 01/08/31 17:25:30
Added: src/bin catchlog.sh nightly-website.sh update-website.sh
Log:
o adding scripts and helper scripts to run the nightly website update
Revision ChangesPath
1.1 newsite/src/bin/catchlog.sh
Index: catchlog.sh
===
#!/bin/sh
### == ###
## ##
## This script executes a child process and catches all output into a ##
## log file. ##
## ##
### == ###
# $Id: catchlog.sh,v 1.1 2001/09/01 00:25:30 user57 Exp $
PROGNAME=`basename $0`
DIRNAME=`dirname $0`
CAT='cat'
TEE='tee'
##
## Print an informative message
##
info() {
echo ${PROGNAME}: $*
}
##
## Print an error message and exit
##
die() {
info $*
exit 1
}
##
## Show command line help
##
show_help() {
$CAT EOF
usage: $PROGNAME [options] [--] program to execute
options:
--logfile, -l logfileThe file where output will be stored
--append, -a Append to the log file
--quiet, -qTry to be quite
--help, -h Show this help message
-- Stop processing options
EOF
}
##
## Where all the fun stuff happens
##
main() {
# the list of arguments to execute
args=
# the file to catch output to
logfile=output.log
# a flag to append to the file
append=
# a flag to tell us to be quiet
quiet=
if [ x$1 = x ]; then
show_help
exit
fi
# parse the command line
while [ x$1 != x ]; do
case $1 in
--logfile|-l)
if [ x$2 = x ]; then
die --logfile requires an additional argument
fi
logfile=$2
shift
;;
--append|-a)
append=-a # set for TEE
;;
--quiet|-q)
quiet=true
;;
--help|-h)
show_help
exit
;;
--)
shift
if [ x$args = x ]; then
args=$*
else
args=$args $*
fi
break
;;
*)
if [ x$args = x ]; then
args=$1
else
args=$args $1
fi
;;
esac
shift
done
# setup the log file
if [ x$append = x ]; then
if [ -e $logfile ]; then
rm $logfile
fi
fi
if [ ! -f $logfile ]; then
touch $logfile
fi
# execute the program
if [ x$quiet = x ]; then
# use tee and let output display to the console
$args | $TEE $append $logfile 21
else
# append all output to the log, nothing goes to console
$args $logfile 21
fi
info Log saved to $logfile
}
##
## Bootstrap
##
main $@
1.1 newsite/src/bin/nightly-website.sh
Index: nightly-website.sh
===
#!/bin/sh
### == ###
## ##
## This script controlls the nighly update of the website. ##
## ##
### == ###
# $Id: nightly-website.sh,v 1.1 2001/09/01 00:25:30 user57 Exp $
PROGNAME=`basename $0`
DIRNAME=`dirname $0`
# Setup Mail
MAIL=mail
MAILTO=[EMAIL PROTECTED] # change to [EMAIL PROTECTED] when done testing
# Where the required scripts live
SCRIPTROOT=$DIRNAME
# A date stamp
DSTAMP=`date +%m%d%Y`
# Where the logs will go
LOGROOT=$HOME/log
LOGFILE=$LOGROOT/nightly-website.log
# Run the update-website.sh script. It must be wrapped with catchlog.sh,
# because it uses the log file to determine build successes from it
$SCRIPTROOT/catchlog.sh --logfile $LOGFILE -- \
$SCRIPTROOT/update-website.sh $LOGFILE
# Send out email about the update
$MAIL $MAILTO -s Website updated successfully $LOGFILE
1.1 newsite/src/bin/update-website.sh
Index: update-website.sh
[JBoss-dev] CVS update: newsite build.xml
User: user57
Date: 01/08/31 17:25:30
Modified:.build.xml
Log:
o adding scripts and helper scripts to run the nightly website update
Revision ChangesPath
1.3 +30 -2 newsite/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/newsite/build.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- build.xml 2001/08/31 05:30:31 1.2
+++ build.xml 2001/09/01 00:25:30 1.3
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.2 2001/08/31 05:30:31 user57 Exp $ --
+!-- $Id: build.xml,v 1.3 2001/09/01 00:25:30 user57 Exp $ --
project default=main name=JBoss/Website
@@ -137,6 +137,7 @@
/path
!-- Where source files live --
+ property name=source.bin value=${module.source}/bin/
property name=source.metadata value=${module.source}/metadata/
property name=source.examples value=${module.source}/examples/
property name=source.stylesheets value=${module.source}/stylesheets/
@@ -144,6 +145,7 @@
property name=source.xdocs value=${module.source}/xdocs/
!-- Where build generated files will go --
+ property name=build.bin value=${module.build}/bin/
property name=build.metadata value=${module.build}/metadata/
property name=build.snapshots value=${module.build}/snapshots/
property name=build.docs value=${module.build}/docs/
@@ -192,7 +194,7 @@
| different type of compile that needs to be performed, short of
| documentation compiles.
--
- target name=compile depends=init, compile-docs, compile-metadata,
compile-snapshots
+ target name=compile depends=init, compile-docs, compile-metadata,
compile-bin, compile-snapshots
description=Compile all source files./
!-- Compile doc sources support files --
@@ -215,6 +217,30 @@
/copy
/target
+ !-- Compile bin scripts --
+ target name=compile-bin depends=init
+mkdir dir=${build.bin}/
+copy todir=${build.bin} filtering=yes
+ fileset dir=${source.bin}
+ include name=**/*/
+ /fileset
+/copy
+
+fixcrlf srcdir=${build.bin}
+ eol=lf eof=remove
+ includes=**/*.sh/
+
+fixcrlf srcdir=${build.bin}
+ eol=crlf eof=remove
+ includes=**/*.bat, **/*.cmd/
+
+chmod perm=+x
+ fileset dir=${build.bin}
+ include name=**/*.sh/
+ /fileset
+/chmod
+ /target
+
property name=snapshot.cvsroot
value=:pserver:[EMAIL PROTECTED]:/cvsroot/jboss/
@@ -227,11 +253,13 @@
!-- Make sure there is an entry for this cvsroot --
cvspass cvsroot=${snapshot.cvsroot} password=/
+!-- skip for testing
cvs cvsroot=${snapshot.cvsroot}
command=export
date=TODAY
package=jboss-all
dest=${build.snapshots}/
+--
/target
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite build.xml
User: user57
Date: 01/08/31 17:44:19
Modified:.build.xml
Log:
o the build pulls from cvs, so I have to check in these with test data to
make sure it works
Revision ChangesPath
1.4 +1 -3 newsite/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/newsite/build.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- build.xml 2001/09/01 00:25:30 1.3
+++ build.xml 2001/09/01 00:44:19 1.4
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.3 2001/09/01 00:25:30 user57 Exp $ --
+!-- $Id: build.xml,v 1.4 2001/09/01 00:44:19 user57 Exp $ --
project default=main name=JBoss/Website
@@ -253,13 +253,11 @@
!-- Make sure there is an entry for this cvsroot --
cvspass cvsroot=${snapshot.cvsroot} password=/
-!-- skip for testing
cvs cvsroot=${snapshot.cvsroot}
command=export
date=TODAY
package=jboss-all
dest=${build.snapshots}/
---
/target
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: build/website build.xml
User: user57
Date: 01/08/31 17:44:19
Modified:website build.xml
Log:
o the build pulls from cvs, so I have to check in these with test data to
make sure it works
Revision ChangesPath
1.4 +20 -4 build/website/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/build/website/build.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- build.xml 2001/08/31 23:22:13 1.3
+++ build.xml 2001/09/01 00:44:19 1.4
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.3 2001/08/31 23:22:13 user57 Exp $ --
+!-- $Id: build.xml,v 1.4 2001/09/01 00:44:19 user57 Exp $ --
project default=main name=JBoss Website/Build
@@ -417,13 +417,29 @@
!-- Generate the Website --
!-- == --
- target name=website-run-once depends=init
- /target
-
target name=website depends=init
+!-- just to be sure, lets clean first --
+call target=call-clean/
+
+!-- all-jars should generate all the deployables --
+call target=all-jars/
/target
target name=website-install depends=init
+!-- we need to know where to deploy files to --
+require property=jboss.deploy.root/
+
+!-- copy the deployables --
+copy todir=${jboss.deploy.root}
+ fileset dir=${project.root}/manual/output/lib
+include name=manual.ear/
+ /fileset
+ fileset dir=${project.root}/website/output/lib
+include name=website.ear/
+ /fileset
+/copy
+
+!-- might have to touch some files to redeploy properly --
/target
/project
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/bin update-website.sh
User: user57 Date: 01/08/31 17:44:19 Modified:src/bin update-website.sh Log: o the build pulls from cvs, so I have to check in these with test data to make sure it works Revision ChangesPath 1.2 +13 -10newsite/src/bin/update-website.sh Index: update-website.sh === RCS file: /cvsroot/jboss/newsite/src/bin/update-website.sh,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- update-website.sh 2001/09/01 00:25:30 1.1 +++ update-website.sh 2001/09/01 00:44:19 1.2 @@ -6,7 +6,7 @@ ## ## ### == ### -# $Id: update-website.sh,v 1.1 2001/09/01 00:25:30 user57 Exp $ +# $Id: update-website.sh,v 1.2 2001/09/01 00:44:19 user57 Exp $ PROGNAME=`basename $0` DIRNAME=`dirname $0` @@ -24,8 +24,11 @@ CVS_OPTIONS=-z3 -d $CVSROOT # Where we will will work from -WORKDIR=$HOME/tmp/jboss/update-website +WORKROOT=$HOME/tmp/jboss/update-website +# Where we will deploy files too +DEPLOYROOT=/home/jason/new/java/JBoss-2.4.0_Jetty-3.1.RC8-1/jboss/deploy # change this to $HOME/JBoss/jboss/deploy + ## ## Print an informative message ## @@ -101,10 +104,10 @@ fi # setup the workdir, change to it -info Setting up WORKDIR: $WORKDIR -rm -rf $WORKDIR -mkdir -p $WORKDIR -cd $WORKDIR +info Setting up WORKROOT: $WORKROOT +rm -rf $WORKROOT +mkdir -p $WORKROOT +cd $WORKROOT # pull down a fresh copy of jboss-website info Pulling down a fresh copy of jboss-website @@ -123,15 +126,15 @@ checkBuild build 'website' was not successful $logfile # install the website -info Installing website -./build/build.sh website-install +info Installing website; DEPLOYROOT: $DEPLOYROOT +./build/build.sh -Djboss.deploy.root=$DEPLOYROOT website-install status=$? checkStatus $status 0 build 'website-install' failed $logfile checkBuild build 'website-install' was not successful $logfile # Clean up and say goodbye -info Cleaning up WORKDIR -rm -rf $WORKDIR +info Cleaning up WORKROOT +rm -rf $WORKROOT info Done } ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: build/website build.xml
User: user57 Date: 01/08/31 17:47:28 Modified:website build.xml Log: o there is no call-clean target... Revision ChangesPath 1.5 +2 -2 build/website/build.xml Index: build.xml === RCS file: /cvsroot/jboss/build/website/build.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- build.xml 2001/09/01 00:44:19 1.4 +++ build.xml 2001/09/01 00:47:28 1.5 @@ -10,7 +10,7 @@ !---- !-- == -- -!-- $Id: build.xml,v 1.4 2001/09/01 00:44:19 user57 Exp $ -- +!-- $Id: build.xml,v 1.5 2001/09/01 00:47:28 user57 Exp $ -- project default=main name=JBoss Website/Build @@ -419,7 +419,7 @@ target name=website depends=init !-- just to be sure, lets clean first -- -call target=call-clean/ +call target=all-clean/ !-- all-jars should generate all the deployables -- call target=all-jars/ ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: manual/src/xdocs/howto howtopetstore.xml
User: user57 Date: 01/08/31 17:56:48 Modified:src/xdocs/howto howtopetstore.xml Log: o fixed missing formalpara Revision ChangesPath 1.3 +1 -0 manual/src/xdocs/howto/howtopetstore.xml Index: howtopetstore.xml === RCS file: /cvsroot/jboss/manual/src/xdocs/howto/howtopetstore.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- howtopetstore.xml 2001/08/31 19:00:20 1.2 +++ howtopetstore.xml 2001/09/01 00:56:48 1.3 @@ -22,6 +22,7 @@ titleInitializing the Database/title paraThe current Pet Store application should automatically build required database tables the first time the Pet Store application is started. Apparently the latest database schema is slightly different from the earlier release, so you may encounter problems if you have an existing Pet Store database from a previous installation. When tring to determine the initial status of the database, this conflict may cause one of the drop commands to fail, and the application will not create the required tables. If this is the case, you may need to manually drop all existing tables before deploying the Pet Store for the first time./para /formalpara +formalpara titleThe Admin Client/title paraThe Admin application apparently needs some work on the deployment descriptors. Please post your experences with the Admin application to the mailing list./para /formalpara ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/bin update-website.sh
User: user57 Date: 01/08/31 18:06:58 Modified:src/bin update-website.sh Log: o so far so good... now for error testing Revision ChangesPath 1.3 +3 -2 newsite/src/bin/update-website.sh Index: update-website.sh === RCS file: /cvsroot/jboss/newsite/src/bin/update-website.sh,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- update-website.sh 2001/09/01 00:44:19 1.2 +++ update-website.sh 2001/09/01 01:06:58 1.3 @@ -6,7 +6,7 @@ ## ## ### == ### -# $Id: update-website.sh,v 1.2 2001/09/01 00:44:19 user57 Exp $ +# $Id: update-website.sh,v 1.3 2001/09/01 01:06:58 user57 Exp $ PROGNAME=`basename $0` DIRNAME=`dirname $0` @@ -21,7 +21,7 @@ # Setup CVS CVS=cvs CVSROOT=:pserver:[EMAIL PROTECTED]:/cvsroot/jboss -CVS_OPTIONS=-z3 -d $CVSROOT +CVS_OPTIONS=-q -r -f -z3 -d $CVSROOT # Where we will will work from WORKROOT=$HOME/tmp/jboss/update-website @@ -52,6 +52,7 @@ logfile=$2 $MAIL $MAILTO -s $subject $logfile +info Email notification sent to $MAILTO } ## ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite build.xml
User: user57
Date: 01/08/31 18:08:45
Modified:.build.xml
Log:
o added test bomb
Revision ChangesPath
1.5 +3 -1 newsite/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/newsite/build.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- build.xml 2001/09/01 00:44:19 1.4
+++ build.xml 2001/09/01 01:08:45 1.5
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.4 2001/09/01 00:44:19 user57 Exp $ --
+!-- $Id: build.xml,v 1.5 2001/09/01 01:08:45 user57 Exp $ --
project default=main name=JBoss/Website
@@ -249,6 +249,8 @@
!-- Compile cvs source snapshots --
target name=compile-snapshots depends=init
mkdir dir=${build.snapshots}/
+
+fail message=oops/
!-- Make sure there is an entry for this cvsroot --
cvspass cvsroot=${snapshot.cvsroot} password=/
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/bin catchlog.sh nightly-website.sh
User: user57 Date: 01/08/31 18:31:41 Modified:src/bin catchlog.sh nightly-website.sh Log: o minor logging updates, default to --quiet so we don't loose any logs from tee. o moved bomb to manual Revision ChangesPath 1.2 +8 -1 newsite/src/bin/catchlog.sh Index: catchlog.sh === RCS file: /cvsroot/jboss/newsite/src/bin/catchlog.sh,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- catchlog.sh 2001/09/01 00:25:30 1.1 +++ catchlog.sh 2001/09/01 01:31:40 1.2 @@ -6,7 +6,7 @@ ## ## ### == ### -# $Id: catchlog.sh,v 1.1 2001/09/01 00:25:30 user57 Exp $ +# $Id: catchlog.sh,v 1.2 2001/09/01 01:31:40 user57 Exp $ PROGNAME=`basename $0` DIRNAME=`dirname $0` @@ -120,17 +120,24 @@ if [ ! -f $logfile ]; then touch $logfile fi +echo Opened log: `date` $logfile # execute the program if [ x$quiet = x ]; then # use tee and let output display to the console $args | $TEE $append $logfile 21 + status=$? else # append all output to the log, nothing goes to console $args $logfile 21 + status=$? fi +# try to get file to flush +echo Closing log: `date` $logfile info Log saved to $logfile + +exit $status } ## 1.2 +6 -11 newsite/src/bin/nightly-website.sh Index: nightly-website.sh === RCS file: /cvsroot/jboss/newsite/src/bin/nightly-website.sh,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- nightly-website.sh2001/09/01 00:25:30 1.1 +++ nightly-website.sh2001/09/01 01:31:40 1.2 @@ -5,15 +5,11 @@ ## ## ### == ### -# $Id: nightly-website.sh,v 1.1 2001/09/01 00:25:30 user57 Exp $ +# $Id: nightly-website.sh,v 1.2 2001/09/01 01:31:40 user57 Exp $ PROGNAME=`basename $0` DIRNAME=`dirname $0` -# Setup Mail -MAIL=mail -MAILTO=[EMAIL PROTECTED] # change to [EMAIL PROTECTED] when done testing - # Where the required scripts live SCRIPTROOT=$DIRNAME @@ -21,14 +17,13 @@ DSTAMP=`date +%m%d%Y` # Where the logs will go -LOGROOT=$HOME/log -LOGFILE=$LOGROOT/nightly-website.log +LOGFILE=$HOME/log/nightly-website.log # Run the update-website.sh script. It must be wrapped with catchlog.sh, # because it uses the log file to determine build successes from it -$SCRIPTROOT/catchlog.sh --logfile $LOGFILE -- \ +$SCRIPTROOT/catchlog.sh \ +--quiet \ +--logfile $LOGFILE \ +-- \ $SCRIPTROOT/update-website.sh $LOGFILE - -# Send out email about the update -$MAIL $MAILTO -s Website updated successfully $LOGFILE ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite build.xml
User: user57
Date: 01/08/31 18:31:40
Modified:.build.xml
Log:
o minor logging updates, default to --quiet so we don't loose any logs
from tee.
o moved bomb to manual
Revision ChangesPath
1.6 +14 -16newsite/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/newsite/build.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- build.xml 2001/09/01 01:08:45 1.5
+++ build.xml 2001/09/01 01:31:40 1.6
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.5 2001/09/01 01:08:45 user57 Exp $ --
+!-- $Id: build.xml,v 1.6 2001/09/01 01:31:40 user57 Exp $ --
project default=main name=JBoss/Website
@@ -136,6 +136,11 @@
path refid=javac.classpath/
/path
+ !-- Controls for the compile-snapshot target --
+ property name=snapshot.cvsroot
+ value=:pserver:[EMAIL PROTECTED]:/cvsroot/jboss/
+ property name=snapshot.modules value=jboss-all/
+
!-- Where source files live --
property name=source.bin value=${module.source}/bin/
property name=source.metadata value=${module.source}/metadata/
@@ -241,25 +246,24 @@
/chmod
/target
- property name=snapshot.cvsroot
- value=:pserver:[EMAIL PROTECTED]:/cvsroot/jboss/
-
- property name=snapshot.modules value=jboss-all/
-
!-- Compile cvs source snapshots --
- target name=compile-snapshots depends=init
+ target name=compile-snapshots depends=init unless=snapshot.bypass
mkdir dir=${build.snapshots}/
-fail message=oops/
-
!-- Make sure there is an entry for this cvsroot --
cvspass cvsroot=${snapshot.cvsroot} password=/
cvs cvsroot=${snapshot.cvsroot}
- command=export
+ command=-q -r -f -z3 export
date=TODAY
package=jboss-all
dest=${build.snapshots}/
+
+zip zipfile=${build.jars}/jboss-all-${build.number}.zip
+ fileset dir=${build.snapshots}/jboss-all
+include name=**/*/
+ /fileset
+/zip
/target
@@ -285,12 +289,6 @@
include name=**/*/
/fileset
/war
-
-zip zipfile=${build.jars}/jboss-all-${build.number}.zip
- fileset dir=${build.snapshots}/jboss-all
-include name=**/*/
- /fileset
-/zip
war warfile=${build.jars}/snapshots.war
webxml=${build.metadata}/snapshots-web.xml
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: manual build.xml
User: user57
Date: 01/08/31 18:31:40
Modified:.build.xml
Log:
o minor logging updates, default to --quiet so we don't loose any logs
from tee.
o moved bomb to manual
Revision ChangesPath
1.16 +3 -1 manual/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/manual/build.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- build.xml 2001/08/31 05:30:31 1.15
+++ build.xml 2001/09/01 01:31:40 1.16
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.15 2001/08/31 05:30:31 user57 Exp $ --
+!-- $Id: build.xml,v 1.16 2001/09/01 01:31:40 user57 Exp $ --
project default=main
@@ -260,6 +260,8 @@
zipfileset prefix=printable dir=${build.html.printable}/
/war
+failboom.../fail
+
ear earfile=${build.jars}/manual.ear
appxml=${build.metadata}/manual-application.xml
fileset dir=${build.jars}
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite build.xml
User: user57
Date: 01/08/31 18:39:26
Modified:.build.xml
Log:
o trying to get exit status passed from update-website.sh to catchlog.sh
back to nightly-website.sh
Revision ChangesPath
1.7 +4 -1 newsite/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/newsite/build.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- build.xml 2001/09/01 01:31:40 1.6
+++ build.xml 2001/09/01 01:39:26 1.7
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.6 2001/09/01 01:31:40 user57 Exp $ --
+!-- $Id: build.xml,v 1.7 2001/09/01 01:39:26 user57 Exp $ --
project default=main name=JBoss/Website
@@ -258,6 +258,9 @@
date=TODAY
package=jboss-all
dest=${build.snapshots}/
+
+!-- to keep this simple, these jars task live here --
+mkdir dir=${build.jars}/
zip zipfile=${build.jars}/jboss-all-${build.number}.zip
fileset dir=${build.snapshots}/jboss-all
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/bin catchlog.sh nightly-website.sh
User: user57 Date: 01/08/31 18:39:26 Modified:src/bin catchlog.sh nightly-website.sh Log: o trying to get exit status passed from update-website.sh to catchlog.sh back to nightly-website.sh Revision ChangesPath 1.3 +2 -1 newsite/src/bin/catchlog.sh Index: catchlog.sh === RCS file: /cvsroot/jboss/newsite/src/bin/catchlog.sh,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- catchlog.sh 2001/09/01 01:31:40 1.2 +++ catchlog.sh 2001/09/01 01:39:26 1.3 @@ -6,7 +6,7 @@ ## ## ### == ### -# $Id: catchlog.sh,v 1.2 2001/09/01 01:31:40 user57 Exp $ +# $Id: catchlog.sh,v 1.3 2001/09/01 01:39:26 user57 Exp $ PROGNAME=`basename $0` DIRNAME=`dirname $0` @@ -132,6 +132,7 @@ $args $logfile 21 status=$? fi +info Exit status: $status # try to get file to flush echo Closing log: `date` $logfile 1.3 +12 -1 newsite/src/bin/nightly-website.sh Index: nightly-website.sh === RCS file: /cvsroot/jboss/newsite/src/bin/nightly-website.sh,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- nightly-website.sh2001/09/01 01:31:40 1.2 +++ nightly-website.sh2001/09/01 01:39:26 1.3 @@ -5,7 +5,7 @@ ## ## ### == ### -# $Id: nightly-website.sh,v 1.2 2001/09/01 01:31:40 user57 Exp $ +# $Id: nightly-website.sh,v 1.3 2001/09/01 01:39:26 user57 Exp $ PROGNAME=`basename $0` DIRNAME=`dirname $0` @@ -19,6 +19,14 @@ # Where the logs will go LOGFILE=$HOME/log/nightly-website.log +# Setup Mail +MAIL=mail +MAILTO=[EMAIL PROTECTED] # change to [EMAIL PROTECTED] when done testing + +# Setup CVS +CVSROOT=:pserver:[EMAIL PROTECTED]:/cvsroot/jboss +export CVSROOT + # Run the update-website.sh script. It must be wrapped with catchlog.sh, # because it uses the log file to determine build successes from it @@ -27,3 +35,6 @@ --logfile $LOGFILE \ -- \ $SCRIPTROOT/update-website.sh $LOGFILE + +status=$? +echo Exit status: $status ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] requirements for build
|No worries, nothing is dependent on cygwin. But I don't have the patience |to deal with maintaining a batch script. I have agreed to this experiment with the understanding that it would not break portability. If it does because you don't maintain it and you put the windows developers (80% of our developers) through pain then this is a failed experiment. you work up that fucking patience or it is me that is going to run out of it with you marcf ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss daily build failed
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
Searching for build.xml ...
Buildfile: /home/lubega/jbossro/jboss-all/build/build.xml
init-buildlog:
init:
[echo] user.home = /home/lubega
[echo] build.compiler = ${build.compiler}
[echo] java.home = /opt/jdk1.3_ibm_20010723/jre
[echo] java.class.path =
/home/lubega/jbossro/jboss-all/tools/lib/xerces.jar:/home/lubega/jbossro/jboss-all/tools/lib/xalan.jar:/home/lubega/jbossro/jboss-all/tools/lib/stylebook.jar:/home/lubega/jbossro/jboss-all/tools/lib/saxon.jar:/home/lubega/jbossro/jboss-all/tools/lib/pretty.jar:/home/lubega/jbossro/jboss-all/tools/lib/optional.jar:/home/lubega/jbossro/jboss-all/tools/lib/junit.jar:/home/lubega/jbossro/jboss-all/tools/lib/jaxp.jar:/home/lubega/jbossro/jboss-all/tools/lib/JavaStyle.jar:/home/lubega/jbossro/jboss-all/tools/lib/javac.jar:/home/lubega/jbossro/jboss-all/tools/lib/fop.jar:/home/lubega/jbossro/jboss-all/tools/lib/ejbdoclet.jar:/home/lubega/jbossro/jboss-all/tools/lib/crimson.jar:/home/lubega/jbossro/jboss-all/tools/lib/buildmagic-tasks.jar:/home/lubega/jbossro/jboss-all/tools/lib/bsf.jar:/home/lubega/jbossro/jboss-all/tools/lib/batik.jar:/home/lubega/jbossro/jboss-all/tools/lib/ant.jar:/opt/jdk1.3_ibm_20010723/lib/tools.jar
[echo] java.version = 1.3.0
[echo] java.vendor = IBM Corporation
[echo] java.vm.version = 1.3.0
[echo] java.vm.name = Classic VM
[echo] java.vm.info = J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)
[echo] os.name = Linux
[echo] os.arch = Linux
[echo] os.version = Linux
[echo]
configure:
[projectinfo] Project root: /home/lubega/jbossro/jboss-all
[projectinfo] Modules:
j2ee,naming,server,security,messaging,connector,pool,cluster,admin,testsuite,plugins/varia,plugins/jetty
all-release:
[execmodules]
==
== Executing 'release' in module 'j2ee'...
==
init-buildlog:
init:
[moduleinfo] Project root: /home/lubega/jbossro/jboss-all
[moduleinfo] Module root: /home/lubega/jbossro/jboss-all/j2ee
compile-classes:
[mkdir] Created dir: /home/lubega/jbossro/jboss-all/j2ee/output/classes
[javac] Compiling 154 source files to
/home/lubega/jbossro/jboss-all/j2ee/output/classes
[execmodules]
/home/lubega/jbossro/jboss-all/j2ee/src/main/javax/ejb/EJBContext.java:31: warning:
java.security.Identity in java.security has been deprecated
[execmodules] public Identity getCallerIdentity();
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/j2ee/src/main/javax/ejb/EJBContext.java:112: warning:
java.security.Identity in java.security has been deprecated
[execmodules] public boolean isCallerInRole(Identity role);
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/j2ee/src/main/javax/ejb/EJBContext.java:112: warning:
java.security.Identity in java.security has been deprecated
[execmodules] public boolean isCallerInRole(Identity role);
[execmodules] ^
[execmodules] 3 warnings
compile:
jars:
[mkdir] Created dir: /home/lubega/jbossro/jboss-all/j2ee/output/lib
[jar] Building jar: /home/lubega/jbossro/jboss-all/j2ee/output/lib/jboss-j2ee.jar
javadocs-check:
[mkdir] Created dir: /home/lubega/jbossro/jboss-all/j2ee/output/api
javadocs:
docs-api:
docs:
all:
release:
[mkdir] Created dir:
/home/lubega/jbossro/jboss-all/build/output/jboss-3.0.0alpha-DEV/lib/ext
[copy] Copying 1 file to
/home/lubega/jbossro/jboss-all/build/output/jboss-3.0.0alpha-DEV/lib/ext
[mkdir] Created dir:
/home/lubega/jbossro/jboss-all/build/output/jboss-3.0.0alpha-DEV/client
[copy] Copying 1 file to
/home/lubega/jbossro/jboss-all/build/output/jboss-3.0.0alpha-DEV/client
[mkdir] Created dir:
/home/lubega/jbossro/jboss-all/build/output/jboss-3.0.0alpha-DEV/docs/api/j2ee
[execmodules]
==
== Finished with 'release' in module 'j2ee'.
==
[execmodules]
==
== Executing 'release' in module 'naming'...
==
init-buildlog:
init:
[moduleinfo] Project root: /home/lubega/jbossro/jboss-all
[moduleinfo] Module root: /home/lubega/jbossro/jboss-all/naming
compile-classes:
[mkdir] Created dir: /home/lubega/jbossro/jboss-all/naming/output/classes
[javac] Compiling 12 source files to
/home/lubega/jbossro/jboss-all/naming/output/classes
compile-rmi:
[rmic] Verify has been turned on.
[rmic] RMI Compiling 1 class to
/home/lubega/jbossro/jboss-all/naming/output/classes
compile-etc:
[mkdir] Created dir: /home/lubega/jbossro/jboss-all/naming/output/etc
[copy] Copying 6 files to
[JBoss-dev] jboss daily test failed
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
Searching for build.xml ...
Buildfile: /home/lubega/jbossro/jboss-all/build/build.xml
init-buildlog:
init:
[echo] user.home = /home/lubega
[echo] build.compiler = ${build.compiler}
[echo] java.home = /opt/jdk1.3_ibm_20010723/jre
[echo] java.class.path =
/home/lubega/jbossro/jboss-all/tools/lib/xerces.jar:/home/lubega/jbossro/jboss-all/tools/lib/xalan.jar:/home/lubega/jbossro/jboss-all/tools/lib/stylebook.jar:/home/lubega/jbossro/jboss-all/tools/lib/saxon.jar:/home/lubega/jbossro/jboss-all/tools/lib/pretty.jar:/home/lubega/jbossro/jboss-all/tools/lib/optional.jar:/home/lubega/jbossro/jboss-all/tools/lib/junit.jar:/home/lubega/jbossro/jboss-all/tools/lib/jaxp.jar:/home/lubega/jbossro/jboss-all/tools/lib/JavaStyle.jar:/home/lubega/jbossro/jboss-all/tools/lib/javac.jar:/home/lubega/jbossro/jboss-all/tools/lib/fop.jar:/home/lubega/jbossro/jboss-all/tools/lib/ejbdoclet.jar:/home/lubega/jbossro/jboss-all/tools/lib/crimson.jar:/home/lubega/jbossro/jboss-all/tools/lib/buildmagic-tasks.jar:/home/lubega/jbossro/jboss-all/tools/lib/bsf.jar:/home/lubega/jbossro/jboss-all/tools/lib/batik.jar:/home/lubega/jbossro/jboss-all/tools/lib/ant.jar:/opt/jdk1.3_ibm_20010723/lib/tools.jar
[echo] java.version = 1.3.0
[echo] java.vendor = IBM Corporation
[echo] java.vm.version = 1.3.0
[echo] java.vm.name = Classic VM
[echo] java.vm.info = J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)
[echo] os.name = Linux
[echo] os.arch = Linux
[echo] os.version = Linux
[echo]
configure:
[projectinfo] Project root: /home/lubega/jbossro/jboss-all
[projectinfo] Modules:
j2ee,naming,server,security,messaging,connector,pool,cluster,admin,testsuite,plugins/varia,plugins/jetty
run-testsuite:
[execmodules]
==
== Executing 'tests' in module 'testsuite'...
==
init-buildlog:
init:
[moduleinfo] Project root: /home/lubega/jbossro/jboss-all
[moduleinfo] Module root: /home/lubega/jbossro/jboss-all/testsuite
compile-classes:
[mkdir] Created dir: /home/lubega/jbossro/jboss-all/testsuite/output/classes
[javac] Compiling 274 source files to
/home/lubega/jbossro/jboss-all/testsuite/output/classes
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:8:
cannot resolve symbol
[execmodules] symbol : class Identifier
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.Identifier;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:9:
cannot resolve symbol
[execmodules] symbol : class Operator
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.Operator;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:10:
cannot resolve symbol
[execmodules] symbol : class SelectorParser
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.SelectorParser;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:11:
cannot resolve symbol
[execmodules] symbol : class ISelectorParser
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.ISelectorParser;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:21:
cannot resolve symbol
[execmodules] symbol : class ISelectorParser
[execmodules] location: class org.jboss.test.jbossmq.test.TestSelectorParser
[execmodules] static ISelectorParser parser;
[execmodules]^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:140:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert(!clct.isEmpty());
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:148:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert(bean.getPersonsName().trim().equals(BEAN_NAME));
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:270:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert( this.gotRefOkay(bean, BEAN_NAME) );
[execmodules] ^
[execmodules]
[JBoss-dev] jboss daily test failed
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
Searching for build.xml ...
Buildfile: /home/lubega/jbossro/jboss-all/build/build.xml
init-buildlog:
init:
[echo] user.home = /home/lubega
[echo] build.compiler = ${build.compiler}
[echo] java.home = /opt/jdk1.3.1_blackdown/jre
[echo] java.class.path =
/home/lubega/jbossro/jboss-all/tools/lib/xerces.jar:/home/lubega/jbossro/jboss-all/tools/lib/xalan.jar:/home/lubega/jbossro/jboss-all/tools/lib/stylebook.jar:/home/lubega/jbossro/jboss-all/tools/lib/saxon.jar:/home/lubega/jbossro/jboss-all/tools/lib/pretty.jar:/home/lubega/jbossro/jboss-all/tools/lib/optional.jar:/home/lubega/jbossro/jboss-all/tools/lib/junit.jar:/home/lubega/jbossro/jboss-all/tools/lib/jaxp.jar:/home/lubega/jbossro/jboss-all/tools/lib/JavaStyle.jar:/home/lubega/jbossro/jboss-all/tools/lib/javac.jar:/home/lubega/jbossro/jboss-all/tools/lib/fop.jar:/home/lubega/jbossro/jboss-all/tools/lib/ejbdoclet.jar:/home/lubega/jbossro/jboss-all/tools/lib/crimson.jar:/home/lubega/jbossro/jboss-all/tools/lib/buildmagic-tasks.jar:/home/lubega/jbossro/jboss-all/tools/lib/bsf.jar:/home/lubega/jbossro/jboss-all/tools/lib/batik.jar:/home/lubega/jbossro/jboss-all/tools/lib/ant.jar:/opt/jdk1.3.1_blackdown/lib/tools.jar
[echo] java.version = 1.3.1
[echo] java.vendor = Blackdown Java-Linux Team
[echo] java.vm.version = Blackdown-1.3.1-FCS
[echo] java.vm.name = Classic VM
[echo] java.vm.info = green threads, nojit
[echo] os.name = Linux
[echo] os.arch = Linux
[echo] os.version = Linux
[echo]
configure:
[projectinfo] Project root: /home/lubega/jbossro/jboss-all
[projectinfo] Modules:
j2ee,naming,server,security,messaging,connector,pool,cluster,admin,testsuite,plugins/varia,plugins/jetty
run-testsuite:
[execmodules]
==
== Executing 'tests' in module 'testsuite'...
==
init-buildlog:
init:
[moduleinfo] Project root: /home/lubega/jbossro/jboss-all
[moduleinfo] Module root: /home/lubega/jbossro/jboss-all/testsuite
compile-classes:
[mkdir] Created dir: /home/lubega/jbossro/jboss-all/testsuite/output/classes
[javac] Compiling 274 source files to
/home/lubega/jbossro/jboss-all/testsuite/output/classes
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:8:
cannot resolve symbol
[execmodules] symbol : class Identifier
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.Identifier;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:9:
cannot resolve symbol
[execmodules] symbol : class Operator
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.Operator;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:10:
cannot resolve symbol
[execmodules] symbol : class SelectorParser
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.SelectorParser;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:11:
cannot resolve symbol
[execmodules] symbol : class ISelectorParser
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.ISelectorParser;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:21:
cannot resolve symbol
[execmodules] symbol : class ISelectorParser
[execmodules] location: class org.jboss.test.jbossmq.test.TestSelectorParser
[execmodules] static ISelectorParser parser;
[execmodules]^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:140:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert(!clct.isEmpty());
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:148:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert(bean.getPersonsName().trim().equals(BEAN_NAME));
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:270:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert( this.gotRefOkay(bean, BEAN_NAME) );
[execmodules] ^
[execmodules]
RE: [JBoss-dev] requirements for build
|No worries, nothing is dependent on cygwin. But I don't have the patience |to deal with maintaining a batch script. I have agreed to this experiment with the understanding that it would not break portability. If it does because you don't maintain it and you put the windows developers (80% of our developers) through pain then this is a failed experiment. I do not wish to break portability, I just need some help to make the batch stuff as good as the /bin/sh bits. That is all I meant. you work up that fucking patience or it is me that is going to run out of it with you Chill. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss daily test failed
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
Searching for build.xml ...
Buildfile: /home/lubega/jbossro/jboss-all/build/build.xml
init-buildlog:
init:
[echo] user.home = /home/lubega
[echo] build.compiler = ${build.compiler}
[echo] java.home = /opt/jdk1.3.1_sun/jre
[echo] java.class.path =
/home/lubega/jbossro/jboss-all/tools/lib/xerces.jar:/home/lubega/jbossro/jboss-all/tools/lib/xalan.jar:/home/lubega/jbossro/jboss-all/tools/lib/stylebook.jar:/home/lubega/jbossro/jboss-all/tools/lib/saxon.jar:/home/lubega/jbossro/jboss-all/tools/lib/pretty.jar:/home/lubega/jbossro/jboss-all/tools/lib/optional.jar:/home/lubega/jbossro/jboss-all/tools/lib/junit.jar:/home/lubega/jbossro/jboss-all/tools/lib/jaxp.jar:/home/lubega/jbossro/jboss-all/tools/lib/JavaStyle.jar:/home/lubega/jbossro/jboss-all/tools/lib/javac.jar:/home/lubega/jbossro/jboss-all/tools/lib/fop.jar:/home/lubega/jbossro/jboss-all/tools/lib/ejbdoclet.jar:/home/lubega/jbossro/jboss-all/tools/lib/crimson.jar:/home/lubega/jbossro/jboss-all/tools/lib/buildmagic-tasks.jar:/home/lubega/jbossro/jboss-all/tools/lib/bsf.jar:/home/lubega/jbossro/jboss-all/tools/lib/batik.jar:/home/lubega/jbossro/jboss-all/tools/lib/ant.jar:/opt/jdk1.3.1_sun/lib/tools.jar
[echo] java.version = 1.3.1
[echo] java.vendor = Sun Microsystems Inc.
[echo] java.vm.version = 1.3.1-b24
[echo] java.vm.name = Java HotSpot(TM) Client VM
[echo] java.vm.info = mixed mode
[echo] os.name = Linux
[echo] os.arch = Linux
[echo] os.version = Linux
[echo]
configure:
[projectinfo] Project root: /home/lubega/jbossro/jboss-all
[projectinfo] Modules:
j2ee,naming,server,security,messaging,connector,pool,cluster,admin,testsuite,plugins/varia,plugins/jetty
run-testsuite:
[execmodules]
==
== Executing 'tests' in module 'testsuite'...
==
init-buildlog:
init:
[moduleinfo] Project root: /home/lubega/jbossro/jboss-all
[moduleinfo] Module root: /home/lubega/jbossro/jboss-all/testsuite
compile-classes:
[mkdir] Created dir: /home/lubega/jbossro/jboss-all/testsuite/output/classes
[javac] Compiling 274 source files to
/home/lubega/jbossro/jboss-all/testsuite/output/classes
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:8:
cannot resolve symbol
[execmodules] symbol : class Identifier
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.Identifier;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:9:
cannot resolve symbol
[execmodules] symbol : class Operator
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.Operator;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:10:
cannot resolve symbol
[execmodules] symbol : class SelectorParser
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.SelectorParser;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:11:
cannot resolve symbol
[execmodules] symbol : class ISelectorParser
[execmodules] location: package selectors
[execmodules] import org.jboss.mq.selectors.ISelectorParser;
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/jbossmq/test/TestSelectorParser.java:21:
cannot resolve symbol
[execmodules] symbol : class ISelectorParser
[execmodules] location: class org.jboss.test.jbossmq.test.TestSelectorParser
[execmodules] static ISelectorParser parser;
[execmodules]^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:140:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert(!clct.isEmpty());
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:148:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert(bean.getPersonsName().trim().equals(BEAN_NAME));
[execmodules] ^
[execmodules]
/home/lubega/jbossro/jboss-all/testsuite/src/main/org/jboss/test/cts/test/BmpTest.java:270:
warning: assert(boolean) in junit.framework.Assert has been deprecated
[execmodules] assert( this.gotRefOkay(bean, BEAN_NAME) );
[execmodules] ^
[execmodules]
[JBoss-dev] CVS update: manual build.xml
User: user57
Date: 01/08/31 19:20:52
Modified:.build.xml
Log:
o moved mailing upto nightly-website.sh
o catchlog.sh will return the exit status of its child
o status 2 means that the install failed, website could be down
Revision ChangesPath
1.17 +1 -3 manual/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/manual/build.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- build.xml 2001/09/01 01:31:40 1.16
+++ build.xml 2001/09/01 02:20:52 1.17
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.16 2001/09/01 01:31:40 user57 Exp $ --
+!-- $Id: build.xml,v 1.17 2001/09/01 02:20:52 user57 Exp $ --
project default=main
@@ -260,8 +260,6 @@
zipfileset prefix=printable dir=${build.html.printable}/
/war
-failboom.../fail
-
ear earfile=${build.jars}/manual.ear
appxml=${build.metadata}/manual-application.xml
fileset dir=${build.jars}
___
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/08/31 19:20:52
Modified:website build.xml
Log:
o moved mailing upto nightly-website.sh
o catchlog.sh will return the exit status of its child
o status 2 means that the install failed, website could be down
Revision ChangesPath
1.6 +3 -1 build/website/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/build/website/build.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- build.xml 2001/09/01 00:47:28 1.5
+++ build.xml 2001/09/01 02:20:52 1.6
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.5 2001/09/01 00:47:28 user57 Exp $ --
+!-- $Id: build.xml,v 1.6 2001/09/01 02:20:52 user57 Exp $ --
project default=main name=JBoss Website/Build
@@ -428,6 +428,8 @@
target name=website-install depends=init
!-- we need to know where to deploy files to --
require property=jboss.deploy.root/
+
+failboom/fail
!-- copy the deployables --
copy todir=${jboss.deploy.root}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/bin catchlog.sh nightly-website.sh update-website.sh
User: user57
Date: 01/08/31 19:20:53
Modified:src/bin catchlog.sh nightly-website.sh update-website.sh
Log:
o moved mailing upto nightly-website.sh
o catchlog.sh will return the exit status of its child
o status 2 means that the install failed, website could be down
Revision ChangesPath
1.4 +7 -8 newsite/src/bin/catchlog.sh
Index: catchlog.sh
===
RCS file: /cvsroot/jboss/newsite/src/bin/catchlog.sh,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- catchlog.sh 2001/09/01 01:39:26 1.3
+++ catchlog.sh 2001/09/01 02:20:53 1.4
@@ -6,7 +6,7 @@
## ##
### == ###
-# $Id: catchlog.sh,v 1.3 2001/09/01 01:39:26 user57 Exp $
+# $Id: catchlog.sh,v 1.4 2001/09/01 02:20:53 user57 Exp $
PROGNAME=`basename $0`
DIRNAME=`dirname $0`
@@ -36,9 +36,9 @@
usage: $PROGNAME [options] [--] program to execute
options:
---logfile, -l logfileThe file where output will be stored
+--logfile, -f logfileThe file where output will be stored
--append, -a Append to the log file
---quiet, -qTry to be quite
+--quiet, -qTry to be quite [non-quiet uses $TEE]
--help, -h Show this help message
-- Stop processing options
EOF
@@ -68,7 +68,7 @@
# parse the command line
while [ x$1 != x ]; do
case $1 in
- --logfile|-l)
+ --logfile|-f)
if [ x$2 = x ]; then
die --logfile requires an additional argument
fi
@@ -120,7 +120,7 @@
if [ ! -f $logfile ]; then
touch $logfile
fi
-echo Opened log: `date` $logfile
+info Opened log: `date` $logfile
# execute the program
if [ x$quiet = x ]; then
@@ -132,11 +132,10 @@
$args $logfile 21
status=$?
fi
-info Exit status: $status
+info Exit status: $status $logfile
# try to get file to flush
-echo Closing log: `date` $logfile
-info Log saved to $logfile
+info Closing log: `date` $logfile
exit $status
}
1.4 +68 -19newsite/src/bin/nightly-website.sh
Index: nightly-website.sh
===
RCS file: /cvsroot/jboss/newsite/src/bin/nightly-website.sh,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- nightly-website.sh2001/09/01 01:39:26 1.3
+++ nightly-website.sh2001/09/01 02:20:53 1.4
@@ -5,7 +5,7 @@
## ##
### == ###
-# $Id: nightly-website.sh,v 1.3 2001/09/01 01:39:26 user57 Exp $
+# $Id: nightly-website.sh,v 1.4 2001/09/01 02:20:53 user57 Exp $
PROGNAME=`basename $0`
DIRNAME=`dirname $0`
@@ -13,28 +13,77 @@
# Where the required scripts live
SCRIPTROOT=$DIRNAME
-# A date stamp
-DSTAMP=`date +%m%d%Y`
-
# Where the logs will go
LOGFILE=$HOME/log/nightly-website.log
# Setup Mail
MAIL=mail
MAILTO=[EMAIL PROTECTED] # change to [EMAIL PROTECTED] when done testing
-
-# Setup CVS
-CVSROOT=:pserver:[EMAIL PROTECTED]:/cvsroot/jboss
-export CVSROOT
-
-# Run the update-website.sh script. It must be wrapped with catchlog.sh,
-# because it uses the log file to determine build successes from it
-
-$SCRIPTROOT/catchlog.sh \
---quiet \
---logfile $LOGFILE \
--- \
-$SCRIPTROOT/update-website.sh $LOGFILE
-status=$?
-echo Exit status: $status
+##
+## Print an informative message
+##
+info() {
+echo ${PROGNAME}: $*
+}
+
+##
+## Print an error message and exit
+##
+die() {
+if [ x$exitcode = x ]; then
+ exitcode=1
+fi
+info $*
+exit $exitcode
+}
+
+##
+## Mail out a log file to the MAILTO list
+##
+maillog() {
+subject=$1
+logfile=$2
+
+$MAIL $MAILTO -s $subject $logfile
+info Email notification sent to $MAILTO
+}
+
+##
+## Where all the fun stuff happens
+##
+main() {
+# Run the update-website.sh script. It must be wrapped with catchlog.sh,
+# because it uses the log file to determine build successes from it
+
+$SCRIPTROOT/catchlog.sh \
+ --quiet \
+ --logfile $LOGFILE \
+ -- \
+ $SCRIPTROOT/update-website.sh $LOGFILE
+status=$?
+
+case $status in
+ 0)
+ # everything is ok
+ true
+ ;;
+
+ 2)
+ # website might be down
+
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/pm/jdbc PersistenceManager.java
User: user57
Date: 01/08/31 19:23:52
Modified:src/main/org/jboss/mq/pm/jdbc PersistenceManager.java
Log:
o ServiceMBeanSupport changed packages
Revision ChangesPath
1.5 +7 -4 jbossmq/src/main/org/jboss/mq/pm/jdbc/PersistenceManager.java
Index: PersistenceManager.java
===
RCS file:
/cvsroot/jboss/jbossmq/src/main/org/jboss/mq/pm/jdbc/PersistenceManager.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- PersistenceManager.java 2001/08/31 04:39:08 1.4
+++ PersistenceManager.java 2001/09/01 02:23:52 1.5
@@ -22,7 +22,7 @@
import java.sql.*;
import java.io.*;
-import org.jboss.util.ServiceMBeanSupport;
+import org.jboss.system.ServiceMBeanSupport;
import org.jboss.mq.SpyDestination;
import org.jboss.mq.xml.XElement;
import org.jboss.mq.ConnectionToken;
@@ -38,9 +38,12 @@
*
* @author: Jayesh Parayali ([EMAIL PROTECTED])
*
- * @version $Revision: 1.4 $
+ * @version $Revision: 1.5 $
*/
-public class PersistenceManager extends org.jboss.util.ServiceMBeanSupport
implements PersistenceManagerMBean, org.jboss.mq.pm.PersistenceManager {
+public class PersistenceManager
+ extends ServiceMBeanSupport
+ implements PersistenceManagerMBean, org.jboss.mq.pm.PersistenceManager
+{
protected static DataSource datasource;
@@ -310,4 +313,4 @@
txLog.rollbackTx(txId);
}
-}
\ No newline at end of file
+}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] XML config files, whitespace and CDATA... and JAXB
Did you ever look into this more? --jason On Thu, 9 Aug 2001, David Jencks wrote: On 2001.08.09 17:30:51 -0400 Toby Allsopp wrote: On Wed, Aug 08, 2001 at 11:30:39PM -0400, David Jencks wrote: At the risk of changing the subject ;-) There seem to be two xml-configuration parsing systems in use. The older stuff like for ejb-jar uses code that partially validates the xml while setting properties, whereas the rar deployer uses a reflection based scheme that pretty completely separates the xml structure from the property setting. I like the reflection-based structure-independent way better, although I think it should only be used with a dtd and xml parser validation-- although this should be done anyway imho. Does anyone else have an opinion? Well, I'm quite partial to the reflection-based technique :-) Me too!! Good work Toby!! It will run into problems with complicated data structures because it pretty much just flattens the XML file into a series of setAttribute calls. I didn't find this problem, I made a pretty complicated data structure load. I used [collections of] inner classes, and the appropriate setXXX method created an inner class instance and had the reflective parser call the setYYY on the inner class. This was for the rule engine adapter I worked on, the rules and other config was all in xml. Still I'll have to look at the Castor stuff. Hmmm, just looked at sun - there's something called JAXB that apparently compiles an xml schema into a custom parser that does 2 way translation between xml and an object tree. Since this is an impending standard it will presumably be the way to go.. for castor as well. david jencks Toby. ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] http://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: newsite/src/bin catchlog.sh nightly-website.sh update-website.sh
User: user57
Date: 01/08/31 19:35:39
Modified:src/bin catchlog.sh nightly-website.sh update-website.sh
Log:
o one last test for good measure.
Revision ChangesPath
1.5 +5 -1 newsite/src/bin/catchlog.sh
Index: catchlog.sh
===
RCS file: /cvsroot/jboss/newsite/src/bin/catchlog.sh,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- catchlog.sh 2001/09/01 02:20:53 1.4
+++ catchlog.sh 2001/09/01 02:35:39 1.5
@@ -6,7 +6,11 @@
## ##
### == ###
-# $Id: catchlog.sh,v 1.4 2001/09/01 02:20:53 user57 Exp $
+# $Id: catchlog.sh,v 1.5 2001/09/01 02:35:39 user57 Exp $
+
+##
+## Returns exit code from child process.
+##
PROGNAME=`basename $0`
DIRNAME=`dirname $0`
1.5 +3 -3 newsite/src/bin/nightly-website.sh
Index: nightly-website.sh
===
RCS file: /cvsroot/jboss/newsite/src/bin/nightly-website.sh,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- nightly-website.sh2001/09/01 02:20:53 1.4
+++ nightly-website.sh2001/09/01 02:35:39 1.5
@@ -5,7 +5,7 @@
## ##
### == ###
-# $Id: nightly-website.sh,v 1.4 2001/09/01 02:20:53 user57 Exp $
+# $Id: nightly-website.sh,v 1.5 2001/09/01 02:35:39 user57 Exp $
PROGNAME=`basename $0`
DIRNAME=`dirname $0`
@@ -72,13 +72,13 @@
2)
# website might be down
info Unexpected child exit status; got $status, wanted 0
- maillog ${PROGNAME}: failed to install website (may be down) $LOGFILE
+ maillog FATAL: failed to install website (may be down) $LOGFILE
;;
*)
# a generic failure
info Unexpected child exit status; got $status, wanted 0
- maillog ${PROGNAME}: failed to update website $LOGFILE
+ maillog ERROR: failed to update website $LOGFILE
;;
esac
}
1.5 +5 -1 newsite/src/bin/update-website.sh
Index: update-website.sh
===
RCS file: /cvsroot/jboss/newsite/src/bin/update-website.sh,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- update-website.sh 2001/09/01 02:20:53 1.4
+++ update-website.sh 2001/09/01 02:35:39 1.5
@@ -6,7 +6,11 @@
## ##
### == ###
-# $Id: update-website.sh,v 1.4 2001/09/01 02:20:53 user57 Exp $
+# $Id: update-website.sh,v 1.5 2001/09/01 02:35:39 user57 Exp $
+
+##
+## Returns exit status 0 for success, 1 for errors and 2 for fatal errors.
+##
PROGNAME=`basename $0`
DIRNAME=`dirname $0`
___
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/08/31 19:35:39
Modified:.build.xml
Log:
o one last test for good measure.
Revision ChangesPath
1.8 +3 -1 newsite/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/newsite/build.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- build.xml 2001/09/01 01:39:26 1.7
+++ build.xml 2001/09/01 02:35:39 1.8
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.7 2001/09/01 01:39:26 user57 Exp $ --
+!-- $Id: build.xml,v 1.8 2001/09/01 02:35:39 user57 Exp $ --
project default=main name=JBoss/Website
@@ -249,6 +249,8 @@
!-- Compile cvs source snapshots --
target name=compile-snapshots depends=init unless=snapshot.bypass
mkdir dir=${build.snapshots}/
+
+failboom/fail
!-- Make sure there is an entry for this cvsroot --
cvspass cvsroot=${snapshot.cvsroot} password=/
___
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/08/31 19:35:32
Modified:website build.xml
Log:
o one last test for good measure.
Revision ChangesPath
1.7 +1 -3 build/website/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/build/website/build.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- build.xml 2001/09/01 02:20:52 1.6
+++ build.xml 2001/09/01 02:35:31 1.7
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.6 2001/09/01 02:20:52 user57 Exp $ --
+!-- $Id: build.xml,v 1.7 2001/09/01 02:35:31 user57 Exp $ --
project default=main name=JBoss Website/Build
@@ -428,8 +428,6 @@
target name=website-install depends=init
!-- we need to know where to deploy files to --
require property=jboss.deploy.root/
-
-failboom/fail
!-- copy the deployables --
copy todir=${jboss.deploy.root}
___
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/08/31 19:38:19
Modified:.build.xml
Log:
o removing the bomb
Revision ChangesPath
1.9 +1 -3 newsite/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/newsite/build.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- build.xml 2001/09/01 02:35:39 1.8
+++ build.xml 2001/09/01 02:38:18 1.9
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.8 2001/09/01 02:35:39 user57 Exp $ --
+!-- $Id: build.xml,v 1.9 2001/09/01 02:38:18 user57 Exp $ --
project default=main name=JBoss/Website
@@ -249,8 +249,6 @@
!-- Compile cvs source snapshots --
target name=compile-snapshots depends=init unless=snapshot.bypass
mkdir dir=${build.snapshots}/
-
-failboom/fail
!-- Make sure there is an entry for this cvsroot --
cvspass cvsroot=${snapshot.cvsroot} password=/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/bin nightly-website.sh
User: user57 Date: 01/08/31 19:47:22 Modified:src/bin nightly-website.sh Log: o using the real MAILTO address Revision ChangesPath 1.6 +2 -2 newsite/src/bin/nightly-website.sh Index: nightly-website.sh === RCS file: /cvsroot/jboss/newsite/src/bin/nightly-website.sh,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- nightly-website.sh2001/09/01 02:35:39 1.5 +++ nightly-website.sh2001/09/01 02:47:22 1.6 @@ -5,7 +5,7 @@ ## ## ### == ### -# $Id: nightly-website.sh,v 1.5 2001/09/01 02:35:39 user57 Exp $ +# $Id: nightly-website.sh,v 1.6 2001/09/01 02:47:22 user57 Exp $ PROGNAME=`basename $0` DIRNAME=`dirname $0` @@ -18,7 +18,7 @@ # Setup Mail MAIL=mail -MAILTO=[EMAIL PROTECTED] # change to [EMAIL PROTECTED] when done testing +MAILTO=[EMAIL PROTECTED] ## ## Print an informative message ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: manual/src/xdocs jbossdocs.xml
User: user57 Date: 01/08/31 19:52:42 Modified:src/xdocs jbossdocs.xml Log: o added pubdate, so it is easier to tell when the manual was last updated Revision ChangesPath 1.2 +2 -1 manual/src/xdocs/jbossdocs.xml Index: jbossdocs.xml === RCS file: /cvsroot/jboss/manual/src/xdocs/jbossdocs.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- jbossdocs.xml 2001/08/29 09:19:36 1.1 +++ jbossdocs.xml 2001/09/01 02:52:42 1.2 @@ -39,7 +39,7 @@ !ENTITY howtoclientapplet.xmlSYSTEM howto/howtoclientapplet.xml ] -!-- $Id: jbossdocs.xml,v 1.1 2001/08/29 09:19:36 user57 Exp $ -- +!-- $Id: jbossdocs.xml,v 1.2 2001/09/01 02:52:42 user57 Exp $ -- book bookinfo @@ -49,6 +49,7 @@ year2001/year holderJBoss Organization/holder /copyright + pubdate@TODAY@/pubdate /bookinfo preface.xml; ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: newsite/src/bin nightly-website.sh
User: user57
Date: 01/08/31 19:55:52
Modified:src/bin nightly-website.sh
Log:
o allowing MAILTO to be overriden on the command line, logs a warning message
in that case.
Revision ChangesPath
1.7 +9 -5 newsite/src/bin/nightly-website.sh
Index: nightly-website.sh
===
RCS file: /cvsroot/jboss/newsite/src/bin/nightly-website.sh,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- nightly-website.sh2001/09/01 02:47:22 1.6
+++ nightly-website.sh2001/09/01 02:55:52 1.7
@@ -5,7 +5,7 @@
## ##
### == ###
-# $Id: nightly-website.sh,v 1.6 2001/09/01 02:47:22 user57 Exp $
+# $Id: nightly-website.sh,v 1.7 2001/09/01 02:55:52 user57 Exp $
PROGNAME=`basename $0`
DIRNAME=`dirname $0`
@@ -16,16 +16,20 @@
# Where the logs will go
LOGFILE=$HOME/log/nightly-website.log
-# Setup Mail
-MAIL=mail
-MAILTO=[EMAIL PROTECTED]
-
##
## Print an informative message
##
info() {
echo ${PROGNAME}: $*
}
+
+# Setup Mail
+MAIL=mail
+if [ x$MAILTO = x ]; then
+MAILTO=[EMAIL PROTECTED]
+else
+info Using MAILTO: $MAILTO
+fi
##
## Print an error message and exit
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/pm/file PersistenceManager.java PersistenceManagerMBean.java
User: chirino
Date: 01/08/31 20:00:59
Modified:src/main/org/jboss/mq/pm/file PersistenceManager.java
PersistenceManagerMBean.java
Log:
Fixing compile problems due to migration of classes from jboss.util to jboss.system
Revision ChangesPath
1.4 +462 -255 jbossmq/src/main/org/jboss/mq/pm/file/PersistenceManager.java
Index: PersistenceManager.java
===
RCS file:
/cvsroot/jboss/jbossmq/src/main/org/jboss/mq/pm/file/PersistenceManager.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- PersistenceManager.java 2001/08/30 02:34:52 1.3
+++ PersistenceManager.java 2001/09/01 03:00:59 1.4
@@ -1,5 +1,5 @@
/*
- * JBossMQ, the OpenSource JMS implementation
+ * JBoss, the OpenSource J2EE webOS
*
* Distributable under LGPL license.
* See terms of license at gnu.org.
@@ -15,6 +15,11 @@
import java.util.TreeSet;
import javax.jms.JMSException;
+
+
+
+
+
import javax.management.*;
import org.jboss.mq.SpyDestination;
@@ -23,7 +28,6 @@
import org.jboss.mq.pm.TxManager;
import org.jboss.mq.server.JMSDestination;
import org.jboss.mq.server.JMSServer;
-
import org.jboss.system.ServiceMBeanSupport;
/**
@@ -31,358 +35,512 @@
* persistence.
*
* @author Paul Kendall ([EMAIL PROTECTED])
- * @createdAugust 16, 2001
- * @version$Revision: 1.3 $
+ * @version$Revision: 1.4 $
*/
-public class PersistenceManager extends org.jboss.system.ServiceMBeanSupport
implements PersistenceManagerMBean, org.jboss.mq.pm.PersistenceManager {
+public class PersistenceManager extends ServiceMBeanSupport implements
PersistenceManagerMBean, org.jboss.mq.pm.PersistenceManager
+{
+
+ protected final static int MAX_POOL_SIZE = 50;
protected java.util.ArrayList txPool = new java.util.ArrayList();
- protected long tidcounter = Long.MIN_VALUE;
+ protected long tidcounter = Long.MIN_VALUE;
// The directory where persistence data should be stored
- String dataDirectory;
- URL dataDirURL;
- File dataDirFile;
+ String dataDirectory;
+ URL dataDirURL;
+ File dataDirFile;
//tx manager
org.jboss.mq.pm.TxManager txManager;
// Maps SpyDestinations to SpyMessageLogs
- HashMap messageLogs = new HashMap();
+ HashMap messageLogs = new HashMap();
// Maps (Long)txIds to LinkedList of AddFile tasks
- HashMap transactedTasks = new HashMap();
+ HashMap transactedTasks = new HashMap();
- protected final static int MAX_POOL_SIZE = 50;
-
/**
* PersistenceManager constructor.
*
* @exception javax.jms.JMSException Description of Exception
*/
- public PersistenceManager()
- throws javax.jms.JMSException {
- txManager = new TxManager( this );
+ public PersistenceManager() throws javax.jms.JMSException
+ {
+ txManager = new TxManager(this);
}
- public void setDataDirectory( java.lang.String newDataDirectory ) {
+ /**
+* Sets the DataDirectory attribute of the PersistenceManager object
+*
+* @param newDataDirectory The new DataDirectory value
+*/
+ public void setDataDirectory(java.lang.String newDataDirectory)
+ {
dataDirectory = newDataDirectory;
}
- public String getName() {
+ /**
+* Gets the Name attribute of the PersistenceManager object
+*
+* @returnThe Name value
+*/
+ public String getName()
+ {
return JBossMQ-PersistenceManager;
}
- public java.lang.String getDataDirectory() {
+ /**
+* Gets the DataDirectory attribute of the PersistenceManager object
+*
+* @returnThe DataDirectory value
+*/
+ public java.lang.String getDataDirectory()
+ {
return dataDirectory;
}
- public org.jboss.mq.pm.TxManager getTxManager() {
+ /**
+* Gets the TxManager attribute of the PersistenceManager object
+*
+* @returnThe TxManager value
+*/
+ public org.jboss.mq.pm.TxManager getTxManager()
+ {
return txManager;
}
- public void initService()
- throws Exception {
-
- //URL configFile = getClass().getClassLoader().getResource( jboss.jcml );
- //dataDirURL = new URL( configFile, dataDirectory );
- //dataDirFile = new File( dataDirURL.getFile() );
-
- File homeDir = new File(System.getProperty(jboss.system.home));
- dataDirFile = new File(homeDir,dataDirectory);
- System.out.println(DATADIRFILE+ dataDirFile.getAbsolutePath());
- dataDirURL = dataDirFile.toURL();
-
- JMSServer
[JBoss-dev] JMX Event Notification Asynchronous
Hi Geeks We had a few months ago already this discussion if JMX-Event transport (from the JMX MBean- Server back to the client) should be done asynchronous. Does anyone have an idea how this can be done J2EE based (meaning vendor neutral). From my point of view you cannot create a Queue in the EJB-Container w/o knowing the server (vendor) and a Topic would send all the events to all the clients. Does anyone have a solution ? Andy ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/il ServerILJMXService.java ServerILJMXServiceMBean.java
User: chirino
Date: 01/08/31 20:00:59
Modified:src/main/org/jboss/mq/il ServerILJMXService.java
ServerILJMXServiceMBean.java
Log:
Fixing compile problems due to migration of classes from jboss.util to jboss.system
Revision ChangesPath
1.4 +31 -24jbossmq/src/main/org/jboss/mq/il/ServerILJMXService.java
Index: ServerILJMXService.java
===
RCS file: /cvsroot/jboss/jbossmq/src/main/org/jboss/mq/il/ServerILJMXService.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- ServerILJMXService.java 2001/08/30 02:35:54 1.3
+++ ServerILJMXService.java 2001/09/01 03:00:58 1.4
@@ -1,5 +1,5 @@
/*
- * JBossMQ, the OpenSource JMS implementation
+ * JBoss, the OpenSource J2EE webOS
*
* Distributable under LGPL license.
* See terms of license at gnu.org.
@@ -9,12 +9,15 @@
import java.util.Properties;
import javax.management.*;
import javax.naming.InitialContext;
-
import org.jboss.mq.GenericConnectionFactory;
import org.jboss.mq.SpyConnectionFactory;
import org.jboss.mq.SpyXAConnectionFactory;
import org.jboss.mq.server.JMSServer;
+
+
+
+
import org.jboss.system.ServiceMBeanSupport;
/**
@@ -22,19 +25,20 @@
* extended to provide a full implementation.
*
* @author Hiram Chirino ([EMAIL PROTECTED])
- * @createdAugust 16, 2001
- * @version$Revision: 1.3 $
+ * @version$Revision: 1.4 $
*/
-public abstract class ServerILJMXService extends
org.jboss.system.ServiceMBeanSupport implements ServerILJMXServiceMBean {
- private String connectionFactoryJNDIRef;
+public abstract class ServerILJMXService extends ServiceMBeanSupport implements
ServerILJMXServiceMBean
+{
+ private String connectionFactoryJNDIRef;
- private String xaConnectionFactoryJNDIRef;
+ private String xaConnectionFactoryJNDIRef;
/**
* @param newConnectionFactoryJNDIRef the JNDI reference where the
* connection factory should be bound to
*/
- public void setConnectionFactoryJNDIRef( java.lang.String
newConnectionFactoryJNDIRef ) {
+ public void setConnectionFactoryJNDIRef(java.lang.String
newConnectionFactoryJNDIRef)
+ {
connectionFactoryJNDIRef = newConnectionFactoryJNDIRef;
}
@@ -42,7 +46,8 @@
* @param newXaConnectionFactoryJNDIRef java.lang.String the JNDI reference
* where the xa connection factory should be bound to
*/
- public void setXAConnectionFactoryJNDIRef( java.lang.String
newXaConnectionFactoryJNDIRef ) {
+ public void setXAConnectionFactoryJNDIRef(java.lang.String
newXaConnectionFactoryJNDIRef)
+ {
xaConnectionFactoryJNDIRef = newXaConnectionFactoryJNDIRef;
}
@@ -63,7 +68,8 @@
* @returnjava.lang.String the JNDI reference where the connection
* factory should be bound to
*/
- public java.lang.String getConnectionFactoryJNDIRef() {
+ public java.lang.String getConnectionFactoryJNDIRef()
+ {
return connectionFactoryJNDIRef;
}
@@ -71,7 +77,8 @@
* @returnjava.lang.String the JNDI reference where the xa connection
* factory should be bound to
*/
- public java.lang.String getXAConnectionFactoryJNDIRef() {
+ public java.lang.String getXAConnectionFactoryJNDIRef()
+ {
return xaConnectionFactoryJNDIRef;
}
@@ -80,17 +87,17 @@
*
* @throws javax.naming.NamingException it cannot be unbound
*/
- public void bindJNDIReferences()
- throws javax.naming.NamingException {
+ public void bindJNDIReferences() throws javax.naming.NamingException
+ {
- GenericConnectionFactory gcf = new GenericConnectionFactory( getServerIL(),
getClientConnectionProperties() );
- SpyConnectionFactory scf = new SpyConnectionFactory( gcf );
- SpyXAConnectionFactory sxacf = new SpyXAConnectionFactory( gcf );
+ GenericConnectionFactory gcf = new GenericConnectionFactory(getServerIL(),
getClientConnectionProperties());
+ SpyConnectionFactory scf = new SpyConnectionFactory(gcf);
+ SpyXAConnectionFactory sxacf = new SpyXAConnectionFactory(gcf);
// Get an InitialContext
InitialContext ctx = new InitialContext();
- ctx.bind( connectionFactoryJNDIRef, scf );
- ctx.bind( xaConnectionFactoryJNDIRef, sxacf );
+ ctx.bind(connectionFactoryJNDIRef, scf);
+ ctx.bind(xaConnectionFactoryJNDIRef, sxacf);
}
@@ -99,12 +106,12 @@
*
* @throws javax.naming.NamingException it cannot be unbound
*/
- public void unbindJNDIReferences()
- throws javax.naming.NamingException {
+ public void unbindJNDIReferences() throws javax.naming.NamingException
+ {
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/pm/rollinglogged PersistenceManager.java PersistenceManagerMBean.java
User: chirino
Date: 01/08/31 20:01:00
Modified:src/main/org/jboss/mq/pm/rollinglogged
PersistenceManager.java
PersistenceManagerMBean.java
Log:
Fixing compile problems due to migration of classes from jboss.util to jboss.system
Revision ChangesPath
1.5 +456 -285
jbossmq/src/main/org/jboss/mq/pm/rollinglogged/PersistenceManager.java
Index: PersistenceManager.java
===
RCS file:
/cvsroot/jboss/jbossmq/src/main/org/jboss/mq/pm/rollinglogged/PersistenceManager.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- PersistenceManager.java 2001/08/30 02:35:55 1.4
+++ PersistenceManager.java 2001/09/01 03:01:00 1.5
@@ -1,3 +1,9 @@
+/*
+ * JBoss, the OpenSource J2EE webOS
+ *
+ * Distributable under LGPL license.
+ * See terms of license at gnu.org.
+ */
package org.jboss.mq.pm.rollinglogged;
import java.net.URL;
@@ -6,7 +12,6 @@
import java.util.Iterator;
import java.util.LinkedList;
import java.util.TreeSet;
-
import javax.jms.JMSException;
import javax.management.*;
@@ -20,53 +25,54 @@
import org.jboss.mq.server.JMSDestination;
import org.jboss.mq.server.JMSServer;
import org.jboss.mq.xml.XElement;
-
import org.jboss.system.ServiceMBeanSupport;
/**
* This class manages all persistence related services.
*
* @author David Maplesden ([EMAIL PROTECTED])
- * @createdAugust 16, 2001
- * @version$Revision: 1.4 $
+ * @version$Revision: 1.5 $
*/
-public class PersistenceManager extends org.jboss.system.ServiceMBeanSupport
implements org.jboss.mq.pm.PersistenceManager, PersistenceManagerMBean {
+public class PersistenceManager extends ServiceMBeanSupport implements
org.jboss.mq.pm.PersistenceManager, PersistenceManagerMBean
+{
+ public final static int ROLL_OVER_SIZE = 1000;
+ public final static String TRANS_FILE_NAME = transactions.dat;
+ public final static boolean DEBUG = false;
+
+ protected static int MAX_POOL_SIZE = 50;
+
protected java.util.ArrayList listPool = new java.util.ArrayList();
protected java.util.ArrayList txPool = new java.util.ArrayList();
- protected intmessageCounter = 0;
- int numRollOvers = 0;
- HashMap queues = new HashMap();
+ protected int messageCounter = 0;
+ int numRollOvers = 0;
+ HashMap queues = new HashMap();
// Log file used to store commited transactions.
- SpyTxLog currentTxLog;
- long nextTxId = Long.MIN_VALUE;
+ SpyTxLog currentTxLog;
+ long nextTxId = Long.MIN_VALUE;
// Maps txLogs to Maps of SpyDestinations to SpyMessageLogs
- HashMap messageLogs = null;
+ HashMap messageLogs = new HashMap();
// Maps transactionIds to txInfos
- HashMap transToTxLogs = new HashMap();
+ HashMap transToTxLogs = new HashMap();
- // The directory where persistence data should be stored
- URL dataDirURL;
- TxManagertxManager;
- private String dataDirectory;
- public final static int ROLL_OVER_SIZE = 1000;
- public final static String TRANS_FILE_NAME = transactions.dat;
- public final static boolean DEBUG = false;
+ // The directory where persistence data should be stored
+ URL dataDirURL;
+ TxManager txManager;
- protected static int MAX_POOL_SIZE = 50;
+ private String dataDirectory;
/**
* NewPersistenceManager constructor.
*
* @exception javax.jms.JMSException Description of Exception
*/
- public PersistenceManager()
- throws javax.jms.JMSException {
- txManager = new TxManager( this );
+ public PersistenceManager() throws javax.jms.JMSException
+ {
+ txManager = new TxManager(this);
}
@@ -76,7 +82,8 @@
*
* @param newDataDirectory java.lang.String
*/
- public void setDataDirectory( java.lang.String newDataDirectory ) {
+ public void setDataDirectory(java.lang.String newDataDirectory)
+ {
dataDirectory = newDataDirectory;
}
@@ -86,11 +93,18 @@
*
* @returnjava.lang.String
*/
- public java.lang.String getDataDirectory() {
+ public java.lang.String getDataDirectory()
+ {
return dataDirectory;
}
- public String getName() {
+ /**
+* Gets the Name attribute of the PersistenceManager object
+*
+* @returnThe Name value
+*/
+ public String getName()
+ {
return JBossMQ-PersistenceManager;
}
@@ -99,39 +113,49 @@
*
* @returnThe TxManager value
*/
- public org.jboss.mq.pm.TxManager getTxManager() {
+ public org.jboss.mq.pm.TxManager
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/pm/jdbc PersistenceManagerMBean.java
User: chirino
Date: 01/08/31 20:01:00
Modified:src/main/org/jboss/mq/pm/jdbc PersistenceManagerMBean.java
Log:
Fixing compile problems due to migration of classes from jboss.util to jboss.system
Revision ChangesPath
1.4 +18 -44
jbossmq/src/main/org/jboss/mq/pm/jdbc/PersistenceManagerMBean.java
Index: PersistenceManagerMBean.java
===
RCS file:
/cvsroot/jboss/jbossmq/src/main/org/jboss/mq/pm/jdbc/PersistenceManagerMBean.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- PersistenceManagerMBean.java 2001/08/30 02:35:55 1.3
+++ PersistenceManagerMBean.java 2001/09/01 03:01:00 1.4
@@ -1,62 +1,36 @@
-package org.jboss.mq.pm.jdbc;
-
-/*
- * jBoss, the OpenSource EJB server
- *
- * Distributable under LGPL license.
- * See terms of license at gnu.org.
- */
-
/*
- * jBoss, the OpenSource EJB server
+ * JBoss, the OpenSource J2EE webOS
*
* Distributable under LGPL license.
* See terms of license at gnu.org.
*/
-
-/*
- * jBoss, the OpenSource EJB server
- *
- * Distributable under LGPL license.
- * See terms of license at gnu.org.
- */
-
-/*
- * jBoss, the OpenSource EJB server
- *
- * Distributable under LGPL license.
- * See terms of license at gnu.org.
- */
+package org.jboss.mq.pm.jdbc;
-/*
- * jBoss, the OpenSource EJB server
- *
- * Distributable under LGPL license.
- * See terms of license at gnu.org.
- */
+import org.jboss.system.ServiceMBean;
/**
* descriptionMBean interface for the JBossMQ JMX service.
*
* @author Vincent Sheffer ([EMAIL PROTECTED])
- * @createdAugust 16, 2001
* @seerelated
- * @version$Revision: 1.3 $
+ * @version$Revision: 1.4 $
*/
-public interface PersistenceManagerMBean
- extends org.jboss.system.ServiceMBean {
- // Constants -
- public final static String OBJECT_NAME = :service=JBossMQ;
-
- // Public
+public interface PersistenceManagerMBean extends ServiceMBean
+{
-
- // Public
-
- // Public
+ public final static String OBJECT_NAME = :service=JBossMQ;
- // Public
+ /**
+* Gets the JmsDBPoolName attribute of the PersistenceManagerMBean object
+*
+* @returnThe JmsDBPoolName value
+*/
public java.lang.String getJmsDBPoolName();
- public void setJmsDBPoolName( java.lang.String newJmsDBPoolName );
+ /**
+* Sets the JmsDBPoolName attribute of the PersistenceManagerMBean object
+*
+* @param newJmsDBPoolName The new JmsDBPoolName value
+*/
+ public void setJmsDBPoolName(java.lang.String newJmsDBPoolName);
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/il/uil UILServerILService.java
User: chirino
Date: 01/08/31 20:00:59
Modified:src/main/org/jboss/mq/il/uil UILServerILService.java
Log:
Fixing compile problems due to migration of classes from jboss.util to jboss.system
Revision ChangesPath
1.4 +145 -102 jbossmq/src/main/org/jboss/mq/il/uil/UILServerILService.java
Index: UILServerILService.java
===
RCS file:
/cvsroot/jboss/jbossmq/src/main/org/jboss/mq/il/uil/UILServerILService.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- UILServerILService.java 2001/08/30 02:35:54 1.3
+++ UILServerILService.java 2001/09/01 03:00:59 1.4
@@ -1,5 +1,5 @@
/*
- * JBossMQ, the OpenSource JMS implementation
+ * JBoss, the OpenSource J2EE webOS
*
* Distributable under LGPL license.
* See terms of license at gnu.org.
@@ -8,14 +8,11 @@
import java.io.BufferedInputStream;
import java.io.BufferedOutputStream;
import java.io.EOFException;
-
import java.io.IOException;
-
import java.io.ObjectInputStream;
import java.io.ObjectOutputStream;
import java.net.InetAddress;
import java.net.ServerSocket;
-
import java.net.Socket;
import java.rmi.RemoteException;
@@ -24,11 +21,10 @@
import javax.jms.JMSException;
import javax.jms.Queue;
import javax.jms.TemporaryQueue;
-
import javax.jms.TemporaryTopic;
-
import javax.jms.Topic;
import javax.management.*;
+
import javax.naming.InitialContext;
import org.jboss.mq.AcknowledgementRequest;
import org.jboss.mq.ConnectionToken;
@@ -44,22 +40,14 @@
import org.jboss.mq.il.uil.multiplexor.*;
import org.jboss.mq.server.JMSServer;
-import org.jboss.system.ServiceMBeanSupport;
-
/**
* Implements the ServerILJMXService which is used to manage the JVM IL.
*
* @author Hiram Chirino ([EMAIL PROTECTED])
- * @createdAugust 16, 2001
- * @version$Revision: 1.3 $
+ * @version$Revision: 1.4 $
*/
-public class UILServerILService extends org.jboss.mq.il.ServerILJMXService
implements Runnable, UILServerILServiceMBean {
- protected ServerSocket serverSocket;
- UILServerIL serverIL;
-
- boolean running;
- int serverBindPort = 0;
- Thread worker;
+public class UILServerILService extends org.jboss.mq.il.ServerILJMXService
implements Runnable, UILServerILServiceMBean
+{
//The server implementation
protected static JMSServer server;
@@ -84,13 +72,20 @@
final static int m_destroySubscription = 19;
final static int m_checkUser = 20;
final static int SO_TIMEOUT = 5000;
+ protected ServerSocket serverSocket;
+ UILServerIL serverIL;
+
+ boolean running;
+ int serverBindPort = 0;
+ Thread worker;
/**
* Gives this JMX service a name.
*
* @returnThe Name value
*/
- public String getName() {
+ public String getName()
+ {
return JBossMQ-UILServerIL;
}
@@ -101,7 +96,8 @@
* @return The ServerIL value
* @returnsServerIL the instance of this IL
*/
- public ServerIL getServerIL() {
+ public ServerIL getServerIL()
+ {
return serverIL;
}
@@ -112,9 +108,10 @@
*
* @returnThe ClientConnectionProperties value
*/
- public java.util.Properties getClientConnectionProperties() {
+ public java.util.Properties getClientConnectionProperties()
+ {
Properties rc = new Properties();
- rc.setProperty( GenericConnectionFactory.CLIENT_IL_SERVICE_KEY,
org.jboss.mq.il.uil.UILClientILService );
+ rc.setProperty(GenericConnectionFactory.CLIENT_IL_SERVICE_KEY,
org.jboss.mq.il.uil.UILClientILService);
return rc;
}
@@ -123,20 +120,20 @@
*
* @exception Exception Description of Exception
*/
- public void startService()
- throws Exception {
+ public void startService() throws Exception
+ {
running = true;
this.server = lookupJMSServer();
- serverSocket = new ServerSocket( serverBindPort );
- serverSocket.setSoTimeout( SO_TIMEOUT );
+ serverSocket = new ServerSocket(serverBindPort);
+ serverSocket.setSoTimeout(SO_TIMEOUT);
- category.info( JBossMQ UIL service available at : +
InetAddress.getLocalHost().getHostAddress() + : + serverSocket.getLocalPort() );
- worker = new Thread( server.threadGroup, this, UIL Worker );
+ category.info(JBossMQ UIL service available at : +
InetAddress.getLocalHost().getHostAddress() + : + serverSocket.getLocalPort());
+ worker = new Thread(server.threadGroup, this, UIL Worker);
worker.start();
- serverIL = new UILServerIL( InetAddress.getLocalHost(),
serverSocket.getLocalPort() );
+ serverIL = new
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/il/oil OILServerILService.java
User: chirino
Date: 01/08/31 20:00:59
Modified:src/main/org/jboss/mq/il/oil OILServerILService.java
Log:
Fixing compile problems due to migration of classes from jboss.util to jboss.system
Revision ChangesPath
1.4 +141 -97 jbossmq/src/main/org/jboss/mq/il/oil/OILServerILService.java
Index: OILServerILService.java
===
RCS file:
/cvsroot/jboss/jbossmq/src/main/org/jboss/mq/il/oil/OILServerILService.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- OILServerILService.java 2001/08/30 02:35:54 1.3
+++ OILServerILService.java 2001/09/01 03:00:59 1.4
@@ -1,5 +1,5 @@
/*
- * JBossMQ, the OpenSource JMS implementation
+ * JBoss, the OpenSource J2EE webOS
*
* Distributable under LGPL license.
* See terms of license at gnu.org.
@@ -8,14 +8,11 @@
import java.io.BufferedInputStream;
import java.io.BufferedOutputStream;
import java.io.EOFException;
-
import java.io.IOException;
-
import java.io.ObjectInputStream;
import java.io.ObjectOutputStream;
import java.net.InetAddress;
import java.net.ServerSocket;
-
import java.net.Socket;
import java.rmi.RemoteException;
@@ -24,16 +21,14 @@
import javax.jms.JMSException;
import javax.jms.Queue;
import javax.jms.TemporaryQueue;
-
import javax.jms.TemporaryTopic;
-
import javax.jms.Topic;
import javax.management.*;
+
import javax.naming.InitialContext;
import org.jboss.mq.AcknowledgementRequest;
import org.jboss.mq.ConnectionToken;
import org.jboss.mq.DurableSubcriptionID;
-
import org.jboss.mq.GenericConnectionFactory;
import org.jboss.mq.SpyDestination;
import org.jboss.mq.SpyMessage;
@@ -50,16 +45,10 @@
* Implements the ServerILJMXService which is used to manage the JVM IL.
*
* @author Hiram Chirino ([EMAIL PROTECTED])
- * @createdAugust 16, 2001
- * @version$Revision: 1.3 $
+ * @version$Revision: 1.4 $
*/
-public class OILServerILService extends org.jboss.mq.il.ServerILJMXService
implements Runnable, OILServerILServiceMBean {
- protected ServerSocket serverSocket;
- OILServerIL serverIL;
-
- boolean running;
- int serverBindPort = 0;
- Thread worker;
+public class OILServerILService extends org.jboss.mq.il.ServerILJMXService
implements Runnable, OILServerILServiceMBean
+{
//The server implementation
protected static JMSServer server;
@@ -83,13 +72,20 @@
final static int m_destroySubscription = 19;
final static int m_checkUser = 20;
final static int SO_TIMEOUT = 5000;
+ protected ServerSocket serverSocket;
+ OILServerIL serverIL;
+
+ boolean running;
+ int serverBindPort = 0;
+ Thread worker;
/**
* Gives this JMX service a name.
*
* @returnThe Name value
*/
- public String getName() {
+ public String getName()
+ {
return JBossMQ-OILServerIL;
}
@@ -100,7 +96,8 @@
* @return The ServerIL value
* @returnsServerIL the instance of this IL
*/
- public ServerIL getServerIL() {
+ public ServerIL getServerIL()
+ {
return serverIL;
}
@@ -111,9 +108,10 @@
*
* @returnThe ClientConnectionProperties value
*/
- public java.util.Properties getClientConnectionProperties() {
+ public java.util.Properties getClientConnectionProperties()
+ {
Properties rc = new Properties();
- rc.setProperty( GenericConnectionFactory.CLIENT_IL_SERVICE_KEY,
org.jboss.mq.il.oil.OILClientILService );
+ rc.setProperty(GenericConnectionFactory.CLIENT_IL_SERVICE_KEY,
org.jboss.mq.il.oil.OILClientILService);
return rc;
}
@@ -122,20 +120,20 @@
*
* @exception Exception Description of Exception
*/
- public void startService()
- throws Exception {
+ public void startService() throws Exception
+ {
running = true;
this.server = lookupJMSServer();
- serverSocket = new ServerSocket( serverBindPort );
- serverSocket.setSoTimeout( SO_TIMEOUT );
+ serverSocket = new ServerSocket(serverBindPort);
+ serverSocket.setSoTimeout(SO_TIMEOUT);
- category.info( JBossMQ OIL service available at : +
InetAddress.getLocalHost().getHostAddress() + : + serverSocket.getLocalPort() );
- worker = new Thread( server.threadGroup, this, OIL Worker );
+ category.info(JBossMQ OIL service available at : +
InetAddress.getLocalHost().getHostAddress() + : + serverSocket.getLocalPort());
+ worker = new Thread(server.threadGroup, this, OIL Worker);
worker.start();
- serverIL = new OILServerIL( InetAddress.getLocalHost(),
serverSocket.getLocalPort() );
+
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/pm/jdbc PersistenceManager.java
User: chirino
Date: 01/08/31 20:03:05
Modified:src/main/org/jboss/mq/pm/jdbc PersistenceManager.java
Log:
fixing compile problems
Revision ChangesPath
1.6 +6 -7 jbossmq/src/main/org/jboss/mq/pm/jdbc/PersistenceManager.java
Index: PersistenceManager.java
===
RCS file:
/cvsroot/jboss/jbossmq/src/main/org/jboss/mq/pm/jdbc/PersistenceManager.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- PersistenceManager.java 2001/09/01 02:23:52 1.5
+++ PersistenceManager.java 2001/09/01 03:03:05 1.6
@@ -22,7 +22,7 @@
import java.sql.*;
import java.io.*;
-import org.jboss.system.ServiceMBeanSupport;
+
import org.jboss.mq.SpyDestination;
import org.jboss.mq.xml.XElement;
import org.jboss.mq.ConnectionToken;
@@ -32,18 +32,17 @@
import org.jboss.mq.SpyMessage;
import org.jboss.mq.SpyJMSException;
+import org.jboss.system.ServiceMBeanSupport;
+
/**
* This class manages all persistence related services for file based
* persistence.
*
* @author: Jayesh Parayali ([EMAIL PROTECTED])
*
- * @version $Revision: 1.5 $
+ * @version $Revision: 1.6 $
*/
-public class PersistenceManager
- extends ServiceMBeanSupport
- implements PersistenceManagerMBean, org.jboss.mq.pm.PersistenceManager
-{
+public class PersistenceManager extends ServiceMBeanSupport implements
PersistenceManagerMBean, org.jboss.mq.pm.PersistenceManager {
protected static DataSource datasource;
@@ -313,4 +312,4 @@
txLog.rollbackTx(txId);
}
-}
+}
\ No newline at end of file
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/il/rmi RMIServerILService.java
User: chirino
Date: 01/08/31 20:00:59
Modified:src/main/org/jboss/mq/il/rmi RMIServerILService.java
Log:
Fixing compile problems due to migration of classes from jboss.util to jboss.system
Revision ChangesPath
1.4 +21 -16jbossmq/src/main/org/jboss/mq/il/rmi/RMIServerILService.java
Index: RMIServerILService.java
===
RCS file:
/cvsroot/jboss/jbossmq/src/main/org/jboss/mq/il/rmi/RMIServerILService.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- RMIServerILService.java 2001/08/30 02:35:54 1.3
+++ RMIServerILService.java 2001/09/01 03:00:59 1.4
@@ -1,5 +1,5 @@
/*
- * JBossMQ, the OpenSource JMS implementation
+ * JBoss, the OpenSource J2EE webOS
*
* Distributable under LGPL license.
* See terms of license at gnu.org.
@@ -15,24 +15,23 @@
import org.jboss.mq.il.ServerILJMXService;
import org.jboss.mq.server.JMSServer;
-import org.jboss.system.ServiceMBeanSupport;
-
/**
* Implements the ServerILJMXService which is used to manage the JVM IL.
*
* @author Hiram Chirino ([EMAIL PROTECTED])
- * @createdAugust 16, 2001
- * @version$Revision: 1.3 $
+ * @version$Revision: 1.4 $
*/
-public class RMIServerILService extends org.jboss.mq.il.ServerILJMXService
implements RMIServerILServiceMBean {
- RMIServerIL serverIL;
+public class RMIServerILService extends org.jboss.mq.il.ServerILJMXService
implements RMIServerILServiceMBean
+{
+ RMIServerIL serverIL;
/**
* Gives this JMX service a name.
*
* @returnThe Name value
*/
- public String getName() {
+ public String getName()
+ {
return JBossMQ-JVMServerIL;
}
@@ -43,7 +42,8 @@
* @return The ServerIL value
* @returnsServerIL the instance of this IL
*/
- public ServerIL getServerIL() {
+ public ServerIL getServerIL()
+ {
return serverIL;
}
@@ -54,9 +54,10 @@
*
* @returnThe ClientConnectionProperties value
*/
- public java.util.Properties getClientConnectionProperties() {
+ public java.util.Properties getClientConnectionProperties()
+ {
Properties rc = new Properties();
- rc.setProperty( GenericConnectionFactory.CLIENT_IL_SERVICE_KEY,
org.jboss.mq.il.rmi.RMIClientILService );
+ rc.setProperty(GenericConnectionFactory.CLIENT_IL_SERVICE_KEY,
org.jboss.mq.il.rmi.RMIClientILService);
return rc;
}
@@ -65,10 +66,10 @@
*
* @exception Exception Description of Exception
*/
- public void startService()
- throws Exception {
+ public void startService() throws Exception
+ {
- serverIL = new RMIServerIL( lookupJMSServer() );
+ serverIL = new RMIServerIL(lookupJMSServer());
bindJNDIReferences();
}
@@ -76,10 +77,14 @@
/**
* Stops this IL, and unbinds it from JNDI
*/
- public void stopService() {
- try {
+ public void stopService()
+ {
+ try
+ {
unbindJNDIReferences();
- } catch ( Exception e ) {
+ }
+ catch (Exception e)
+ {
e.printStackTrace();
}
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/system ServiceConfigurator.java
User: chirino
Date: 01/08/31 20:51:05
Modified:src/main/org/jboss/system ServiceConfigurator.java
Log:
Added suppport for org.w3c.dom.Element type mbean attributes.
The first child Element of the attribute ... is used
to set the value of the attribute.
Revision ChangesPath
1.2 +31 -8 jboss/src/main/org/jboss/system/ServiceConfigurator.java
Index: ServiceConfigurator.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/system/ServiceConfigurator.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ServiceConfigurator.java 2001/08/29 23:08:21 1.1
+++ ServiceConfigurator.java 2001/09/01 03:51:05 1.2
@@ -42,13 +42,20 @@
*
*
* @author a href=mailto:[EMAIL PROTECTED];Marc Fleury/a`
-* @version $Revision: 1.1 $
+* @author a href=mailto:[EMAIL PROTECTED];Hiram Chirino/a`
+* @version $Revision: 1.2 $
*
* pb20010830 marc fleury:/b
* ul
* initial import
* li
* /ul
+* pb20010831 hiram chirino:/b
+* ul
+* li Added suppport for org.w3c.dom.Element type mbean attributes.
+*The first child Element of the lt;attribute ...gt; is used
+*to set the value of the attribute.
+* /ul
*/
public class ServiceConfigurator
@@ -183,11 +190,30 @@
typeClass =
(Class)primitives.get(typeName);
} else {
typeClass =
Class.forName(typeName);
+ }
+
+ Object value = null;
+
+ // HRC: Is the attribute type a
org.w3c.dom.Element??
+ if( typeClass.equals(Element.class) )
{
+ // Then we can pass the first
child Element of this
+ // attributeElement
+ NodeList nl =
attributeElement.getChildNodes();
+ for(int i=0; i
nl.getLength(); i++) {
+ org.w3c.dom.Node n =
nl.item(i);
+ if( n.getNodeType() ==
n.ELEMENT_NODE ) {
+ value =
(Element)n;
+ break;
+ }
+ }
}
- PropertyEditor editor =
PropertyEditorManager.findEditor(typeClass);
- editor.setAsText(attributeValue);
- Object value = editor.getValue();
+ if( value == null ) {
+ PropertyEditor editor =
PropertyEditorManager.findEditor(typeClass);
+
editor.setAsText(attributeValue);
+ value = editor.getValue();
+ }
+
log.debug(attributeName + set to +
attributeValue + in + objectName);
server.setAttribute(objectName, new
Attribute(attributeName, value));
@@ -290,7 +316,4 @@
return false;
}
-}
-
-
-
+}
\ No newline at end of file
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss Main.java Version.java
User: user57
Date: 01/08/31 21:11:59
Modified:src/main/org/jboss Main.java Version.java
Log:
o re-enabled usage of Version changed back to using Calader to avoid
deprecated warnings.
Revision ChangesPath
1.45 +21 -12jboss/src/main/org/jboss/Main.java
Index: Main.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/Main.java,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -r1.44 -r1.45
--- Main.java 2001/08/30 04:28:42 1.44
+++ Main.java 2001/09/01 04:11:59 1.45
@@ -20,6 +20,7 @@
import java.util.ArrayList;
import java.util.Iterator;
import java.util.Set;
+import java.util.Calendar;
import java.security.AccessController;
import java.security.PrivilegedAction;
@@ -40,7 +41,7 @@
*
* @see related
* @author a href=mailto:[EMAIL PROTECTED];Marc Fleury/a.
-* @version $Revision: 1.44 $
+* @version $Revision: 1.45 $
*
* pb Revisions:/b
* pb 20010830 marcf: /b
@@ -52,10 +53,12 @@
*/
public class Main
{
- // Constants -
-
- String versionIdentifier = pre-3.0 [RABBIT-HOLE];
- // Attributes
+ // Constants -
+
+ /** The version build information holder. */
+ private Version version = Version.getInstance();
+
+ // Attributes
// Static
public static void main(final String[] args)
@@ -150,7 +153,8 @@
System.setProperty(jboss.system.configurationDirectory,
confDir);
System.setProperty(jboss.system.patchDirectory, patchDir);
System.setProperty(jboss.system.libraryDirectory, libDir);
- System.setProperty(jboss.system.version, versionIdentifier);
+ System.setProperty(jboss.system.version, version.toString());
+System.setProperty(jboss.system.version.name,
version.getName());
// Give feedback about from where jndi.properties is read
URL jndiLocation =
this.getClass().getResource(/jndi.properties);
@@ -265,11 +269,16 @@
{
e.printStackTrace();
}
-
- // Done
- Date stopTime = new Date();
- Date lapsedTime = new Date(stopTime.getTime()-startTime.getTime());
- System.out.println(JBoss +versionIdentifier+ Started in
+lapsedTime.getMinutes()+m:+lapsedTime.getSeconds()+s);
+
+// Done
+Date lapsedTime = new Date(new Date().getTime() -
startTime.getTime());
+Calendar cal = Calendar.getInstance();
+cal.setTime(lapsedTime);
+
+System.out.println(JBoss + version +
+[ + version.getName() + ] Started in +
+ cal.get(Calendar.MINUTE) + m: +
+ cal.get(Calendar.SECOND) + s);
}
@@ -336,4 +345,4 @@
if (System.getProperty(java.security.manager) != null)
System.setSecurityManager((SecurityManager)Class.forName(System.getProperty(java.security.manager)).newInstance());
*/
-}
\ No newline at end of file
+}
1.2 +113 -84 jboss/src/main/org/jboss/Version.java
Index: Version.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/Version.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Version.java 2001/08/28 02:08:18 1.1
+++ Version.java 2001/09/01 04:11:59 1.2
@@ -1,171 +1,164 @@
/*
- * JBoss, the OpenSource EJB server
+ * JBoss, the OpenSource J2EE webOS
*
* Distributable under LGPL license.
* See terms of license at gnu.org.
*/
-
package org.jboss;
+import java.io.IOException;
-import java.util.Properties;
-import java.util.Map;
+import java.io.InputStream;
import java.util.Collections;
+import java.util.Map;
-import java.io.InputStream;
-import java.io.IOException;
+import java.util.Properties;
/**
- * Provides access to JBoss version (and build) properties.
- *
- * @author a href=mailto:[EMAIL PROTECTED];Jason Dillon/a
- * @version $Revision: 1.1 $
+ * Provides access to JBoss version (and build) properties.
+ *
+ * @author a href=mailto:[EMAIL PROTECTED];Jason Dillon/a
+ * @version$Revision: 1.2 $
*/
public final class Version
{
-
[JBoss-dev] CVS update: build/jboss/etc/.Refactory pretty.settings
User: user57
Date: 01/08/31 21:21:25
Modified:jboss/etc/.Refactory pretty.settings
Log:
o cleaned up tabs, changed generated comments for classes with main
Revision ChangesPath
1.3 +6 -10 build/jboss/etc/.Refactory/pretty.settings
Index: pretty.settings
===
RCS file: /cvsroot/jboss/build/jboss/etc/.Refactory/pretty.settings,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- pretty.settings 2001/08/21 02:33:18 1.2
+++ pretty.settings 2001/09/01 04:21:25 1.3
@@ -1,7 +1,3 @@
-
-
-
-
###
# pretty.settings
###
@@ -155,10 +151,10 @@
#
# method.minimum applies to constructors and methods
-method.minimum=public
+method.minimum=protected
# field.minimum applies to fields
-field.minimum=none
+field.minimum=protected
# class.minimum applies to classes and interfaces
class.minimum=all
@@ -177,7 +173,7 @@
javadoc.id.lineup=true
# How many spaces should javadoc comments be indented?
-javadoc.indent=2
+javadoc.indent=1
# Wordwrap the javadoc comments
reformat.comments=true
@@ -252,7 +248,7 @@
# Default description of the run method. {0} is not
# applicable, {1} is the name of the class, {2} is 'class'
# or 'object' depending on whether it is static or not
-main.descr=The main program for the {1} {2}
+main.descr=The main entry-point for the {1} {2}
# Description of the main arguments
main.param.descr=The command line arguments
@@ -288,10 +284,10 @@
#
# Here is the order for tags for classes and interfaces
-class.tags=author
+class.tags=deprecated,see,author,version
# Here is the order for tags for methods and constructors
-method.tags=param,return,exception
+method.tags=param,return,throws,exception
# Here is the order for tags for fields
field.tags=#since
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss build.xml
User: user57
Date: 01/08/31 21:21:25
Modified:.build.xml
Log:
o cleaned up tabs, changed generated comments for classes with main
Revision ChangesPath
1.21 +18 -15jboss/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/jboss/build.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- build.xml 2001/08/31 05:39:08 1.20
+++ build.xml 2001/09/01 04:21:25 1.21
@@ -10,7 +10,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.20 2001/08/31 05:39:08 user57 Exp $ --
+!-- $Id: build.xml,v 1.21 2001/09/01 04:21:25 user57 Exp $ --
project name=JBoss default=main
@@ -260,7 +260,7 @@
!-- Override JUnit defaults --
property name=junit.timeout value=24/ !-- 4 minutes --
property name=junit.batchtest.todir value=${build.reports}/
- property name=junit.jvm.options value=-client/
+ property name=junit.jvm.options value=-Ddummy/
!-- RMIC should generate stubs compatible with Java 1.2+ --
property name=rmic.stubVersion value=1.2/
@@ -314,15 +314,19 @@
| Pretty print everything.
|
| This uses the jedit JavaStyle plugin via the ejbdoclet pretty ant task.
+ |
| cvs=true only pretties files you have already modified.
| cvs=false pretties all files.
--
+ property name=pretty.cvs value=true/
+ property name=pretty.includes value=**/*.java/
+
target name=pretty depends=init
taskdef name=pretty classname=pretty.Pretty/
-pretty settingsDir=${control.root}/etc cvs=true
+pretty settingsDir=${control.root}/etc cvs=${pretty.cvs}
fileset dir=${source.java}
-include name=**/*.java/
+include name=${pretty.includes}/
/fileset
/pretty
/target
@@ -451,8 +455,8 @@
include name=org/jboss/**/
!-- Exclude Main, it will go into run.jar --
exclude name=org/jboss/Main*/
- !-- Exclude JMX Connector stuff we will use the connector JSR for
that --
- exclude name=org/jboss/jmx/**/
+!-- Exclude JMX Connector stuff we will use the connector JSR for that --
+ exclude name=org/jboss/jmx/**/
/fileset
fileset dir=${build.resources}
@@ -542,18 +546,17 @@
fileset dir=${build.resources}/org/jboss/verifier/
/jar
-!-- Build jmx-connector.jsr --
-unjar src=${thirdparty.root}/sun/jmx/lib/jmxtools.jar
-dest=${build.classes}/
- jar jarfile=${build.jars}/jmx-connector.jsr
+!-- Build jmx-connector.jsr (should try to use jlink for this)--
+unjar src=${sun.jmx.lib}/jmxtools.jar dest=${build.classes}/
+jar jarfile=${build.jars}/jmx-connector.jsr
manifest=${build.etc}/rmiconnector.mf
fileset dir=${build.classes}
include name=org/jboss/jmx/**/
- include name=com/sun/jdmk/**/
- /fileset
- fileset dir=${source.java}/org/jboss/jmx
- include name=META-INF/**/
- /fileset
+ include name=com/sun/jdmk/**/
+ /fileset
+ fileset dir=${source.java}/org/jboss/jmx
+include name=META-INF/**/
+ /fileset
/jar
!-- Build rmiconnector.jar --
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss Main.java
User: user57
Date: 01/08/31 21:31:39
Modified:src/main/org/jboss Main.java
Log:
o pretty'd removed the extra versionIdentifer from main()
Revision ChangesPath
1.46 +358 -320 jboss/src/main/org/jboss/Main.java
Index: Main.java
===
RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/Main.java,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- Main.java 2001/09/01 04:11:59 1.45
+++ Main.java 2001/09/01 04:31:39 1.46
@@ -1,348 +1,386 @@
/*
-* JBoss, the OpenSource J2EE webOS
-*
-* Distributable under LGPL license.
-* See terms of license at gnu.org.
-*/
-
+ * JBoss, the OpenSource J2EE webOS
+ *
+ * Distributable under LGPL license.
+ * See terms of license at gnu.org.
+ */
package org.jboss;
+import java.io.BufferedReader;
import java.io.File;
+import java.io.FileWriter;
import java.io.IOException;
import java.io.InputStream;
-import java.io.PrintStream;
-import java.io.BufferedReader;
import java.io.InputStreamReader;
+import java.io.PrintStream;
import java.io.PrintWriter;
-import java.io.FileWriter;
import java.net.URL;
-import java.util.Date;
import java.util.ArrayList;
+import java.util.Calendar;
+import java.util.Date;
import java.util.Iterator;
import java.util.Set;
-import java.util.Calendar;
import java.security.AccessController;
import java.security.PrivilegedAction;
+import javax.management.MBeanException;
import javax.management.MBeanServer;
-import javax.management.ObjectName;
import javax.management.MBeanServerFactory;
-import javax.management.loading.MLet;
+import javax.management.ObjectName;
import javax.management.ReflectionException;
-import javax.management.RuntimeMBeanException;
-import javax.management.MBeanException;
import javax.management.RuntimeErrorException;
+import javax.management.RuntimeMBeanException;
import javax.management.RuntimeOperationsException;
+import javax.management.loading.MLet;
-import org.jboss.system.ServiceLibraries;
import org.jboss.system.MBeanClassLoader;
+import org.jboss.system.ServiceLibraries;
import org.jboss.system.URLClassLoader;
+
/**
-*
-* @see related
-* @author a href=mailto:[EMAIL PROTECTED];Marc Fleury/a.
-* @version $Revision: 1.45 $
-*
-* pb Revisions:/b
-* pb 20010830 marcf: /b
-* ul
-*liInitial import, support for net-install
-* /ul
-*
-*
-*/
+ * The main entry point for the JBoss server.
+ *
+ * @authora href=mailto:[EMAIL PROTECTED];Marc Fleury/a
+ * @authora href=mailto:[EMAIL PROTECTED];Jason Dillon/a
+ * @version $Revision: 1.46 $
+ *
+ * bRevisions:/b
+ * p
+ * b20010830 marcf:/b
+ * ul
+ * liInitial import, support for net-install
+ * /ul
+ */
public class Main
{
- // Constants -
-
- /** The version build information holder. */
+ /**
+* The version build information holder.
+*/
private Version version = Version.getInstance();
+
+ /**
+* Constructor for the Main object
+*
+* @param installURL Description of Parameter
+* @param confDir Description of Parameter
+* @param patchDirDescription of Parameter
+* @param libDir Description of Parameter
+* @param spineDirDescription of Parameter
+*/
+ public Main(String installURL,
+ String confDir,
+ String patchDir,
+ String libDir,
+ String spineDir)
+ {
+ Date startTime = new Date();
+
+ try
+ {
+ final PrintStream err = System.err;
+
+ System.setProperty(jboss.system.installationURL, installURL);
+ System.setProperty(jboss.system.configurationDirectory, confDir);
+ System.setProperty(jboss.system.patchDirectory, patchDir);
+ System.setProperty(jboss.system.libraryDirectory, libDir);
+ System.setProperty(jboss.system.version, version.toString());
+ System.setProperty(jboss.system.version.name, version.getName());
+
+ // Give feedback about from where jndi.properties is read
+ URL jndiLocation = this.getClass().getResource(/jndi.properties);
+ if (jndiLocation instanceof URL)
+ {
+System.out.println(Please make sure the following is intended (check
your CLASSPATH):);
+System.out.println( jndi.properties is read from + jndiLocation);
+ }
+
+ // Create MBeanServer
+ final MBeanServer server =
MBeanServerFactory.createMBeanServer(JBOSS-SYSTEM);
+
+ // Initialize the MBean libraries repository
+ server.registerMBean(ServiceLibraries.getLibraries(), new
[JBoss-dev] pretty sucks
=P --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/main/org/jboss/system package.html
User: user57
Date: 01/08/31 21:57:56
Added: src/main/org/jboss/system package.html
Log:
o adding package javadoc files
Revision ChangesPath
1.1 jboss/src/main/org/jboss/system/package.html
Index: package.html
===
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
html
head
!--
JBoss, the OpenSource J2EE webOS
This library is free software; you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published
by the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This library is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
--
!-- $Id: package.html,v 1.1 2001/09/01 04:57:56 user57 Exp $ --
/head
body bgcolor=white
pemPackage description goes here/em.
h2Package Specification/h2
ul
lia href=javascript: alert('not available')Not Available/a
/ul
h2Related Documentation/h2
ul
lia href=javascript: alert('not available')Not Available/a
/ul
h2Package Status/h2
ul
lifont color=greenbSTABLE/b/font
/ul
!-- Put @see and @since tags down here. --
/body
/html
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
