RE: [Concern-users] Installation failures
Brought to you by:
hengels,
leonchiver
|
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/
|