Of course, datasources.xml is the purvue of the J2EE Deployer role, not of
the developers, but purity aside, not all Orion apps are delivered to
sophisticated deployment environments with a full complement of skilled
staff. I'm sure a lot of us have spent some time trying to pre-deploy
things so
Commonly, developers build a Stateless Session EJB facade through which
all access to Entity EJBs is accomplished. If you were to employ such a
pattern, the method of this facade that invokes the CMP finder in question
would be an appropriate place to manipulate the results before returning
them
I've been in the same boat. The deployment.cache file is not particularly
interesting, since it doesn't contain the source. When creating the
wrappers, Orion generates the source and compiles it in the root of the
Orion installation. When done compiling, it places the class files in the
reversing the order of the fields in the primkey-mapping block for
the bean in the orion-ejb-jar.xml. Might also work just to change the
order in the ejb-jar.xml, especially if you deploy from scratch.
Jeff
-Original Message-
From: Peter Pontbriand [mailto:[EMAIL PROTECTED]]
Sent:
the order of insertion in the finder code.
P.Pontbriand
Canlink Interactive Technologies Inc.
- Original Message -
From: "Peter Pontbriand" [EMAIL PROTECTED]
To: "Orion-Interest" [EMAIL PROTECTED]
Sent: Wednesday, April 04, 2001 10:56 AM
Subject: Re: Collection Finders
PS: Is this what it takes to get a question answered? Is there a
different
forum for paying customers? If I pay $1500, will I get my questions
answered faster?
One would assume so. Paying customers are prioritised in the support queue
(from personal experience).
Hani
Interesting.
The DataSourceUserManager that is provided with Orion exhibits this same
problem - the principals.xml must still contain the group declarations.
We've created out own custom UserManager that uses our User and Group EJBs.
This custom user manager will work fine for EJB and Web modules without
rporate Center
9960 Corporate Campus Drive,
Suite 2000
Louisville, KY 40223
"Peter Pontbriand"
peter.pontbriand@canlink.To:
Orion-Interest [EMAIL PROTECTED]
com cc:
S
- Original Message -
From: "Valentijn Scholten" [EMAIL PROTECTED]
To: "Peter Pontbriand" [EMAIL PROTECTED]
Sent: Thursday, March 08, 2001 3:51 AM
Subject: RE: Inconsistent EJB JNDI Locations
what do you mean just the ejb-name?
So use "MyBean" in
Hi Peter!
As I'm not sure if you are on the mailing list (orion) and it was a while
ago I posted my question, I send this question privately. I hope that this
will not disturb you.
Anyway, I succeeded in making relation between jars, but not between ears.
As I understood it, by your reply,
Hi everbody!
I'm trying to create relationships between components, both within the
same
jar and outside to another jar.
In the first alternative, i.e. within the same jar, I succeded in creating
the relationship, but unfortunately orion maps this to a blob. I have been
playing around
Arved - or anybody - have you found a solution to this problem? Our
application uses DataSourceUserManager and accessing it from servlets works
reasonable well so far. However, when accessing it from an
application-client any credentials not declared in the principals.xml file
are rejected. Even
We've been using composite primary key classes since the beginning of our
J2EE project. Notably, a number of our Entity EJBs use a primary key
composed of both an identity String and a Locale. Works perfectly for us.
What's the problem you are having?
P.Pontbriand
Canlink Interactive
- Original Message -
From: "Jennifer Grechuk" [EMAIL PROTECTED]
To: "Orion-Interest" [EMAIL PROTECTED]
Sent: Monday, January 22, 2001 4:08 PM
Subject: Influencing the order that EJB jars are deployed
Hello everyone,
On friday I posted a question about the relationships between two
String homeName = "CustomerHome";
Context context = new InitialContext();
String interfaceName = "java:comp/env/ejb/" + homeName;
LogManager.log("Looking up " + interfaceName);
Object object;
try {
object = context.lookup(interfaceName);
}
catch(NameNotFoundException e) {
//Handle Orion
but how do I get hold of the home interface of _another_ bean?
We've found that Orion exhibits an 'idiosyncracy' in this regard. It can't
seem to decide where to make the home interfaces available in the JNDI ENC.
As I understand it, using the following example EJB-REF in an EJB's
deployment
Does anybody know what could cause a javax.naming.NameNotFoundException:
my
bean name not found? I think my .xml files are fine, and I think this
used
to work!
We've got the same problem - it seems Orion 1.4.4 can't decide whether to
make EJB home interfaces available at
We haven't been using any jndi.properties file. We've always gotten our
contexts from simply invoking the default constructor for
javax.naming.InitialContext.
Obviously some change in our code or DDs has caused Orion to change its
behaviour, but we have no idea what, and cannot waste any more
Strangely enough, context-param works fine in our Orion 1.4.4 installs,
and the ejb-refs in our web.xml files can be properly found the the
environment naming context "java:comp/env". Unfortunately, ejb-jar.xml
env-entry doesn't, though. Nor are our ejb-jar.xml ejb-refs available in
the
- Original Message -
From: David Smith
To: Orion-Interest
Sent: Thursday, December 14, 2000 12:00 PM
Subject: Re: Inconsistent EJB JNDI Locations
How are you ejb-ref entries set up in your ejb-jar.xml?
Here's a sample from one of our ejb-jar.xml files:
session
sage-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Peter Pontbriand
Sent: Thursday, December 14, 2000 5:58 PM
To: Orion-Interest
Subject: Re: Inconsistent EJB JNDI Locations
We haven't been using any jndi.properties file. We've always gotten our
contexts from simply invok
- Original Message -
From: "Jeff Schnitzer" [EMAIL PROTECTED]
To: "Orion-Interest" [EMAIL PROTECTED]
Sent: Monday, December 11, 2000 4:57 PM
Subject: RE: EJB2.0 Generated class uncompilable
FYI, as a workaround, you can make bidirectional relationships work by
manually setting both
Is there a problem with Orion 1.4.4's interpretation on the ejb-jar.xml
env-entry tag? Nothing we put in such a tag is ever available in a Context
lookup() call whether we prefix with "java:comp/env" or not.
P. Pontbriand
Canlink Interactive Technologies Inc.
For quite some time, our Stateless Session EJBs have been finding the home
interfaces for our Entity EJBs using "java:comp/env/ejb/whatever" in the
context lookup() invocation. Suddenly and for no apparent reason, we now get
a "javax.naming.NameNotFoundException" exception when doing so. The
- Original Message -
From: "Tim Drury" [EMAIL PROTECTED]
To: "Orion-Interest" [EMAIL PROTECTED]
Sent: Friday, December 08, 2000 5:39 PM
Subject: RE: EJB2.0 Generated class uncompilable
Since your bean is called "Foo" I'm going to guess
that it is a trivial "Hello World" bean. Why
EJB2.0 DTD _is_ specified in ejb-jar.xml ...
ejb-jar.xml is:
-
?xml version="1.0"?
!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_2_0.dtd"
P.Pontbriand
Canlink Interactive Technologies Inc.
Hello All.
We've just written our first pair of 2.0-spec EJBs and are experiencing some
really strange problems deploying them. Orion 1.4.4 auto-generates the DB
tables for these beans, but then spits out the following message for every
CMP field in each EJB:
- Original Message -
And for what it's worth, setting up JProbe to run Orion is about as
simple...
Arved Sandstrom
-Original Message-
- Adding orion.jar and ejb.jar to the required libraries of the project
properties 'paths' tab.
- Setting the main class to
Error compiling
file:/C:/orion/applications/phlox/producer-ejb.jar:
Variable contained illegal space
Orion/1.2.9 initialized
It seems that the cause of this error was defining a primkey-field in the
deployment descriptor for a CMP bean with a custom primary key class.
Dare I suggest that
I suspect that despite the erroneous deployment descriptor, the problem in
this case is likely to be CMP fields and/or custom PK class properties not
being declared public.
P. Pontbriand
Canlink Interactive Technologies
- Original Message -
From: "Lawrence Fry" [EMAIL PROTECTED]
To:
Has anybody seen this error before:
C:\orionjava -jar orion.jar
Auto-deploying producer-ejb.jar (ejb-jar.xml had been touched since the
previous
deployment)... Error compiling
file:/C:/orion/applications/phlox/producer-ejb.j
ar: Variable contained illegal space
Orion/1.2.9 initialized
I've
31 matches
Mail list logo
