wow! Im definitely not there yet... thanks Erik but unfortunatelly my
knowledge is not enough YET to get you. :-(
Anyway, I have my ant and everything all setup and working , all my other
methods work, except that one. For example:

 /**
    * This is a bi-directional one-to-many relationship CMR method
    *
    * @return a java.util.Collection of related NumeroSerieLocal
    *
    * @ejb.interface-method view-type="local"
    *
    * @ejb.value-object
    *   aggregate="br.com.xerox.sapbf.ejb.entity.value.NumeroSerieValue"
    *   aggregate-name="NumeroSerie"
    *   members="br.com.xerox.sapbf.ejb.entity.NumeroSerieLocal"
    *   members-name="NumeroSerie"
    *   relation="external"
    *   type="Collection"
    *
    * @ejb.relation
    *    name="ItemProposta-NumeroSerie"
    *    role-name="ItemProposta-has-NumeroSerie"
    *
    */
   public abstract java.util.Collection getNumeroSeries();

works fine but I noticed it has this @ejb-value-object tag while mine doesnt
and has a 

* @ejb.relation
    *    name="ItemTradeIn-ItemProposta"
    *    role-name="ItemProposta-has-ItemTradeIn"
    *    cascade-delete="yes"
    *    target-multiple="yes"

instead. Does anyone know of any weblogic 7.0 problem with this kind of get
method ? 



-----Mensagem original-----
De: [EMAIL PROTECTED]
[ mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> ]Em nome de Erik Hatcher
Enviada em: quinta-feira, 27 de novembro de 2003 08:23
Para: [EMAIL PROTECTED]
Assunto: Re: [Xdoclet-user] supporting multiple databases


On Thursday, November 27, 2003, at 04:25  AM, Andrew Stevens wrote:
> If you're going to generate multiple DDs, you're going to have to run
> the task/subtask multiple times.  So, just use e.g.
> @jboss.sql type="${jboss.sql.typex}"
> in your tag, and before each run of the task have it read in a
> different
> properties file, where the different properties file have the relevant
> values each database.  No need for any tinkering.
>
> At least, that's the theory.  I've never actually tried it myself, so
> your mileage may vary...  Let us know how you get on.

Sounds good in theory!  :)

But in reality you have to deal with Ant property immutability.  You
cannot change the value of a property under normal conditions.  You
would have to do it under an <antcall>'d target or a separate build
file or some other roundabout way.

        Erik



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
<http://sourceforge.net/donate/> 
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
<https://lists.sourceforge.net/lists/listinfo/xdoclet-user> 




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to