I'm interested as to how you cansay this...
we just did a series of tests here to see what the effect of pulling out some
fairly complex stored procedures into CMP beans, and the performance impact was
enormous. We've actually gone the other way, that is, developing stored
procedures for
Hi Steve,
I hate this kind of I had that too follow-up, but in this case, it's
probably relevant... I had that too. I got *exactly* the results that you
did, and then we gave up since we were actually trying to get a project
done. Please do keep us up-to-date if you learn anything.
Rian
Look in the docs for orion-ejb-jar.xml. It's in there.
Rian
--
Rian Schmidt
Fine Brand Media, Inc.
Internet Professional Services
http://www.finebrand.com/
- Original Message -
From: [EMAIL PROTECTED]
To: Orion-Interest [EMAIL PROTECTED]
Sent: Tuesday, July 24, 2001 12:04 PM
Subject
Hi,
Does anyone have any idea why we would be seeing an env-entry-mapping
disappear from orion-ejb-jar.xml upon deployment? There is a stateless
session bean that reads a value
env-entry-mapping name=databaseTypeMSSQL/env-entry-mapping
from a stateless session beans entry in orion-ejb-jar.xml.
I do believe you can use the:
response.setHeader(Window-target,_blank);
approach to do such a thing, but I also recall that it's non-standard, and
so you should check it to make sure it works with your target browser.
Rian
- Original Message -
From: Kemp Randy [EMAIL PROTECTED]
To:
query="model in ($1)"
where $1 is a Collection of models taken from ModelHome.findByManufacturer?
Any thoughts on the best way to approach this?
Thanks,
Rian
--
Rian Schmidt
[EMAIL PROTECTED]
stick SQL directly in my beans.
Thanks,
Rian
--
Rian Schmidt
[EMAIL PROTECTED]
- Original Message -
From: "elephantwalker" [EMAIL PROTECTED]
To: "Orion-Interest" [EMAIL PROTECTED]
Sent: Monday, April 16, 2001 2:54 PM
Subject: RE: findBy referencing another entity reference
implementation specific, so I
don't have much to offer there.
Rian
--
Rian Schmidt
[EMAIL PROTECTED]
- Original Message -
From: "Topher LaFata" [EMAIL PROTECTED]
To: "Orion-Interest" [EMAIL PROTECTED]
Sent: Monday, April 16, 2001 3:12 PM
Subject: Migratingfrom GSP
something out.
Thanks,
Rian
--
Rian Schmidt
[EMAIL PROTECTED]
- Original Message -
From: [EMAIL PROTECTED]
To: "Orion-Interest" [EMAIL PROTECTED]
Sent: Thursday, April 12, 2001 11:34 AM
Subject: ORION RISE FROM THE DEAD!
I've been watching Orion for awhile using/testing. It so clos
lterConfig().getServletContext().getRequestDispatcher("/login/index.jsp
").forward(null,response);
it works like you'd expect.
As I said, we've got it working, but I'm curious what this is about. Thanks
for any insight.
Rian
--
Rian Schmidt
[EMAIL PROTECTED]
Consider this a friendly pat on the back...
I had this on my list of things to get done for a big, nasty internal
project, and this fits the bill perfectly. Maybe I'll send you a
netcentive, or possibly a been, or even a flooz... unit? Uh... nah...
nevermind.
Thanks,
Rian
- Original
Sounds like you need to turn off exclusive-write-access in orion-ejb-jar.xml
while you're putzing with the database outside of the application. We're
running with SQL Server 7 (*gasp*) and Orion will try to "fix" any manual
changes we make to the database through the admin console. Otherwise,
I'd suggest something a little less radical
first... go into the orion-ejb-jar.xml file in your deployment directory and
make sure that your updates were reflected there. In particular, make sure
that Orion not only added what you did, but that it removed what you did.
Orion seems to,
I'd guess, though I haven't tried it, that you could declare a finder with
two arguments- your object and a String. Something like:
findByGroupNameSorted(GroupName gn, String dir)
where dir would be asc or desc (either constants or a special
mini-bean{tm})
Then, in your orion-ejb-jar.xml, do
improvements of 20X
very consistently.
Both environments are running on the same RedHat 7 system.
Rian
--
Rian Schmidt
[EMAIL PROTECTED]
Fine Brand Media, Inc.
Internet Professional Services
http://www.finebrand.com/
- Original Message -
From: "David Morton" [EMAIL PROTECTED]
To: "
Hi,
Can anyone give me a pointer on how I might successfully lookup an EJB from
within another EJB in a different application (both in Orion)?
Here's the scenario:
Application 'two'- EJB TwoBean looks up - Application 'one'- EJB OneBean
Make sense?
Now, java:comp/env/One and java:comp/env/Two
Follow up for posterity...
Turns out that there's an, apparently, Orion-specific thing... the
"parent=..." tag in the server.xml file in /config (specifically the
application tag therein.) The closest I could get without that was to be
able to lookup the home just like an external client... but
17 matches
Mail list logo