Hello Rickard,
Actually, yes, I tried the jndi.properties approach, and it worked for
setting the properties, as did a couple of other things we did, but the
problem boiled down to a couple of things:
1) ColdFusion doesn't like jdk1.3 on Linux, and I don't like Windows for
serving. So we had to make the necessary changes to allow for that in both
jBoss (setting configuration-name to "jdk1.2.2 Stateless SessionBean" in
jboss.xml for the bean) and our comparative client code (we were narrowing,
for instance...).
2) ColdFusion also just didn't like us twiddling the properties more than
once. Being a closed system, there's no way for us to know why that is, and
Allaire isn't the most responsive group in the world. So, we went for the
work-around of the application scope for the Context.
Just to be clear, jBoss is not at fault on the slowness factor, as far as I
can tell. When I say that the bean runs quickly as a JSP or Servlet, I mean
that the very same bean called from those environments executes quickly.
jBoss is the EJB server in all test cases. It's the ColdFusion client
environment that is to blame.
Since our evaluation of CF/jBoss is only to maintain and improve a legacy
investment in CF/Java, any savings are completely swamped by the frustration
we experience with the proprietary system and the execution speed issue.
So, we're currently looking at porting the app to Enhydra/XMLC for the
front-end with jBoss as the EJB server. That seems to address both the
design/code separation issue as well as allowing us to take advantage of the
container's scalability and management facilities for our business logic.
Rian
----- Original Message -----
From: Rickard �berg <[EMAIL PROTECTED]>
To: jBoss <[EMAIL PROTECTED]>
Sent: Wednesday, January 03, 2001 12:07 AM
Subject: Re: [jBoss-User] jBoss/ColdFusion
> Hi!
>
> > Rian Schmidt wrote:
> > What we had to do to get around the NamingContextFactory exception was
> > to set up an Application scope context instead of resetting it each
> > time through. Now it sets up the context the first time through and
> > just refers to the Application.jndiContext subsequently.
>
> Have you tried adding a jndi.properties file to your web application in
> WEB-INF/classes?
>
> > The biggest problem is that it takes a r e a l l y long time to run
> > (the example Interest bean takes nearly 5 seconds on a 800MHz/512MB
> > Linux box. On the very same machine, the very same bean takes <<1 sec
> > as a JSP or servlet or java app.
>
> This is bad, but this will be fixed later on this spring. Hang in there!
> :-)
>
> regards,
> Rickard
>
> --
> Rickard �berg
>
> Email: [EMAIL PROTECTED]
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
