🚀 go-pugleaf

I want to append to the first item that in fact it would be a very good idea
to place the class file in another location to prevent accidental inclusion
and illegal usage.

Chris
"Chris" <inprise@houghten.com> wrote in message news:3aa3e7aa$1_1@dnews...
> I need someone to tell me if the following 2 items are true or false:
>
>
> first of all is the visibility of classes to other classes:
>
> If I am following the EJB specifications and I have designed classes with
> interfaces and homes then other classes that use my class should NEVER be
> able to see my class file. They should be able to see my home and my
> interface to thay can construct my class, but for all intents and
purposes,
> I could move my class into another directory that is not imported by any
> other classes.
>
>
>
> secondly, is information ported to a visible front end:
>
> If I write a JSP that displays information from 2 objects, lets say an
> Account and an Address and an Account interface is designated to have an
> Address with a getter. Also, each of these objects has a value bean.. that
> is to say a non EJB bean that implements the corosponding business
> interfaces that the EJB's themselves also implement. Now here is where I
am
> getting lip. I believe that my JSP would obtain an Account value bean,
> display that info, then ask the Account value bean for it's Address object
> and then display that info. I have been told that that would not be
correct,
> but instead one should have create a new calue bean that does not
implement
> anything except Serializable that contains all the info in simple types of
> the Address AND the Account objects and that the JSP should ask for that
> object and use it instead.
>
>
> I have been working with interfaces for quite some time and also with the
> EJB specification and the CORBA specifications and I'm pretty sure I am
> right, but apparantly I need someone else to help me in my argument.
>
> Thanks in advance,
> Chris Houghten
> chris@houghten.com
>
>