Randy,
sorry for not getting back earlier - had a couple of days of ;-)
> 1. What version of Resin are you using?
1.1.5 and 1.2.?
> 2. I assume you are using the latest Jboss?
2.2Final, 2.2.1 and 2.2.2
> 3. Can you share the code you used for the jndi link in the
> resin.config file?
Yup. No link ;-)
> 4. What jars from the jboss client directory did you load into
> the Resin lib directory?
None. I stuffed around with ".../bin/wrapper.pl" - I usually
find it really annoying to sort out what goes in which lib and
ext and stuff and try and find how the VM gets started and "patch"
the classpath till it is "right" ... I know not a clean solution,
but it works ;-)
> 5. Anything else you did I might have forgot?
Nope. Did not do anything else.
> I think I got everything right, but I just want to verify
> with someone else
> using this wonderful combination, who got it to work.
It is a wonderful combination. Works like a charm - quick
and no odd effects and stuff. Played around with Tomcat for
a while ... "too hard".
But while we are at it ... maybe you want to share your resin.conf
Sounds like you have the nicer setup. I never really looked into
cleaning it up, as it works for us.
Cheers,
Robert.
>
>
>
> From: Robert Schulz <[EMAIL PROTECTED]>
> To: "'[EMAIL PROTECTED]'"
> <[EMAIL PROTECTED]>
> Subject: RE: [JBoss-user] DEAR JBOSS USERS
> Date: Fri, 8 Jun 2001 12:49:21 +1000
> Reply-To: [EMAIL PROTECTED]
>
> We are very happy with it - we are currently using 2.2 on
> jdk1.3.0/Linux against postgres/Linux. We run resin as the
> servlet engine in separate VMs plugged into apache.
>
> We have about 10 entitiy and 20 session beans and written a
> fairly substantial web app on top of it and it works like
> a dream. We have a reasonable amount of data in the database
> (around 100,000 rows in the biggest table). I have to add that
> we are only using the "core" EJB features (entity and session
> beans) and took out all the other stuff (MDB, Tomcat/Jetty
> integration, soap, ...)
>
> We are not in production yet but reasonably close to it - we have
> done some load testing and it is looking good.
>
> The hardest part is (or used to be in PRE2.0) getting it to work
> in the first place ... but in comparison to say oracle it is quite
> easy (in comparison to postgres, it is quite hard).
>
> You need to spend a bit of time setting up a productive development
> environment - I recommend a IDE of your choice (not entering this
> discussion again) and a good build tool - we use ANT (and it rocks).
> The hot deploy of jboss and the automatic checking of newer class
> files of resin makes the develop / compile / run cycle really quick.
>
> Ok 'nough said. We love it - good opportunity to place a "BIG THANKS"
> to the jboss team - keep up the good work!
>
> Cheers,
>
> Robert.
>
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
