concern-users Mailing List for osbl (Page 9)
Brought to you by:
hengels,
leonchiver
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(41) |
Feb
(3) |
Mar
|
Apr
(1) |
May
(24) |
Jun
|
Jul
(13) |
Aug
(5) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
(6) |
Jun
(4) |
Jul
|
Aug
|
Sep
(7) |
Oct
(4) |
Nov
|
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
(2) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
(4) |
Dec
(3) |
| 2008 |
Jan
(1) |
Feb
(1) |
Mar
(3) |
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(12) |
Dec
(30) |
| 2009 |
Jan
|
Feb
(1) |
Mar
(5) |
Apr
(1) |
May
|
Jun
(17) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Holger E. <he...@me...> - 2004-01-08 12:23:08
|
this codeblock is part of the xdoclet target in demo/build.xml:
<exec executable="../devel/dist/bin/cg.sh">
<env key="JAVA_HOME" file="${java.home}"/>
<arg value="-j"/>
<arg file="src/java"/>
<arg value="-m"/>
<arg file="src/meta"/>
<arg value="-c"/>
<arg file="src/controller"/>
<arg value="-d"/>
<arg file="src/ddl"/>
<arg file="src/cpd/engagement.cpd"/>
</exec>
it should produce those directories! Maybe it's going somewhere else for
whatever reason. try:
find -name ApplicationController.jar
maybe try running the code generator by hand.
holger
Quoting Lisa Retief <lis...@sa...>:
> I ran
>
> ant xdoclet jca ejb web
>
> ant it reported BUILD SUCCESSFUL.
>
> Under demo/src I only have:
>
> [lisa@mandrake1 src]$ pwd
> /home/lisa/concern/concern-src-1.0.1/demo/src
> [lisa@mandrake1 src]$ ls
> cml/ cpd/ CVS/ html/ java/ meta/ res/
>
> Any suggestions?
>
> Thanks,
> Lisa
>
> Holger Engels wrote:
>
> >Quoting Lisa Retief <lis...@sa...>:
> >
> >
> >
> >>Also
> >>
> >>cp src/controller/Application* $DEPLOY
> >>cp src/controller/Engagement* $DEPLOY
> >>
> >>no src/controller directory?
> >>
> >>
> >
> >and no demo/src/controller demo/src/ddl ?
> >
> >did you run ant xdoclet in demo ? someting like:
> >
> > ant xdoclet jca ejb web
> >
> >please post to concern-users!
> >
> >regards,
> >
> >holger
> >
> >-------------------------------------------------
> >This mail sent through IMP: http://horde.org/imp/
> >
> >
> >-------------------------------------------------------
> >This SF.net email is sponsored by: Perforce Software.
> >Perforce is the Fast Software Configuration Management System offering
> >advanced branching capabilities and atomic changes on 50+ platforms.
> >Free Eval! http://www.perforce.com/perforce/loadprog.html
> >_______________________________________________
> >Concern-users mailing list
> >Con...@li...
> >https://lists.sourceforge.net/lists/listinfo/concern-users
> >
> >
> >
>
>
>
Holger Engels
(Dipl Inf Med)
--
Consultant, Architect, Developer
Mobile: +49 176 20119752
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
|
|
From: Lisa R. <lis...@sa...> - 2004-01-08 12:10:31
|
I ran ant xdoclet jca ejb web ant it reported BUILD SUCCESSFUL. Under demo/src I only have: [lisa@mandrake1 src]$ pwd /home/lisa/concern/concern-src-1.0.1/demo/src [lisa@mandrake1 src]$ ls cml/ cpd/ CVS/ html/ java/ meta/ res/ Any suggestions? Thanks, Lisa Holger Engels wrote: >Quoting Lisa Retief <lis...@sa...>: > > > >>Also >> >>cp src/controller/Application* $DEPLOY >>cp src/controller/Engagement* $DEPLOY >> >>no src/controller directory? >> >> > >and no demo/src/controller demo/src/ddl ? > >did you run ant xdoclet in demo ? someting like: > > ant xdoclet jca ejb web > >please post to concern-users! > >regards, > >holger > >------------------------------------------------- >This mail sent through IMP: http://horde.org/imp/ > > >------------------------------------------------------- >This SF.net email is sponsored by: Perforce Software. >Perforce is the Fast Software Configuration Management System offering >advanced branching capabilities and atomic changes on 50+ platforms. >Free Eval! http://www.perforce.com/perforce/loadprog.html >_______________________________________________ >Concern-users mailing list >Con...@li... >https://lists.sourceforge.net/lists/listinfo/concern-users > > > |
|
From: Holger E. <he...@me...> - 2004-01-08 11:59:31
|
Quoting Lisa Retief <lis...@sa...>: > Also > > cp src/controller/Application* $DEPLOY > cp src/controller/Engagement* $DEPLOY > > no src/controller directory? and no demo/src/controller demo/src/ddl ? did you run ant xdoclet in demo ? someting like: ant xdoclet jca ejb web please post to concern-users! regards, holger ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ |
|
From: Lisa R. <lis...@sa...> - 2004-01-08 11:18:07
|
Hi, Got the build working. Did a new cvs co but ClaimLoader was still missing so I made on with the load method just throwing an exception as implementation. Then no compile errors but: BUILD FAILED file:/home/lisa/concern/concern-src-1.0.1/demo/build.xml:329: Warning: Could not find file /home/lisa/concern/concern-src-1.0.1/demo/src/meta/engagement-jboss-web.xml to copy. So I made a copy of /demo/src/meta/engagement-web.xml and named it engagement-jboss-web.xml and BUILD SUCCESSFUL! Now I am confused because the end of your instructions say: run the src/ddl/Engagement*-scripts that match your db run the src/ddl/Application*-scripts that match your db but there is no src/ddl directory? Please assist. Thanks, Lisa Holger Engels wrote: >1. the jars have been marked as binary in the repository (hopefully ;-) > >2. the new demo process is checked in > >ant xdoclet ejb jca web >cp -r build/web/engagement.war $DEPLOY >cp build/jca $DEPLOY >cp src/controller/Application* $DEPLOY >cp src/controller/Engagement* $DEPLOY >cp build/ejb/ApplicationProcess.jar $DEPLOY >cp build/ejb/BasicActivityLibrary.jar $DEPLOY >cp build/ejb/ControllerSupport.jar $DEPLOY >cp build/ejb/EngagementProcess.jar $DEPLOY >cp build/ejb/WingsClient.jar $DEPLOY > >run the Engagement_model.ddl in etc/db >run the src/ddl/Engagement*-scripts that match your db >run the src/ddl/Application*-scripts that match your db > >be sure to remove ApplicationSupport.jar and maybe other old stuff from >$DEPLOY. > >access http://localhost:8080/engagement/engagement-index.html with your >browser > >we should automate the deployment process somehow! > >tell me, if something doesn't work! This will help me, so I will help you ;-) > >regards, > >holger > > |
|
From: Lisa R. <lis...@sa...> - 2004-01-08 08:43:08
|
Hi Holger, Holger Engels wrote: >Sorry, I forgot to add ClaimLoader. ClaimLoader is not implemented anyway .. > > Is it added now? Can I update and try again? Thanks, Lisa |
|
From: Holger E. <he...@me...> - 2004-01-08 08:28:02
|
Quoting Lisa Retief <lis...@sa...>:
> Hi Holger,
>
> I have started the testing. Here are some issues as they occur.
>
> 1. Running $CONCERN_HOME/ant dist fails as ${jboss.home} ant property is
> not defined anywhere. Shall I add it to etc/build.properies? For now I
> have created custom-build.properties with it defined and the 'dist' task
> works.
Don't add it to build.properties. custom-build.properties is the right place
for it. Custom configuration shouldn't reside in the repository.
> 2. The $CONCERN_HOME/ant 'client' task has been removed - is this right?
It's part of the dist task now.
> 3. 'demo/ant xdoclet ejb jca web' fails because it can't find hibernate
> libraries. I downloaded it and added jar to demo/lib ant we get further,
> but still break with these compile errors:
> compile:
> [javac] Compiling 91 source files to
> /home/lisa/concern/concern-src-1.0.1/demo/build/class
> [javac]
> /home/lisa/concern/concern-src-1.0.1/demo/src/java/org/concern/test/claim/
CheckWarrantabilityBase.java:18:
>
> cannot resolve symbol
> [javac] symbol : class ClaimLoader
> [javac] location: package claim
> [javac]return org.concern.test.claim.ClaimLoader.load(id);
> [javac]^
> [javac]
> /home/lisa/concern/concern-src-1.0.1/demo/src/java/org/concern/test/claim/
RefuseBase.java:17:
>
> cannot resolve symbol
> [javac] symbol : class ClaimLoader
> [javac] location: package claim
> [javac]return org.concern.test.claim.ClaimLoader.load(id);
> [javac]
> [javac]
> /home/lisa/concern/concern-src-1.0.1/demo/src/java/org/concern/test/claim/
ReplaceBase.java:18:
>
> cannot resolve symbol
> [javac] symbol : class ClaimLoader
> [javac] location: package claim
> [javac] return org.concern.test.claim.ClaimLoader.load(id);
> [javac] ^
> [javac] 3 errors
>
> BUILD FAILED
> file:/home/lisa/concern/concern-src-1.0.1/demo/build.xml:134: Compile
> failed; see the compiler error output for details
Sorry, I forgot to add ClaimLoader. ClaimLoader is not implemented anyway ..
Holger Engels
(Dipl Inf Med)
--
Consultant, Architect, Developer
Mobile: +49 176 20119752
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
|
|
From: Lisa R. <lis...@sa...> - 2004-01-07 17:45:02
|
Hi Holger,
I have started the testing. Here are some issues as they occur.
1. Running $CONCERN_HOME/ant dist fails as ${jboss.home} ant property is
not defined anywhere. Shall I add it to etc/build.properies? For now I
have created custom-build.properties with it defined and the 'dist' task
works.
2. The $CONCERN_HOME/ant 'client' task has been removed - is this right?
3. 'demo/ant xdoclet ejb jca web' fails because it can't find hibernate
libraries. I downloaded it and added jar to demo/lib ant we get further,
but still break with these compile errors:
compile:
[javac] Compiling 91 source files to
/home/lisa/concern/concern-src-1.0.1/demo/build/class
[javac]
/home/lisa/concern/concern-src-1.0.1/demo/src/java/org/concern/test/claim/CheckWarrantabilityBase.java:18:
cannot resolve symbol
[javac] symbol : class ClaimLoader
[javac] location: package claim
[javac]return org.concern.test.claim.ClaimLoader.load(id);
[javac]^
[javac]
/home/lisa/concern/concern-src-1.0.1/demo/src/java/org/concern/test/claim/RefuseBase.java:17:
cannot resolve symbol
[javac] symbol : class ClaimLoader
[javac] location: package claim
[javac]return org.concern.test.claim.ClaimLoader.load(id);
[javac]
[javac]
/home/lisa/concern/concern-src-1.0.1/demo/src/java/org/concern/test/claim/ReplaceBase.java:18:
cannot resolve symbol
[javac] symbol : class ClaimLoader
[javac] location: package claim
[javac] return org.concern.test.claim.ClaimLoader.load(id);
[javac] ^
[javac] 3 errors
BUILD FAILED
file:/home/lisa/concern/concern-src-1.0.1/demo/build.xml:134: Compile
failed; see the compiler error output for details
Over to you for now :)
Thanks, Lisa
Holger Engels wrote:
>1. the jars have been marked as binary in the repository (hopefully ;-)
>
>2. the new demo process is checked in
>
>ant xdoclet ejb jca web
>cp -r build/web/engagement.war $DEPLOY
>cp build/jca $DEPLOY
>cp src/controller/Application* $DEPLOY
>cp src/controller/Engagement* $DEPLOY
>cp build/ejb/ApplicationProcess.jar $DEPLOY
>cp build/ejb/BasicActivityLibrary.jar $DEPLOY
>cp build/ejb/ControllerSupport.jar $DEPLOY
>cp build/ejb/EngagementProcess.jar $DEPLOY
>cp build/ejb/WingsClient.jar $DEPLOY
>
>run the Engagement_model.ddl in etc/db
>run the src/ddl/Engagement*-scripts that match your db
>run the src/ddl/Application*-scripts that match your db
>
>be sure to remove ApplicationSupport.jar and maybe other old stuff from
>$DEPLOY.
>
>access http://localhost:8080/engagement/engagement-index.html with your
>browser
>
>we should automate the deployment process somehow!
>
>tell me, if something doesn't work! This will help me, so I will help you ;-)
>
>regards,
>
>holger
>
>
|
|
From: Holger E. <he...@me...> - 2004-01-06 17:52:15
|
1. the jars have been marked as binary in the repository (hopefully ;-) 2. the new demo process is checked in ant xdoclet ejb jca web cp -r build/web/engagement.war $DEPLOY cp build/jca $DEPLOY cp src/controller/Application* $DEPLOY cp src/controller/Engagement* $DEPLOY cp build/ejb/ApplicationProcess.jar $DEPLOY cp build/ejb/BasicActivityLibrary.jar $DEPLOY cp build/ejb/ControllerSupport.jar $DEPLOY cp build/ejb/EngagementProcess.jar $DEPLOY cp build/ejb/WingsClient.jar $DEPLOY run the Engagement_model.ddl in etc/db run the src/ddl/Engagement*-scripts that match your db run the src/ddl/Application*-scripts that match your db be sure to remove ApplicationSupport.jar and maybe other old stuff from $DEPLOY. access http://localhost:8080/engagement/engagement-index.html with your browser we should automate the deployment process somehow! tell me, if something doesn't work! This will help me, so I will help you ;-) regards, holger Quoting Holger Engels <he...@me...>: > Quoting Lisa Retief <lis...@sa...>: > > > Okay Holger, > > > > After reverting to revision 1.5 of src/ant/concern-build.xml I got > > further, but this error occurred: > > > > [signjar] Signing Jar : > > /home/lisa/concern/concern-src-1.0.1/demo/build/web/mo > > deller/lib/jgraph.jar > > [signjar] jarsigner error: java.lang.RuntimeException: keystore load: > > null > > > > BUILD FAILED > > file:/home/lisa/concern/concern-src-1.0.1/demo/build.xml:224: exec > > returned: 1 > > > > So I commented the signjar task out of build.xml and it worked! Thanks. > > That's ok. The signed jars are only for webstarting the modeller. > > > > Now I have problems deploying. Initially there were problems again with > > corrupt jars under $CONCERN_HOME/demo/build/web/WEB_INF/lib but I sorted > > that out. Below some information on problems I cannot solve... any help > > appreciated. Compressed JBoss log file attached. I can help to write the > > English docs when I am done :) > > > > 1) I have a postgres db called TST (user test, password test) with all > > the tables in demo/etc/db/claim_postgres.ddl and > > dist/etc/db/concern_postgres.ddl created. > > 2) I have test-postgres-ds.xml in $JBOSS_HOME/server/default/deploy and > > JBoss is establishing a connection to the datasource just fine, and the > > JNDI ref corresponds to the one in process.properties. > > 3)I have copied contents of $CONCERN_HOME/demo/build/web to > > $JBOSS_HOME/server/default/deploy/irl.war > > 4) I have copied contents of $CONCERN_HOME/demo/build/ejb to > > $JBOSS_HOME/server/default/deploy/ > > 5) In the JBoss logs I get the following error on startup and it > > continues recurring: > > 2004-01-05 21:06:50,462 ERROR [STDERR] javax.ejb.FinderException: Find > > failed: j > > ava.sql.SQLException: ERROR: parser: parse error at or near "." at > > character 15 > > 2 > > 2004-01-05 21:06:50,466 ERROR [STDERR] at > > org.jboss.ejb.plugins.cmp.jdbc.JDBCAb > > stractQueryCommand.execute(JDBCAbstractQueryCommand.java:238) > > 2004-01-05 21:06:50,467 ERROR [STDERR] at > > org.jboss.ejb.plugins.cmp.jdbc.JDBCAb > > stractQueryCommand.execute(JDBCAbstractQueryCommand.java:111) > > 2004-01-05 21:06:50,467 ERROR [STDERR] at > > org.jboss.ejb.plugins.cmp.jdbc.JDBCFi > > ndEntitiesCommand.execute(JDBCFindEntitiesCommand.java:38) > > 2004-01-05 21:06:50,467 ERROR [STDERR] at > > org.jboss.ejb.plugins.cmp.jdbc.JDBCSt > > oreManager.findEntities(JDBCStoreManager.java:579) > > 2004-01-05 21:06:50,468 ERROR [STDERR] at > > org.jboss.ejb.plugins.CMPPersistenceM > > anager.findEntities(CMPPersistenceManager.java:311) > > 2004-01-05 21:06:50,468 ERROR [STDERR] at > > org.jboss.resource.connectionmanager. > > CachedConnectionInterceptor.findEntities(CachedConnectionInterceptor.jav > > a:322) > > 2004-01-05 21:06:50,468 ERROR [STDERR] at > > org.jboss.ejb.EntityContainer.findLoc > > al(EntityContainer.java:613) etc....... > > Hm, seems like something in the generated deployment descriptors of the > controller is corrupt. Have a look in: > > $CONCERN_HOME/dist/etc/process/jbosscmp-jdbc.xml > > You have deployed two processes: claim and project. I remember, there was a > > deployment problem some time ago, if you have more than one process at a > time. > However, the new packaging on my machine is working (the new demo actually > has > two processes). > > Also try to remove the claim scheduler and add it, when jboss has started. > > > > 6) Also, I am trying to access the demo web interface at URL > > http://myserver:8080/claim > > http://myserver:8080/claim/ClaimWorker > > as per your online demo. Is this correct? > > Yes, that's ok. > > Holger > > > > -----Original Message----- > > From: con...@li... > > [mailto:con...@li...] On Behalf Of Holger > > Engels > > Sent: 05 January 2004 19:41 > > To: con...@li... > > Cc: lis...@sa... > > Subject: [Concern-users] RE: [Concern-developers] New demo process > > > > Quoting Lisa Retief <lis...@sa...>: > > > > > Hi, > > > > > > Okay, fixed that then got: > > > > > > BUILD FAILED > > > file:/home/lisa/concern/concern-src-1.0.1/demo/build.xml:166: > > > /home/lisa/concern/concern-src-1.0.1/dist/dist/deploy not found. > > > > > > So, I thought I would go to $CONCERN_HOME/dist and run ant first, and > > > then I end up with this: > > > > > > BUILD FAILED > > > file:/home/lisa/concern/concern-src-1.0.1/dist/build.xml:47: Warning: > > > Could not find file > > > /home/lisa/concern/concern-src-1.0.1/dist/lib/ControllerSupport.jar to > > > > > copy. > > > > > > I can't find that anywhere. What next? > > > > Shit, I changed the packaging too and accidentally commited a new > > src/ant/ > > concern-build.xml, that is inconsistent with the old version. Go to > > $CONCERN_HOME and: > > > > rm src/ant/concern-build.xml > > cvs update -r 1.5 src/ant/concern-build.xml > > ant dist > > > > Then try 'ant' in $CONCERN_HOME/dist again. It should work now! If your > > patience isn't used up already ... where do you get now? > > > > You have been added as a developer to the project .. you're welcome! You > > will > > keep your write access to the repository as long as you make more or > > less > > valuable contributions from time to time. > > > > Regards, > > > > Holger Engels > > (Dipl Inf Med) > > > > -- > > Consultant, Architect, Developer > > Mobile: +49 176 20119752 > > > > ------------------------------------------------- > > This mail sent through IMP: http://horde.org/imp/ > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: IBM Linux Tutorials. > > Become an expert in LINUX or just sharpen your skills. Sign up for > > IBM's > > Free Linux Tutorials. Learn everything from the bash shell to sys > > admin. > > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > > _______________________________________________ > > Concern-users mailing list > > Con...@li... > > https://lists.sourceforge.net/lists/listinfo/concern-users > > > > --- > > Incoming mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.558 / Virus Database: 350 - Release Date: 02/01/2004 > > > > > > --- > > Outgoing mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.558 / Virus Database: 350 - Release Date: 02/01/2004 > > > > > > > > > Holger Engels > (Dipl Inf Med) > > -- > Consultant, Architect, Developer > Mobile: +49 176 20119752 > > ------------------------------------------------- > This mail sent through IMP: http://horde.org/imp/ > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Concern-users mailing list > Con...@li... > https://lists.sourceforge.net/lists/listinfo/concern-users > > Holger Engels (Dipl Inf Med) -- Consultant, Architect, Developer Mobile: +49 176 20119752 ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ |
|
From: Holger E. <he...@me...> - 2004-01-05 19:50:19
|
Quoting Lisa Retief <lis...@sa...>: > Okay Holger, > > After reverting to revision 1.5 of src/ant/concern-build.xml I got > further, but this error occurred: > > [signjar] Signing Jar : > /home/lisa/concern/concern-src-1.0.1/demo/build/web/mo > deller/lib/jgraph.jar > [signjar] jarsigner error: java.lang.RuntimeException: keystore load: > null > > BUILD FAILED > file:/home/lisa/concern/concern-src-1.0.1/demo/build.xml:224: exec > returned: 1 > > So I commented the signjar task out of build.xml and it worked! Thanks. That's ok. The signed jars are only for webstarting the modeller. > Now I have problems deploying. Initially there were problems again with > corrupt jars under $CONCERN_HOME/demo/build/web/WEB_INF/lib but I sorted > that out. Below some information on problems I cannot solve... any help > appreciated. Compressed JBoss log file attached. I can help to write the > English docs when I am done :) > > 1) I have a postgres db called TST (user test, password test) with all > the tables in demo/etc/db/claim_postgres.ddl and > dist/etc/db/concern_postgres.ddl created. > 2) I have test-postgres-ds.xml in $JBOSS_HOME/server/default/deploy and > JBoss is establishing a connection to the datasource just fine, and the > JNDI ref corresponds to the one in process.properties. > 3)I have copied contents of $CONCERN_HOME/demo/build/web to > $JBOSS_HOME/server/default/deploy/irl.war > 4) I have copied contents of $CONCERN_HOME/demo/build/ejb to > $JBOSS_HOME/server/default/deploy/ > 5) In the JBoss logs I get the following error on startup and it > continues recurring: > 2004-01-05 21:06:50,462 ERROR [STDERR] javax.ejb.FinderException: Find > failed: j > ava.sql.SQLException: ERROR: parser: parse error at or near "." at > character 15 > 2 > 2004-01-05 21:06:50,466 ERROR [STDERR] at > org.jboss.ejb.plugins.cmp.jdbc.JDBCAb > stractQueryCommand.execute(JDBCAbstractQueryCommand.java:238) > 2004-01-05 21:06:50,467 ERROR [STDERR] at > org.jboss.ejb.plugins.cmp.jdbc.JDBCAb > stractQueryCommand.execute(JDBCAbstractQueryCommand.java:111) > 2004-01-05 21:06:50,467 ERROR [STDERR] at > org.jboss.ejb.plugins.cmp.jdbc.JDBCFi > ndEntitiesCommand.execute(JDBCFindEntitiesCommand.java:38) > 2004-01-05 21:06:50,467 ERROR [STDERR] at > org.jboss.ejb.plugins.cmp.jdbc.JDBCSt > oreManager.findEntities(JDBCStoreManager.java:579) > 2004-01-05 21:06:50,468 ERROR [STDERR] at > org.jboss.ejb.plugins.CMPPersistenceM > anager.findEntities(CMPPersistenceManager.java:311) > 2004-01-05 21:06:50,468 ERROR [STDERR] at > org.jboss.resource.connectionmanager. > CachedConnectionInterceptor.findEntities(CachedConnectionInterceptor.jav > a:322) > 2004-01-05 21:06:50,468 ERROR [STDERR] at > org.jboss.ejb.EntityContainer.findLoc > al(EntityContainer.java:613) etc....... Hm, seems like something in the generated deployment descriptors of the controller is corrupt. Have a look in: $CONCERN_HOME/dist/etc/process/jbosscmp-jdbc.xml You have deployed two processes: claim and project. I remember, there was a deployment problem some time ago, if you have more than one process at a time. However, the new packaging on my machine is working (the new demo actually has two processes). Also try to remove the claim scheduler and add it, when jboss has started. > 6) Also, I am trying to access the demo web interface at URL > http://myserver:8080/claim > http://myserver:8080/claim/ClaimWorker > as per your online demo. Is this correct? Yes, that's ok. Holger > -----Original Message----- > From: con...@li... > [mailto:con...@li...] On Behalf Of Holger > Engels > Sent: 05 January 2004 19:41 > To: con...@li... > Cc: lis...@sa... > Subject: [Concern-users] RE: [Concern-developers] New demo process > > Quoting Lisa Retief <lis...@sa...>: > > > Hi, > > > > Okay, fixed that then got: > > > > BUILD FAILED > > file:/home/lisa/concern/concern-src-1.0.1/demo/build.xml:166: > > /home/lisa/concern/concern-src-1.0.1/dist/dist/deploy not found. > > > > So, I thought I would go to $CONCERN_HOME/dist and run ant first, and > > then I end up with this: > > > > BUILD FAILED > > file:/home/lisa/concern/concern-src-1.0.1/dist/build.xml:47: Warning: > > Could not find file > > /home/lisa/concern/concern-src-1.0.1/dist/lib/ControllerSupport.jar to > > > copy. > > > > I can't find that anywhere. What next? > > Shit, I changed the packaging too and accidentally commited a new > src/ant/ > concern-build.xml, that is inconsistent with the old version. Go to > $CONCERN_HOME and: > > rm src/ant/concern-build.xml > cvs update -r 1.5 src/ant/concern-build.xml > ant dist > > Then try 'ant' in $CONCERN_HOME/dist again. It should work now! If your > patience isn't used up already ... where do you get now? > > You have been added as a developer to the project .. you're welcome! You > will > keep your write access to the repository as long as you make more or > less > valuable contributions from time to time. > > Regards, > > Holger Engels > (Dipl Inf Med) > > -- > Consultant, Architect, Developer > Mobile: +49 176 20119752 > > ------------------------------------------------- > This mail sent through IMP: http://horde.org/imp/ > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for > IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys > admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Concern-users mailing list > Con...@li... > https://lists.sourceforge.net/lists/listinfo/concern-users > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.558 / Virus Database: 350 - Release Date: 02/01/2004 > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.558 / Virus Database: 350 - Release Date: 02/01/2004 > > > Holger Engels (Dipl Inf Med) -- Consultant, Architect, Developer Mobile: +49 176 20119752 ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ |
|
From: Holger E. <he...@me...> - 2004-01-05 17:41:05
|
Quoting Lisa Retief <lis...@sa...>: > Hi, > > Okay, fixed that then got: > > BUILD FAILED > file:/home/lisa/concern/concern-src-1.0.1/demo/build.xml:166: > /home/lisa/concern/concern-src-1.0.1/dist/dist/deploy not found. > > So, I thought I would go to $CONCERN_HOME/dist and run ant first, and > then I end up with this: > > BUILD FAILED > file:/home/lisa/concern/concern-src-1.0.1/dist/build.xml:47: Warning: > Could not find file > /home/lisa/concern/concern-src-1.0.1/dist/lib/ControllerSupport.jar to > copy. > > I can't find that anywhere. What next? Shit, I changed the packaging too and accidentally commited a new src/ant/ concern-build.xml, that is inconsistent with the old version. Go to $CONCERN_HOME and: rm src/ant/concern-build.xml cvs update -r 1.5 src/ant/concern-build.xml ant dist Then try 'ant' in $CONCERN_HOME/dist again. It should work now! If your patience isn't used up already ... where do you get now? You have been added as a developer to the project .. you're welcome! You will keep your write access to the repository as long as you make more or less valuable contributions from time to time. Regards, Holger Engels (Dipl Inf Med) -- Consultant, Architect, Developer Mobile: +49 176 20119752 ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ |
|
From: Holger E. <he...@me...> - 2003-12-05 09:42:32
|
Hi, 1.0.1 has been released and is available for download on SourceForge. See the sf news feed / changelogs for a list of new fetures und bugfixes. Regards, Holger Engels (Dipl Inf Med) -- Consultant, Architect, Developer Mobile: +49 176 20119752 ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ |
|
From: Holger E. <he...@me...> - 2003-11-20 15:44:35
|
Hi, I've just released con:cern 1.0 .. BTW: there are rss feeds on the home page, now Cheers, Holger Holger Engels (Dipl Inf Med) -- Consultant, Architect, Developer Mobile: +49 176 20119752 ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ |