concern-users Mailing List for osbl (Page 7)
Brought to you by:
hengels,
leonchiver
Menu
▾
▴
concern-users — users
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: Raoul Z. <rao...@to...> - 2004-05-14 09:21:27
|
Probably doing something wrong..... (again) I'm running from eclipse now, as I kept getting NoClassDefFoundError. Now I get other errors, like: "Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial" Which appears when executing: controllerHome =3D (ControllerHome)new InitialContext().lookup(name + "/Controller"); Seems it does not have access to the Jboss server. I've checked my lib directory and have the exact same jars there as you do... Is there any other way to do what you'd normally do with the script or this class? How do you specify the pk?? I've tried [SQLUser].Engagement.id, just Engagement.id and just id. Raoul -----Oorspronkelijk bericht----- Van: Holger Engels [mailto:he...@me...]=20 Verzonden: vrijdag 14 mei 2004 10:16 Aan: Raoul Zon CC: con...@li... Onderwerp: RE: server.log and jmx-console output Quoting Raoul Zon <rao...@to...>:=20 =20 > Holger, > =20 > I've checked in the new AbstractActivity class. =20 Thanks!=20 =20 > I've tried running both: <pk> and the primary key, both fail. > The first one (how stupid of me to even try...) gives the newline error.=20 > The other one gives:=20 > "[: =3D=3D: unknown operand=20 > Exception in thread "main" java.lang.NoClassDefFoundError:=20 > org/concern/j2ee/client/commandline/Concern"=20 > I've checked the dist/lib and the jar containing the class does exist. > I've tried setting the classpath manually by overriding the shellscript,=20 > but without success.=20 =20 The cygwin bash has problems to interprete the script. Don't know why.=20 =20 > I run the command from the root of the project...in my case: > /cygdrive/c/eclipse/workspace/concern=20 =20 You need the jboss client jars to access jboss. The client jars are copied by=20 the build script, if you set jboss.client in the custom-build.properties of=20 this module. The content of my client/dist/lib is:=20 =20 dist/=20 dist/lib=20 dist/lib/concern-client.jar=20 dist/lib/concern-client-commandline.jar=20 dist/lib/jboss-j2ee.jar=20 dist/lib/concern-controller.jar=20 dist/lib/concern-model.jar=20 dist/lib/jsse.jar=20 dist/lib/jbossjmx-ant.jar=20 dist/lib/jbosssx-client.jar=20 dist/lib/jacorb.jar=20 dist/lib/getopt.jar=20 dist/lib/jboss-common-client.jar=20 dist/lib/log4j.jar=20 dist/lib/jbosscx-client.jar=20 dist/lib/jboss-client.jar=20 dist/lib/jmx-ejb-connector-client.jar=20 dist/lib/jboss-transaction-client.jar=20 dist/lib/jbossha-client.jar=20 dist/lib/gnu-regexp.jar=20 dist/lib/jnet.jar=20 dist/lib/concurrent.jar=20 dist/lib/jboss-net-client.jar=20 dist/lib/auth.conf=20 dist/lib/jmx-connector-client-factory.jar=20 dist/lib/xdoclet-module-jboss-net.jar=20 dist/lib/jboss-jaas.jar=20 dist/lib/jmx-rmi-connector-client.jar=20 dist/lib/jboss-system-client.jar=20 dist/lib/jbossmqha.jar=20 dist/lib/jboss-iiop-client.jar=20 dist/lib/jmx-invoker-adaptor-client.jar=20 dist/lib/jbossmq-client.jar=20 dist/lib/jboss-jsr77-client.jar=20 dist/lib/jbossall-client.jar=20 dist/lib/jnp-client.jar=20 dist/lib/jcert.jar=20 =20 =20 Holger=20 ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ |
|
From: Holger E. <he...@me...> - 2004-05-14 08:16:29
|
Quoting Raoul Zon <rao...@to...>: > Holger, > > I've checked in the new AbstractActivity class. Thanks! > I've tried running both: <pk> and the primary key, both fail. > The first one (how stupid of me to even try...) gives the newline error. > The other one gives: > "[: ==: unknown operand > Exception in thread "main" java.lang.NoClassDefFoundError: > org/concern/j2ee/client/commandline/Concern" > I've checked the dist/lib and the jar containing the class does exist. > I've tried setting the classpath manually by overriding the shellscript, > but without success. The cygwin bash has problems to interprete the script. Don't know why. > I run the command from the root of the project...in my case: > /cygdrive/c/eclipse/workspace/concern You need the jboss client jars to access jboss. The client jars are copied by the build script, if you set jboss.client in the custom-build.properties of this module. The content of my client/dist/lib is: dist/ dist/lib dist/lib/concern-client.jar dist/lib/concern-client-commandline.jar dist/lib/jboss-j2ee.jar dist/lib/concern-controller.jar dist/lib/concern-model.jar dist/lib/jsse.jar dist/lib/jbossjmx-ant.jar dist/lib/jbosssx-client.jar dist/lib/jacorb.jar dist/lib/getopt.jar dist/lib/jboss-common-client.jar dist/lib/log4j.jar dist/lib/jbosscx-client.jar dist/lib/jboss-client.jar dist/lib/jmx-ejb-connector-client.jar dist/lib/jboss-transaction-client.jar dist/lib/jbossha-client.jar dist/lib/gnu-regexp.jar dist/lib/jnet.jar dist/lib/concurrent.jar dist/lib/jboss-net-client.jar dist/lib/auth.conf dist/lib/jmx-connector-client-factory.jar dist/lib/xdoclet-module-jboss-net.jar dist/lib/jboss-jaas.jar dist/lib/jmx-rmi-connector-client.jar dist/lib/jboss-system-client.jar dist/lib/jbossmqha.jar dist/lib/jboss-iiop-client.jar dist/lib/jmx-invoker-adaptor-client.jar dist/lib/jbossmq-client.jar dist/lib/jboss-jsr77-client.jar dist/lib/jbossall-client.jar dist/lib/jnp-client.jar dist/lib/jcert.jar Holger ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ |
|
From: Raoul Z. <rao...@to...> - 2004-05-14 08:04:57
|
Holger, I've checked in the new AbstractActivity class. I've tried running both: <pk> and the primary key, both fail. The first one (how stupid of me to even try...) gives the newline error. The other one gives: "[: =3D=3D: unknown operand Exception in thread "main" java.lang.NoClassDefFoundError: org/concern/j2ee/client/commandline/Concern" I've checked the dist/lib and the jar containing the class does exist. I've tried setting the classpath manually by overriding the shellscript, but without success. I run the command from the root of the project...in my case: /cygdrive/c/eclipse/workspace/concern Shouldn't this action be integral part of the build?! Any suggestions?? Regards, Raoul -----Oorspronkelijk bericht----- Van: Holger Engels [mailto:he...@me...]=20 Verzonden: donderdag 13 mei 2004 18:10 Aan: Raoul Zon CC: rj...@zo... Onderwerp: RE: server.log and jmx-console output Quoting Raoul Zon <rao...@to...>:=20 =20 > Holger, > =20 > My sourceforge account is: rj...@us... =20 I have added you as a developer. =20 =20 > Somehow I keep losing my mail here at Topicus so could you, once=20 > again, > explain how to check in changes made to the con:cern code.=20 > Please also CC to rj...@zo..., so I have a backup in case I=20 > lose that e-mail as well.=20 =20 You can either get a fresh checkout as described on the sf site or you can=20 relocate your anonymous checkout, using the following command:=20 =20 for f in `find -name Root` =20 do =20 echo ":ext:rj...@cv...:/cvsroot/concern" > $f =20 done=20 =20 =20 > Having difficulties running the shell scripts..... > Running "client/dist/bin/cc.sh Engagement create <pk>" gives error:=20 > bash: syntax error near unexpected token `newline'=20 =20 Did you run exactly this command or did you replace <pk> with the primary key=20 of the engagements?=20 =20 Holger=20 =20 =20 > Regards, > =20 > Raoul > =20 > -----Oorspronkelijk bericht----- > Van: Holger Engels [mailto:he...@me...] =20 > Verzonden: donderdag 13 mei 2004 17:11=20 > Aan: Raoul Zon=20 > CC: con...@li...=20 > Onderwerp: RE: server.log and jmx-console output=20 > =20 > =20 > Quoting Raoul Zon <rao...@to...>: > =20 > > Hi Holger, > > =20 > > I fixed the servlet errors I received yesterday by fixing some bugs=20 > > in > > the code in the j2ee folder. =20 > > There are ClassCastExceptions in org.concern.j2ee.AbstractActivity =20 > > =20 > > Where you do a Classcast in the getDescriptor method you cast "this" > > to=20 > > the wrong type. My guess (and it works), is to cast the code in the > > first if to AbstractAsynchronousActivity and the second to =20 > > AbstractSynchronousActivity as you also check for that type with =20 > > instanceof. =20 > > =20 > > After the recompile and redeploy I don't have errors anymore. > =20 > .. so, what was your sourceforge account? > =20 > > Still one problem though.....: > > I can create engagements, but can't see them or alter them in the =20 > > worklist parts. I CAN see them in the supervisor part.... =20 > > My guess here is the problem has to do something with the =20 > > AdvertisedInternally and AdvertisedExternally as they seem to be asked=20 > =20 > > from the DB and are not present. > =20 > The supervisor shows the content of the engagement table. Check, if=20 > the > engagements are in the engagement_subject table, too. I suppose they're=20 > not. =20 > If you don't see them, use the command line client to create them: =20 > =20 > client/dist/bin/cc.sh Engagement create <pk> > =20 > and tell the controller to process them: > =20 > client/dist/bin/cc.sh Engagement process <pk> > =20 > watch the jboss log. The controller should present the engagement to > all activities. The precondition of InternalAdvertising will match and > thus it will be enlisted. The following command should list your=20 > engagements: =20 > =20 > client/dist/bin/cc.sh Engagement list InternalAdvertising > =20 > ciao, > =20 > holger > =20 > > =20 > > -----Oorspronkelijk bericht-----=20 > > Van: Holger Engels [mailto:he...@me...] =20 > > Verzonden: donderdag 13 mei 2004 14:47 > > Aan: Raoul Zon =20 > > Onderwerp: RE: server.log and jmx-console output =20 > > =20 > > =20 > > Hi, > > =20 > > there's a delay of up to 5h between cvs checkins and availability on > > anonymous =20 > > cvs. This was the reason, why you didn't see the changes, I made =20 > > yesterday. =20 > > =20 > > Holger > > =20 > > =20 > > ------------------------------------------------- > > This mail sent through IMP: http://horde.org/imp/ =20 > > =20 > > =20 > =20 > =20 > Holger Engels > (Dipl Inf Med) =20 > =20 > -- > Consultant, Architect, Developer =20 > Mobile: +49 176 20119752 =20 > =20 > ------------------------------------------------- > This mail sent through IMP: http://horde.org/imp/=20 > =20 > =20 =20 =20 Holger Engels=20 (Dipl Inf Med)=20 =20 --=20 Consultant, Architect, Developer=20 Mobile: +49 176 20119752=20 ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ |
|
From: Raoul Z. <rao...@to...> - 2004-05-13 14:14:32
|
Hi Holger, I fixed the servlet errors I received yesterday by fixing some bugs in the code in the j2ee folder. There are ClassCastExceptions in org.concern.j2ee.AbstractActivity Where you do a Classcast in the getDescriptor method you cast "this" to the wrong type. My guess (and it works), is to cast the code in the first if to AbstractAsynchronousActivity and the second to AbstractSynchronousActivity as you also check for that type with instanceof. After the recompile and redeploy I don't have errors anymore. Still one problem though.....: I can create engagements, but can't see them or alter them in the worklist parts. I CAN see them in the supervisor part.... My guess here is the problem has to do something with the AdvertisedInternally and AdvertisedExternally as they seem to be asked from the DB and are not present. Regards, Raoul -----Oorspronkelijk bericht----- Van: Holger Engels [mailto:he...@me...]=20 Verzonden: donderdag 13 mei 2004 14:47 Aan: Raoul Zon Onderwerp: RE: server.log and jmx-console output Hi,=20 =20 there's a delay of up to 5h between cvs checkins and availability on anonymous=20 cvs. This was the reason, why you didn't see the changes, I made yesterday.=20 =20 Holger=20 =20 ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ |
|
From: Holger E. <he...@me...> - 2004-05-12 12:49:05
|
Quoting Raoul Zon <rao...@to...>: > Holger, > > There's no bigint datatype in MaxDB, the only relevant types are > integer, long, char and varchar. > I have it running now (I can log in), but there are some servlet errors > when trying to access EngagementWorker and ApplicationWorker. Try to restart jboss. It seems like you have loaded some classes several times from different class loaders. This can happen, when the process or controller is redeployed after the war has been accessed. Alternatively you could redploy the jars in the correct order: touch Allication*.jar Engagement*.jar engagement/WEB-INF/web.xml This could be avoided, if you put all deployables into an ear and thus always reload the whole ear. However this takes longer and I don't like long roundtrips. If I keep the deployables separate and don't deploy them in mixed order, it is working without the ear. > Can I check in the altered sapdb.xsl? If you tell me your sf account, I can add you to the project. You will have to modify your CVS/Root files or get a fresh checkout with your account: for f in `find -name Root` do echo ":ext:you...@cv...:/cvsroot/concern" > $f done > By the way, is this your daily job developing con:cern or is it a > hobbyproject you're running? It started as a hobby project, when I was a freelancer. Now, I'm employed in a company, that is integrating con:cern with their ERP suite, shop, etc. From beginning of next month on, it will be my daily job. You're welcome! Holger > -----Oorspronkelijk bericht----- > Van: Holger Engels [mailto:he...@me...] > Verzonden: woensdag 12 mei 2004 13:18 > Aan: Raoul Zon > CC: con...@li... > Onderwerp: RE: server.log and jmx-console output > > > Quoting Raoul Zon <rao...@to...>: > > > Holger, > > > > I changed timeout to "varchar(256)" and currently it runs without > > errors!!! > > .. hm, maybe something like bigint instead of varchar? > > It would be great, if you could correct the xsl according to your > findings > with sapdb .. > > > BUT....as the never ending story continues, logging in seems to be a > > problem. I provide an arbitrary user and pass (which are the same) but > > > get a authentication failed. > > Sorry, I forgot to mention that in the documentation. You have to tell > jboss, > how to authenticate by editing the > jboss/server/default/conf/login-config.xml. > Add the following lines: > > <application-policy name = "concern"> > <authentication> > <login-module > code="org.jboss.security.auth.spi.SimpleServerLoginModule" > flag = "required" /> > </authentication> > </application-policy> > > > Regards, > > Holger > > > > -----Oorspronkelijk bericht----- > > Van: Holger Engels [mailto:he...@me...] > > Verzonden: woensdag 12 mei 2004 12:11 > > Aan: Raoul Zon > > Onderwerp: RE: server.log and jmx-console output > > > > > > Quoting Raoul Zon <rao...@to...>: > > > > > Holger, > > > > > > What did you fix....I did a complete "Replace with latest from > > > HEAD", > > > but still get the conversion error after the build. Anything > > particular > > > you changed or haven't you checked in the fix yet? > > > > The ddls are generated from xsl templates located in > > devel/src/res/xsl/ddl. > > You have to run > > > > cd devel > > ant dist > > cd .. > > cd j2ee-demo > > ant concern > > > > then you should have ddls with an integer typed timeout field in the > > timer > > table. > > > > Holger > > > > > Raoul > > > > > > -----Oorspronkelijk bericht----- > > > Van: Holger Engels [mailto:he...@me...] > > > Verzonden: woensdag 12 mei 2004 11:45 > > > Aan: Raoul Zon > > > Onderwerp: Re: server.log and jmx-console output > > > > > > > > > Quoting Raoul Zon <rao...@to...>: > > > > > > > Holger, > > > > > > > > Here are my server.log containing the errors and the jmx-console > > > > output > > > > in textfile. > > > > > > Thanks, > > > > > > it's looking quite ok. Only the column type of field timeout in the > > > *_timer > > > tables is wrong. The error occurs periodically, because the > scheduler > > > service > > > polls these tables. I fixed it in cvs. > > > > > > Regards, > > > > > > Holger Engels > > > (Dipl Inf Med) > > > > > > -- > > > Consultant, Architect, Developer > > > Mobile: +49 176 20119752 > > > > > > ------------------------------------------------- > > > This mail sent through IMP: http://horde.org/imp/ > > > > > > > > > > > > Holger Engels > > (Dipl Inf Med) > > > > -- > > Consultant, Architect, Developer > > Mobile: +49 176 20119752 > > > > ------------------------------------------------- > > This mail sent through IMP: http://horde.org/imp/ > > > > > > > Holger Engels > (Dipl Inf Med) > > -- > Consultant, Architect, Developer > Mobile: +49 176 20119752 > > ------------------------------------------------- > This mail sent through IMP: http://horde.org/imp/ > 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-05-12 11:18:22
|
Quoting Raoul Zon <rao...@to...>:
> Holger,
>
> I changed timeout to "varchar(256)" and currently it runs without
> errors!!!
.. hm, maybe something like bigint instead of varchar?
It would be great, if you could correct the xsl according to your findings
with sapdb ..
> BUT....as the never ending story continues, logging in seems to be a
> problem. I provide an arbitrary user and pass (which are the same) but
> get a authentication failed.
Sorry, I forgot to mention that in the documentation. You have to tell jboss,
how to authenticate by editing the jboss/server/default/conf/login-config.xml.
Add the following lines:
<application-policy name = "concern">
<authentication>
<login-module
code="org.jboss.security.auth.spi.SimpleServerLoginModule"
flag = "required" />
</authentication>
</application-policy>
Regards,
Holger
> -----Oorspronkelijk bericht-----
> Van: Holger Engels [mailto:he...@me...]
> Verzonden: woensdag 12 mei 2004 12:11
> Aan: Raoul Zon
> Onderwerp: RE: server.log and jmx-console output
>
>
> Quoting Raoul Zon <rao...@to...>:
>
> > Holger,
> >
> > What did you fix....I did a complete "Replace with latest from HEAD",
> > but still get the conversion error after the build. Anything
> particular
> > you changed or haven't you checked in the fix yet?
>
> The ddls are generated from xsl templates located in
> devel/src/res/xsl/ddl.
> You have to run
>
> cd devel
> ant dist
> cd ..
> cd j2ee-demo
> ant concern
>
> then you should have ddls with an integer typed timeout field in the
> timer
> table.
>
> Holger
>
> > Raoul
> >
> > -----Oorspronkelijk bericht-----
> > Van: Holger Engels [mailto:he...@me...]
> > Verzonden: woensdag 12 mei 2004 11:45
> > Aan: Raoul Zon
> > Onderwerp: Re: server.log and jmx-console output
> >
> >
> > Quoting Raoul Zon <rao...@to...>:
> >
> > > Holger,
> > >
> > > Here are my server.log containing the errors and the jmx-console
> > > output
> > > in textfile.
> >
> > Thanks,
> >
> > it's looking quite ok. Only the column type of field timeout in the
> > *_timer
> > tables is wrong. The error occurs periodically, because the scheduler
> > service
> > polls these tables. I fixed it in cvs.
> >
> > Regards,
> >
> > Holger Engels
> > (Dipl Inf Med)
> >
> > --
> > Consultant, Architect, Developer
> > Mobile: +49 176 20119752
> >
> > -------------------------------------------------
> > This mail sent through IMP: http://horde.org/imp/
> >
> >
>
>
> Holger Engels
> (Dipl Inf Med)
>
> --
> Consultant, Architect, Developer
> Mobile: +49 176 20119752
>
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/
>
>
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-05-12 08:10:32
|
Quoting Raoul Zon <rao...@to...>:
> Holger,
>
> I proceeded with the steps you mentioned and deployed everything step by
> step.
> The moment I deploy the war I get errors.
> It seems to me there's some problem with the EJB's and some conversion
> in the DB.
can you please check the jndi view (jmx-console) .. which beans have been
deployed so far?
> The first error I get is about unbound EJB's Engagement/Scheduler and
> Application/Scheduler.
Hm, that's strange. The war is not accessing the scheduler bean at all. It is
only used by the controller bean.
> Then it loads the hibernate mappings without problems and runs into a
> "ConversionExceptionSapDB: Cannot convert data 1084347054092 to type
> Timestamp" from the SapDB driver.=20
This could be the scheduler bean. try to change the column "timeout" in the
tables named *_timer to type integer or bigint. If this solves the problem, I
will fix the sapdb script .. I should have tested it on sapdb once again. I
admit, I was only using postgres in the past.
> Maybe I can send you my server.log so you can see what's wrong.
Good idea. Send it to he...@me... and include the jndi view.
Thanks,
Holger
> Raoul
>
> -----Original Message-----
> From: Holger Engels [mailto:he...@me...]=20
> Sent: dinsdag 11 mei 2004 17:32
> To: con...@li...
> Cc: Raoul Zon
> Subject: RE: [Concern-users] Installation failures
>
> Raoul,=20
> =20
> I fixed a bug in the j2ee-demo/build.xml script. now con:cern should
> generate=20
> the correct ddl scripts for the specified database.vendor defined in=20
> custom-build.properties=20
> =20
> Quoting Raoul Zon <rao...@to...>:=20
> =20
> > Holger,
> > =20
> > Sorry for my late reaction, but got a bit further with the process.
> > I found the generated ddl-scripts don't comply with MaxDB 7.5=20
> > I had to manually alter them and generate the tables. After that I had
>
> > some problems with users on the DB as well, so I re-installed MaxDB
> and=20
> > while I was at it, I re-installed Jboss as well.=20
> > The DB is now connecting properly, so that's fixed....=20
> > The last time I ran con:cern it almost completely started without
> error,=20
> > but sometimes can't seem to register the EJB's and when started it=20
> > starts generating errors.=20
> =20
> The errors during startup might be ok, if it is only the scheduler
> errors. the=20
> scheduler tries to call the controller before it is actually available.=20
> =20
> > I'm still using the CVS version, as the binary seems to be broken as I
> > can't get it to build properly.=20
> > Did a new checkout by the way, which I will start building in a
> minute.=20
> > =20
> > What jars are required in server/lib that aren't part of the build of
> > con:cern??=20
> =20
> Look at the deploy_* tasks in the j2ee-demo/build.xml. The build is
> supposed=20
> to copy all required files (hopefully).=20
> =20
> Regards,=20
> =20
> Holger=20
> =20
> > -----Original Message-----
> > From: Holger Engels [mailto:he...@me...]=3D20=20
> > Sent: maandag 10 mei 2004 17:28=20
> > To: con...@li...=20
> > Cc: Raoul Zon=20
> > Subject: RE: [Concern-users] Installation failures=20
> > =20
> > Quoting Raoul Zon <rao...@to...>:=3D20
> > =3D20=20
> > > Holger,
> > > =3D20=20
> > > Didn't get the binary dist to run, but the one I checked out from
> CVS=3D20=20
> > > is=20
> > > able to compile once I removed three invalid (non-existent) calls
> to=3D20=20
> > > methods within AbstractActivity.java=3D20=20
> > =3D20
> > I moved some methods from abstract activity to its descendants and was
>
> > not=3D20=20
> > finished. does it look like this:=3D20=20
> > =3D20=20
> > [javac]=3D20=20
> >
> /home/hengels/jdevel/concern/j2ee/src/java/org/concern/j2ee/AbstractActi
>
> > vity.java:209:=3D20=20
> > cannot resolve symbol=3D20=20
> > [javac] symbol : method getTimeout ()=3D20=20
> > [javac] location: class org.concern.j2ee.AbstractActivity=3D20=20
> > [javac] buffer.append("" + getTimeout());=3D20=20
> > [javac] ^=3D20=20
> > [javac]=3D20=20
> >
> /home/hengels/jdevel/concern/j2ee/src/java/org/concern/j2ee/AbstractActi
>
> > vity.java:213:=3D20=20
> > cannot resolve symbol=3D20=20
> > [javac] symbol : method getRetryDelay ()=3D20=20
> > [javac] location: class org.concern.j2ee.AbstractActivity=3D20=20
> > [javac] buffer.append("" + getRetryDelay());=3D20=20
> > [javac] ^=3D20=20
> > [javac]=3D20=20
> >
> /home/hengels/jdevel/concern/j2ee/src/java/org/concern/j2ee/AbstractActi
>
> > vity.java:215:=3D20=20
> > cannot resolve symbol=3D20=20
> > [javac] symbol : method getTrials ()=3D20=20
> > [javac] location: class org.concern.j2ee.AbstractActivity=3D20=20
> > [javac] buffer.append("" + getTrials());=3D20=20
> > =3D20=20
> > if yes, you can savely ignore it.=3D20=20
> > =3D20=20
> > =3D20=20
> > =3D20=20
> > > However....when I deploy the j2ee-demo with the engagement war after
> > > doing an "all" on the build file of j2ee-demo and running the server
> I=20
> > =20
> > > get loads and loads of errors and can't seem to login, whatever I=20
> > > use.
> > =20
> > > Probably something simple I overlooked to compile or run, but =
> any=3D20
> > > suggestions.=3D20=20
> > =3D20
> > try to deploy the components one by one:=3D20=20
> > =3D20=20
> > 0. remove all con:cern components from jboss=3D20=20
> > 1. copy the required jars to jboss/default/server/lib=3D20=20
> > 2. start jboss (you should see no errors)=3D20=20
> > 3. configure your datasource and deploy it=3D20=20
> > 4. deploy the jta session service=3D20=20
> > 5. deploy the engagement model=3D20=20
> > 6. deploy the engagement process=3D20=20
> > 7. deploy the engagement controller=3D20=20
> > 8. deploy the engagement scheduler=3D20=20
> > 9. deploy application process/controller/scheduler=3D20=20
> > 10. deploy the engagement.war=3D20=20
> > =3D20=20
> > send me your first errors.=3D20=20
> > =3D20=20
> > =3D20=20
> > > FYI:
> > > I'm using MaxDB (latest version) (old SapDB as you probably
> know).=3D20=20
> > > Jboss 3.2.3=3D20=20
> > =3D20
> > I'm using postgres. however maxdb should work, too. make sure, that
> the=3D20=20
> > engagement model is configured correctly (dialect / datasource). make=20
> > sure,=3D20=20
> > that the controller's entity beans are configured correctly=3D20=20
> > (jbosscmp-jdbc.xml). normally these configurations are applied by the=20
> > build=3D20=20
> > scripts according to the respective etc/custom-build.properties. did
> you=20
> > =20
> > customize them? can you please verify that your configuration is in
> > effect?=3D20=20
> > =3D20=20
> > unzip -c EngagementModel.sar META-INF/jboss-service.xml=3D20=20
> > unzip -c EngagementController.jar META-INF/jbosscmp-jdbc.xml=3D20=20
> > =3D20=20
> > thanks for your patience,=3D20=20
> > =3D20=20
> > holger=3D20=20
> > =3D20=20
> > =3D20=20
> > > Raoul
> > > =3D20=20
> > > -----Oorspronkelijk bericht-----=20
> > > Van: Holger Engels [mailto:he...@me...] =3D20=20
> > > Verzonden: maandag 10 mei 2004 15:15=3D20=20
> > > Aan: con...@li...=3D20=20
> > > CC: Raoul Zon=3D20=20
> > > Onderwerp: RE: [Concern-users] Installation failures=3D20=20
> > > =3D20=20
> > > =3D20=20
> > > Hm,=20
> > > =3D20=20
> > > seems like there's a target dependency missing. dist should depend
> on=20
> > > build! =3D20=20
> > > Try: =3D20=20
> > > =3D20=20
> > > cd client=20
> > > ant build dist =3D20=20
> > > =3D20=20
> > > afterwards, the j2ee-demo build should work, too (hopefully).=20
> > > =3D20=20
> > > Holger=20
> > > =3D20=20
> > > =3D20=20
> > > Quoting Raoul Zon <rao...@to...>:=20
> > > =3D20=20
> > > > Holger,
> > > > =3D20=20
> > > > Your suggestion does seem to work. I get two succesfull builds
> and=3D20=20
> > > > the=20
> > > > search on *Local.java gave exactly the same results as you wrote.
> =3D20=20
> > > > =3D20=20
> > > > Building model and modeller succeeded as well.=20
> > > > =3D20=20
> > > > Now only client and j2ee-demo fail:=20
> > > > Client can't find the file concern-client.jar as it seems make a=20
> > copy=3D20
> > > of
> > > > it somewhere.
> > > > j2ee-demo gives 70 compilation errors concerning, among others,
> the=20
> > =20
> > > > classes Work and DefaultWorkList, which it can't resolve. =3D20
> > > > =3D20=20
> > > > Raoul Zon=20
> > > > =3D20=20
> > > > -----Oorspronkelijk bericht-----=3D20=20
> > > > Van: Holger Engels [mailto:he...@me...] =3D20=20
> > > > Verzonden: maandag 10 mei 2004 14:34=20
> > > > Aan: Raoul Zon =3D20=20
> > > > Onderwerp: Re: [Concern-users] Installation failures =3D20=20
> > > > =3D20=20
> > > > =3D20=20
> > > > try it like this:=20
> > > > =3D20=20
> > > > cd j2ee=3D20=20
> > > > ant xdoclet =3D20=20
> > > > ant dist =3D20=20
> > > > =3D20=20
> > > > some of the local interfaces should be generated by xdoclet:=20
> > > > =3D20=20
> > > > find -name *Local.java=3D20=20
> > > > ./src/java/org/concern/j2ee/ActionLocal.java =3D20=20
> > > > ./src/java/org/concern/j2ee/ActivityLocal.java =3D20=20
> > > > ./src/java/org/concern/j2ee/ConditionLocal.java =3D20=20
> > > > ./src/java/org/concern/j2ee/ExitLocal.java =3D20=20
> > > > ./src/java/org/concern/j2ee/ControllerLocal.java =3D20=20
> > > > ./src/java/org/concern/j2ee/LoaderLocal.java =3D20=20
> > > > ./build/src/java/org/concern/j2ee/LogLocal.java =3D20=20
> > > > ./build/src/java/org/concern/j2ee/ArchiveLocal.java =3D20=20
> > > > ./build/src/java/org/concern/j2ee/TimerLocal.java =3D20=20
> > > > ./build/src/java/org/concern/j2ee/EnlistmentLocal.java =3D20=20
> > > > ./build/src/java/org/concern/j2ee/SchedulerLocal.java =3D20=20
> > > > ./build/src/java/org/concern/j2ee/SubjectLocal.java =3D20=20
> > > > =3D20=20
> > > > can you confirm this? If not, come back to me,=20
> > > > =3D20=20
> > > > regards,=20
> > > > =3D20=20
> > > > Holger=20
> > > > =3D20=20
> > > > Quoting Raoul Zon <rao...@to...>:=20
> > > > =3D20=20
> > > > > Hi,=20
> > > > > =3D20
> > > > > I've downloaded the concern-all-1.1.tgz and followed the
> procedure=20
> > > > > on=3D20=20
> > > > > the installation page. =3D20=20
> > > > > I've tried installing on both windows and linux, but I keep=20
> > getting=3D20
> > > =3D20
> > > > > build failures when compiling. =3D20
> > > > > Model compiles oke. =3D20=20
> > > > > =3D20=20
> > > > > j2ee gives loads of errors, here's a bit of the list of errors:
> =3D20=20
> > > > > [javac]=3D20=20
> > > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =
> =3D20
>
> > > > > rBean.java:346: cannot resolve symbol =3D20=20
> > > > > [javac] symbol : class EnlistmentLocal =3D20=20
> > > > > [javac] location: class org.concern.j2ee.ControllerBean =
> =3D20
>
> > > > > [javac] EnlistmentLocal enlistment =3D3D =
> =3D20=20
> > > > > enlistmentHome.findBySu =3D20=20
> > > > > bjectAndActivity(subject.getId(), activityName); =3D20=20
> > > > > [javac] ^ =3D20=20
> > > > > [javac] =3D20=20
> > > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =
> =3D20
>
> > > > > rBean.java:422: cannot resolve symbol =3D20=20
> > > > > [javac] symbol : class SubjectLocal =3D20=20
> > > > > [javac] location: class org.concern.j2ee.ControllerBean =
> =3D20
>
> > > > > [javac] SubjectLocal subject =3D3D =3D20=20
> > > > > subjectHome.findByUserValue(userV =3D20=20
> > > > > alue); =3D20=20
> > > > > [javac] ^ =3D20=20
> > > > > [javac] =3D20=20
> > > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =
> =3D20
>
> > > > > rBean.java:423: incompatible types =3D20=20
> > > > > [javac] found : void =3D20=20
> > > > > [javac] required: boolean =3D20=20
> > > > > [javac] while (process(subject)); =3D20=20
> > > > > [javac] ^ =3D20=20
> > > > > [javac] =3D20=20
> > > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =
> =3D20
>
> > > > > rBean.java:631: cannot resolve symbol =3D20=20
> > > > > [javac] symbol : class EnlistmentLocal =3D20=20
> > > > > [javac] location: class org.concern.j2ee.ControllerBean =
> =3D20
>
> > > > > [javac] EnlistmentLocal enlistment =3D3D =3D20=20
> > > > > getEnlistment(subject, acti =3D20=20
> > > > > vity); =3D20=20
> > > > > [javac] ^ =3D20=20
> > > > > [javac] =3D20=20
> > > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =
> =3D20
>
> > > > > rBean.java:685: cannot resolve symbol =3D20=20
> > > > > [javac] symbol : class EnlistmentLocal =3D20=20
> > > > > [javac] location: class org.concern.j2ee.ControllerBean =
> =3D20
>
> > > > > [javac] EnlistmentLocal enlistment =3D3D =3D20=20
> > > > > getEnlistment(subject, acti =3D20=20
> > > > > vity); =3D20=20
> > > > > [javac] ^ =3D20=20
> > > > > [javac] =3D20=20
> > > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeDelegate. =
> =3D20
>
> > > > > java:63: cannot resolve symbol =3D20=20
> > > > > [javac] symbol : class ControllerHome =3D20=20
> > > > > [javac] location: class org.concern.j2ee.Delegate =3D20=20
> > > > > [javac] controllerHome =3D3D =3D20=20
> > > > > (ControllerHome)initialContext.lookup(p =3D20=20
> > > > > rocessName + "/Controller"); =3D20=20
> > > > > [javac] ^ =3D20=20
> > > > > [javac] =3D20=20
> > > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eejbossTri =
> =3D20=20
> > > > > gger.java:88: cannot resolve symbol =3D20=20
> > > > > [javac] symbol : class SchedulerLocal =3D20=20
> > > > > [javac] location: class org.concern.j2ee.jboss.Trigger =
> =3D20=20
> > > > > [javac] Invocation invocation =3D3D new=3D20=20
> > > Invocation(object,
> > > > =3D20
> > > > > Scheduler=3D20
> > > > > Local.class.getMethod("trigger", null), null, null, null, null);
>
> > =20
> > > > > [javac]
> > > > ^
> > > > > [javac]=3D20
> > > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =
> =3D20
>
> > > > > Bean.java:70: cannot resolve symbol =3D20=20
> > > > > [javac] symbol : class TimerLocalHome =3D20=20
> > > > > [javac] location: class org.concern.j2ee.SchedulerBean =
> =3D20=20
> > > > > [javac] timerHome =3D3D (TimerLocalHome)new =
> =3D20=20
> > > > > InitialContext().lookup( =3D20=20
> > > > > "java:" + processName + "/Timer"); =3D20=20
> > > > > [javac] ^ =3D20=20
> > > > > [javac] =3D20=20
> > > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =
> =3D20
>
> > > > > Bean.java:93: cannot resolve symbol =3D20=20
> > > > > [javac] symbol : class TimerLocal =3D20=20
> > > > > [javac] location: class org.concern.j2ee.SchedulerBean =
> =3D20=20
> > > > > [javac] TimerLocal timerLocal =3D3D =3D20=20
> > > > > (TimerLocal)iterator.next(); =3D20=20
> > > > > =3D20=20
> > > > > [javac] ^ =3D20=20
> > > > > [javac]=3D20=20
> > > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =
> =3D20
>
> > > > > Bean.java:93: cannot resolve symbol =3D20=20
> > > > > [javac] symbol : class TimerLocal =3D20=20
> > > > > [javac] location: class org.concern.j2ee.SchedulerBean =
> =3D20=20
> > > > > [javac] TimerLocal timerLocal =3D3D =3D20=20
> > > > > (TimerLocal)iterator.next(); =3D20=20
> > > > > =3D20=20
> > > > > [javac] ^ =3D20=20
> > > > > [javac]=3D20=20
> > > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =
> =3D20
>
> > > > > Bean.java:118: cannot resolve symbol =3D20=20
> > > > > [javac] symbol : class TimerLocal =3D20=20
> > > > > [javac] location: class org.concern.j2ee.SchedulerBean =
> =3D20=20
> > > > > [javac] TimerLocal timer =3D3D =3D20=20
> > > > > (TimerLocal)iterator.next(); =3D20=20
> > > > > [javac] ^ =3D20=20
> > > > > [javac] =3D20=20
> > > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =
> =3D20
>
> > > > > Bean.java:118: cannot resolve symbol =3D20=20
> > > > > [javac] symbol : class TimerLocal =3D20=20
> > > > > [javac] location: class org.concern.j2ee.SchedulerBean =
> =3D20=20
> > > > > [javac] TimerLocal timer =3D3D =3D20=20
> > > > > (TimerLocal)iterator.next(); =3D20=20
> > > > > [javac] ^ =3D20=20
> > > > > [javac] 68 errors =3D20=20
> > > > > =3D20=20
> > > > > Client keeps giving errors on the missing Scheduler class, =
> in=3D20
>
> > > > > total=20
> > > > > 12=3D20=20
> > > > > errors. =3D20=20
> > > > > =3D20=20
> > > > > This keeps going on. I've checked out the project with CVS in=20
> > > > > Eclipse=3D20=20
> > > > > IDE and tried to build that, again with errors. Those errors are
> =3D20=20
> > > > however
> > > > > a bit different and seem to point to missing methods within=3D20
> > > > > org.concern.j2ee.AbstractActivity =3D20=20
> > > > > =3D20=20
> > > > > I guess I'm missing some critical point in the installation=20
> > > > > procedure,=3D20=20
> > > > > but can't seem to figure out what. =3D20=20
> > > > > =3D20=20
> > > > > Can anyone point me to a solution or is there a more
> extensive=3D20=20
> > > > > installation guide for con:cern. =3D20=20
> > > > > =3D20=20
> > > > > Thanks a lot in advance,=20
> > > > > =3D20=20
> > > > > Raoul Zon=3D20=20
> > > > > Java Software Developer =3D20=20
> > > > > Topicus Information Architects =3D20=20
> > > > > =3D20=20
> > > > =3D20=20
> > > > =3D20
> > > > Holger Engels=3D20=20
> > > > (Dipl Inf Med) =3D20=20
> > > > =3D20=20
> > > > --=3D20=20
> > > > Consultant, Architect, Developer =3D20=20
> > > > Mobile: +49 176 20119752 =3D20=20
> > > > =3D20=20
> > > > -------------------------------------------------=20
> > > > This mail sent through IMP: http://horde.org/imp/ =3D20=20
> > > > =3D20=20
> > > > =3D20=20
> > > =3D20
> > > =3D20=20
> > > Holger Engels=20
> > > (Dipl Inf Med) =3D20=20
> > > =3D20=20
> > > --=20
> > > Consultant, Architect, Developer =3D20=20
> > > Mobile: +49 176 20119752 =3D20=20
> > > =3D20=20
> > > -------------------------------------------------=20
> > > This mail sent through IMP: http://horde.org/imp/=3D20=20
> > > =3D20=20
> > > =3D20=20
> > =3D20
> > =3D20=20
> > Holger Engels=3D20=20
> > (Dipl Inf Med)=3D20=20
> > =3D20=20
> > --=3D20=20
> > Consultant, Architect, Developer=3D20=20
> > Mobile: +49 176 20119752=3D20=20
> > =20
> > -------------------------------------------------
> > This mail sent through IMP: http://horde.org/imp/=20
> > =20
> > =20
> > -------------------------------------------------------
> > This SF.Net email is sponsored by Sleepycat Software=20
> > Learn developer strategies Cisco, Motorola, Ericsson & Lucent use
> to=3D20=20
> > deliver higher performing products faster, at low TCO.=20
> > http://www.sleepycat.com/telcomwpreg.php?From=3D3Dosdnemail3=20
> > _______________________________________________=20
> > Concern-users mailing list=20
> > Con...@li...=20
> > https://lists.sourceforge.net/lists/listinfo/concern-users=20
> > =20
> > =20
> > -------------------------------------------------------
> > This SF.Net email is sponsored by Sleepycat Software=20
> > Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to =20
> > deliver higher performing products faster, at low TCO.=20
> > http://www.sleepycat.com/telcomwpreg.php?From=3Dosdnemail3=20
> > _______________________________________________=20
> > Concern-users mailing list=20
> > Con...@li...=20
> > https://lists.sourceforge.net/lists/listinfo/concern-users=20
> > =20
> > =20
> =20
> =20
> Holger Engels=20
> (Dipl Inf Med)=20
> =20
> --=20
> Consultant, Architect, Developer=20
> Mobile: +49 176 20119752=20
>
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Sleepycat Software
> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to=20
> deliver higher performing products faster, at low TCO.
> http://www.sleepycat.com/telcomwpreg.php?From=3Dosdnemail3
> _______________________________________________
> Concern-users mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/concern-users
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Sleepycat Software
> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
> deliver higher performing products faster, at low TCO.
> http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
> _______________________________________________
> 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: Raoul Z. <rao...@to...> - 2004-05-12 07:42:15
|
Holger,
I proceeded with the steps you mentioned and deployed everything step by
step.
The moment I deploy the war I get errors.
It seems to me there's some problem with the EJB's and some conversion
in the DB.
The first error I get is about unbound EJB's Engagement/Scheduler and
Application/Scheduler.
Then it loads the hibernate mappings without problems and runs into a
"ConversionExceptionSapDB: Cannot convert data 1084347054092 to type
Timestamp" from the SapDB driver.=20
Maybe I can send you my server.log so you can see what's wrong.
Raoul
-----Original Message-----
From: Holger Engels [mailto:he...@me...]=20
Sent: dinsdag 11 mei 2004 17:32
To: con...@li...
Cc: Raoul Zon
Subject: RE: [Concern-users] Installation failures
Raoul,=20
=20
I fixed a bug in the j2ee-demo/build.xml script. now con:cern should
generate=20
the correct ddl scripts for the specified database.vendor defined in=20
custom-build.properties=20
=20
Quoting Raoul Zon <rao...@to...>:=20
=20
> Holger,
> =20
> Sorry for my late reaction, but got a bit further with the process.
> I found the generated ddl-scripts don't comply with MaxDB 7.5=20
> I had to manually alter them and generate the tables. After that I had
> some problems with users on the DB as well, so I re-installed MaxDB
and=20
> while I was at it, I re-installed Jboss as well.=20
> The DB is now connecting properly, so that's fixed....=20
> The last time I ran con:cern it almost completely started without
error,=20
> but sometimes can't seem to register the EJB's and when started it=20
> starts generating errors.=20
=20
The errors during startup might be ok, if it is only the scheduler
errors. the=20
scheduler tries to call the controller before it is actually available.=20
=20
> I'm still using the CVS version, as the binary seems to be broken as I
> can't get it to build properly.=20
> Did a new checkout by the way, which I will start building in a
minute.=20
> =20
> What jars are required in server/lib that aren't part of the build of
> con:cern??=20
=20
Look at the deploy_* tasks in the j2ee-demo/build.xml. The build is
supposed=20
to copy all required files (hopefully).=20
=20
Regards,=20
=20
Holger=20
=20
> -----Original Message-----
> From: Holger Engels [mailto:he...@me...]=3D20=20
> Sent: maandag 10 mei 2004 17:28=20
> To: con...@li...=20
> Cc: Raoul Zon=20
> Subject: RE: [Concern-users] Installation failures=20
> =20
> Quoting Raoul Zon <rao...@to...>:=3D20
> =3D20=20
> > Holger,
> > =3D20=20
> > Didn't get the binary dist to run, but the one I checked out from
CVS=3D20=20
> > is=20
> > able to compile once I removed three invalid (non-existent) calls
to=3D20=20
> > methods within AbstractActivity.java=3D20=20
> =3D20
> I moved some methods from abstract activity to its descendants and was
> not=3D20=20
> finished. does it look like this:=3D20=20
> =3D20=20
> [javac]=3D20=20
>
/home/hengels/jdevel/concern/j2ee/src/java/org/concern/j2ee/AbstractActi
> vity.java:209:=3D20=20
> cannot resolve symbol=3D20=20
> [javac] symbol : method getTimeout ()=3D20=20
> [javac] location: class org.concern.j2ee.AbstractActivity=3D20=20
> [javac] buffer.append("" + getTimeout());=3D20=20
> [javac] ^=3D20=20
> [javac]=3D20=20
>
/home/hengels/jdevel/concern/j2ee/src/java/org/concern/j2ee/AbstractActi
> vity.java:213:=3D20=20
> cannot resolve symbol=3D20=20
> [javac] symbol : method getRetryDelay ()=3D20=20
> [javac] location: class org.concern.j2ee.AbstractActivity=3D20=20
> [javac] buffer.append("" + getRetryDelay());=3D20=20
> [javac] ^=3D20=20
> [javac]=3D20=20
>
/home/hengels/jdevel/concern/j2ee/src/java/org/concern/j2ee/AbstractActi
> vity.java:215:=3D20=20
> cannot resolve symbol=3D20=20
> [javac] symbol : method getTrials ()=3D20=20
> [javac] location: class org.concern.j2ee.AbstractActivity=3D20=20
> [javac] buffer.append("" + getTrials());=3D20=20
> =3D20=20
> if yes, you can savely ignore it.=3D20=20
> =3D20=20
> =3D20=20
> =3D20=20
> > However....when I deploy the j2ee-demo with the engagement war after
> > doing an "all" on the build file of j2ee-demo and running the server
I=20
> =20
> > get loads and loads of errors and can't seem to login, whatever I=20
> > use.
> =20
> > Probably something simple I overlooked to compile or run, but =
any=3D20
> > suggestions.=3D20=20
> =3D20
> try to deploy the components one by one:=3D20=20
> =3D20=20
> 0. remove all con:cern components from jboss=3D20=20
> 1. copy the required jars to jboss/default/server/lib=3D20=20
> 2. start jboss (you should see no errors)=3D20=20
> 3. configure your datasource and deploy it=3D20=20
> 4. deploy the jta session service=3D20=20
> 5. deploy the engagement model=3D20=20
> 6. deploy the engagement process=3D20=20
> 7. deploy the engagement controller=3D20=20
> 8. deploy the engagement scheduler=3D20=20
> 9. deploy application process/controller/scheduler=3D20=20
> 10. deploy the engagement.war=3D20=20
> =3D20=20
> send me your first errors.=3D20=20
> =3D20=20
> =3D20=20
> > FYI:
> > I'm using MaxDB (latest version) (old SapDB as you probably
know).=3D20=20
> > Jboss 3.2.3=3D20=20
> =3D20
> I'm using postgres. however maxdb should work, too. make sure, that
the=3D20=20
> engagement model is configured correctly (dialect / datasource). make=20
> sure,=3D20=20
> that the controller's entity beans are configured correctly=3D20=20
> (jbosscmp-jdbc.xml). normally these configurations are applied by the=20
> build=3D20=20
> scripts according to the respective etc/custom-build.properties. did
you=20
> =20
> customize them? can you please verify that your configuration is in
> effect?=3D20=20
> =3D20=20
> unzip -c EngagementModel.sar META-INF/jboss-service.xml=3D20=20
> unzip -c EngagementController.jar META-INF/jbosscmp-jdbc.xml=3D20=20
> =3D20=20
> thanks for your patience,=3D20=20
> =3D20=20
> holger=3D20=20
> =3D20=20
> =3D20=20
> > Raoul
> > =3D20=20
> > -----Oorspronkelijk bericht-----=20
> > Van: Holger Engels [mailto:he...@me...] =3D20=20
> > Verzonden: maandag 10 mei 2004 15:15=3D20=20
> > Aan: con...@li...=3D20=20
> > CC: Raoul Zon=3D20=20
> > Onderwerp: RE: [Concern-users] Installation failures=3D20=20
> > =3D20=20
> > =3D20=20
> > Hm,=20
> > =3D20=20
> > seems like there's a target dependency missing. dist should depend
on=20
> > build! =3D20=20
> > Try: =3D20=20
> > =3D20=20
> > cd client=20
> > ant build dist =3D20=20
> > =3D20=20
> > afterwards, the j2ee-demo build should work, too (hopefully).=20
> > =3D20=20
> > Holger=20
> > =3D20=20
> > =3D20=20
> > Quoting Raoul Zon <rao...@to...>:=20
> > =3D20=20
> > > Holger,
> > > =3D20=20
> > > Your suggestion does seem to work. I get two succesfull builds
and=3D20=20
> > > the=20
> > > search on *Local.java gave exactly the same results as you wrote.
=3D20=20
> > > =3D20=20
> > > Building model and modeller succeeded as well.=20
> > > =3D20=20
> > > Now only client and j2ee-demo fail:=20
> > > Client can't find the file concern-client.jar as it seems make a=20
> copy=3D20
> > of
> > > it somewhere.
> > > j2ee-demo gives 70 compilation errors concerning, among others,
the=20
> =20
> > > classes Work and DefaultWorkList, which it can't resolve. =3D20
> > > =3D20=20
> > > Raoul Zon=20
> > > =3D20=20
> > > -----Oorspronkelijk bericht-----=3D20=20
> > > Van: Holger Engels [mailto:he...@me...] =3D20=20
> > > Verzonden: maandag 10 mei 2004 14:34=20
> > > Aan: Raoul Zon =3D20=20
> > > Onderwerp: Re: [Concern-users] Installation failures =3D20=20
> > > =3D20=20
> > > =3D20=20
> > > try it like this:=20
> > > =3D20=20
> > > cd j2ee=3D20=20
> > > ant xdoclet =3D20=20
> > > ant dist =3D20=20
> > > =3D20=20
> > > some of the local interfaces should be generated by xdoclet:=20
> > > =3D20=20
> > > find -name *Local.java=3D20=20
> > > ./src/java/org/concern/j2ee/ActionLocal.java =3D20=20
> > > ./src/java/org/concern/j2ee/ActivityLocal.java =3D20=20
> > > ./src/java/org/concern/j2ee/ConditionLocal.java =3D20=20
> > > ./src/java/org/concern/j2ee/ExitLocal.java =3D20=20
> > > ./src/java/org/concern/j2ee/ControllerLocal.java =3D20=20
> > > ./src/java/org/concern/j2ee/LoaderLocal.java =3D20=20
> > > ./build/src/java/org/concern/j2ee/LogLocal.java =3D20=20
> > > ./build/src/java/org/concern/j2ee/ArchiveLocal.java =3D20=20
> > > ./build/src/java/org/concern/j2ee/TimerLocal.java =3D20=20
> > > ./build/src/java/org/concern/j2ee/EnlistmentLocal.java =3D20=20
> > > ./build/src/java/org/concern/j2ee/SchedulerLocal.java =3D20=20
> > > ./build/src/java/org/concern/j2ee/SubjectLocal.java =3D20=20
> > > =3D20=20
> > > can you confirm this? If not, come back to me,=20
> > > =3D20=20
> > > regards,=20
> > > =3D20=20
> > > Holger=20
> > > =3D20=20
> > > Quoting Raoul Zon <rao...@to...>:=20
> > > =3D20=20
> > > > Hi,=20
> > > > =3D20
> > > > I've downloaded the concern-all-1.1.tgz and followed the
procedure=20
> > > > on=3D20=20
> > > > the installation page. =3D20=20
> > > > I've tried installing on both windows and linux, but I keep=20
> getting=3D20
> > =3D20
> > > > build failures when compiling. =3D20
> > > > Model compiles oke. =3D20=20
> > > > =3D20=20
> > > > j2ee gives loads of errors, here's a bit of the list of errors:
=3D20=20
> > > > [javac]=3D20=20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =
=3D20
> > > > rBean.java:346: cannot resolve symbol =3D20=20
> > > > [javac] symbol : class EnlistmentLocal =3D20=20
> > > > [javac] location: class org.concern.j2ee.ControllerBean =
=3D20
> > > > [javac] EnlistmentLocal enlistment =3D3D =
=3D20=20
> > > > enlistmentHome.findBySu =3D20=20
> > > > bjectAndActivity(subject.getId(), activityName); =3D20=20
> > > > [javac] ^ =3D20=20
> > > > [javac] =3D20=20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =
=3D20
> > > > rBean.java:422: cannot resolve symbol =3D20=20
> > > > [javac] symbol : class SubjectLocal =3D20=20
> > > > [javac] location: class org.concern.j2ee.ControllerBean =
=3D20
> > > > [javac] SubjectLocal subject =3D3D =3D20=20
> > > > subjectHome.findByUserValue(userV =3D20=20
> > > > alue); =3D20=20
> > > > [javac] ^ =3D20=20
> > > > [javac] =3D20=20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =
=3D20
> > > > rBean.java:423: incompatible types =3D20=20
> > > > [javac] found : void =3D20=20
> > > > [javac] required: boolean =3D20=20
> > > > [javac] while (process(subject)); =3D20=20
> > > > [javac] ^ =3D20=20
> > > > [javac] =3D20=20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =
=3D20
> > > > rBean.java:631: cannot resolve symbol =3D20=20
> > > > [javac] symbol : class EnlistmentLocal =3D20=20
> > > > [javac] location: class org.concern.j2ee.ControllerBean =
=3D20
> > > > [javac] EnlistmentLocal enlistment =3D3D =3D20=20
> > > > getEnlistment(subject, acti =3D20=20
> > > > vity); =3D20=20
> > > > [javac] ^ =3D20=20
> > > > [javac] =3D20=20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =
=3D20
> > > > rBean.java:685: cannot resolve symbol =3D20=20
> > > > [javac] symbol : class EnlistmentLocal =3D20=20
> > > > [javac] location: class org.concern.j2ee.ControllerBean =
=3D20
> > > > [javac] EnlistmentLocal enlistment =3D3D =3D20=20
> > > > getEnlistment(subject, acti =3D20=20
> > > > vity); =3D20=20
> > > > [javac] ^ =3D20=20
> > > > [javac] =3D20=20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeDelegate. =
=3D20
> > > > java:63: cannot resolve symbol =3D20=20
> > > > [javac] symbol : class ControllerHome =3D20=20
> > > > [javac] location: class org.concern.j2ee.Delegate =3D20=20
> > > > [javac] controllerHome =3D3D =3D20=20
> > > > (ControllerHome)initialContext.lookup(p =3D20=20
> > > > rocessName + "/Controller"); =3D20=20
> > > > [javac] ^ =3D20=20
> > > > [javac] =3D20=20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eejbossTri =
=3D20=20
> > > > gger.java:88: cannot resolve symbol =3D20=20
> > > > [javac] symbol : class SchedulerLocal =3D20=20
> > > > [javac] location: class org.concern.j2ee.jboss.Trigger =
=3D20=20
> > > > [javac] Invocation invocation =3D3D new=3D20=20
> > Invocation(object,
> > > =3D20
> > > > Scheduler=3D20
> > > > Local.class.getMethod("trigger", null), null, null, null, null);
> =20
> > > > [javac]
> > > ^
> > > > [javac]=3D20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =
=3D20
> > > > Bean.java:70: cannot resolve symbol =3D20=20
> > > > [javac] symbol : class TimerLocalHome =3D20=20
> > > > [javac] location: class org.concern.j2ee.SchedulerBean =
=3D20=20
> > > > [javac] timerHome =3D3D (TimerLocalHome)new =
=3D20=20
> > > > InitialContext().lookup( =3D20=20
> > > > "java:" + processName + "/Timer"); =3D20=20
> > > > [javac] ^ =3D20=20
> > > > [javac] =3D20=20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =
=3D20
> > > > Bean.java:93: cannot resolve symbol =3D20=20
> > > > [javac] symbol : class TimerLocal =3D20=20
> > > > [javac] location: class org.concern.j2ee.SchedulerBean =
=3D20=20
> > > > [javac] TimerLocal timerLocal =3D3D =3D20=20
> > > > (TimerLocal)iterator.next(); =3D20=20
> > > > =3D20=20
> > > > [javac] ^ =3D20=20
> > > > [javac]=3D20=20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =
=3D20
> > > > Bean.java:93: cannot resolve symbol =3D20=20
> > > > [javac] symbol : class TimerLocal =3D20=20
> > > > [javac] location: class org.concern.j2ee.SchedulerBean =
=3D20=20
> > > > [javac] TimerLocal timerLocal =3D3D =3D20=20
> > > > (TimerLocal)iterator.next(); =3D20=20
> > > > =3D20=20
> > > > [javac] ^ =3D20=20
> > > > [javac]=3D20=20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =
=3D20
> > > > Bean.java:118: cannot resolve symbol =3D20=20
> > > > [javac] symbol : class TimerLocal =3D20=20
> > > > [javac] location: class org.concern.j2ee.SchedulerBean =
=3D20=20
> > > > [javac] TimerLocal timer =3D3D =3D20=20
> > > > (TimerLocal)iterator.next(); =3D20=20
> > > > [javac] ^ =3D20=20
> > > > [javac] =3D20=20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =
=3D20
> > > > Bean.java:118: cannot resolve symbol =3D20=20
> > > > [javac] symbol : class TimerLocal =3D20=20
> > > > [javac] location: class org.concern.j2ee.SchedulerBean =
=3D20=20
> > > > [javac] TimerLocal timer =3D3D =3D20=20
> > > > (TimerLocal)iterator.next(); =3D20=20
> > > > [javac] ^ =3D20=20
> > > > [javac] 68 errors =3D20=20
> > > > =3D20=20
> > > > Client keeps giving errors on the missing Scheduler class, =
in=3D20
> > > > total=20
> > > > 12=3D20=20
> > > > errors. =3D20=20
> > > > =3D20=20
> > > > This keeps going on. I've checked out the project with CVS in=20
> > > > Eclipse=3D20=20
> > > > IDE and tried to build that, again with errors. Those errors are
=3D20=20
> > > however
> > > > a bit different and seem to point to missing methods within=3D20
> > > > org.concern.j2ee.AbstractActivity =3D20=20
> > > > =3D20=20
> > > > I guess I'm missing some critical point in the installation=20
> > > > procedure,=3D20=20
> > > > but can't seem to figure out what. =3D20=20
> > > > =3D20=20
> > > > Can anyone point me to a solution or is there a more
extensive=3D20=20
> > > > installation guide for con:cern. =3D20=20
> > > > =3D20=20
> > > > Thanks a lot in advance,=20
> > > > =3D20=20
> > > > Raoul Zon=3D20=20
> > > > Java Software Developer =3D20=20
> > > > Topicus Information Architects =3D20=20
> > > > =3D20=20
> > > =3D20=20
> > > =3D20
> > > Holger Engels=3D20=20
> > > (Dipl Inf Med) =3D20=20
> > > =3D20=20
> > > --=3D20=20
> > > Consultant, Architect, Developer =3D20=20
> > > Mobile: +49 176 20119752 =3D20=20
> > > =3D20=20
> > > -------------------------------------------------=20
> > > This mail sent through IMP: http://horde.org/imp/ =3D20=20
> > > =3D20=20
> > > =3D20=20
> > =3D20
> > =3D20=20
> > Holger Engels=20
> > (Dipl Inf Med) =3D20=20
> > =3D20=20
> > --=20
> > Consultant, Architect, Developer =3D20=20
> > Mobile: +49 176 20119752 =3D20=20
> > =3D20=20
> > -------------------------------------------------=20
> > This mail sent through IMP: http://horde.org/imp/=3D20=20
> > =3D20=20
> > =3D20=20
> =3D20
> =3D20=20
> Holger Engels=3D20=20
> (Dipl Inf Med)=3D20=20
> =3D20=20
> --=3D20=20
> Consultant, Architect, Developer=3D20=20
> Mobile: +49 176 20119752=3D20=20
> =20
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/=20
> =20
> =20
> -------------------------------------------------------
> This SF.Net email is sponsored by Sleepycat Software=20
> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use
to=3D20=20
> deliver higher performing products faster, at low TCO.=20
> http://www.sleepycat.com/telcomwpreg.php?From=3D3Dosdnemail3=20
> _______________________________________________=20
> Concern-users mailing list=20
> Con...@li...=20
> https://lists.sourceforge.net/lists/listinfo/concern-users=20
> =20
> =20
> -------------------------------------------------------
> This SF.Net email is sponsored by Sleepycat Software=20
> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to =20
> deliver higher performing products faster, at low TCO.=20
> http://www.sleepycat.com/telcomwpreg.php?From=3Dosdnemail3=20
> _______________________________________________=20
> Concern-users mailing list=20
> Con...@li...=20
> https://lists.sourceforge.net/lists/listinfo/concern-users=20
> =20
> =20
=20
=20
Holger Engels=20
(Dipl Inf Med)=20
=20
--=20
Consultant, Architect, Developer=20
Mobile: +49 176 20119752=20
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to=20
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=3Dosdnemail3
_______________________________________________
Concern-users mailing list
Con...@li...
https://lists.sourceforge.net/lists/listinfo/concern-users
|
|
From: Holger E. <he...@me...> - 2004-05-11 15:31:38
|
Raoul,
I fixed a bug in the j2ee-demo/build.xml script. now con:cern should generate
the correct ddl scripts for the specified database.vendor defined in
custom-build.properties
Quoting Raoul Zon <rao...@to...>:
> Holger,
>
> Sorry for my late reaction, but got a bit further with the process.
> I found the generated ddl-scripts don't comply with MaxDB 7.5
> I had to manually alter them and generate the tables. After that I had
> some problems with users on the DB as well, so I re-installed MaxDB and
> while I was at it, I re-installed Jboss as well.
> The DB is now connecting properly, so that's fixed....
> The last time I ran con:cern it almost completely started without error,
> but sometimes can't seem to register the EJB's and when started it
> starts generating errors.
The errors during startup might be ok, if it is only the scheduler errors. the
scheduler tries to call the controller before it is actually available.
> I'm still using the CVS version, as the binary seems to be broken as I
> can't get it to build properly.
> Did a new checkout by the way, which I will start building in a minute.
>
> What jars are required in server/lib that aren't part of the build of
> con:cern??
Look at the deploy_* tasks in the j2ee-demo/build.xml. The build is supposed
to copy all required files (hopefully).
Regards,
Holger
> -----Original Message-----
> From: Holger Engels [mailto:he...@me...]=20
> Sent: maandag 10 mei 2004 17:28
> To: con...@li...
> Cc: Raoul Zon
> Subject: RE: [Concern-users] Installation failures
>
> Quoting Raoul Zon <rao...@to...>:=20
> =20
> > Holger,
> > =20
> > Didn't get the binary dist to run, but the one I checked out from CVS=20
> > is
> > able to compile once I removed three invalid (non-existent) calls to=20
> > methods within AbstractActivity.java=20
> =20
> I moved some methods from abstract activity to its descendants and was
> not=20
> finished. does it look like this:=20
> =20
> [javac]=20
> /home/hengels/jdevel/concern/j2ee/src/java/org/concern/j2ee/AbstractActi
> vity.java:209:=20
> cannot resolve symbol=20
> [javac] symbol : method getTimeout ()=20
> [javac] location: class org.concern.j2ee.AbstractActivity=20
> [javac] buffer.append("" + getTimeout());=20
> [javac] ^=20
> [javac]=20
> /home/hengels/jdevel/concern/j2ee/src/java/org/concern/j2ee/AbstractActi
> vity.java:213:=20
> cannot resolve symbol=20
> [javac] symbol : method getRetryDelay ()=20
> [javac] location: class org.concern.j2ee.AbstractActivity=20
> [javac] buffer.append("" + getRetryDelay());=20
> [javac] ^=20
> [javac]=20
> /home/hengels/jdevel/concern/j2ee/src/java/org/concern/j2ee/AbstractActi
> vity.java:215:=20
> cannot resolve symbol=20
> [javac] symbol : method getTrials ()=20
> [javac] location: class org.concern.j2ee.AbstractActivity=20
> [javac] buffer.append("" + getTrials());=20
> =20
> if yes, you can savely ignore it.=20
> =20
> =20
> =20
> > However....when I deploy the j2ee-demo with the engagement war after
> > doing an "all" on the build file of j2ee-demo and running the server I
>
> > get loads and loads of errors and can't seem to login, whatever I use.
>
> > Probably something simple I overlooked to compile or run, but any=20
> > suggestions.=20
> =20
> try to deploy the components one by one:=20
> =20
> 0. remove all con:cern components from jboss=20
> 1. copy the required jars to jboss/default/server/lib=20
> 2. start jboss (you should see no errors)=20
> 3. configure your datasource and deploy it=20
> 4. deploy the jta session service=20
> 5. deploy the engagement model=20
> 6. deploy the engagement process=20
> 7. deploy the engagement controller=20
> 8. deploy the engagement scheduler=20
> 9. deploy application process/controller/scheduler=20
> 10. deploy the engagement.war=20
> =20
> send me your first errors.=20
> =20
> =20
> > FYI:
> > I'm using MaxDB (latest version) (old SapDB as you probably know).=20
> > Jboss 3.2.3=20
> =20
> I'm using postgres. however maxdb should work, too. make sure, that the=20
> engagement model is configured correctly (dialect / datasource). make
> sure,=20
> that the controller's entity beans are configured correctly=20
> (jbosscmp-jdbc.xml). normally these configurations are applied by the
> build=20
> scripts according to the respective etc/custom-build.properties. did you
>
> customize them? can you please verify that your configuration is in
> effect?=20
> =20
> unzip -c EngagementModel.sar META-INF/jboss-service.xml=20
> unzip -c EngagementController.jar META-INF/jbosscmp-jdbc.xml=20
> =20
> thanks for your patience,=20
> =20
> holger=20
> =20
> =20
> > Raoul
> > =20
> > -----Oorspronkelijk bericht-----
> > Van: Holger Engels [mailto:he...@me...] =20
> > Verzonden: maandag 10 mei 2004 15:15=20
> > Aan: con...@li...=20
> > CC: Raoul Zon=20
> > Onderwerp: RE: [Concern-users] Installation failures=20
> > =20
> > =20
> > Hm,
> > =20
> > seems like there's a target dependency missing. dist should depend on
> > build! =20
> > Try: =20
> > =20
> > cd client
> > ant build dist =20
> > =20
> > afterwards, the j2ee-demo build should work, too (hopefully).
> > =20
> > Holger
> > =20
> > =20
> > Quoting Raoul Zon <rao...@to...>:
> > =20
> > > Holger,
> > > =20
> > > Your suggestion does seem to work. I get two succesfull builds and=20
> > > the
> > > search on *Local.java gave exactly the same results as you wrote. =20
> > > =20
> > > Building model and modeller succeeded as well.
> > > =20
> > > Now only client and j2ee-demo fail:
> > > Client can't find the file concern-client.jar as it seems make a
> copy=20
> > of
> > > it somewhere.
> > > j2ee-demo gives 70 compilation errors concerning, among others, the
>
> > > classes Work and DefaultWorkList, which it can't resolve. =20
> > > =20
> > > Raoul Zon
> > > =20
> > > -----Oorspronkelijk bericht-----=20
> > > Van: Holger Engels [mailto:he...@me...] =20
> > > Verzonden: maandag 10 mei 2004 14:34
> > > Aan: Raoul Zon =20
> > > Onderwerp: Re: [Concern-users] Installation failures =20
> > > =20
> > > =20
> > > try it like this:
> > > =20
> > > cd j2ee=20
> > > ant xdoclet =20
> > > ant dist =20
> > > =20
> > > some of the local interfaces should be generated by xdoclet:
> > > =20
> > > find -name *Local.java=20
> > > ./src/java/org/concern/j2ee/ActionLocal.java =20
> > > ./src/java/org/concern/j2ee/ActivityLocal.java =20
> > > ./src/java/org/concern/j2ee/ConditionLocal.java =20
> > > ./src/java/org/concern/j2ee/ExitLocal.java =20
> > > ./src/java/org/concern/j2ee/ControllerLocal.java =20
> > > ./src/java/org/concern/j2ee/LoaderLocal.java =20
> > > ./build/src/java/org/concern/j2ee/LogLocal.java =20
> > > ./build/src/java/org/concern/j2ee/ArchiveLocal.java =20
> > > ./build/src/java/org/concern/j2ee/TimerLocal.java =20
> > > ./build/src/java/org/concern/j2ee/EnlistmentLocal.java =20
> > > ./build/src/java/org/concern/j2ee/SchedulerLocal.java =20
> > > ./build/src/java/org/concern/j2ee/SubjectLocal.java =20
> > > =20
> > > can you confirm this? If not, come back to me,
> > > =20
> > > regards,
> > > =20
> > > Holger
> > > =20
> > > Quoting Raoul Zon <rao...@to...>:
> > > =20
> > > > Hi,
> > > > =20
> > > > I've downloaded the concern-all-1.1.tgz and followed the procedure
> > > > on=20
> > > > the installation page. =20
> > > > I've tried installing on both windows and linux, but I keep
> getting=20
> > =20
> > > > build failures when compiling. =20
> > > > Model compiles oke. =20
> > > > =20
> > > > j2ee gives loads of errors, here's a bit of the list of errors: =20
> > > > [javac]=20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =20
> > > > rBean.java:346: cannot resolve symbol =20
> > > > [javac] symbol : class EnlistmentLocal =20
> > > > [javac] location: class org.concern.j2ee.ControllerBean =20
> > > > [javac] EnlistmentLocal enlistment =3D =20
> > > > enlistmentHome.findBySu =20
> > > > bjectAndActivity(subject.getId(), activityName); =20
> > > > [javac] ^ =20
> > > > [javac] =20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =20
> > > > rBean.java:422: cannot resolve symbol =20
> > > > [javac] symbol : class SubjectLocal =20
> > > > [javac] location: class org.concern.j2ee.ControllerBean =20
> > > > [javac] SubjectLocal subject =3D =20
> > > > subjectHome.findByUserValue(userV =20
> > > > alue); =20
> > > > [javac] ^ =20
> > > > [javac] =20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =20
> > > > rBean.java:423: incompatible types =20
> > > > [javac] found : void =20
> > > > [javac] required: boolean =20
> > > > [javac] while (process(subject)); =20
> > > > [javac] ^ =20
> > > > [javac] =20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =20
> > > > rBean.java:631: cannot resolve symbol =20
> > > > [javac] symbol : class EnlistmentLocal =20
> > > > [javac] location: class org.concern.j2ee.ControllerBean =20
> > > > [javac] EnlistmentLocal enlistment =3D =20
> > > > getEnlistment(subject, acti =20
> > > > vity); =20
> > > > [javac] ^ =20
> > > > [javac] =20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =20
> > > > rBean.java:685: cannot resolve symbol =20
> > > > [javac] symbol : class EnlistmentLocal =20
> > > > [javac] location: class org.concern.j2ee.ControllerBean =20
> > > > [javac] EnlistmentLocal enlistment =3D =20
> > > > getEnlistment(subject, acti =20
> > > > vity); =20
> > > > [javac] ^ =20
> > > > [javac] =20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeDelegate. =20
> > > > java:63: cannot resolve symbol =20
> > > > [javac] symbol : class ControllerHome =20
> > > > [javac] location: class org.concern.j2ee.Delegate =20
> > > > [javac] controllerHome =3D =20
> > > > (ControllerHome)initialContext.lookup(p =20
> > > > rocessName + "/Controller"); =20
> > > > [javac] ^ =20
> > > > [javac] =20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eejbossTri =20
> > > > gger.java:88: cannot resolve symbol =20
> > > > [javac] symbol : class SchedulerLocal =20
> > > > [javac] location: class org.concern.j2ee.jboss.Trigger =20
> > > > [javac] Invocation invocation =3D new=20
> > Invocation(object,
> > > =20
> > > > Scheduler=20
> > > > Local.class.getMethod("trigger", null), null, null, null, null);
>
> > > > [javac]
> > > ^
> > > > [javac]=20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =20
> > > > Bean.java:70: cannot resolve symbol =20
> > > > [javac] symbol : class TimerLocalHome =20
> > > > [javac] location: class org.concern.j2ee.SchedulerBean =20
> > > > [javac] timerHome =3D (TimerLocalHome)new =20
> > > > InitialContext().lookup( =20
> > > > "java:" + processName + "/Timer"); =20
> > > > [javac] ^ =20
> > > > [javac] =20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =20
> > > > Bean.java:93: cannot resolve symbol =20
> > > > [javac] symbol : class TimerLocal =20
> > > > [javac] location: class org.concern.j2ee.SchedulerBean =20
> > > > [javac] TimerLocal timerLocal =3D =20
> > > > (TimerLocal)iterator.next(); =20
> > > > =20
> > > > [javac] ^ =20
> > > > [javac]=20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =20
> > > > Bean.java:93: cannot resolve symbol =20
> > > > [javac] symbol : class TimerLocal =20
> > > > [javac] location: class org.concern.j2ee.SchedulerBean =20
> > > > [javac] TimerLocal timerLocal =3D =20
> > > > (TimerLocal)iterator.next(); =20
> > > > =20
> > > > [javac] ^ =20
> > > > [javac]=20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =20
> > > > Bean.java:118: cannot resolve symbol =20
> > > > [javac] symbol : class TimerLocal =20
> > > > [javac] location: class org.concern.j2ee.SchedulerBean =20
> > > > [javac] TimerLocal timer =3D =20
> > > > (TimerLocal)iterator.next(); =20
> > > > [javac] ^ =20
> > > > [javac] =20
> > > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =20
> > > > Bean.java:118: cannot resolve symbol =20
> > > > [javac] symbol : class TimerLocal =20
> > > > [javac] location: class org.concern.j2ee.SchedulerBean =20
> > > > [javac] TimerLocal timer =3D =20
> > > > (TimerLocal)iterator.next(); =20
> > > > [javac] ^ =20
> > > > [javac] 68 errors =20
> > > > =20
> > > > Client keeps giving errors on the missing Scheduler class, in=20
> > > > total
> > > > 12=20
> > > > errors. =20
> > > > =20
> > > > This keeps going on. I've checked out the project with CVS in
> > > > Eclipse=20
> > > > IDE and tried to build that, again with errors. Those errors are =20
> > > however
> > > > a bit different and seem to point to missing methods within=20
> > > > org.concern.j2ee.AbstractActivity =20
> > > > =20
> > > > I guess I'm missing some critical point in the installation
> > > > procedure,=20
> > > > but can't seem to figure out what. =20
> > > > =20
> > > > Can anyone point me to a solution or is there a more extensive=20
> > > > installation guide for con:cern. =20
> > > > =20
> > > > Thanks a lot in advance,
> > > > =20
> > > > Raoul Zon=20
> > > > Java Software Developer =20
> > > > Topicus Information Architects =20
> > > > =20
> > > =20
> > > =20
> > > Holger Engels=20
> > > (Dipl Inf Med) =20
> > > =20
> > > --=20
> > > Consultant, Architect, Developer =20
> > > Mobile: +49 176 20119752 =20
> > > =20
> > > -------------------------------------------------
> > > This mail sent through IMP: http://horde.org/imp/ =20
> > > =20
> > > =20
> > =20
> > =20
> > Holger Engels
> > (Dipl Inf Med) =20
> > =20
> > --
> > Consultant, Architect, Developer =20
> > Mobile: +49 176 20119752 =20
> > =20
> > -------------------------------------------------
> > This mail sent through IMP: http://horde.org/imp/=20
> > =20
> > =20
> =20
> =20
> Holger Engels=20
> (Dipl Inf Med)=20
> =20
> --=20
> Consultant, Architect, Developer=20
> Mobile: +49 176 20119752=20
>
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Sleepycat Software
> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to=20
> deliver higher performing products faster, at low TCO.
> http://www.sleepycat.com/telcomwpreg.php?From=3Dosdnemail3
> _______________________________________________
> Concern-users mailing list
> Con...@li...
> https://lists.sourceforge.net/lists/listinfo/concern-users
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Sleepycat Software
> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
> deliver higher performing products faster, at low TCO.
> http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
> _______________________________________________
> 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: Raoul Z. <rao...@to...> - 2004-05-11 14:09:49
|
Holger,
Sorry for my late reaction, but got a bit further with the process.
I found the generated ddl-scripts don't comply with MaxDB 7.5
I had to manually alter them and generate the tables. After that I had
some problems with users on the DB as well, so I re-installed MaxDB and
while I was at it, I re-installed Jboss as well.
The DB is now connecting properly, so that's fixed....
The last time I ran con:cern it almost completely started without error,
but sometimes can't seem to register the EJB's and when started it
starts generating errors.
I'm still using the CVS version, as the binary seems to be broken as I
can't get it to build properly.
Did a new checkout by the way, which I will start building in a minute.
What jars are required in server/lib that aren't part of the build of
con:cern??
I'll keep you posted on the new installation and I'll post you my errors
as soon as I come across some..
Raoul
-----Original Message-----
From: Holger Engels [mailto:he...@me...]=20
Sent: maandag 10 mei 2004 17:28
To: con...@li...
Cc: Raoul Zon
Subject: RE: [Concern-users] Installation failures
Quoting Raoul Zon <rao...@to...>:=20
=20
> Holger,
> =20
> Didn't get the binary dist to run, but the one I checked out from CVS=20
> is
> able to compile once I removed three invalid (non-existent) calls to=20
> methods within AbstractActivity.java=20
=20
I moved some methods from abstract activity to its descendants and was
not=20
finished. does it look like this:=20
=20
[javac]=20
/home/hengels/jdevel/concern/j2ee/src/java/org/concern/j2ee/AbstractActi
vity.java:209:=20
cannot resolve symbol=20
[javac] symbol : method getTimeout ()=20
[javac] location: class org.concern.j2ee.AbstractActivity=20
[javac] buffer.append("" + getTimeout());=20
[javac] ^=20
[javac]=20
/home/hengels/jdevel/concern/j2ee/src/java/org/concern/j2ee/AbstractActi
vity.java:213:=20
cannot resolve symbol=20
[javac] symbol : method getRetryDelay ()=20
[javac] location: class org.concern.j2ee.AbstractActivity=20
[javac] buffer.append("" + getRetryDelay());=20
[javac] ^=20
[javac]=20
/home/hengels/jdevel/concern/j2ee/src/java/org/concern/j2ee/AbstractActi
vity.java:215:=20
cannot resolve symbol=20
[javac] symbol : method getTrials ()=20
[javac] location: class org.concern.j2ee.AbstractActivity=20
[javac] buffer.append("" + getTrials());=20
=20
if yes, you can savely ignore it.=20
=20
=20
=20
> However....when I deploy the j2ee-demo with the engagement war after
> doing an "all" on the build file of j2ee-demo and running the server I
> get loads and loads of errors and can't seem to login, whatever I use.
> Probably something simple I overlooked to compile or run, but any=20
> suggestions.=20
=20
try to deploy the components one by one:=20
=20
0. remove all con:cern components from jboss=20
1. copy the required jars to jboss/default/server/lib=20
2. start jboss (you should see no errors)=20
3. configure your datasource and deploy it=20
4. deploy the jta session service=20
5. deploy the engagement model=20
6. deploy the engagement process=20
7. deploy the engagement controller=20
8. deploy the engagement scheduler=20
9. deploy application process/controller/scheduler=20
10. deploy the engagement.war=20
=20
send me your first errors.=20
=20
=20
> FYI:
> I'm using MaxDB (latest version) (old SapDB as you probably know).=20
> Jboss 3.2.3=20
=20
I'm using postgres. however maxdb should work, too. make sure, that the=20
engagement model is configured correctly (dialect / datasource). make
sure,=20
that the controller's entity beans are configured correctly=20
(jbosscmp-jdbc.xml). normally these configurations are applied by the
build=20
scripts according to the respective etc/custom-build.properties. did you
customize them? can you please verify that your configuration is in
effect?=20
=20
unzip -c EngagementModel.sar META-INF/jboss-service.xml=20
unzip -c EngagementController.jar META-INF/jbosscmp-jdbc.xml=20
=20
thanks for your patience,=20
=20
holger=20
=20
=20
> Raoul
> =20
> -----Oorspronkelijk bericht-----
> Van: Holger Engels [mailto:he...@me...] =20
> Verzonden: maandag 10 mei 2004 15:15=20
> Aan: con...@li...=20
> CC: Raoul Zon=20
> Onderwerp: RE: [Concern-users] Installation failures=20
> =20
> =20
> Hm,
> =20
> seems like there's a target dependency missing. dist should depend on
> build! =20
> Try: =20
> =20
> cd client
> ant build dist =20
> =20
> afterwards, the j2ee-demo build should work, too (hopefully).
> =20
> Holger
> =20
> =20
> Quoting Raoul Zon <rao...@to...>:
> =20
> > Holger,
> > =20
> > Your suggestion does seem to work. I get two succesfull builds and=20
> > the
> > search on *Local.java gave exactly the same results as you wrote. =20
> > =20
> > Building model and modeller succeeded as well.
> > =20
> > Now only client and j2ee-demo fail:
> > Client can't find the file concern-client.jar as it seems make a
copy=20
> of
> > it somewhere.
> > j2ee-demo gives 70 compilation errors concerning, among others, the
> > classes Work and DefaultWorkList, which it can't resolve. =20
> > =20
> > Raoul Zon
> > =20
> > -----Oorspronkelijk bericht-----=20
> > Van: Holger Engels [mailto:he...@me...] =20
> > Verzonden: maandag 10 mei 2004 14:34
> > Aan: Raoul Zon =20
> > Onderwerp: Re: [Concern-users] Installation failures =20
> > =20
> > =20
> > try it like this:
> > =20
> > cd j2ee=20
> > ant xdoclet =20
> > ant dist =20
> > =20
> > some of the local interfaces should be generated by xdoclet:
> > =20
> > find -name *Local.java=20
> > ./src/java/org/concern/j2ee/ActionLocal.java =20
> > ./src/java/org/concern/j2ee/ActivityLocal.java =20
> > ./src/java/org/concern/j2ee/ConditionLocal.java =20
> > ./src/java/org/concern/j2ee/ExitLocal.java =20
> > ./src/java/org/concern/j2ee/ControllerLocal.java =20
> > ./src/java/org/concern/j2ee/LoaderLocal.java =20
> > ./build/src/java/org/concern/j2ee/LogLocal.java =20
> > ./build/src/java/org/concern/j2ee/ArchiveLocal.java =20
> > ./build/src/java/org/concern/j2ee/TimerLocal.java =20
> > ./build/src/java/org/concern/j2ee/EnlistmentLocal.java =20
> > ./build/src/java/org/concern/j2ee/SchedulerLocal.java =20
> > ./build/src/java/org/concern/j2ee/SubjectLocal.java =20
> > =20
> > can you confirm this? If not, come back to me,
> > =20
> > regards,
> > =20
> > Holger
> > =20
> > Quoting Raoul Zon <rao...@to...>:
> > =20
> > > Hi,
> > > =20
> > > I've downloaded the concern-all-1.1.tgz and followed the procedure
> > > on=20
> > > the installation page. =20
> > > I've tried installing on both windows and linux, but I keep
getting=20
> =20
> > > build failures when compiling. =20
> > > Model compiles oke. =20
> > > =20
> > > j2ee gives loads of errors, here's a bit of the list of errors: =20
> > > [javac]=20
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =20
> > > rBean.java:346: cannot resolve symbol =20
> > > [javac] symbol : class EnlistmentLocal =20
> > > [javac] location: class org.concern.j2ee.ControllerBean =20
> > > [javac] EnlistmentLocal enlistment =3D =20
> > > enlistmentHome.findBySu =20
> > > bjectAndActivity(subject.getId(), activityName); =20
> > > [javac] ^ =20
> > > [javac] =20
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =20
> > > rBean.java:422: cannot resolve symbol =20
> > > [javac] symbol : class SubjectLocal =20
> > > [javac] location: class org.concern.j2ee.ControllerBean =20
> > > [javac] SubjectLocal subject =3D =20
> > > subjectHome.findByUserValue(userV =20
> > > alue); =20
> > > [javac] ^ =20
> > > [javac] =20
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =20
> > > rBean.java:423: incompatible types =20
> > > [javac] found : void =20
> > > [javac] required: boolean =20
> > > [javac] while (process(subject)); =20
> > > [javac] ^ =20
> > > [javac] =20
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =20
> > > rBean.java:631: cannot resolve symbol =20
> > > [javac] symbol : class EnlistmentLocal =20
> > > [javac] location: class org.concern.j2ee.ControllerBean =20
> > > [javac] EnlistmentLocal enlistment =3D =20
> > > getEnlistment(subject, acti =20
> > > vity); =20
> > > [javac] ^ =20
> > > [javac] =20
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle =20
> > > rBean.java:685: cannot resolve symbol =20
> > > [javac] symbol : class EnlistmentLocal =20
> > > [javac] location: class org.concern.j2ee.ControllerBean =20
> > > [javac] EnlistmentLocal enlistment =3D =20
> > > getEnlistment(subject, acti =20
> > > vity); =20
> > > [javac] ^ =20
> > > [javac] =20
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeDelegate. =20
> > > java:63: cannot resolve symbol =20
> > > [javac] symbol : class ControllerHome =20
> > > [javac] location: class org.concern.j2ee.Delegate =20
> > > [javac] controllerHome =3D =20
> > > (ControllerHome)initialContext.lookup(p =20
> > > rocessName + "/Controller"); =20
> > > [javac] ^ =20
> > > [javac] =20
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eejbossTri =20
> > > gger.java:88: cannot resolve symbol =20
> > > [javac] symbol : class SchedulerLocal =20
> > > [javac] location: class org.concern.j2ee.jboss.Trigger =20
> > > [javac] Invocation invocation =3D new=20
> Invocation(object,
> > =20
> > > Scheduler=20
> > > Local.class.getMethod("trigger", null), null, null, null, null);
> > > [javac]
> > ^
> > > [javac]=20
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =20
> > > Bean.java:70: cannot resolve symbol =20
> > > [javac] symbol : class TimerLocalHome =20
> > > [javac] location: class org.concern.j2ee.SchedulerBean =20
> > > [javac] timerHome =3D (TimerLocalHome)new =20
> > > InitialContext().lookup( =20
> > > "java:" + processName + "/Timer"); =20
> > > [javac] ^ =20
> > > [javac] =20
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =20
> > > Bean.java:93: cannot resolve symbol =20
> > > [javac] symbol : class TimerLocal =20
> > > [javac] location: class org.concern.j2ee.SchedulerBean =20
> > > [javac] TimerLocal timerLocal =3D =20
> > > (TimerLocal)iterator.next(); =20
> > > =20
> > > [javac] ^ =20
> > > [javac]=20
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =20
> > > Bean.java:93: cannot resolve symbol =20
> > > [javac] symbol : class TimerLocal =20
> > > [javac] location: class org.concern.j2ee.SchedulerBean =20
> > > [javac] TimerLocal timerLocal =3D =20
> > > (TimerLocal)iterator.next(); =20
> > > =20
> > > [javac] ^ =20
> > > [javac]=20
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =20
> > > Bean.java:118: cannot resolve symbol =20
> > > [javac] symbol : class TimerLocal =20
> > > [javac] location: class org.concern.j2ee.SchedulerBean =20
> > > [javac] TimerLocal timer =3D =20
> > > (TimerLocal)iterator.next(); =20
> > > [javac] ^ =20
> > > [javac] =20
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler =20
> > > Bean.java:118: cannot resolve symbol =20
> > > [javac] symbol : class TimerLocal =20
> > > [javac] location: class org.concern.j2ee.SchedulerBean =20
> > > [javac] TimerLocal timer =3D =20
> > > (TimerLocal)iterator.next(); =20
> > > [javac] ^ =20
> > > [javac] 68 errors =20
> > > =20
> > > Client keeps giving errors on the missing Scheduler class, in=20
> > > total
> > > 12=20
> > > errors. =20
> > > =20
> > > This keeps going on. I've checked out the project with CVS in
> > > Eclipse=20
> > > IDE and tried to build that, again with errors. Those errors are =20
> > however
> > > a bit different and seem to point to missing methods within=20
> > > org.concern.j2ee.AbstractActivity =20
> > > =20
> > > I guess I'm missing some critical point in the installation
> > > procedure,=20
> > > but can't seem to figure out what. =20
> > > =20
> > > Can anyone point me to a solution or is there a more extensive=20
> > > installation guide for con:cern. =20
> > > =20
> > > Thanks a lot in advance,
> > > =20
> > > Raoul Zon=20
> > > Java Software Developer =20
> > > Topicus Information Architects =20
> > > =20
> > =20
> > =20
> > Holger Engels=20
> > (Dipl Inf Med) =20
> > =20
> > --=20
> > Consultant, Architect, Developer =20
> > Mobile: +49 176 20119752 =20
> > =20
> > -------------------------------------------------
> > This mail sent through IMP: http://horde.org/imp/ =20
> > =20
> > =20
> =20
> =20
> Holger Engels
> (Dipl Inf Med) =20
> =20
> --
> Consultant, Architect, Developer =20
> Mobile: +49 176 20119752 =20
> =20
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/=20
> =20
> =20
=20
=20
Holger Engels=20
(Dipl Inf Med)=20
=20
--=20
Consultant, Architect, Developer=20
Mobile: +49 176 20119752=20
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to=20
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=3Dosdnemail3
_______________________________________________
Concern-users mailing list
Con...@li...
https://lists.sourceforge.net/lists/listinfo/concern-users
|
|
From: Holger E. <he...@me...> - 2004-05-10 15:28:29
|
Quoting Raoul Zon <rao...@to...>:
> Holger,
>
> Didn't get the binary dist to run, but the one I checked out from CVS is
> able to compile once I removed three invalid (non-existent) calls to
> methods within AbstractActivity.java
I moved some methods from abstract activity to its descendants and was not
finished. does it look like this:
[javac]
/home/hengels/jdevel/concern/j2ee/src/java/org/concern/j2ee/AbstractActivity.java:209:
cannot resolve symbol
[javac] symbol : method getTimeout ()
[javac] location: class org.concern.j2ee.AbstractActivity
[javac] buffer.append("" + getTimeout());
[javac] ^
[javac]
/home/hengels/jdevel/concern/j2ee/src/java/org/concern/j2ee/AbstractActivity.java:213:
cannot resolve symbol
[javac] symbol : method getRetryDelay ()
[javac] location: class org.concern.j2ee.AbstractActivity
[javac] buffer.append("" + getRetryDelay());
[javac] ^
[javac]
/home/hengels/jdevel/concern/j2ee/src/java/org/concern/j2ee/AbstractActivity.java:215:
cannot resolve symbol
[javac] symbol : method getTrials ()
[javac] location: class org.concern.j2ee.AbstractActivity
[javac] buffer.append("" + getTrials());
if yes, you can savely ignore it.
> However....when I deploy the j2ee-demo with the engagement war after
> doing an "all" on the build file of j2ee-demo and running the server I
> get loads and loads of errors and can't seem to login, whatever I use.
> Probably something simple I overlooked to compile or run, but any
> suggestions.
try to deploy the components one by one:
0. remove all con:cern components from jboss
1. copy the required jars to jboss/default/server/lib
2. start jboss (you should see no errors)
3. configure your datasource and deploy it
4. deploy the jta session service
5. deploy the engagement model
6. deploy the engagement process
7. deploy the engagement controller
8. deploy the engagement scheduler
9. deploy application process/controller/scheduler
10. deploy the engagement.war
send me your first errors.
> FYI:
> I'm using MaxDB (latest version) (old SapDB as you probably know).
> Jboss 3.2.3
I'm using postgres. however maxdb should work, too. make sure, that the
engagement model is configured correctly (dialect / datasource). make sure,
that the controller's entity beans are configured correctly
(jbosscmp-jdbc.xml). normally these configurations are applied by the build
scripts according to the respective etc/custom-build.properties. did you
customize them? can you please verify that your configuration is in effect?
unzip -c EngagementModel.sar META-INF/jboss-service.xml
unzip -c EngagementController.jar META-INF/jbosscmp-jdbc.xml
thanks for your patience,
holger
> Raoul
>
> -----Oorspronkelijk bericht-----
> Van: Holger Engels [mailto:he...@me...]
> Verzonden: maandag 10 mei 2004 15:15
> Aan: con...@li...
> CC: Raoul Zon
> Onderwerp: RE: [Concern-users] Installation failures
>
>
> Hm,
>
> seems like there's a target dependency missing. dist should depend on
> build!
> Try:
>
> cd client
> ant build dist
>
> afterwards, the j2ee-demo build should work, too (hopefully).
>
> Holger
>
>
> Quoting Raoul Zon <rao...@to...>:
>
> > Holger,
> >
> > Your suggestion does seem to work. I get two succesfull builds and the
> > search on *Local.java gave exactly the same results as you wrote.
> >
> > Building model and modeller succeeded as well.
> >
> > Now only client and j2ee-demo fail:
> > Client can't find the file concern-client.jar as it seems make a copy
> of
> > it somewhere.
> > j2ee-demo gives 70 compilation errors concerning, among others, the
> > classes Work and DefaultWorkList, which it can't resolve.
> >
> > Raoul Zon
> >
> > -----Oorspronkelijk bericht-----
> > Van: Holger Engels [mailto:he...@me...]
> > Verzonden: maandag 10 mei 2004 14:34
> > Aan: Raoul Zon
> > Onderwerp: Re: [Concern-users] Installation failures
> >
> >
> > try it like this:
> >
> > cd j2ee
> > ant xdoclet
> > ant dist
> >
> > some of the local interfaces should be generated by xdoclet:
> >
> > find -name *Local.java
> > ./src/java/org/concern/j2ee/ActionLocal.java
> > ./src/java/org/concern/j2ee/ActivityLocal.java
> > ./src/java/org/concern/j2ee/ConditionLocal.java
> > ./src/java/org/concern/j2ee/ExitLocal.java
> > ./src/java/org/concern/j2ee/ControllerLocal.java
> > ./src/java/org/concern/j2ee/LoaderLocal.java
> > ./build/src/java/org/concern/j2ee/LogLocal.java
> > ./build/src/java/org/concern/j2ee/ArchiveLocal.java
> > ./build/src/java/org/concern/j2ee/TimerLocal.java
> > ./build/src/java/org/concern/j2ee/EnlistmentLocal.java
> > ./build/src/java/org/concern/j2ee/SchedulerLocal.java
> > ./build/src/java/org/concern/j2ee/SubjectLocal.java
> >
> > can you confirm this? If not, come back to me,
> >
> > regards,
> >
> > Holger
> >
> > Quoting Raoul Zon <rao...@to...>:
> >
> > > Hi,
> > >
> > > I've downloaded the concern-all-1.1.tgz and followed the procedure
> > > on
> > > the installation page.
> > > I've tried installing on both windows and linux, but I keep getting
>
> > > build failures when compiling.
> > > Model compiles oke.
> > >
> > > j2ee gives loads of errors, here's a bit of the list of errors:
> > > [javac]
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle
> > > rBean.java:346: cannot resolve symbol
> > > [javac] symbol : class EnlistmentLocal
> > > [javac] location: class org.concern.j2ee.ControllerBean
> > > [javac] EnlistmentLocal enlistment =
> > > enlistmentHome.findBySu
> > > bjectAndActivity(subject.getId(), activityName);
> > > [javac] ^
> > > [javac]
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle
> > > rBean.java:422: cannot resolve symbol
> > > [javac] symbol : class SubjectLocal
> > > [javac] location: class org.concern.j2ee.ControllerBean
> > > [javac] SubjectLocal subject =
> > > subjectHome.findByUserValue(userV
> > > alue);
> > > [javac] ^
> > > [javac]
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle
> > > rBean.java:423: incompatible types
> > > [javac] found : void
> > > [javac] required: boolean
> > > [javac] while (process(subject));
> > > [javac] ^
> > > [javac]
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle
> > > rBean.java:631: cannot resolve symbol
> > > [javac] symbol : class EnlistmentLocal
> > > [javac] location: class org.concern.j2ee.ControllerBean
> > > [javac] EnlistmentLocal enlistment =
> > > getEnlistment(subject, acti
> > > vity);
> > > [javac] ^
> > > [javac]
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle
> > > rBean.java:685: cannot resolve symbol
> > > [javac] symbol : class EnlistmentLocal
> > > [javac] location: class org.concern.j2ee.ControllerBean
> > > [javac] EnlistmentLocal enlistment =
> > > getEnlistment(subject, acti
> > > vity);
> > > [javac] ^
> > > [javac]
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeDelegate.
> > > java:63: cannot resolve symbol
> > > [javac] symbol : class ControllerHome
> > > [javac] location: class org.concern.j2ee.Delegate
> > > [javac] controllerHome =
> > > (ControllerHome)initialContext.lookup(p
> > > rocessName + "/Controller");
> > > [javac] ^
> > > [javac]
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eejbossTri
> > > gger.java:88: cannot resolve symbol
> > > [javac] symbol : class SchedulerLocal
> > > [javac] location: class org.concern.j2ee.jboss.Trigger
> > > [javac] Invocation invocation = new
> Invocation(object,
> >
> > > Scheduler
> > > Local.class.getMethod("trigger", null), null, null, null, null);
> > > [javac]
> > ^
> > > [javac]
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler
> > > Bean.java:70: cannot resolve symbol
> > > [javac] symbol : class TimerLocalHome
> > > [javac] location: class org.concern.j2ee.SchedulerBean
> > > [javac] timerHome = (TimerLocalHome)new
> > > InitialContext().lookup(
> > > "java:" + processName + "/Timer");
> > > [javac] ^
> > > [javac]
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler
> > > Bean.java:93: cannot resolve symbol
> > > [javac] symbol : class TimerLocal
> > > [javac] location: class org.concern.j2ee.SchedulerBean
> > > [javac] TimerLocal timerLocal =
> > > (TimerLocal)iterator.next();
> > >
> > > [javac] ^
> > > [javac]
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler
> > > Bean.java:93: cannot resolve symbol
> > > [javac] symbol : class TimerLocal
> > > [javac] location: class org.concern.j2ee.SchedulerBean
> > > [javac] TimerLocal timerLocal =
> > > (TimerLocal)iterator.next();
> > >
> > > [javac] ^
> > > [javac]
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler
> > > Bean.java:118: cannot resolve symbol
> > > [javac] symbol : class TimerLocal
> > > [javac] location: class org.concern.j2ee.SchedulerBean
> > > [javac] TimerLocal timer =
> > > (TimerLocal)iterator.next();
> > > [javac] ^
> > > [javac]
> > > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler
> > > Bean.java:118: cannot resolve symbol
> > > [javac] symbol : class TimerLocal
> > > [javac] location: class org.concern.j2ee.SchedulerBean
> > > [javac] TimerLocal timer =
> > > (TimerLocal)iterator.next();
> > > [javac] ^
> > > [javac] 68 errors
> > >
> > > Client keeps giving errors on the missing Scheduler class, in total
> > > 12
> > > errors.
> > >
> > > This keeps going on. I've checked out the project with CVS in
> > > Eclipse
> > > IDE and tried to build that, again with errors. Those errors are
> > however
> > > a bit different and seem to point to missing methods within
> > > org.concern.j2ee.AbstractActivity
> > >
> > > I guess I'm missing some critical point in the installation
> > > procedure,
> > > but can't seem to figure out what.
> > >
> > > Can anyone point me to a solution or is there a more extensive
> > > installation guide for con:cern.
> > >
> > > Thanks a lot in advance,
> > >
> > > Raoul Zon
> > > Java Software Developer
> > > Topicus Information Architects
> > >
> >
> >
> > Holger Engels
> > (Dipl Inf Med)
> >
> > --
> > Consultant, Architect, Developer
> > Mobile: +49 176 20119752
> >
> > -------------------------------------------------
> > This mail sent through IMP: http://horde.org/imp/
> >
> >
>
>
> Holger Engels
> (Dipl Inf Med)
>
> --
> Consultant, Architect, Developer
> Mobile: +49 176 20119752
>
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/
>
>
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-05-10 13:15:26
|
Hm,
seems like there's a target dependency missing. dist should depend on build!
Try:
cd client
ant build dist
afterwards, the j2ee-demo build should work, too (hopefully).
Holger
Quoting Raoul Zon <rao...@to...>:
> Holger,
>
> Your suggestion does seem to work. I get two succesfull builds and the
> search on *Local.java gave exactly the same results as you wrote.
>
> Building model and modeller succeeded as well.
>
> Now only client and j2ee-demo fail:
> Client can't find the file concern-client.jar as it seems make a copy of
> it somewhere.
> j2ee-demo gives 70 compilation errors concerning, among others, the
> classes Work and DefaultWorkList, which it can't resolve.
>
> Raoul Zon
>
> -----Oorspronkelijk bericht-----
> Van: Holger Engels [mailto:he...@me...]
> Verzonden: maandag 10 mei 2004 14:34
> Aan: Raoul Zon
> Onderwerp: Re: [Concern-users] Installation failures
>
>
> try it like this:
>
> cd j2ee
> ant xdoclet
> ant dist
>
> some of the local interfaces should be generated by xdoclet:
>
> find -name *Local.java
> ./src/java/org/concern/j2ee/ActionLocal.java
> ./src/java/org/concern/j2ee/ActivityLocal.java
> ./src/java/org/concern/j2ee/ConditionLocal.java
> ./src/java/org/concern/j2ee/ExitLocal.java
> ./src/java/org/concern/j2ee/ControllerLocal.java
> ./src/java/org/concern/j2ee/LoaderLocal.java
> ./build/src/java/org/concern/j2ee/LogLocal.java
> ./build/src/java/org/concern/j2ee/ArchiveLocal.java
> ./build/src/java/org/concern/j2ee/TimerLocal.java
> ./build/src/java/org/concern/j2ee/EnlistmentLocal.java
> ./build/src/java/org/concern/j2ee/SchedulerLocal.java
> ./build/src/java/org/concern/j2ee/SubjectLocal.java
>
> can you confirm this? If not, come back to me,
>
> regards,
>
> Holger
>
> Quoting Raoul Zon <rao...@to...>:
>
> > Hi,
> >
> > I've downloaded the concern-all-1.1.tgz and followed the procedure on
> > the installation page.
> > I've tried installing on both windows and linux, but I keep getting
> > build failures when compiling.
> > Model compiles oke.
> >
> > j2ee gives loads of errors, here's a bit of the list of errors:
> > [javac]
> > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle
> > rBean.java:346: cannot resolve symbol
> > [javac] symbol : class EnlistmentLocal
> > [javac] location: class org.concern.j2ee.ControllerBean
> > [javac] EnlistmentLocal enlistment =
> > enlistmentHome.findBySu
> > bjectAndActivity(subject.getId(), activityName);
> > [javac] ^
> > [javac]
> > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle
> > rBean.java:422: cannot resolve symbol
> > [javac] symbol : class SubjectLocal
> > [javac] location: class org.concern.j2ee.ControllerBean
> > [javac] SubjectLocal subject =
> > subjectHome.findByUserValue(userV
> > alue);
> > [javac] ^
> > [javac]
> > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle
> > rBean.java:423: incompatible types
> > [javac] found : void
> > [javac] required: boolean
> > [javac] while (process(subject));
> > [javac] ^
> > [javac]
> > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle
> > rBean.java:631: cannot resolve symbol
> > [javac] symbol : class EnlistmentLocal
> > [javac] location: class org.concern.j2ee.ControllerBean
> > [javac] EnlistmentLocal enlistment =
> > getEnlistment(subject, acti
> > vity);
> > [javac] ^
> > [javac]
> > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeControlle
> > rBean.java:685: cannot resolve symbol
> > [javac] symbol : class EnlistmentLocal
> > [javac] location: class org.concern.j2ee.ControllerBean
> > [javac] EnlistmentLocal enlistment =
> > getEnlistment(subject, acti
> > vity);
> > [javac] ^
> > [javac]
> > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeDelegate.
> > java:63: cannot resolve symbol
> > [javac] symbol : class ControllerHome
> > [javac] location: class org.concern.j2ee.Delegate
> > [javac] controllerHome =
> > (ControllerHome)initialContext.lookup(p
> > rocessName + "/Controller");
> > [javac] ^
> > [javac]
> > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eejbossTri
> > gger.java:88: cannot resolve symbol
> > [javac] symbol : class SchedulerLocal
> > [javac] location: class org.concern.j2ee.jboss.Trigger
> > [javac] Invocation invocation = new Invocation(object,
>
> > Scheduler
> > Local.class.getMethod("trigger", null), null, null, null, null);
> > [javac]
> ^
> > [javac]
> > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler
> > Bean.java:70: cannot resolve symbol
> > [javac] symbol : class TimerLocalHome
> > [javac] location: class org.concern.j2ee.SchedulerBean
> > [javac] timerHome = (TimerLocalHome)new
> > InitialContext().lookup(
> > "java:" + processName + "/Timer");
> > [javac] ^
> > [javac]
> > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler
> > Bean.java:93: cannot resolve symbol
> > [javac] symbol : class TimerLocal
> > [javac] location: class org.concern.j2ee.SchedulerBean
> > [javac] TimerLocal timerLocal =
> > (TimerLocal)iterator.next();
> >
> > [javac] ^
> > [javac]
> > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler
> > Bean.java:93: cannot resolve symbol
> > [javac] symbol : class TimerLocal
> > [javac] location: class org.concern.j2ee.SchedulerBean
> > [javac] TimerLocal timerLocal =
> > (TimerLocal)iterator.next();
> >
> > [javac] ^
> > [javac]
> > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler
> > Bean.java:118: cannot resolve symbol
> > [javac] symbol : class TimerLocal
> > [javac] location: class org.concern.j2ee.SchedulerBean
> > [javac] TimerLocal timer =
> > (TimerLocal)iterator.next();
> > [javac] ^
> > [javac]
> > C:devtoolsconcern-all-1.1j2eesrcjavaorgconcernj2eeScheduler
> > Bean.java:118: cannot resolve symbol
> > [javac] symbol : class TimerLocal
> > [javac] location: class org.concern.j2ee.SchedulerBean
> > [javac] TimerLocal timer =
> > (TimerLocal)iterator.next();
> > [javac] ^
> > [javac] 68 errors
> >
> > Client keeps giving errors on the missing Scheduler class, in total 12
> > errors.
> >
> > This keeps going on. I've checked out the project with CVS in Eclipse
> > IDE and tried to build that, again with errors. Those errors are
> however
> > a bit different and seem to point to missing methods within
> > org.concern.j2ee.AbstractActivity
> >
> > I guess I'm missing some critical point in the installation procedure,
> > but can't seem to figure out what.
> >
> > Can anyone point me to a solution or is there a more extensive
> > installation guide for con:cern.
> >
> > Thanks a lot in advance,
> >
> > Raoul Zon
> > Java Software Developer
> > Topicus Information Architects
> >
>
>
> Holger Engels
> (Dipl Inf Med)
>
> --
> Consultant, Architect, Developer
> Mobile: +49 176 20119752
>
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/
>
>
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-05-10 13:15:15
|
Hm,
seems like there's a target dependency missing. dist should depend on build!
Try:
cd client
ant build dist
afterwards, the j2ee-demo build should work, too (hopefully).
Holger
Quoting Raoul Zon <rao...@to...>:
> Holger,
>
> Your suggestion does seem to work. I get two succesfull builds and the
> search on *Local.java gave exactly the same results as you wrote.
>
> Building model and modeller succeeded as well.
>
> Now only client and j2ee-demo fail:
> Client can't find the file concern-client.jar as it seems make a copy of
> it somewhere.
> j2ee-demo gives 70 compilation errors concerning, among others, the
> classes Work and DefaultWorkList, which it can't resolve.
>
> Raoul Zon
>
> -----Oorspronkelijk bericht-----
> Van: Holger Engels [mailto:he...@me...]
> Verzonden: maandag 10 mei 2004 14:34
> Aan: Raoul Zon
> Onderwerp: Re: [Concern-users] Installation failures
>
>
> try it like this:
>
> cd j2ee
> ant xdoclet
> ant dist
>
> some of the local interfaces should be generated by xdoclet:
>
> find -name *Local.java
> ./src/java/org/concern/j2ee/ActionLocal.java
> ./src/java/org/concern/j2ee/ActivityLocal.java
> ./src/java/org/concern/j2ee/ConditionLocal.java
> ./src/java/org/concern/j2ee/ExitLocal.java
> ./src/java/org/concern/j2ee/ControllerLocal.java
> ./src/java/org/concern/j2ee/LoaderLocal.java
> ./build/src/java/org/concern/j2ee/LogLocal.java
> ./build/src/java/org/concern/j2ee/ArchiveLocal.java
> ./build/src/java/org/concern/j2ee/TimerLocal.java
> ./build/src/java/org/concern/j2ee/EnlistmentLocal.java
> ./build/src/java/org/concern/j2ee/SchedulerLocal.java
> ./build/src/java/org/concern/j2ee/SubjectLocal.java
>
> can you confirm this? If not, come back to me,
>
> regards,
>
> Holger
>
> Quoting Raoul Zon <rao...@to...>:
>
> > Hi,
> >
> > I've downloaded the concern-all-1.1.tgz and followed the procedure on
> > the installation page.
> > I've tried installing on both windows and linux, but I keep getting
> > build failures when compiling.
> > Model compiles oke.
> >
> > j2ee gives loads of errors, here's a bit of the list of errors:
> > [javac]
> > C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Controlle
> > rBean.java:346: cannot resolve symbol
> > [javac] symbol : class EnlistmentLocal
> > [javac] location: class org.concern.j2ee.ControllerBean
> > [javac] EnlistmentLocal enlistment =
> > enlistmentHome.findBySu
> > bjectAndActivity(subject.getId(), activityName);
> > [javac] ^
> > [javac]
> > C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Controlle
> > rBean.java:422: cannot resolve symbol
> > [javac] symbol : class SubjectLocal
> > [javac] location: class org.concern.j2ee.ControllerBean
> > [javac] SubjectLocal subject =
> > subjectHome.findByUserValue(userV
> > alue);
> > [javac] ^
> > [javac]
> > C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Controlle
> > rBean.java:423: incompatible types
> > [javac] found : void
> > [javac] required: boolean
> > [javac] while (process(subject));
> > [javac] ^
> > [javac]
> > C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Controlle
> > rBean.java:631: cannot resolve symbol
> > [javac] symbol : class EnlistmentLocal
> > [javac] location: class org.concern.j2ee.ControllerBean
> > [javac] EnlistmentLocal enlistment =
> > getEnlistment(subject, acti
> > vity);
> > [javac] ^
> > [javac]
> > C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Controlle
> > rBean.java:685: cannot resolve symbol
> > [javac] symbol : class EnlistmentLocal
> > [javac] location: class org.concern.j2ee.ControllerBean
> > [javac] EnlistmentLocal enlistment =
> > getEnlistment(subject, acti
> > vity);
> > [javac] ^
> > [javac]
> > C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Delegate.
> > java:63: cannot resolve symbol
> > [javac] symbol : class ControllerHome
> > [javac] location: class org.concern.j2ee.Delegate
> > [javac] controllerHome =
> > (ControllerHome)initialContext.lookup(p
> > rocessName + "/Controller");
> > [javac] ^
> > [javac]
> > C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\jboss\Tri
> > gger.java:88: cannot resolve symbol
> > [javac] symbol : class SchedulerLocal
> > [javac] location: class org.concern.j2ee.jboss.Trigger
> > [javac] Invocation invocation = new Invocation(object,
>
> > Scheduler
> > Local.class.getMethod("trigger", null), null, null, null, null);
> > [javac]
> ^
> > [javac]
> > C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Scheduler
> > Bean.java:70: cannot resolve symbol
> > [javac] symbol : class TimerLocalHome
> > [javac] location: class org.concern.j2ee.SchedulerBean
> > [javac] timerHome = (TimerLocalHome)new
> > InitialContext().lookup(
> > "java:" + processName + "/Timer");
> > [javac] ^
> > [javac]
> > C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Scheduler
> > Bean.java:93: cannot resolve symbol
> > [javac] symbol : class TimerLocal
> > [javac] location: class org.concern.j2ee.SchedulerBean
> > [javac] TimerLocal timerLocal =
> > (TimerLocal)iterator.next();
> >
> > [javac] ^
> > [javac]
> > C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Scheduler
> > Bean.java:93: cannot resolve symbol
> > [javac] symbol : class TimerLocal
> > [javac] location: class org.concern.j2ee.SchedulerBean
> > [javac] TimerLocal timerLocal =
> > (TimerLocal)iterator.next();
> >
> > [javac] ^
> > [javac]
> > C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Scheduler
> > Bean.java:118: cannot resolve symbol
> > [javac] symbol : class TimerLocal
> > [javac] location: class org.concern.j2ee.SchedulerBean
> > [javac] TimerLocal timer =
> > (TimerLocal)iterator.next();
> > [javac] ^
> > [javac]
> > C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Scheduler
> > Bean.java:118: cannot resolve symbol
> > [javac] symbol : class TimerLocal
> > [javac] location: class org.concern.j2ee.SchedulerBean
> > [javac] TimerLocal timer =
> > (TimerLocal)iterator.next();
> > [javac] ^
> > [javac] 68 errors
> >
> > Client keeps giving errors on the missing Scheduler class, in total 12
> > errors.
> >
> > This keeps going on. I've checked out the project with CVS in Eclipse
> > IDE and tried to build that, again with errors. Those errors are
> however
> > a bit different and seem to point to missing methods within
> > org.concern.j2ee.AbstractActivity
> >
> > I guess I'm missing some critical point in the installation procedure,
> > but can't seem to figure out what.
> >
> > Can anyone point me to a solution or is there a more extensive
> > installation guide for con:cern.
> >
> > Thanks a lot in advance,
> >
> > Raoul Zon
> > Java Software Developer
> > Topicus Information Architects
> >
>
>
> Holger Engels
> (Dipl Inf Med)
>
> --
> Consultant, Architect, Developer
> Mobile: +49 176 20119752
>
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/
>
>
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-05-10 12:34:19
|
try it like this:
cd j2ee
ant xdoclet
ant dist
some of the local interfaces should be generated by xdoclet:
find -name *Local.java
./src/java/org/concern/j2ee/ActionLocal.java
./src/java/org/concern/j2ee/ActivityLocal.java
./src/java/org/concern/j2ee/ConditionLocal.java
./src/java/org/concern/j2ee/ExitLocal.java
./src/java/org/concern/j2ee/ControllerLocal.java
./src/java/org/concern/j2ee/LoaderLocal.java
./build/src/java/org/concern/j2ee/LogLocal.java
./build/src/java/org/concern/j2ee/ArchiveLocal.java
./build/src/java/org/concern/j2ee/TimerLocal.java
./build/src/java/org/concern/j2ee/EnlistmentLocal.java
./build/src/java/org/concern/j2ee/SchedulerLocal.java
./build/src/java/org/concern/j2ee/SubjectLocal.java
can you confirm this? If not, come back to me,
regards,
Holger
Quoting Raoul Zon <rao...@to...>:
> Hi,
>
> I've downloaded the concern-all-1.1.tgz and followed the procedure on
> the installation page.
> I've tried installing on both windows and linux, but I keep getting
> build failures when compiling.
> Model compiles oke.
>
> j2ee gives loads of errors, here's a bit of the list of errors:
> [javac]
> C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Controlle
> rBean.java:346: cannot resolve symbol
> [javac] symbol : class EnlistmentLocal
> [javac] location: class org.concern.j2ee.ControllerBean
> [javac] EnlistmentLocal enlistment =
> enlistmentHome.findBySu
> bjectAndActivity(subject.getId(), activityName);
> [javac] ^
> [javac]
> C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Controlle
> rBean.java:422: cannot resolve symbol
> [javac] symbol : class SubjectLocal
> [javac] location: class org.concern.j2ee.ControllerBean
> [javac] SubjectLocal subject =
> subjectHome.findByUserValue(userV
> alue);
> [javac] ^
> [javac]
> C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Controlle
> rBean.java:423: incompatible types
> [javac] found : void
> [javac] required: boolean
> [javac] while (process(subject));
> [javac] ^
> [javac]
> C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Controlle
> rBean.java:631: cannot resolve symbol
> [javac] symbol : class EnlistmentLocal
> [javac] location: class org.concern.j2ee.ControllerBean
> [javac] EnlistmentLocal enlistment =
> getEnlistment(subject, acti
> vity);
> [javac] ^
> [javac]
> C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Controlle
> rBean.java:685: cannot resolve symbol
> [javac] symbol : class EnlistmentLocal
> [javac] location: class org.concern.j2ee.ControllerBean
> [javac] EnlistmentLocal enlistment =
> getEnlistment(subject, acti
> vity);
> [javac] ^
> [javac]
> C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Delegate.
> java:63: cannot resolve symbol
> [javac] symbol : class ControllerHome
> [javac] location: class org.concern.j2ee.Delegate
> [javac] controllerHome =
> (ControllerHome)initialContext.lookup(p
> rocessName + "/Controller");
> [javac] ^
> [javac]
> C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\jboss\Tri
> gger.java:88: cannot resolve symbol
> [javac] symbol : class SchedulerLocal
> [javac] location: class org.concern.j2ee.jboss.Trigger
> [javac] Invocation invocation = new Invocation(object,
> Scheduler
> Local.class.getMethod("trigger", null), null, null, null, null);
> [javac] ^
> [javac]
> C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Scheduler
> Bean.java:70: cannot resolve symbol
> [javac] symbol : class TimerLocalHome
> [javac] location: class org.concern.j2ee.SchedulerBean
> [javac] timerHome = (TimerLocalHome)new
> InitialContext().lookup(
> "java:" + processName + "/Timer");
> [javac] ^
> [javac]
> C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Scheduler
> Bean.java:93: cannot resolve symbol
> [javac] symbol : class TimerLocal
> [javac] location: class org.concern.j2ee.SchedulerBean
> [javac] TimerLocal timerLocal =
> (TimerLocal)iterator.next();
>
> [javac] ^
> [javac]
> C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Scheduler
> Bean.java:93: cannot resolve symbol
> [javac] symbol : class TimerLocal
> [javac] location: class org.concern.j2ee.SchedulerBean
> [javac] TimerLocal timerLocal =
> (TimerLocal)iterator.next();
>
> [javac] ^
> [javac]
> C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Scheduler
> Bean.java:118: cannot resolve symbol
> [javac] symbol : class TimerLocal
> [javac] location: class org.concern.j2ee.SchedulerBean
> [javac] TimerLocal timer =
> (TimerLocal)iterator.next();
> [javac] ^
> [javac]
> C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Scheduler
> Bean.java:118: cannot resolve symbol
> [javac] symbol : class TimerLocal
> [javac] location: class org.concern.j2ee.SchedulerBean
> [javac] TimerLocal timer =
> (TimerLocal)iterator.next();
> [javac] ^
> [javac] 68 errors
>
> Client keeps giving errors on the missing Scheduler class, in total 12
> errors.
>
> This keeps going on. I've checked out the project with CVS in Eclipse
> IDE and tried to build that, again with errors. Those errors are however
> a bit different and seem to point to missing methods within
> org.concern.j2ee.AbstractActivity
>
> I guess I'm missing some critical point in the installation procedure,
> but can't seem to figure out what.
>
> Can anyone point me to a solution or is there a more extensive
> installation guide for con:cern.
>
> Thanks a lot in advance,
>
> Raoul Zon
> Java Software Developer
> Topicus Information Architects
>
Holger Engels
(Dipl Inf Med)
--
Consultant, Architect, Developer
Mobile: +49 176 20119752
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
|
|
From: Raoul Z. <rao...@to...> - 2004-05-10 11:40:59
|
Hi,
=20
I've downloaded the concern-all-1.1.tgz and followed the procedure on
the installation page.
I've tried installing on both windows and linux, but I keep getting
build failures when compiling.
Model compiles oke.
=20
j2ee gives loads of errors, here's a bit of the list of errors:
[javac]
C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Controlle
rBean.java:346: cannot resolve symbol
[javac] symbol : class EnlistmentLocal
[javac] location: class org.concern.j2ee.ControllerBean
[javac] EnlistmentLocal enlistment =3D
enlistmentHome.findBySu
bjectAndActivity(subject.getId(), activityName);
[javac] ^
[javac]
C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Controlle
rBean.java:422: cannot resolve symbol
[javac] symbol : class SubjectLocal
[javac] location: class org.concern.j2ee.ControllerBean
[javac] SubjectLocal subject =3D
subjectHome.findByUserValue(userV
alue);
[javac] ^
[javac]
C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Controlle
rBean.java:423: incompatible types
[javac] found : void
[javac] required: boolean
[javac] while (process(subject));
[javac] ^
[javac]
C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Controlle
rBean.java:631: cannot resolve symbol
[javac] symbol : class EnlistmentLocal
[javac] location: class org.concern.j2ee.ControllerBean
[javac] EnlistmentLocal enlistment =3D
getEnlistment(subject, acti
vity);
[javac] ^
[javac]
C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Controlle
rBean.java:685: cannot resolve symbol
[javac] symbol : class EnlistmentLocal
[javac] location: class org.concern.j2ee.ControllerBean
[javac] EnlistmentLocal enlistment =3D
getEnlistment(subject, acti
vity);
[javac] ^
[javac]
C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Delegate.
java:63: cannot resolve symbol
[javac] symbol : class ControllerHome
[javac] location: class org.concern.j2ee.Delegate
[javac] controllerHome =3D
(ControllerHome)initialContext.lookup(p
rocessName + "/Controller");
[javac] ^
[javac]
C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\jboss\Tri
gger.java:88: cannot resolve symbol
[javac] symbol : class SchedulerLocal
[javac] location: class org.concern.j2ee.jboss.Trigger
[javac] Invocation invocation =3D new Invocation(object,
Scheduler
Local.class.getMethod("trigger", null), null, null, null, null);
[javac] ^
[javac]
C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Scheduler
Bean.java:70: cannot resolve symbol
[javac] symbol : class TimerLocalHome
[javac] location: class org.concern.j2ee.SchedulerBean
[javac] timerHome =3D (TimerLocalHome)new
InitialContext().lookup(
"java:" + processName + "/Timer");
[javac] ^
[javac]
C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Scheduler
Bean.java:93: cannot resolve symbol
[javac] symbol : class TimerLocal
[javac] location: class org.concern.j2ee.SchedulerBean
[javac] TimerLocal timerLocal =3D
(TimerLocal)iterator.next();
=20
[javac] ^
[javac]
C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Scheduler
Bean.java:93: cannot resolve symbol
[javac] symbol : class TimerLocal
[javac] location: class org.concern.j2ee.SchedulerBean
[javac] TimerLocal timerLocal =3D
(TimerLocal)iterator.next();
=20
[javac] ^
[javac]
C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Scheduler
Bean.java:118: cannot resolve symbol
[javac] symbol : class TimerLocal
[javac] location: class org.concern.j2ee.SchedulerBean
[javac] TimerLocal timer =3D
(TimerLocal)iterator.next();
[javac] ^
[javac]
C:\devtools\concern-all-1.1\j2ee\src\java\org\concern\j2ee\Scheduler
Bean.java:118: cannot resolve symbol
[javac] symbol : class TimerLocal
[javac] location: class org.concern.j2ee.SchedulerBean
[javac] TimerLocal timer =3D
(TimerLocal)iterator.next();
[javac] ^
[javac] 68 errors
=20
Client keeps giving errors on the missing Scheduler class, in total 12
errors.
=20
This keeps going on. I've checked out the project with CVS in Eclipse
IDE and tried to build that, again with errors. Those errors are however
a bit different and seem to point to missing methods within
org.concern.j2ee.AbstractActivity
=20
I guess I'm missing some critical point in the installation procedure,
but can't seem to figure out what.
=20
Can anyone point me to a solution or is there a more extensive
installation guide for con:cern.
=20
Thanks a lot in advance,
=20
Raoul Zon
Java Software Developer
Topicus Information Architects
|
|
From: Holger E. <he...@me...> - 2004-04-20 11:34:18
|
Hi all, I have just tagged cvs concern-1_1 and uploaded the packages to sourceforge. Please check the homepage for enhanced documentation, a new demo process and the WebStart-able modeller. Thanks to: o Henner Zeller for hosting con:cern on http://con-cern.org o Armin Haaf and Andreas Gruener for their support o all developers, translators, etc. for their contributions 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...> - 2004-02-20 12:34:23
|
Please use the current CVS Head instead. The next release of concern is scheduled for the first week of march. So development is already approaching a stable state. If you encounter any problems with the cvs version, please post them on the developers mailing list or add them to the bugtracker. We will fix them as quick as possible, ofcourse. If you need paid-for support / consulting, please don't hesitate to contact me. Kind regards, Holger Engels Quoting Chris Schrade <chr...@us...>: > > hi, > > while trying generate the java-code with the modeller tool we > > got following exception: > > > > is this a known problem and do you have any help to offer on > > how to get rid of this exception? > > > > best regards > > chris schrade - isl bremen > > > > ; SystemID: file:///C:/concern_old/concern-modeller- > > 1.0.1/etc/xsl/base-java.xsl; Line#: 28; Column#: 101 > > javax.xml.transform.TransformerException: > > java.lang.StringIndexOutOfBoundsException: String index out > > of range: -1 > > at > > org.apache.xalan.extensions.ExtensionHandlerJavaPackage.call > > Function(Unknown Source) > > at > > org.apache.xalan.extensions.ExtensionsTable.extFunction > > (Unknown Source) > > at > > org.apache.xalan.transformer.TransformerImpl.extFunction > > (Unknown Source) > > at org.apache.xpath.functions.FuncExtFunction.execute > > (Unknown Source) > > at org.apache.xpath.XPath.execute(Unknown Source) > > at org.apache.xalan.templates.ElemVariable.getValue > > (Unknown Source) > > at org.apache.xalan.templates.ElemVariable.execute > > (Unknown Source) > > at > > org.apache.xalan.templates.ElemApplyTemplates.transformSele > > ctedNodes(Unknown Source) > > at > > org.apache.xalan.templates.ElemApplyTemplates.execute > > (Unknown Source) > > at > > org.apache.xalan.templates.ElemApplyTemplates.transformSele > > ctedNodes(Unknown Source) > > at > > org.apache.xalan.templates.ElemApplyTemplates.execute > > (Unknown Source) > > at > > org.apache.xalan.templates.ElemApplyTemplates.transformSele > > ctedNodes(Unknown Source) > > at > > org.apache.xalan.templates.ElemApplyTemplates.execute > > (Unknown Source) > > at > > org.apache.xalan.transformer.TransformerImpl.executeChildTe > > mplates(Unknown Source) > > at > > org.apache.xalan.transformer.TransformerImpl.applyTemplateT > > oNode(Unknown Source) > > at > > org.apache.xalan.transformer.TransformerImpl.transformNode > > (Unknown Source) > > at > > org.apache.xalan.transformer.TransformerImpl.transform > > (Unknown Source) > > at > > org.apache.xalan.transformer.TransformerImpl.transform > > (Unknown Source) > > at > > org.apache.xalan.transformer.TransformerImpl.transform > > (Unknown Source) > > at org.concern.devel.generator.Generator.generate > > (Generator.java:84) > > at org.concern.devel.generator.GeneratorDialog.save > > (GeneratorDialog.java:122) > > at > > org.concern.devel.generator.GeneratorDialog$SaveListener.act > > ionPerformed(GeneratorDialog.java:155) > > at javax.swing.AbstractButton.fireActionPerformed > > (Unknown Source) > > at > > javax.swing.AbstractButton$ForwardActionEvents.actionPerfor > > med(Unknown Source) > > at javax.swing.DefaultButtonModel.fireActionPerformed > > (Unknown Source) > > at javax.swing.DefaultButtonModel.setPressed(Unknown > > Source) > > at > > javax.swing.plaf.basic.BasicButtonListener.mouseReleased > > (Unknown Source) > > at java.awt.Component.processMouseEvent(Unknown > > Source) > > at java.awt.Component.processEvent(Unknown Source) > > at java.awt.Container.processEvent(Unknown Source) > > at java.awt.Component.dispatchEventImpl(Unknown > > Source) > > at java.awt.Container.dispatchEventImpl(Unknown > > Source) > > at java.awt.Component.dispatchEvent(Unknown Source) > > at java.awt.LightweightDispatcher.retargetMouseEvent > > (Unknown Source) > > at java.awt.LightweightDispatcher.processMouseEvent > > (Unknown Source) > > at java.awt.LightweightDispatcher.dispatchEvent > > (Unknown Source) > > at java.awt.Container.dispatchEventImpl(Unknown > > Source) > > at java.awt.Window.dispatchEventImpl(Unknown > > Source) > > at java.awt.Component.dispatchEvent(Unknown Source) > > at java.awt.EventQueue.dispatchEvent(Unknown > > Source) > > at > > java.awt.EventDispatchThread.pumpOneEventForHierarchy > > (Unknown Source) > > at > > java.awt.EventDispatchThread.pumpEventsForHierarchy > > (Unknown Source) > > at java.awt.EventDispatchThread.pumpEvents(Unknown > > Source) > > at java.awt.EventDispatchThread.pumpEvents(Unknown > > Source) > > at java.awt.EventDispatchThread.run(Unknown Source) > > Caused by: java.lang.StringIndexOutOfBoundsException: > > String index out of range: -1 > > at java.lang.String.substring(Unknown Source) > > at org.concern.devel.generator.Utils.packagename > > (Utils.java:26) > > at sun.reflect.NativeMethodAccessorImpl.invoke0 > > (Native Method) > > at sun.reflect.NativeMethodAccessorImpl.invoke > > (Unknown Source) > > at sun.reflect.DelegatingMethodAccessorImpl.invoke > > (Unknown Source) > > at java.lang.reflect.Method.invoke(Unknown Source) > > ... 45 more > > --------- > > java.lang.StringIndexOutOfBoundsException: String index out > > of range: -1 > > at java.lang.String.substring(Unknown Source) > > at org.concern.devel.generator.Utils.packagename > > (Utils.java:26) > > at sun.reflect.NativeMethodAccessorImpl.invoke0 > > (Native Method) > > at sun.reflect.NativeMethodAccessorImpl.invoke > > (Unknown Source) > > at sun.reflect.DelegatingMethodAccessorImpl.invoke > > (Unknown Source) > > at java.lang.reflect.Method.invoke(Unknown Source) > > at > > org.apache.xalan.extensions.ExtensionHandlerJavaPackage.call > > Function(Unknown Source) > > at > > org.apache.xalan.extensions.ExtensionsTable.extFunction > > (Unknown Source) > > at > > org.apache.xalan.transformer.TransformerImpl.extFunction > > (Unknown Source) > > at org.apache.xpath.functions.FuncExtFunction.execute > > (Unknown Source) > > at org.apache.xpath.XPath.execute(Unknown Source) > > at org.apache.xalan.templates.ElemVariable.getValue > > (Unknown Source) > > at org.apache.xalan.templates.ElemVariable.execute > > (Unknown Source) > > at > > org.apache.xalan.templates.ElemApplyTemplates.transformSele > > ctedNodes(Unknown Source) > > at > > org.apache.xalan.templates.ElemApplyTemplates.execute > > (Unknown Source) > > at > > org.apache.xalan.templates.ElemApplyTemplates.transformSele > > ctedNodes(Unknown Source) > > at > > org.apache.xalan.templates.ElemApplyTemplates.execute > > (Unknown Source) > > at > > org.apache.xalan.templates.ElemApplyTemplates.transformSele > > ctedNodes(Unknown Source) > > at > > org.apache.xalan.templates.ElemApplyTemplates.execute > > (Unknown Source) > > at > > org.apache.xalan.transformer.TransformerImpl.executeChildTe > > mplates(Unknown Source) > > at > > org.apache.xalan.transformer.TransformerImpl.applyTemplateT > > oNode(Unknown Source) > > at > > org.apache.xalan.transformer.TransformerImpl.transformNode > > (Unknown Source) > > at > > org.apache.xalan.transformer.TransformerImpl.transform > > (Unknown Source) > > at > > org.apache.xalan.transformer.TransformerImpl.transform > > (Unknown Source) > > at > > org.apache.xalan.transformer.TransformerImpl.transform > > (Unknown Source) > > at org.concern.devel.generator.Generator.generate > > (Generator.java:84) > > at org.concern.devel.generator.GeneratorDialog.save > > (GeneratorDialog.java:122) > > at > > org.concern.devel.generator.GeneratorDialog$SaveListener.act > > ionPerformed(GeneratorDialog.java:155) > > at javax.swing.AbstractButton.fireActionPerformed > > (Unknown Source) > > at > > javax.swing.AbstractButton$ForwardActionEvents.actionPerfor > > med(Unknown Source) > > at javax.swing.DefaultButtonModel.fireActionPerformed > > (Unknown Source) > > at javax.swing.DefaultButtonModel.setPressed(Unknown > > Source) > > at > > javax.swing.plaf.basic.BasicButtonListener.mouseReleased > > (Unknown Source) > > at java.awt.Component.processMouseEvent(Unknown > > Source) > > at java.awt.Component.processEvent(Unknown Source) > > at java.awt.Container.processEvent(Unknown Source) > > at java.awt.Component.dispatchEventImpl(Unknown > > Source) > > at java.awt.Container.dispatchEventImpl(Unknown > > Source) > > at java.awt.Component.dispatchEvent(Unknown Source) > > at java.awt.LightweightDispatcher.retargetMouseEvent > > (Unknown Source) > > at java.awt.LightweightDispatcher.processMouseEvent > > (Unknown Source) > > at java.awt.LightweightDispatcher.dispatchEvent > > (Unknown Source) > > at java.awt.Container.dispatchEventImpl(Unknown > > Source) > > at java.awt.Window.dispatchEventImpl(Unknown > > Source) > > at java.awt.Component.dispatchEvent(Unknown Source) > > at java.awt.EventQueue.dispatchEvent(Unknown > > Source) > > at > > java.awt.EventDispatchThread.pumpOneEventForHierarchy > > (Unknown Source) > > at > > java.awt.EventDispatchThread.pumpEventsForHierarchy > > (Unknown Source) > > at java.awt.EventDispatchThread.pumpEvents(Unknown > > Source) > > at java.awt.EventDispatchThread.pumpEvents(Unknown > > Source) > > at java.awt.EventDispatchThread.run(Unknown Source) > > > > 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-02-03 13:44:01
|
Quoting Lisa Retief <lis...@sa...>: > Hi, > > Can anyone tell me if it it currently possible to have nested or "sub" > activities. For example, in the enagagement demo scenarion the activity > "Interview" could be made up of the three child activities "Run IQ > test", "Meet team" and "Interrogate"? The subprocess could share the subject and / or the controller. Holger ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ |
|
From: Holger E. <he...@me...> - 2004-02-02 07:48:09
|
Quoting Lisa Retief <lis...@sa...>: > Hi, > > Can anyone tell me if it it currently possible to have nested or "sub" > activities. For example, in the enagagement demo scenarion the activity > "Interview" could be made up of the three child activities "Run IQ > test", "Meet team" and "Interrogate"? this could be modelled as a different process with the subject "Interview". 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-30 22:45:08
|
Hi, Can anyone tell me if it it currently possible to have nested or "sub" activities. For example, in the enagagement demo scenarion the activity "Interview" could be made up of the three child activities "Run IQ test", "Meet team" and "Interrogate"? Thanks, Lisa |
|
From: Justin W. <jus...@sa...> - 2004-01-27 21:17:19
|
Hi, Yes - Postgres This was a problem that I encountered when I ran a new build (I thought I had followed the instructions but hadn't). Lisa sorted this out for me by pointing out the postgres does not support the for update column syntax. She has included these intructions in her build documentation. I suspect that you can only include exclude the whole for update statement (i.e. can't tweak the column bit) but I'll have a snoop around... Justin Holger Engels wrote: >Hi, > >you're not the only one, who is seeing this exception. I suppose, you're using >postgres, right? The timer entity bean is configured to use row locking and >jboss is generating this code, which is not understood by postgres: > > select * from timer for update of <column list> where timeout < ... > >the 'of' is the problem. postgres only understands 'for update' without 'of' and >column list. remove the rowlocking tags from the deployment descriptors and >you're fine. this shouldn't be a problem, as long as there's not too much >concurrency. then it could lead to deadlock exceptions, which are handled >correctly but may cost performance. > >however, i'd like to know how to tell jboss not to generate the 'of <column >list>' for postgres. we should adapt the concern-build.xml (which is copied to >dist/build.xml and then devel/dist/etc/kernel/build.xml) to remove the tag for >postgres. > >holger > > >Quoting Justin Walsh <jus...@sa...>: > > > >>Hi, >> >>I am set up on postgres, JBoss. I am using a build from CVS checkout on >>22/01/2004 >> >>I am getting the following exception when the schedular triggers (from >>server.log): >> >>2004-01-24 00:25:31,482 ERROR [STDERR] javax.ejb.FinderException: Find >>failed: java.sql.SQLException: ERROR: parser: parse error at or near >>"." at character 158 >>2004-01-24 00:25:31,516 ERROR [STDERR] at >> >> >> >org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:238) > > >>2004-01-24 00:25:31,517 ERROR [STDERR] at >> >> >> >org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:111) > > >>2004-01-24 00:25:31,517 ERROR [STDERR] at >> >> >> >org.jboss.ejb.plugins.cmp.jdbc.JDBCFindEntitiesCommand.execute(JDBCFindEntitiesCommand.java:38) > > >>2004-01-24 00:25:31,518 ERROR [STDERR] at >> >> >> >org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.findEntities(JDBCStoreManager.java:579) > > >>2004-01-24 00:25:31,518 ERROR [STDERR] at >> >> >> >org.jboss.ejb.plugins.CMPPersistenceManager.findEntities(CMPPersistenceManager.java:311) > > >>2004-01-24 00:25:31,518 ERROR [STDERR] at >> >> >> >org.jboss.resource.connectionmanager.CachedConnectionInterceptor.findEntities(CachedConnectionInterceptor.java:322) > > >>2004-01-24 00:25:31,519 ERROR [STDERR] at >>org.jboss.ejb.EntityContainer.findLocal(EntityContainer.java:613) >>2004-01-24 00:25:31,519 ERROR [STDERR] at >>sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>2004-01-24 00:25:31,520 ERROR [STDERR] at >>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>2004-01-24 00:25:31,520 ERROR [STDERR] at >> >> >> >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > > >>2004-01-24 00:25:31,521 ERROR [STDERR] at >>java.lang.reflect.Method.invoke(Method.java:324) >>2004-01-24 00:25:31,521 ERROR [STDERR] at >> >> >> >org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContainer.java:1043) > > >>2004-01-24 00:25:31,521 ERROR [STDERR] at >>org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:88) >>2004-01-24 00:25:31,522 ERROR [STDERR] at >> >> >> >org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:197) > > >>2004-01-24 00:25:31,523 ERROR [STDERR] at >> >> >> >org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome(CachedConnectionInterceptor.java:214) > > >>2004-01-24 00:25:31,531 ERROR [STDERR] at >>org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:88) >>2004-01-24 00:25:31,532 ERROR [STDERR] at >> >> >> >org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceInterceptor.java:89) > > >>2004-01-24 00:25:31,532 ERROR [STDERR] at >> >> >> >org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLockInterceptor.java:61) > > >>2004-01-24 00:25:31,533 ERROR [STDERR] at >> >> >> >org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationInterceptor.java:28) > > >>The exception is occurring at TimerLocalHome: >> >> public java.util.Collection findDue(long timeout) >> throws javax.ejb.FinderException; >> >> >>The generated finder (from the jboss.xml ejb-ql) is: >> >><ejb-ql><![CDATA[SELECT DISTINCT OBJECT(i) FROM Timer i WHERE i.timeout >><= ?1]]></ejb-ql> >> >>I don't have any ejb-ql experience - so any help would be appreciated. >> >>Thanks >> >>Justin >> >> >> >> >> >> >> >> >> >>------------------------------------------------------- >>The SF.Net email is sponsored by EclipseCon 2004 >>Premiere Conference on Open Tools Development and Integration >>See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. >>http://www.eclipsecon.org/osdn >>_______________________________________________ >>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/ > > >------------------------------------------------------- >The SF.Net email is sponsored by EclipseCon 2004 >Premiere Conference on Open Tools Development and Integration >See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. >http://www.eclipsecon.org/osdn >_______________________________________________ >Concern-users mailing list >Con...@li... >https://lists.sourceforge.net/lists/listinfo/concern-users > > > |
|
From: Holger E. <he...@me...> - 2004-01-27 07:34:43
|
Hi, you're not the only one, who is seeing this exception. I suppose, you're using postgres, right? The timer entity bean is configured to use row locking and jboss is generating this code, which is not understood by postgres: select * from timer for update of <column list> where timeout < ... the 'of' is the problem. postgres only understands 'for update' without 'of' and column list. remove the rowlocking tags from the deployment descriptors and you're fine. this shouldn't be a problem, as long as there's not too much concurrency. then it could lead to deadlock exceptions, which are handled correctly but may cost performance. however, i'd like to know how to tell jboss not to generate the 'of <column list>' for postgres. we should adapt the concern-build.xml (which is copied to dist/build.xml and then devel/dist/etc/kernel/build.xml) to remove the tag for postgres. holger Quoting Justin Walsh <jus...@sa...>: > Hi, > > I am set up on postgres, JBoss. I am using a build from CVS checkout on > 22/01/2004 > > I am getting the following exception when the schedular triggers (from > server.log): > > 2004-01-24 00:25:31,482 ERROR [STDERR] javax.ejb.FinderException: Find > failed: java.sql.SQLException: ERROR: parser: parse error at or near > "." at character 158 > 2004-01-24 00:25:31,516 ERROR [STDERR] at > org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:238) > 2004-01-24 00:25:31,517 ERROR [STDERR] at > org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:111) > 2004-01-24 00:25:31,517 ERROR [STDERR] at > org.jboss.ejb.plugins.cmp.jdbc.JDBCFindEntitiesCommand.execute(JDBCFindEntitiesCommand.java:38) > 2004-01-24 00:25:31,518 ERROR [STDERR] at > org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.findEntities(JDBCStoreManager.java:579) > 2004-01-24 00:25:31,518 ERROR [STDERR] at > org.jboss.ejb.plugins.CMPPersistenceManager.findEntities(CMPPersistenceManager.java:311) > 2004-01-24 00:25:31,518 ERROR [STDERR] at > org.jboss.resource.connectionmanager.CachedConnectionInterceptor.findEntities(CachedConnectionInterceptor.java:322) > 2004-01-24 00:25:31,519 ERROR [STDERR] at > org.jboss.ejb.EntityContainer.findLocal(EntityContainer.java:613) > 2004-01-24 00:25:31,519 ERROR [STDERR] at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > 2004-01-24 00:25:31,520 ERROR [STDERR] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > 2004-01-24 00:25:31,520 ERROR [STDERR] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > 2004-01-24 00:25:31,521 ERROR [STDERR] at > java.lang.reflect.Method.invoke(Method.java:324) > 2004-01-24 00:25:31,521 ERROR [STDERR] at > org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContainer.java:1043) > 2004-01-24 00:25:31,521 ERROR [STDERR] at > org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:88) > 2004-01-24 00:25:31,522 ERROR [STDERR] at > org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:197) > 2004-01-24 00:25:31,523 ERROR [STDERR] at > org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome(CachedConnectionInterceptor.java:214) > 2004-01-24 00:25:31,531 ERROR [STDERR] at > org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:88) > 2004-01-24 00:25:31,532 ERROR [STDERR] at > org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceInterceptor.java:89) > 2004-01-24 00:25:31,532 ERROR [STDERR] at > org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLockInterceptor.java:61) > 2004-01-24 00:25:31,533 ERROR [STDERR] at > org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationInterceptor.java:28) > > The exception is occurring at TimerLocalHome: > > public java.util.Collection findDue(long timeout) > throws javax.ejb.FinderException; > > > The generated finder (from the jboss.xml ejb-ql) is: > > <ejb-ql><![CDATA[SELECT DISTINCT OBJECT(i) FROM Timer i WHERE i.timeout > <= ?1]]></ejb-ql> > > I don't have any ejb-ql experience - so any help would be appreciated. > > Thanks > > Justin > > > > > > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > 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: Justin W. <jus...@sa...> - 2004-01-27 04:13:12
|
Hi,
I am set up on postgres, JBoss. I am using a build from CVS checkout on
22/01/2004
I am getting the following exception when the schedular triggers (from
server.log):
2004-01-24 00:25:31,482 ERROR [STDERR] javax.ejb.FinderException: Find
failed: java.sql.SQLException: ERROR: parser: parse error at or near
"." at character 158
2004-01-24 00:25:31,516 ERROR [STDERR] at
org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:238)
2004-01-24 00:25:31,517 ERROR [STDERR] at
org.jboss.ejb.plugins.cmp.jdbc.JDBCAbstractQueryCommand.execute(JDBCAbstractQueryCommand.java:111)
2004-01-24 00:25:31,517 ERROR [STDERR] at
org.jboss.ejb.plugins.cmp.jdbc.JDBCFindEntitiesCommand.execute(JDBCFindEntitiesCommand.java:38)
2004-01-24 00:25:31,518 ERROR [STDERR] at
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.findEntities(JDBCStoreManager.java:579)
2004-01-24 00:25:31,518 ERROR [STDERR] at
org.jboss.ejb.plugins.CMPPersistenceManager.findEntities(CMPPersistenceManager.java:311)
2004-01-24 00:25:31,518 ERROR [STDERR] at
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.findEntities(CachedConnectionInterceptor.java:322)
2004-01-24 00:25:31,519 ERROR [STDERR] at
org.jboss.ejb.EntityContainer.findLocal(EntityContainer.java:613)
2004-01-24 00:25:31,519 ERROR [STDERR] at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2004-01-24 00:25:31,520 ERROR [STDERR] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
2004-01-24 00:25:31,520 ERROR [STDERR] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
2004-01-24 00:25:31,521 ERROR [STDERR] at
java.lang.reflect.Method.invoke(Method.java:324)
2004-01-24 00:25:31,521 ERROR [STDERR] at
org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContainer.java:1043)
2004-01-24 00:25:31,521 ERROR [STDERR] at
org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:88)
2004-01-24 00:25:31,522 ERROR [STDERR] at
org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:197)
2004-01-24 00:25:31,523 ERROR [STDERR] at
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome(CachedConnectionInterceptor.java:214)
2004-01-24 00:25:31,531 ERROR [STDERR] at
org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:88)
2004-01-24 00:25:31,532 ERROR [STDERR] at
org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceInterceptor.java:89)
2004-01-24 00:25:31,532 ERROR [STDERR] at
org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLockInterceptor.java:61)
2004-01-24 00:25:31,533 ERROR [STDERR] at
org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationInterceptor.java:28)
The exception is occurring at TimerLocalHome:
public java.util.Collection findDue(long timeout)
throws javax.ejb.FinderException;
The generated finder (from the jboss.xml ejb-ql) is:
<ejb-ql><![CDATA[SELECT DISTINCT OBJECT(i) FROM Timer i WHERE i.timeout
<= ?1]]></ejb-ql>
I don't have any ejb-ql experience - so any help would be appreciated.
Thanks
Justin
|
|
From: Lisa R. <lis...@sa...> - 2004-01-23 05:17:22
|
Hi, I have updated demo/lib/hibernate2.jar to be binary. For those who don't know (or need reminding), from the CVS FAQ: When you add a binary file for the first time, use the -kb option: cvs add -kb binary-file cvs commit Regards, Lisa |
|
From: <ju...@ex...> - 2004-01-20 09:10:48
|
My other messsage did not come through - this is just a test. Thanks Justin |
1 message has been excluded from this view by a project administrator.
