Jira issue created! 

http://issues.appfuse.org/browse/APF-1003 

thanks
Christophe
 

-----Original Message-----
From: Matt Raible [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, January 16, 2008 5:59 PM
To: [email protected]
Subject: Re: [appfuse-user] 2.0.1 jpa issue

Yes, if you create a JIRA issue, you should be able to attach it there.

Matt

On Jan 16, 2008, at 3:11 AM, Christophe Thiebaud wrote:

>
> jpa (as documented in http://appfuse.org/display/APF/Using+JPA,)
> I have a zip file containing both 2.0 (OK) and 2.0.1 (NOK) samples but

> the mail server does not accept it (~300k). How could I share it ?
> Issuing a jira ?
>
> thanks
> Christophe
>
>
> -----Original Message-----
> From: Matt Raible [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 15, 2008 4:20 PM
> To: [email protected]
> Subject: Re: [appfuse-user] 2.0.1 jpa issue
>
> What is <dao.framework> set to in your application?
>
> On 1/15/08, Christophe Thiebaud <[EMAIL PROTECTED]> wrote:
>> Hi all,
>>
>> summary
>> -------
>> I have noticed a regression from appfuse version 2.0 to version 
>> 2.0.1.
>> I use struts modular + jpa.
>>
>> Basically, version 2.0.1 now introduce (how? why? no idea ...) the 
>> following dependency in the web app
>>
>> my app
>> (...)
>>    +- org.appfuse:appfuse-struts:warpath:2.0.1:compile
>>    (...)
>>       +- org.appfuse:appfuse-service:jar:2.0.1:compile
>>       (...)
>>          +- org.appfuse:appfuse-hibernate:jar:2.0.1:compile
>>
>> (output from 'mvn dependency:tree')
>>
>> Which eventually results in the war file containing both 
>> appfuse-hibernate and appfuse-jpa jars, which is bad.
>>
>> how to reproduce
>> ----------------
>> generate struts modular artifact
>> mvn clean install gives [INFO] BUILD SUCCESSFUL Change pom.xml, 
>> core/pom.xml and remove/rename hibernate config file as documented in

>> http://appfuse.org/display/APF/Using+JPA,
>> mvn clean install gives [ERROR] BUILD ERROR A quick look at the 
>> WEB-INF/lib dir shows :
>> (...)
>> appfuse-data-common-2.0.1.jar
>> appfuse-hibernate-2.0.1.jar
>> appfuse-jpa-2.0.1.jar
>> (...)
>> removing appfuse-hibernate-2.0.1.jar fixes the issue.
>>
>> Same workflow in 2.0 works fine.
>>
>> workaround
>> ----------
>> I have been able to workaround the issue by setting 
>> <dao.framework>jpa</dao.framework>
>> in <M2_REPO>/org/appfuse/appfuse/2.0.1/appfuse-2.0.1.pom
>> which I do not feel like a good idea.
>>
>> fix
>> ---
>> I do not understand how this dependency gets into the web app.
>> What could be a cleaner solution than patching appfuse pom ?
>>
>> Thanks
>> Christophe
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to