> Hello Karl,
>
> You have solved the underscore problem but not the other Oracle problems:
>
> -table identifiers too long:
> the only solution is to manually change table names in orion-ejb-jar.xml
but
> is not simple if the application is packaged (ATM or news sample) in a
.ear
> file
We will add the max-table-name-length attribute in the oracle.xml schema in
the next
release (<database-schema max-table-name-length="xx">). Note that Orion also
reads this info from the JDBC driver if there is no schema specified so that
should work
as well.
As for "deployment info in the .ear" we strongly recommend setting up a
deployment-directory.
This seperates your assembly and deployment info (we might make this the
default in a future release).
Make your server.xml's root tag look like something like this:
<application-server deployment-directory="../application-deployments">
Now all the deployment info for your applications will be created in the
application-deployments dir,
easily editable (and you can reuse the .ear for multiple deployments).
> -support for java.io.Serializable (used in ATM sample):
> solved adding <type-mapping type="java.io.Serializable" name="long raw"
/>
> in oracle.xml
Thank you, we will update the schema with this info.
We dont generally recommend using serialized objects (unless it's called for
which it is at times) in
situations like the ATM though. I take it your serializable field is the log
entries one, and for that one
we recommend an object-relational mapping. Since the LogEntryBean is a bean
you'd use the "properties"
type of mapping, in order to do this you'd change the config that at first
should look something like this:
<value-mapping type="com.acme.atm.ejb.LogEntryBean">
<cmp-field-mapping name="value" />
</value-mapping>
to look like this:
<value-mapping type="com.acme.atm.ejb.LogEntryBean">
<cmp-field-mapping name="value">
<properties />
</cmp-field-mapping>
</value-mapping>
Now when you redeploy Orion will expand the properties tag with all the
property info which you can then alter
further.
Hope it helps, have a nice day!
/Magnus Stenman, the Orion team
> Regards
>
> Luciano Montebove
> Finsiel
> [EMAIL PROTECTED]
>
>
> -----Messaggio originale-----
> Da: Karl Avedal [mailto:[EMAIL PROTECTED]]
> Inviato: gioved� 9 marzo 2000 21.25
> A: Orion-Interest
> Cc: Orion-Interest
> Oggetto: Re: News demo, Oracle invalid character
>
>
> Hello James,
>
> This is an issue with Oracle not liking leading underscores in
> identifiers, if you download the latest orion jar
> (http://www.orionserver.com/orion/orion.jar) and replace your orion.jar
> with it, the problem should disappear.With that version, no identifiers
> with leading underscores will be generated.
>
> Regards,
> Karl Avedal
>
> James McMullen wrote:
>
> > I've just installed Orion for the first time and am attempting to run
> > the news demo.
> > Orion came up just fine, and I'm refering the Oracle xml file, but
> > nevertheless I fail to create the table.
> >
> > Has anyone seen this "invalid character" problem?
> >
> > Thanks,
> >
> > James McMullen
> >
> > Auto-unpacking D:\orion\applications\news.ear... done.
> > Auto-unpacking D:\orion\applications\news\news-web.war... done.
> > Auto-deploying news...
> > Auto-deploying news-ejb.jar...
> > Auto-creating table: create table com_evermind_ejb_NewsItem (id
> > number(20,0) not null primary key, subject varchar2(255) null, _date
> > date null, submitter varchar2(255) null, text varchar2(255) null,
> > locale varchar (5) null, _parent number(20,0) null)
> > Warning: Error creating table: ORA-00911: invalid character
> >
> > --
> > http://www.iiCity.com
> > [EMAIL PROTECTED]
>
