Hani, you have misunderstood me.
My problem is not that orion does not overwrite the deployment file. This
is good. The problem is that orion on redeployment totaly ignores DDs, and
starts from scratch. I had to look for a mile to see, why my MDBs are not
subscribed on redeployment. Orion igno
I have to agree - everyone is far to quick to yell about bug when this is
actually one of Orion's better features.
See this document for a full explanation of why Orion does what it does:
http://kb.atlassian.com/content/atlassian/howto/orionxml.jsp
Cheers,
Mike
Mike Cannon-Brookes
[EMAIL PROTE
Incidentally, you can also tell orion NOT to use a separate deployment
directory, in which case it'll read and write from the ear/jar file itself,
rather than maintain a separate tree.
You can do this by specifying deployment-directory="[none]" in server.xml,
or in your orion-application.xml if y
Wrong, this is not a bug, this is part of application assembly/deployment.
The reason that orion does not wipe out the application-deployments files is
so that you can have different deployments of the same app in different
systems, with different table names perhaps or column names (just as an
e
Maybe I don't get it. What is the problem. When you redeploy the ear it
should get the new DDs.
However, I WILL recommend to delete the deployment dir before
(re)deployment. Orion has a nasty "bug", that ignores the DD in the
jar/ear/war on redeployment. That is nasty. You should delete the di
o.k. it works! Thanks for comments!
Now we have got another problem, since the orion-ejb-jar.xml is placed in
the corresponding jar-file,
orion detects an updated orion-ejb-jar.xml every time i deployd the
ear-file, wich contains theses jar-file.
In my opinion this happens because the generat
Hi.
Yes. You may include an orion-ejb-jar.xml in the jar file. Orion wiull
read it on deployment, mix-in the missing values, and then use that xml.
Since orion 1.4.8 the orion-ejb-jar.xml should be in the META-INF
directory in the jar. Earlier versions had the deployment dd in another
direct
Hi,
thank you for the comment on my last posting "distibute beans in different
jar"!
Here is another question:
We develop in a small team. One person create the entity-beans with finder,
interfaces , dd and so on
If he creates an new finder, he has to create the where clause of the
SQL-S
