Tapestry5 and Appfuse

[Jim O'Callaghan]

Hi,

First post to this list, so please cut me some slack if it's in the wrong location etc.  I'm trying to get AppFuse up and running with Tap 5.1.0.5 and notice that a lot of the package imports refer to org.apache.tapestry.xxx rather than org.apache.tapestry5.xxx - the package name must have changed at some point during tap dev - I'm currently doing a global search and replace - is there another approach / tap5 module that uses the latest package names?

A second, less immediate question I have is with the general AppFuse approach to dealing with persistent entities in the system - the approach appears to be to use services to perform operations upon persistence implementation specific dao objects via interfaces, and model objects for presentation purposes.  The Tap5 approach allows for example using BeanModelEditor editor to get a CRUDable entity on screen quite quickly and the use of annotations to specify persistence, and also adds any entities in the entities package automagically into hibernate.  The AppFuse separation is very clean/structured and no doubt mandated by the use of Spring - to cut a long question short - are there any disadvantages to mixing the approaches within the same application?

Thanks,
Jim.

[mraible]

What version of AppFuse are you using? Tapestry 5 support is only available in trunk (not yet released) and it hasn't been fully polished yet.

Most of the code for our implementation came from: http://code.google.com/p/tapestry5-appfuse/

Matt

On Fri, Sep 18, 2009 at 6:42 AM, jc1001 <[hidden email]> wrote:

Hi,

First post to this list, so please cut me some slack if it's in the wrong
location etc.  I'm trying to get AppFuse up and running with Tap 5.1.0.5 and
notice that a lot of the package imports refer to org.apache.tapestry.xxx
rather than org.apache.tapestry5.xxx - the package name must have changed at
some point during tap dev - I'm currently doing a global search and replace
- is there another approach / tap5 module that uses the latest package
names?

A second, less immediate question I have is with the general AppFuse
approach to dealing with persistent entities in the system - the approach
appears to be to use services to perform operations upon persistence
implementation specific dao objects via interfaces, and model objects for
presentation purposes.  The Tap5 approach allows for example using
BeanModelEditor editor to get a CRUDable entity on screen quite quickly and
the use of annotations to specify persistence, and also adds any entities in
the entities package automagically into hibernate.  The AppFuse separation
is very clean/structured and no doubt mandated by the use of Spring - to cut
a long question short - are there any disadvantages to mixing the approaches
within the same application?

Thanks,
Jim.
--
View this message in context: http://www.nabble.com/Tapestry5-and-Appfuse-tp25506606s2369p25506606.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]

[Jim O'Callaghan]

Matt,

I'm using the Tapestry Modular starter project at http://appfuse.org/display/APF/AppFuse+QuickStart -

mvn archetype:create -DarchetypeGroupId=org.appfuse.archetypes -DarchetypeArtifactId=appfuse-modular-tapestry -DremoteRepositories=http://static.appfuse.org/releases -DarchetypeVersion=2.0.2 -DgroupId=com.mycompany.app -DartifactId=myproject

so this is AppFuse 2.x <?>.  I had a look at the source at http://tapestry5-appfuse.googlecode.com/files/tapestry5-appfuse-sources-1.0.1.tgz and see that it's using the T5 packages.

Are there any anticipated dates for a starter project using the T5 packages or in the interim is manual rename / search replace of the packages / project name  from the tapestry5-appfuse-sources-1.0.1.tgz archive the only way to go?

Are there any known showstoppers in the tapestry5-appfuse-sources-1.0.1.tgz?

Many thanks,
Jim.

mraible wrote:

What version of AppFuse are you using? Tapestry 5 support is only available
in trunk (not yet released) and it hasn't been fully polished yet.

Most of the code for our implementation came from:
http://code.google.com/p/tapestry5-appfuse/

Matt

On Fri, Sep 18, 2009 at 6:42 AM, jc1001 <[e-mail]> wrote:

>
> Hi,
>
> First post to this list, so please cut me some slack if it's in the wrong
> location etc.  I'm trying to get AppFuse up and running with Tap 5.1.0.5
> and
> notice that a lot of the package imports refer to org.apache.tapestry.xxx
> rather than org.apache.tapestry5.xxx - the package name must have changed
> at
> some point during tap dev - I'm currently doing a global search and replace
> - is there another approach / tap5 module that uses the latest package
> names?
>
> A second, less immediate question I have is with the general AppFuse
> approach to dealing with persistent entities in the system - the approach
> appears to be to use services to perform operations upon persistence
> implementation specific dao objects via interfaces, and model objects for
> presentation purposes.  The Tap5 approach allows for example using
> BeanModelEditor editor to get a CRUDable entity on screen quite quickly and
> the use of annotations to specify persistence, and also adds any entities
> in
> the entities package automagically into hibernate.  The AppFuse separation
> is very clean/structured and no doubt mandated by the use of Spring - to
> cut
> a long question short - are there any disadvantages to mixing the
> approaches
> within the same application?
>
> Thanks,
> Jim.
> --
> View this message in context:
> http://www.nabble.com/Tapestry5-and-Appfuse-tp25506606s2369p25506606.html
> Sent from the AppFuse - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [e-mail]
> For additional commands, e-mail: [e-mail]
>
>

[mraible]

On Sat, Sep 19, 2009 at 1:23 PM, jc1001 <[hidden email]> wrote:

Matt,

I'm using the Tapestry Modular starter project at
http://appfuse.org/display/APF/AppFuse+QuickStart -

mvn archetype:create -DarchetypeGroupId=org.appfuse.archetypes
-DarchetypeArtifactId=appfuse-modular-tapestry
-DremoteRepositories=http://static.appfuse.org/releases
-DarchetypeVersion=2.0.2 -DgroupId=com.mycompany.app -DartifactId=myproject

You're using Tapestry 4 then. 

so this is AppFuse 2.x <?>.  I had a look at the source at
http://tapestry5-appfuse.googlecode.com/files/tapestry5-appfuse-sources-1.0.1.tgz
and see that it's using the T5 packages.

Are there any anticipated dates for a starter project using the T5 packages
or in the interim is manual rename / search replace of the packages /
project name  from the tapestry5-appfuse-sources-1.0.1.tgz archive the only
way to go?

I could give you dates, but I'd probably miss them. I was hoping to have AppFuse 2.1 done this month, but I haven't found the time to do it. It's tough being a single dad. ;-)
 

Are there any known showstoppers in the tapestry5-appfuse-sources-1.0.1.tgz?

Not that I know of - I'd try it out and see what you think.

Matt

Many thanks,
Jim.

mraible wrote:
>
> What version of AppFuse are you using? Tapestry 5 support is only
> available
> in trunk (not yet released) and it hasn't been fully polished yet.
>
> Most of the code for our implementation came from:
> http://code.google.com/p/tapestry5-appfuse/
>
> Matt
>
> On Fri, Sep 18, 2009 at 6:42 AM, jc1001 <[hidden email]> wrote:
>
>>
>> Hi,
>>
>> First post to this list, so please cut me some slack if it's in the wrong
>> location etc.  I'm trying to get AppFuse up and running with Tap 5.1.0.5
>> and
>> notice that a lot of the package imports refer to org.apache.tapestry.xxx
>> rather than org.apache.tapestry5.xxx - the package name must have changed
>> at
>> some point during tap dev - I'm currently doing a global search and
>> replace
>> - is there another approach / tap5 module that uses the latest package
>> names?
>>
>> A second, less immediate question I have is with the general AppFuse
>> approach to dealing with persistent entities in the system - the approach
>> appears to be to use services to perform operations upon persistence
>> implementation specific dao objects via interfaces, and model objects for
>> presentation purposes.  The Tap5 approach allows for example using
>> BeanModelEditor editor to get a CRUDable entity on screen quite quickly
>> and
>> the use of annotations to specify persistence, and also adds any entities
>> in
>> the entities package automagically into hibernate.  The AppFuse
>> separation
>> is very clean/structured and no doubt mandated by the use of Spring - to
>> cut
>> a long question short - are there any disadvantages to mixing the
>> approaches
>> within the same application?
>>
>> Thanks,
>> Jim.
>> --
>> View this message in context:
>> http://www.nabble.com/Tapestry5-and-Appfuse-tp25506606s2369p25506606.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]
>>
>>
>
>

--
View this message in context: http://www.nabble.com/Tapestry5-and-Appfuse-tp25506606s2369p25524642.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]