humm... ok, for sure it will solve my problem now.. but in a strange way..
it will allow any application to touch the persistence layer of my
original application.
I believe that sharing ejb-jar is a extreme useful feature for
Glassfish, but it should also include a management on which context
can access which resource.. or at least provide some security
mechanism..
* of course I can use tricks to simulate that, and if I control my
server I can manage the security somehow.. but I feel we really need
such feature.. I will open an issue asap.. if one of you has another
observation on top of this topic, please share with us..
On Mon, Feb 22, 2010 at 9:10 PM, Judy Tang <Judy.J.Tang_at_sun.com> wrote:
> Hi Felipe,
>
> Nice to hear from you :-)
>
> Just checked with EJB developer and got suggestion to try with putting the
> EJB jar into GF lib dir.
> May be you can give this a try?
>
> Thanks,
> Judy
> Felipe Gaścho wrote:
>>
>> I read in the Glassfish documentation that it is not possible to share
>> an ejb-jar between different applications.
>>
>> Questions:
>>
>> - Is there a roadmap to include this in Glassfish ?
>> - If not, make sense to open an issue asking for this feature ?
>>
>> meanwhile, what is my alternative ?
>>
>> I have an ejb-jar with JPA entities and its EJB 3.1 facade .. I want
>> this persistence layer module to be used by different applications,
>> but I don't want to pack them all in a same EAR due to development
>> environment complications.. (and time wasted with packing the EAR all
>> the time..)
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: quality-help_at_glassfish.dev.java.net
>
>
--
------------------------------------------
Felipe Gaścho
10+ Java Programmer
CEJUG Senior Advisor