Hi Markus,
I don't know the solution, but for me it's convenient to put mapping.xml
to the subdir of "conf",
because we have many beans that use the same mapping.xml and they are
packaged into many jar files.
IMHO, the best solution is to change Castor: to make database.xml
independent of mapping.xml.
Regards,
Oleg
[EMAIL PROTECTED] wrote:
>
> Hi all !
>
> I am using JBoss/Castor and have a problem
> with the mapping-file deployment.
>
> When configuring Castor one has to provide a
> JDO-mappingfile where you write the mapping
> between java attributes and table columns.
>
> Using the castorjdo-module you have to provide this
> mapping and a database-specification file in
> the jboss.conf file.
>
> While there is no problem in having the database
> specification-file integrated in the configuration of
> jboss it is not practical to do that with the mapping-file.
> (compare to jaws.xml which is in META-INF of the
> ejb.jar file)
>
> of course i can put a URL as pointer to the mapping-file,
> but at jboss-configuration time i don't know exactly where
> the war will be deployed :)
>
> Is somebody using castorjdo and has a solution/workaround
> for this problem ?
>
> If not so, what would be the right way to solve the
> problem ? I am willing to help out with this, but have no
> clue which direction to go :)
>
> --
> greetings
> markus
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
