On Tuesday, June 19, 2001, at 06:15 pm, John Menke wrote:
>
> -- the problem with this is that beans might be too simple and not do
> exactly what the user wants. I think that some customization will have
> to
> able to made if the user selects to do so. (EJBDoclet should be able to
> handle this be letting the user specify a base class for the Entity
> Bean and
> base class for the Session bean)
Instead of specifying the base class, you can generate a skeleton class
that is not overwritten if the class file already exists. The user can
modify the skeleton to do what s/he wants. The problem is, how to
integrate this with the Peer mechanism
>
> Question is: Does this represent a valid architecture? (One session
> bean
> per entity bean?) Or should we try to develop some sort of abstraction
> where
> one session bean controls many entity beans? Personally, I think that
> with
> the auto generation the 1/1 mapping of session beans to entity beans
> will be
> OK.
>
> 2. I am just learning Ant, so it would be helpful if somebody pointed
> to the
> scripts that read the schema file and generate the SQL. (I will
> probably be
> able to find them, but at the moment I'm still looking).
>
>
-- Denis.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
