Hi,
the procedure is quite easy, but far from obvious without docs (yes, we are working on 
it ;).
You were on the right track, just a few more steps, from the start:
1. Deploy the EJB, this attempts to create a table (which in your case will fail) and 
writes the
orion/orion-ejb-jar.xml descriptor.
2. Edit the orion/orion-ejb-jar.xml descriptor to fit your needs (as you did).
3. Touch (open and save) the META-INF/ejb-jar.xml file to make Orion aware of the 
update.
4. Restart Orion or touch the config/ejb.xml file, Orion should now redeploy the beans 
with the
new settings.

Hope it helps, let us know if you have any additional problems! :)

/Magnus Stenman, the Orion team

----- Original Message ----- 
From: Andrew Liles <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, October 29, 1999 1:10 PM
Subject: Re: How to deploy EJBs


> Using Orion 0.7.9, I have got further attempting to deploy the News demo.  However, 
>I want to use Oracle and 
> have taken these steps:
> 
> create a jdbc/DefaultDS pointing to an Oracle database which the account has DBA 
>privileges on.
> uncommented jdbc/xa/DefaultXADS to point to the above
> uncommented the web-app and ejb stuff
> 
> The EJB then attempts auto-deployment but the CREATE TABLE fails as it wants to use 
>a column called "date" to 
> match the bean attribute.  In Oracle, "date" is a reserved word.  
> 
> I see that a orion-ejb-jar gets autocreated (if the orion folder is missing). [Wow! 
>cool deployment mechanism].  
> This .xml seems to have everything I want; I can modify the table name, modify the 
>column names, datatypes, 
> etc.  But I cannot seem to get the .xml to be recognised/re-read.  Am I missing 
>something here?
> 
> In an attempt to get past the "date" issue, I recompiled NewsItemEJB modifying the 
>bean object from "date" to 
> "dt".  Next error is an incompatible date-type for Oracle (TIMESTAMP).  So I really 
>need to have control over the 
> .xml.
> 
> How?!
> 
> Andrew.

Reply via email to