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