Hello Rickard,
Thank you for your answer.
...
>
> > Can a same CMP Bean "AB" be accessed by A and B?
> > How to deploy this?
>
> Well the best advice I think is "just do it". :-)
Great!
> Create the ejb-jar.xml just as with any other beans. The only difference
> is that two entries will have the same bean class.
So, the deployer uses the fully qualified class name (FQCN) to determine
what to map to the database i.e. it won't create two (identical) DB tables
(with different names!) for the two beans but instead share it? If this is
true, that means that the "discriminant" for determining when to map a CMP
bean to a new table is the FQCN? Right? (it might have been the bean name,
...)
> > The goal is to have a remote interface used by external clients
> and another
> > remote interface used by other EJB (i.e. internal clients) with more
> > powerfull methods (management, ...)
>
> The above is not the best way to solve this. Use security instead.
> That's what it's for. I.e. restrict the methods that are not supposed to
> be used by certain types of users. If you don't use security at all it
> is still possible for (malicious) external clients to lookup the bean
> with the admin interface and call it as it wishes.
Yes, I thought about this, but my problem is not security related : I just
want not to give to the client a HUGE (not so big in fact...) list of
methods it will never use! It is more a "pedagogic" goal : not to confuse
the client with tricky interfaces ;)
Cheers,
Sacha
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
