HibernateExtensionPostProcessor

10 messages Options
Embed this post
Permalink
David Whitehurst

HibernateExtensionPostProcessor

Reply Threaded More More options
Print post
Permalink
Does the use of:

@Entity(name=Person) allow us not to need the registration snippet for HibernateExtensionPostProcessor?  If not needed, what's the fix or replacement?  What ties the JPA annotations into being understood by the Hibernate Session?


David
mraible

Re: HibernateExtensionPostProcessor

Reply Threaded More More options
Print post
Permalink
You need to register your Person object in hibernate.cfg.xml. The
reason this didn't work before (and we needed
HibernateExtensionPostProcessor) was because AppFuse's
hibernate.cfg.xml was picked up from one of the JARs.

Matt

On 4/22/07, David Whitehurst <[hidden email]> wrote:

> Does the use of:
>
> @Entity(name=Person) allow us not to need the registration snippet for
> HibernateExtensionPostProcessor?  If not needed, what's the
> fix or replacement?  What ties the JPA annotations into being understood by
> the Hibernate Session?
>
>
> David
>


--
http://raibledesigns.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

David Whitehurst

Re: HibernateExtensionPostProcessor

Reply Threaded More More options
Print post
Permalink
I knew that but is the PostProcessor still needed?  The JIRA ticket seemed like two model registrations were still needed.


David

On 4/22/07, Matt Raible <[hidden email]> wrote:
You need to register your Person object in hibernate.cfg.xml. The
reason this didn't work before (and we needed
HibernateExtensionPostProcessor) was because AppFuse's
hibernate.cfg.xml was picked up from one of the JARs.

Matt

On 4/22/07, David Whitehurst <[hidden email]> wrote:
> Does the use of:
>
> @Entity(name=Person) allow us not to need the registration snippet for
> HibernateExtensionPostProcessor?  If not needed, what's the
> fix or replacement?  What ties the JPA annotations into being understood by
> the Hibernate Session?
>
>
> David
>


--
http://raibledesigns.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


mraible

Re: HibernateExtensionPostProcessor

Reply Threaded More More options
Print post
Permalink
No, it is no longer needed as of 2.0 M4.

Matt

On 4/22/07, David Whitehurst <[hidden email]> wrote:

> I knew that but is the PostProcessor still needed?  The JIRA ticket seemed
> like two model registrations were still needed.
>
>
> David
>
>
> On 4/22/07, Matt Raible <[hidden email]> wrote:
> >
> > You need to register your Person object in hibernate.cfg.xml. The
> > reason this didn't work before (and we needed
> > HibernateExtensionPostProcessor) was because AppFuse's
> > hibernate.cfg.xml was picked up from one of the JARs.
> >
> > Matt
> >
> > On 4/22/07, David Whitehurst <[hidden email]> wrote:
> > > Does the use of:
> > >
> > > @Entity(name=Person) allow us not to need the registration snippet for
> > > HibernateExtensionPostProcessor?  If not needed, what's
> the
> > > fix or replacement?  What ties the JPA annotations into being understood
> by
> > > the Hibernate Session?
> > >
> > >
> > > David
> > >
> >
> >
> > --
> > http://raibledesigns.com
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
>


--
http://raibledesigns.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

tibi

Re: HibernateExtensionPostProcessor

Reply Threaded More More options
Print post
Permalink
In reply to this post by David Whitehurst
if the HibernateExtensionPostProcessor is not needed any more. why is it still there??

can i remove it from my project?
and more fundamental can it be removed from appfuse??
mraible

Re: HibernateExtensionPostProcessor

Reply Threaded More More options
Print post
Permalink
Why is it not needed anymore? It's always been available to users as a mechanism to extend the sessionFactory bean. It's not necessary when folks run appfuse:full-source, but it still can be handy when running in embedded mode.

Matt

On Tue, Mar 31, 2009 at 6:00 AM, tibi <[hidden email]> wrote:

if the HibernateExtensionPostProcessor is not needed any more. why is it
still there??

can i remove it from my project?
and more fundamental can it be removed from appfuse??

--
View this message in context: http://www.nabble.com/HibernateExtensionPostProcessor-tp10129077s2369p22803662.html
Sent from the AppFuse - Dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


tibi

Re: HibernateExtensionPostProcessor

Reply Threaded More More options
Print post
Permalink
ok so its like this:
not needed when running full-source
handy in other cases?

so in my project (full source) i can remove the class.

am i correct??

thanks
mraible wrote:
Why is it not needed anymore? It's always been available to users as a
mechanism to extend the sessionFactory bean. It's not necessary when folks
run appfuse:full-source, but it still can be handy when running in embedded
mode.

Matt

On Tue, Mar 31, 2009 at 6:00 AM, tibi <tibi@dds.nl> wrote:

>
> if the HibernateExtensionPostProcessor is not needed any more. why is it
> still there??
>
> can i remove it from my project?
> and more fundamental can it be removed from appfuse??
>
> --
> View this message in context:
> http://www.nabble.com/HibernateExtensionPostProcessor-tp10129077s2369p22803662.html
> Sent from the AppFuse - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@appfuse.dev.java.net
> For additional commands, e-mail: dev-help@appfuse.dev.java.net
>
>
tibi

Re: HibernateExtensionPostProcessor

Reply Threaded More More options
Print post
Permalink
In reply to this post by mraible

mraible wrote:
No, it is no longer needed as of 2.0 M4.

Matt
thats is why i thought it was not needed anymore....
mraible

Re: HibernateExtensionPostProcessor

Reply Threaded More More options
Print post
Permalink
You may be right. Especially if you read the Javadocs.

http://static.appfuse.org/appfuse-hibernate/apidocs/org/appfuse/dao/spring/HibernateExtensionPostProcessor.html

Matt

On Tue, Mar 31, 2009 at 2:00 PM, tibi <[hidden email]> wrote:



mraible wrote:
>
> No, it is no longer needed as of 2.0 M4.
>
> Matt
>
thats is why i thought it was not needed anymore....
--
View this message in context: http://www.nabble.com/HibernateExtensionPostProcessor-tp10129077s2369p22810012.html
Sent from the AppFuse - Dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


john kola

Re: HibernateExtensionPostProcessor

Reply Threaded More More options
Print post
Permalink
Some javascript/style in this post has been disabled (why?)

Dude I still getting emails from you guy... please delete this email address from your list..
----- Original Message -----
Sent: Tuesday, March 31, 2009 4:32 PM
Subject: Re: [appfuse-dev] HibernateExtensionPostProcessor

You may be right. Especially if you read the Javadocs.

http://static.appfuse.org/appfuse-hibernate/apidocs/org/appfuse/dao/spring/HibernateExtensionPostProcessor.html

Matt

On Tue, Mar 31, 2009 at 2:00 PM, tibi <[hidden email]> wrote:



mraible wrote:
>
> No, it is no longer needed as of 2.0 M4.
>
> Matt
>
thats is why i thought it was not needed anymore....
--
View this message in context: http://www.nabble.com/HibernateExtensionPostProcessor-tp10129077s2369p22810012.html
Sent from the AppFuse - Dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]