You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2009/12/11 01:40:18 UTC

[jira] Created: (OWB-188) remove webbeans-jpa and cleanup webbeans-resource

remove webbeans-jpa and cleanup webbeans-resource
-------------------------------------------------

                 Key: OWB-188
                 URL: https://issues.apache.org/jira/browse/OWB-188
             Project: OpenWebBeans
          Issue Type: Improvement
    Affects Versions: M3
            Reporter: Mark Struberg
            Assignee: Mark Struberg
             Fix For: M4


Most of the code from webbeans-jpa has been dupped over to webbeans-resource. The whole plugin is now essentially obsolete and shall be removed.
We also have to cleanup webbeans-resource and webbeans-geronimo and remove unused code.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Re: [jira] Resolved: (OWB-188) remove webbeans-jpa and cleanup webbeans-resource

Posted by Gurkan Erdogdu <cg...@gmail.com>.
>
> true, I think we should really go and rename webbeans-geronimo to
> webbeans-openejb.
>

Not that way. The way is to

1*  rename webbeans-ejb to webbeans-openejb
2*  move codes from webbeans-geronimo into  webbeans-openejb
3*  remove webbeans-geronimo folder.

2009/12/11 Mark Struberg <st...@yahoo.de>

> true, I think we should really go and rename webbeans-geronimo to
> webbeans-openejb.
>
> In fact there is a 4th layer: the integration via bundles of 3) for the
> default packages of various containers (all with preconfigured
> openwebbeans.properties):
>
> just a few ideas
> bundles/geronimo (MyFaces + OpenEJB + OpenJPA ...)
> bundles/web_se (MyFaces + OpenJPA)
> bundles/web_wicket(wicket + OpenJPA)
> bundles/standalone
>
> LieGrue,
> strub
>
> --- Gurkan Erdogdu <cg...@gmail.com> schrieb am Fr, 11.12.2009:
>
> > Von: Gurkan Erdogdu <cg...@gmail.com>
> > Betreff: Re: [jira] Resolved: (OWB-188) remove webbeans-jpa and cleanup
>  webbeans-resource
> > An: openwebbeans-dev@incubator.apache.org
> > Datum: Freitag, 11. Dezember 2009, 12:30
> > Good seperation Mark!
> >
> > Actually webbeans-geronimo will be leading to some
> > confusion. The main
> > motivation behind this project was that it will include
> > integration code for
> > geronimo .But currently it includes OpenEJB code. I think
> > that we have to
> > separate those things and some refactoring.
> >
> > My advice is that
> >
> > 1* Change project name of webbeans-ejb -->
> > webbeans-openejb as Mark stated
> > earlier
> > 2* Move OpenEJB related code from webbeans-geronimo to
> > webbeans-ejb
> > 3* Remove webbeans-geronimo
> >     In reality Geronimo integration code will be
> > implemented in the Geronimo
> > code base using its plugin architecture. This will use the
> > same technique
> > for what happened to MyFaces and OpenJPA, OpenEJB etc.
> > integration.
> >
> >
> > --Gurkan
> >
> >
> > 2009/12/11 Mark Struberg <st...@yahoo.de>
> >
> > > > We sure that all examples still work :)
> > > Heh, I hope so, I at least tried out samples/guess and
> > samples/reservation
> > > before checking in ;)
> > >
> > > I hope I can sum up the magic behind this (maybe even
> > in the new xdoc) this
> > > weekend.
> > >
> > > In general it seems like we have a 3-staged mechanism
> > (even if this is not
> > > so visible from the first glance)
> > >
> > > 1st layer:
> > > webbeans-core
> > >
> > > 2nd layer:
> > > the general plugin on a specific specification area
> > (e.g. JMS, JPA, EJB)
> > >
> > > 3rd layer:
> > > the 2) bound to a specific product or technique: e.g.
> > the JPA
> > > Implementation for SE (provided originally with
> > webbeans-jpa, now moved over
> > > to webbeans-resource) will give you a
> > @PersistenceContext EntityManager with
> > > PersitenceType.EXTENDED whereas if you switch over to
> > the SPI Implementation
> > > from webbeans-geronimo you will get a TRANSACTIONAL
> > PersistenceContext
> > > (which we get from OpenEJB + it's JTA layer).
> > > It's really important to know these differences and to
> > understand the
> > > fundamentally different way those 2 EntityManagers
> > work internally. But I
> > > think David or the other geronimo and OpenEJB folks
> > here can explain this
> > > much better than I can, so I'll focus on the OWB
> > part.
> > >
> > > LieGrue,
> > > strub
> > >
> > >
> > > --- Gurkan Erdogdu <cg...@gmail.com>
> > schrieb am Fr, 11.12.2009:
> > >
> > > > Von: Gurkan Erdogdu <cg...@gmail.com>
> > > > Betreff: Re: [jira] Resolved: (OWB-188) remove
> > webbeans-jpa and cleanup
> > >  webbeans-resource
> > > > An: openwebbeans-dev@incubator.apache.org
> > > > Datum: Freitag, 11. Dezember 2009, 10:51
> > > > Awesome thanks! Good idea to throw
> > > > out trashed code.
> > > >
> > > > We sure that all examples still work :)
> > > >
> > > > --Gurkan
> > > >
> > > > 2009/12/11 Mark Struberg (JIRA) <ji...@apache.org>
> > > >
> > > > >
> > > > >     [
> > > > >
> > >
> https://issues.apache.org/jira/browse/OWB-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> > > ]
> > > > >
> > > > > Mark Struberg resolved OWB-188.
> > > > > -------------------------------
> > > > >
> > > > >    Resolution: Fixed
> > > > >
> > > > > > remove webbeans-jpa and cleanup
> > > > webbeans-resource
> > > > > >
> > > >
> > -------------------------------------------------
> > > > > >
> > > > > >
> > > >    Key: OWB-188
> > > > > >
> > > >    URL: https://issues.apache.org/jira/browse/OWB-188
> > > > > >
> > > >    Project: OpenWebBeans
> > > > > >          Issue
> > Type:
> > > > Improvement
> > > > > >    Affects Versions: M3
> > > > > >
> > > > Reporter: Mark Struberg
> > > > > >
> > > > Assignee: Mark Struberg
> > > > > >
> > > >    Fix For: M4
> > > > > >
> > > > > >
> > > > > > Most of the code from webbeans-jpa has
> > been
> > > > dupped over to
> > > > > webbeans-resource. The whole plugin is now
> > essentially
> > > > obsolete and shall be
> > > > > removed.
> > > > > > We also have to cleanup
> > webbeans-resource and
> > > > webbeans-geronimo and
> > > > > remove unused code.
> > > > >
> > > > > --
> > > > > This message is automatically generated by
> > JIRA.
> > > > > -
> > > > > You can reply to this email to add a comment
> > to the
> > > > issue online.
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Gurkan Erdogdu
> > > > http://gurkanerdogdu.blogspot.com
> > > >
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Sie sind Spam leid? Yahoo! Mail verfügt über einen
> > herausragenden Schutz
> > > gegen Massenmails.
> > > http://mail.yahoo.com
> > >
> >
> >
> >
> > --
> > Gurkan Erdogdu
> > http://gurkanerdogdu.blogspot.com
> >
>
> __________________________________________________
> Do You Yahoo!?
> Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz
> gegen Massenmails.
> http://mail.yahoo.com
>



-- 
Gurkan Erdogdu
http://gurkanerdogdu.blogspot.com

Re: [jira] Resolved: (OWB-188) remove webbeans-jpa and cleanup webbeans-resource

Posted by Gurkan Erdogdu <cg...@gmail.com>.
We will update those projects to integrate with geronimo

https://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/openwebbeans/.<https://svn.apache.org/repos/asf/geronimo/server/trunk/plugins/openwebbeans/>

This is a very good candidate that needs contribution!

Thanks;

--Gurkan

2009/12/11 Gurkan Erdogdu <cg...@gmail.com>

> Good seperation Mark!
>
> Actually webbeans-geronimo will be leading to some confusion. The main
> motivation behind this project was that it will include integration code for
> geronimo .But currently it includes OpenEJB code. I think that we have to
> separate those things and some refactoring.
>
> My advice is that
>
> 1* Change project name of webbeans-ejb --> webbeans-openejb as Mark stated
> earlier
> 2* Move OpenEJB related code from webbeans-geronimo to webbeans-ejb
> 3* Remove webbeans-geronimo
>     In reality Geronimo integration code will be implemented in the
> Geronimo code base using its plugin architecture. This will use the same
> technique for what happened to MyFaces and OpenJPA, OpenEJB etc.
> integration.
>
>
> --Gurkan
>
>
> 2009/12/11 Mark Struberg <st...@yahoo.de>
>
> > We sure that all examples still work :)
>> Heh, I hope so, I at least tried out samples/guess and samples/reservation
>> before checking in ;)
>>
>> I hope I can sum up the magic behind this (maybe even in the new xdoc)
>> this weekend.
>>
>> In general it seems like we have a 3-staged mechanism (even if this is not
>> so visible from the first glance)
>>
>> 1st layer:
>> webbeans-core
>>
>> 2nd layer:
>> the general plugin on a specific specification area (e.g. JMS, JPA, EJB)
>>
>> 3rd layer:
>> the 2) bound to a specific product or technique: e.g. the JPA
>> Implementation for SE (provided originally with webbeans-jpa, now moved over
>> to webbeans-resource) will give you a @PersistenceContext EntityManager with
>> PersitenceType.EXTENDED whereas if you switch over to the SPI Implementation
>> from webbeans-geronimo you will get a TRANSACTIONAL PersistenceContext
>> (which we get from OpenEJB + it's JTA layer).
>> It's really important to know these differences and to understand the
>> fundamentally different way those 2 EntityManagers work internally. But I
>> think David or the other geronimo and OpenEJB folks here can explain this
>> much better than I can, so I'll focus on the OWB part.
>>
>> LieGrue,
>> strub
>>
>>
>> --- Gurkan Erdogdu <cg...@gmail.com> schrieb am Fr, 11.12.2009:
>>
>> > Von: Gurkan Erdogdu <cg...@gmail.com>
>> > Betreff: Re: [jira] Resolved: (OWB-188) remove webbeans-jpa and cleanup
>>  webbeans-resource
>> > An: openwebbeans-dev@incubator.apache.org
>> > Datum: Freitag, 11. Dezember 2009, 10:51
>> > Awesome thanks! Good idea to throw
>> > out trashed code.
>> >
>> > We sure that all examples still work :)
>> >
>> > --Gurkan
>> >
>> > 2009/12/11 Mark Struberg (JIRA) <ji...@apache.org>
>> >
>> > >
>> > >     [
>> > >
>> https://issues.apache.org/jira/browse/OWB-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>> > >
>> > > Mark Struberg resolved OWB-188.
>> > > -------------------------------
>> > >
>> > >    Resolution: Fixed
>> > >
>> > > > remove webbeans-jpa and cleanup
>> > webbeans-resource
>> > > >
>> > -------------------------------------------------
>> > > >
>> > > >
>> >    Key: OWB-188
>> > > >
>> >    URL: https://issues.apache.org/jira/browse/OWB-188
>> > > >
>> >    Project: OpenWebBeans
>> > > >          Issue Type:
>> > Improvement
>> > > >    Affects Versions: M3
>> > > >
>> > Reporter: Mark Struberg
>> > > >
>> > Assignee: Mark Struberg
>> > > >
>> >    Fix For: M4
>> > > >
>> > > >
>> > > > Most of the code from webbeans-jpa has been
>> > dupped over to
>> > > webbeans-resource. The whole plugin is now essentially
>> > obsolete and shall be
>> > > removed.
>> > > > We also have to cleanup webbeans-resource and
>> > webbeans-geronimo and
>> > > remove unused code.
>> > >
>> > > --
>> > > This message is automatically generated by JIRA.
>> > > -
>> > > You can reply to this email to add a comment to the
>> > issue online.
>> > >
>> > >
>> >
>> >
>> > --
>> > Gurkan Erdogdu
>> > http://gurkanerdogdu.blogspot.com
>> >
>>
>> __________________________________________________
>> Do You Yahoo!?
>> Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz
>> gegen Massenmails.
>> http://mail.yahoo.com
>>
>
>
>
> --
> Gurkan Erdogdu
> http://gurkanerdogdu.blogspot.com
>



-- 
Gurkan Erdogdu
http://gurkanerdogdu.blogspot.com

Re: [jira] Resolved: (OWB-188) remove webbeans-jpa and cleanup webbeans-resource

Posted by Mark Struberg <st...@yahoo.de>.
true, I think we should really go and rename webbeans-geronimo to webbeans-openejb.

In fact there is a 4th layer: the integration via bundles of 3) for the default packages of various containers (all with preconfigured openwebbeans.properties):

just a few ideas
bundles/geronimo (MyFaces + OpenEJB + OpenJPA ...)
bundles/web_se (MyFaces + OpenJPA)
bundles/web_wicket(wicket + OpenJPA)
bundles/standalone 

LieGrue,
strub

--- Gurkan Erdogdu <cg...@gmail.com> schrieb am Fr, 11.12.2009:

> Von: Gurkan Erdogdu <cg...@gmail.com>
> Betreff: Re: [jira] Resolved: (OWB-188) remove webbeans-jpa and cleanup  webbeans-resource
> An: openwebbeans-dev@incubator.apache.org
> Datum: Freitag, 11. Dezember 2009, 12:30
> Good seperation Mark!
> 
> Actually webbeans-geronimo will be leading to some
> confusion. The main
> motivation behind this project was that it will include
> integration code for
> geronimo .But currently it includes OpenEJB code. I think
> that we have to
> separate those things and some refactoring.
> 
> My advice is that
> 
> 1* Change project name of webbeans-ejb -->
> webbeans-openejb as Mark stated
> earlier
> 2* Move OpenEJB related code from webbeans-geronimo to
> webbeans-ejb
> 3* Remove webbeans-geronimo
>     In reality Geronimo integration code will be
> implemented in the Geronimo
> code base using its plugin architecture. This will use the
> same technique
> for what happened to MyFaces and OpenJPA, OpenEJB etc.
> integration.
> 
> 
> --Gurkan
> 
> 
> 2009/12/11 Mark Struberg <st...@yahoo.de>
> 
> > > We sure that all examples still work :)
> > Heh, I hope so, I at least tried out samples/guess and
> samples/reservation
> > before checking in ;)
> >
> > I hope I can sum up the magic behind this (maybe even
> in the new xdoc) this
> > weekend.
> >
> > In general it seems like we have a 3-staged mechanism
> (even if this is not
> > so visible from the first glance)
> >
> > 1st layer:
> > webbeans-core
> >
> > 2nd layer:
> > the general plugin on a specific specification area
> (e.g. JMS, JPA, EJB)
> >
> > 3rd layer:
> > the 2) bound to a specific product or technique: e.g.
> the JPA
> > Implementation for SE (provided originally with
> webbeans-jpa, now moved over
> > to webbeans-resource) will give you a
> @PersistenceContext EntityManager with
> > PersitenceType.EXTENDED whereas if you switch over to
> the SPI Implementation
> > from webbeans-geronimo you will get a TRANSACTIONAL
> PersistenceContext
> > (which we get from OpenEJB + it's JTA layer).
> > It's really important to know these differences and to
> understand the
> > fundamentally different way those 2 EntityManagers
> work internally. But I
> > think David or the other geronimo and OpenEJB folks
> here can explain this
> > much better than I can, so I'll focus on the OWB
> part.
> >
> > LieGrue,
> > strub
> >
> >
> > --- Gurkan Erdogdu <cg...@gmail.com>
> schrieb am Fr, 11.12.2009:
> >
> > > Von: Gurkan Erdogdu <cg...@gmail.com>
> > > Betreff: Re: [jira] Resolved: (OWB-188) remove
> webbeans-jpa and cleanup
> >  webbeans-resource
> > > An: openwebbeans-dev@incubator.apache.org
> > > Datum: Freitag, 11. Dezember 2009, 10:51
> > > Awesome thanks! Good idea to throw
> > > out trashed code.
> > >
> > > We sure that all examples still work :)
> > >
> > > --Gurkan
> > >
> > > 2009/12/11 Mark Struberg (JIRA) <ji...@apache.org>
> > >
> > > >
> > > >     [
> > > >
> > https://issues.apache.org/jira/browse/OWB-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> > ]
> > > >
> > > > Mark Struberg resolved OWB-188.
> > > > -------------------------------
> > > >
> > > >    Resolution: Fixed
> > > >
> > > > > remove webbeans-jpa and cleanup
> > > webbeans-resource
> > > > >
> > >
> -------------------------------------------------
> > > > >
> > > > >
> > >    Key: OWB-188
> > > > >
> > >    URL: https://issues.apache.org/jira/browse/OWB-188
> > > > >
> > >    Project: OpenWebBeans
> > > > >          Issue
> Type:
> > > Improvement
> > > > >    Affects Versions: M3
> > > > >
> > > Reporter: Mark Struberg
> > > > >
> > > Assignee: Mark Struberg
> > > > >
> > >    Fix For: M4
> > > > >
> > > > >
> > > > > Most of the code from webbeans-jpa has
> been
> > > dupped over to
> > > > webbeans-resource. The whole plugin is now
> essentially
> > > obsolete and shall be
> > > > removed.
> > > > > We also have to cleanup
> webbeans-resource and
> > > webbeans-geronimo and
> > > > remove unused code.
> > > >
> > > > --
> > > > This message is automatically generated by
> JIRA.
> > > > -
> > > > You can reply to this email to add a comment
> to the
> > > issue online.
> > > >
> > > >
> > >
> > >
> > > --
> > > Gurkan Erdogdu
> > > http://gurkanerdogdu.blogspot.com
> > >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Sie sind Spam leid? Yahoo! Mail verfügt über einen
> herausragenden Schutz
> > gegen Massenmails.
> > http://mail.yahoo.com
> >
> 
> 
> 
> -- 
> Gurkan Erdogdu
> http://gurkanerdogdu.blogspot.com
> 

__________________________________________________
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. 
http://mail.yahoo.com 

Re: [jira] Resolved: (OWB-188) remove webbeans-jpa and cleanup webbeans-resource

Posted by Gurkan Erdogdu <cg...@gmail.com>.
Good seperation Mark!

Actually webbeans-geronimo will be leading to some confusion. The main
motivation behind this project was that it will include integration code for
geronimo .But currently it includes OpenEJB code. I think that we have to
separate those things and some refactoring.

My advice is that

1* Change project name of webbeans-ejb --> webbeans-openejb as Mark stated
earlier
2* Move OpenEJB related code from webbeans-geronimo to webbeans-ejb
3* Remove webbeans-geronimo
    In reality Geronimo integration code will be implemented in the Geronimo
code base using its plugin architecture. This will use the same technique
for what happened to MyFaces and OpenJPA, OpenEJB etc. integration.


--Gurkan


2009/12/11 Mark Struberg <st...@yahoo.de>

> > We sure that all examples still work :)
> Heh, I hope so, I at least tried out samples/guess and samples/reservation
> before checking in ;)
>
> I hope I can sum up the magic behind this (maybe even in the new xdoc) this
> weekend.
>
> In general it seems like we have a 3-staged mechanism (even if this is not
> so visible from the first glance)
>
> 1st layer:
> webbeans-core
>
> 2nd layer:
> the general plugin on a specific specification area (e.g. JMS, JPA, EJB)
>
> 3rd layer:
> the 2) bound to a specific product or technique: e.g. the JPA
> Implementation for SE (provided originally with webbeans-jpa, now moved over
> to webbeans-resource) will give you a @PersistenceContext EntityManager with
> PersitenceType.EXTENDED whereas if you switch over to the SPI Implementation
> from webbeans-geronimo you will get a TRANSACTIONAL PersistenceContext
> (which we get from OpenEJB + it's JTA layer).
> It's really important to know these differences and to understand the
> fundamentally different way those 2 EntityManagers work internally. But I
> think David or the other geronimo and OpenEJB folks here can explain this
> much better than I can, so I'll focus on the OWB part.
>
> LieGrue,
> strub
>
>
> --- Gurkan Erdogdu <cg...@gmail.com> schrieb am Fr, 11.12.2009:
>
> > Von: Gurkan Erdogdu <cg...@gmail.com>
> > Betreff: Re: [jira] Resolved: (OWB-188) remove webbeans-jpa and cleanup
>  webbeans-resource
> > An: openwebbeans-dev@incubator.apache.org
> > Datum: Freitag, 11. Dezember 2009, 10:51
> > Awesome thanks! Good idea to throw
> > out trashed code.
> >
> > We sure that all examples still work :)
> >
> > --Gurkan
> >
> > 2009/12/11 Mark Struberg (JIRA) <ji...@apache.org>
> >
> > >
> > >     [
> > >
> https://issues.apache.org/jira/browse/OWB-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
> > >
> > > Mark Struberg resolved OWB-188.
> > > -------------------------------
> > >
> > >    Resolution: Fixed
> > >
> > > > remove webbeans-jpa and cleanup
> > webbeans-resource
> > > >
> > -------------------------------------------------
> > > >
> > > >
> >    Key: OWB-188
> > > >
> >    URL: https://issues.apache.org/jira/browse/OWB-188
> > > >
> >    Project: OpenWebBeans
> > > >          Issue Type:
> > Improvement
> > > >    Affects Versions: M3
> > > >
> > Reporter: Mark Struberg
> > > >
> > Assignee: Mark Struberg
> > > >
> >    Fix For: M4
> > > >
> > > >
> > > > Most of the code from webbeans-jpa has been
> > dupped over to
> > > webbeans-resource. The whole plugin is now essentially
> > obsolete and shall be
> > > removed.
> > > > We also have to cleanup webbeans-resource and
> > webbeans-geronimo and
> > > remove unused code.
> > >
> > > --
> > > This message is automatically generated by JIRA.
> > > -
> > > You can reply to this email to add a comment to the
> > issue online.
> > >
> > >
> >
> >
> > --
> > Gurkan Erdogdu
> > http://gurkanerdogdu.blogspot.com
> >
>
> __________________________________________________
> Do You Yahoo!?
> Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz
> gegen Massenmails.
> http://mail.yahoo.com
>



-- 
Gurkan Erdogdu
http://gurkanerdogdu.blogspot.com

Re: [jira] Resolved: (OWB-188) remove webbeans-jpa and cleanup webbeans-resource

Posted by Mark Struberg <st...@yahoo.de>.
> We sure that all examples still work :)
Heh, I hope so, I at least tried out samples/guess and samples/reservation before checking in ;)

I hope I can sum up the magic behind this (maybe even in the new xdoc) this weekend.

In general it seems like we have a 3-staged mechanism (even if this is not so visible from the first glance)

1st layer: 
webbeans-core

2nd layer: 
the general plugin on a specific specification area (e.g. JMS, JPA, EJB)

3rd layer: 
the 2) bound to a specific product or technique: e.g. the JPA Implementation for SE (provided originally with webbeans-jpa, now moved over to webbeans-resource) will give you a @PersistenceContext EntityManager with PersitenceType.EXTENDED whereas if you switch over to the SPI Implementation from webbeans-geronimo you will get a TRANSACTIONAL PersistenceContext (which we get from OpenEJB + it's JTA layer).
It's really important to know these differences and to understand the fundamentally different way those 2 EntityManagers work internally. But I think David or the other geronimo and OpenEJB folks here can explain this much better than I can, so I'll focus on the OWB part.

LieGrue,
strub


--- Gurkan Erdogdu <cg...@gmail.com> schrieb am Fr, 11.12.2009:

> Von: Gurkan Erdogdu <cg...@gmail.com>
> Betreff: Re: [jira] Resolved: (OWB-188) remove webbeans-jpa and cleanup  webbeans-resource
> An: openwebbeans-dev@incubator.apache.org
> Datum: Freitag, 11. Dezember 2009, 10:51
> Awesome thanks! Good idea to throw
> out trashed code.
> 
> We sure that all examples still work :)
> 
> --Gurkan
> 
> 2009/12/11 Mark Struberg (JIRA) <ji...@apache.org>
> 
> >
> >     [
> > https://issues.apache.org/jira/browse/OWB-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
> >
> > Mark Struberg resolved OWB-188.
> > -------------------------------
> >
> >    Resolution: Fixed
> >
> > > remove webbeans-jpa and cleanup
> webbeans-resource
> > >
> -------------------------------------------------
> > >
> > >             
>    Key: OWB-188
> > >             
>    URL: https://issues.apache.org/jira/browse/OWB-188
> > >         
>    Project: OpenWebBeans
> > >          Issue Type:
> Improvement
> > >    Affects Versions: M3
> > >           
> Reporter: Mark Struberg
> > >           
> Assignee: Mark Struberg
> > >         
>    Fix For: M4
> > >
> > >
> > > Most of the code from webbeans-jpa has been
> dupped over to
> > webbeans-resource. The whole plugin is now essentially
> obsolete and shall be
> > removed.
> > > We also have to cleanup webbeans-resource and
> webbeans-geronimo and
> > remove unused code.
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > You can reply to this email to add a comment to the
> issue online.
> >
> >
> 
> 
> -- 
> Gurkan Erdogdu
> http://gurkanerdogdu.blogspot.com
> 

__________________________________________________
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. 
http://mail.yahoo.com 

Re: [jira] Resolved: (OWB-188) remove webbeans-jpa and cleanup webbeans-resource

Posted by Gurkan Erdogdu <cg...@gmail.com>.
Awesome thanks! Good idea to throw out trashed code.

We sure that all examples still work :)

--Gurkan

2009/12/11 Mark Struberg (JIRA) <ji...@apache.org>

>
>     [
> https://issues.apache.org/jira/browse/OWB-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Mark Struberg resolved OWB-188.
> -------------------------------
>
>    Resolution: Fixed
>
> > remove webbeans-jpa and cleanup webbeans-resource
> > -------------------------------------------------
> >
> >                 Key: OWB-188
> >                 URL: https://issues.apache.org/jira/browse/OWB-188
> >             Project: OpenWebBeans
> >          Issue Type: Improvement
> >    Affects Versions: M3
> >            Reporter: Mark Struberg
> >            Assignee: Mark Struberg
> >             Fix For: M4
> >
> >
> > Most of the code from webbeans-jpa has been dupped over to
> webbeans-resource. The whole plugin is now essentially obsolete and shall be
> removed.
> > We also have to cleanup webbeans-resource and webbeans-geronimo and
> remove unused code.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>


-- 
Gurkan Erdogdu
http://gurkanerdogdu.blogspot.com

[jira] Resolved: (OWB-188) remove webbeans-jpa and cleanup webbeans-resource

Posted by "Mark Struberg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OWB-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Struberg resolved OWB-188.
-------------------------------

    Resolution: Fixed

> remove webbeans-jpa and cleanup webbeans-resource
> -------------------------------------------------
>
>                 Key: OWB-188
>                 URL: https://issues.apache.org/jira/browse/OWB-188
>             Project: OpenWebBeans
>          Issue Type: Improvement
>    Affects Versions: M3
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: M4
>
>
> Most of the code from webbeans-jpa has been dupped over to webbeans-resource. The whole plugin is now essentially obsolete and shall be removed.
> We also have to cleanup webbeans-resource and webbeans-geronimo and remove unused code.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.