Hi!
Vaughn Vernon wrote:
> Cool. That's the key statement that was missing. I assumed from your first
> post -- and the jboss tutorial docs -- that you (and jboss.org) were not
> recommending building a "client jar." In your first post you stated:
>
> > > > So, package ABean,AHome and ARemote in A.jar and deploy, and package
> > > > BBean, BHome, BRemote, Ahome, and ARemote in B.jar and deploy.
> > > > Any B instances can now access the A component.
>
> My only confusion, then, is why not just build a client jar for "A" and let
> "B" see "A" through "A's" client jar? After all, "B" IS "A's" client,
> whether it is part of the same app or not... of course "no black and white
> here" but it would save a step if you have to build a client jar anyway.
Correct. And my intent was not to "recommend" anything. I just described
one option. Making decisions is your task, based on the information that
is available to you :-)
> > > I think Ken will be able to get his app to work the way you stated, but
> it
> > > is not the way the book author intended for it to work.
> >
> > Then how did he intend for it to work? Is this stated?
>
> I will not try to defend the author of whom I have never discussed this
> matter, nor will I criticize your volunteer documentation folks for holes in
> their work. But Monson-Haefel does sell a lot of books! ;-)
Indeed. But shouting loud does not make the message itself better. ;-)
Anyway, I get your point.
> That was all it was meant to be, "food for thought," not an exercise in
> legalese. I wonder if jboss would benefit from having his samples run
> unchanged. That's all. If conforming to his brand of app would help you,
> great!
>
> <question> Do you think it would help you? </question>
> <opinion> I think it would. </opinion>
Indeed. I'm just curious as to how he want it to work. Do all beans then
have their own deployment descriptors? And no EJB-references? I am
unfamiliar with the example, so let me know.
> > > So what if Monson-Haefel asked: "How do we get TravelAgent to see
> Cabin?"
> > > :-)
> >
> > If both are part of same application -> package in same jar.
> > If they are part of two separate applications (each comprising one
> > bean..?) -> package in two jars with shared interfaces.
> >
> > Makes sense?
>
> Does now. And based on what we have both finally stated clearly I think we
> have been *thinking* about the same or similar solution.
Alrighty :-)
regards,
Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
