AppFuse 1.9

[Matt Raible-3]

Hello all,

The current plan for AppFuse 1.9 is to cram quite a bit of stuff into
a single release.  For example, the big "features" I'm planning on
implementing are dependency downloading and the ability to use AppFuse
as a single appfuse.jar.

However, there's quite a bit of stuff on the roadmap:

http://issues.appfuse.org/browse/APF?report=com.atlassian.jira.plugin.system.project:roadmap-panel

It might make more sense to do something like this:

1. Quit implementing new features and concentrate on fixing bugs in 1.9.
2. Release 1.9.
3. Start 1.9.1 with dependency downloading.
4. Release 1.9.1.
5. Start 1.9.2 with easily-upgradable AppFuse version (appfuse.jar).

1.9.1 will likely include upgrades for WebWork (2.2) and Tapestry (4.0).

A couple of other things I'm considering:

1. Change build.xml to be simpler like Equinox - removing pmd,
checkstyle, etc. Part of the removal would entail documenting how to
add them back in.

2. Change AppFuse to be modular, similar to how Maven suggests you
build projects:

pom.xml
build.xml
    - modules
        - data (services and daos)
        - web

Thoughts?

Matt

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

[Smiley, Stuart A.]

It sounds like a very good plan with the exception of removing pmd and
checkstyle from build.xml.  I have found these to be very useful and they
are relatively simple targets. You might say a good IDE does everything that
pmd does interactively, but on a project with multiple developers, it helps
to make sure everyone is paying attention to details.  It would be easy to
overlook them if one had to add them back in.

Stuart

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]
]On Behalf Of Matt Raible
Sent: Tuesday, December 20, 2005 12:41 PM
To: AppFuse
Subject: [appfuse-user] AppFuse 1.9


Hello all,

The current plan for AppFuse 1.9 is to cram quite a bit of stuff into
a single release.  For example, the big "features" I'm planning on
implementing are dependency downloading and the ability to use AppFuse
as a single appfuse.jar.

However, there's quite a bit of stuff on the roadmap:

http://issues.appfuse.org/browse/APF?report=com.atlassian.jira.plugin.system
.project:roadmap-panel

It might make more sense to do something like this:

1. Quit implementing new features and concentrate on fixing bugs in 1.9.
2. Release 1.9.
3. Start 1.9.1 with dependency downloading.
4. Release 1.9.1.
5. Start 1.9.2 with easily-upgradable AppFuse version (appfuse.jar).

1.9.1 will likely include upgrades for WebWork (2.2) and Tapestry (4.0).

A couple of other things I'm considering:

1. Change build.xml to be simpler like Equinox - removing pmd,
checkstyle, etc. Part of the removal would entail documenting how to
add them back in.

2. Change AppFuse to be modular, similar to how Maven suggests you
build projects:

pom.xml
build.xml
    - modules
        - data (services and daos)
        - web

Thoughts?

Matt

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

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

[melinate]

By just looking at the version numbers, I would expect that 1.9.1 and
1.9.2 would be bug fixed and minor improvements to version 1.9.  And
they would all be structurally identical.  But the goals you outline
sound like much more significant differences.  It would make more sense
to me to have 1.9, 1.10 and 1.11, especially since each may have their
own set of bug fixes [e.g 1.9.1, 1.10.1 and 1.11.1].  I know you are
thinking of AppFuse 2.0 as the Java 1.5 version, but these new
structural changes sound like they might be as significant of a change
as moving to Java 1.5. So maybe the versioning could be something like this:

 * Fix remaining bugs in 1.9
 * Release 1.9
 * Start 2.0M1 with dependancy downloading
 * Release 2.0M1
 * Start 2.0M2 with easily upgradeable version
 * Release 2.0M2
 * Freeze feature enhancements and fix bugs
 * Release 2.0

My 2 cents,
Nathan

Matt Raible wrote:

>Hello all,
>
>The current plan for AppFuse 1.9 is to cram quite a bit of stuff into
>a single release.  For example, the big "features" I'm planning on
>implementing are dependency downloading and the ability to use AppFuse
>as a single appfuse.jar.
>
>However, there's quite a bit of stuff on the roadmap:
>
>http://issues.appfuse.org/browse/APF?report=com.atlassian.jira.plugin.system.project:roadmap-panel
>
>It might make more sense to do something like this:
>
>1. Quit implementing new features and concentrate on fixing bugs in 1.9.
>2. Release 1.9.
>3. Start 1.9.1 with dependency downloading.
>4. Release 1.9.1.
>5. Start 1.9.2 with easily-upgradable AppFuse version (appfuse.jar).
>
>1.9.1 will likely include upgrades for WebWork (2.2) and Tapestry (4.0).
>
>A couple of other things I'm considering:
>
>1. Change build.xml to be simpler like Equinox - removing pmd,
>checkstyle, etc. Part of the removal would entail documenting how to
>add them back in.
>
>2. Change AppFuse to be modular, similar to how Maven suggests you
>build projects:
>
>pom.xml
>build.xml
>    - modules
>        - data (services and daos)
>        - web
>
>Thoughts?
>
>Matt
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [hidden email]
>For additional commands, e-mail: [hidden email]
>
>  
>

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

[Matt Raible-3]

On 12/20/05, Nathan Anderson <[hidden email]> wrote:

> By just looking at the version numbers, I would expect that 1.9.1 and
> 1.9.2 would be bug fixed and minor improvements to version 1.9.  And
> they would all be structurally identical.  But the goals you outline
> sound like much more significant differences.  It would make more sense
> to me to have 1.9, 1.10 and 1.11, especially since each may have their
> own set of bug fixes [e.g 1.9.1, 1.10.1 and 1.11.1].  I know you are
> thinking of AppFuse 2.0 as the Java 1.5 version, but these new
> structural changes sound like they might be as significant of a change
> as moving to Java 1.5. So maybe the versioning could be something like this:
>
>  * Fix remaining bugs in 1.9
>  * Release 1.9
>  * Start 2.0M1 with dependancy downloading
>  * Release 2.0M1
>  * Start 2.0M2 with easily upgradeable version
>  * Release 2.0M2
>  * Freeze feature enhancements and fix bugs
>  * Release 2.0

This sounds like a good idea.  I think by doing the upgradeable
version - and the modularization, it'll make it easier to create an
appfuse-tiger.jar, like many other projects have been doing.  I think
it's important to keep backwards compatibility rather than making the
leap to JDK 5.  It's my experience that many are still using 1.4.2,
even if they'd rather be using 5.

Matt

>
> My 2 cents,
> Nathan
>
> Matt Raible wrote:
>
> >Hello all,
> >
> >The current plan for AppFuse 1.9 is to cram quite a bit of stuff into
> >a single release.  For example, the big "features" I'm planning on
> >implementing are dependency downloading and the ability to use AppFuse
> >as a single appfuse.jar.
> >
> >However, there's quite a bit of stuff on the roadmap:
> >
> >http://issues.appfuse.org/browse/APF?report=com.atlassian.jira.plugin.system.project:roadmap-panel
> >
> >It might make more sense to do something like this:
> >
> >1. Quit implementing new features and concentrate on fixing bugs in 1.9.
> >2. Release 1.9.
> >3. Start 1.9.1 with dependency downloading.
> >4. Release 1.9.1.
> >5. Start 1.9.2 with easily-upgradable AppFuse version (appfuse.jar).
> >
> >1.9.1 will likely include upgrades for WebWork (2.2) and Tapestry (4.0).
> >
> >A couple of other things I'm considering:
> >
> >1. Change build.xml to be simpler like Equinox - removing pmd,
> >checkstyle, etc. Part of the removal would entail documenting how to
> >add them back in.
> >
> >2. Change AppFuse to be modular, similar to how Maven suggests you
> >build projects:
> >
> >pom.xml
> >build.xml
> >    - modules
> >        - data (services and daos)
> >        - web
> >
> >Thoughts?
> >
> >Matt
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [hidden email]
> >For additional commands, e-mail: [hidden email]
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

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

[David Moran]

 I'm having trouble getting appfuse to work on resin 2.1.16. I have tried
the suggestions in the mail archives and the tutorial.   Could someone send
me thereconf files and web.xml for a working application.

Thank you


David Moran
Vigilant Management Systems
[hidden email]
919-604-3758 (cell)
919-577-0026  (work)


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

[Matt Raible-3]

What problems are you having?

On 12/20/05, David Moran <[hidden email]> wrote:

>  I'm having trouble getting appfuse to work on resin 2.1.16. I have tried
> the suggestions in the mail archives and the tutorial.   Could someone send
> me thereconf files and web.xml for a working application.
>
> Thank you
>
>
> David Moran
> Vigilant Management Systems
> [hidden email]
> 919-604-3758 (cell)
> 919-577-0026  (work)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

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

[koevet]

Hello,
I'm not sure how you are planning to stick everything in a big
appfuse.jar, but it sounds like a great idea.
Upgrading Appfuse version has been always a little complicated and it
would be great to have this process simplified. Personally, I would put
this requirement on top of the queue (along with the bug fixing for 1.9).
It would be also nice to facilitate Ajax integration (maybe with DWR). I
believe that it would broaden the users base of this project.
I don't understand 100%  what do you mean with:

> 2. Change AppFuse to be modular, similar to how Maven suggests you
> build projects:

The application is already modular. You mean change in the build process?

Luciano

Matt Raible wrote:

> Hello all,
>
> The current plan for AppFuse 1.9 is to cram quite a bit of stuff into
> a single release.  For example, the big "features" I'm planning on
> implementing are dependency downloading and the ability to use AppFuse
> as a single appfuse.jar.
>
> However, there's quite a bit of stuff on the roadmap:
>
> http://issues.appfuse.org/browse/APF?report=com.atlassian.jira.plugin.system.project:roadmap-panel
>
> It might make more sense to do something like this:
>
> 1. Quit implementing new features and concentrate on fixing bugs in 1.9.
> 2. Release 1.9.
> 3. Start 1.9.1 with dependency downloading.
> 4. Release 1.9.1.
> 5. Start 1.9.2 with easily-upgradable AppFuse version (appfuse.jar).
>
> 1.9.1 will likely include upgrades for WebWork (2.2) and Tapestry (4.0).
>
> A couple of other things I'm considering:
>
> 1. Change build.xml to be simpler like Equinox - removing pmd,
> checkstyle, etc. Part of the removal would entail documenting how to
> add them back in.
>
> 2. Change AppFuse to be modular, similar to how Maven suggests you
> build projects:
>
> pom.xml
> build.xml
>     - modules
>         - data (services and daos)
>         - web
>
> Thoughts?
>
> Matt
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
____________________________
Luciano Fiandesio
http://www.lucianofiandesio.com
IT Consultant
e: [hidden email]
gsm BE: ([phone]
gsm IT: ([phone]
gsm FI: ([phone]
____________________________

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

[Matt Raible-3]

On 12/20/05, Luciano Fiandesio <[hidden email]> wrote:
> Hello,
> I'm not sure how you are planning to stick everything in a big
> appfuse.jar, but it sounds like a great idea.
> Upgrading Appfuse version has been always a little complicated and it
> would be great to have this process simplified. Personally, I would put
> this requirement on top of the queue (along with the bug fixing for 1.9).

I agree, but the downloading dependencies is part of that.  An ideal
solution IMO is you have a pom.xml that specifies all your
dependencies (including appfuse) and an empty directory structure.  Of
course, some files will need to remain, such as images, css,
javascript and web.xml - but the rest we should be able to package
into a JAR.  Of course, the question is - does everything go in the
same JAR or are there separate JARs for each web framework?  If
everything is in the same JAR, it should be easy enough to change
org.appfuse.webapp.action to org.appfuse.webapp.struts, etc.

I *really* do want to work on this stuff, but I think it's important
to listen to the users and fix bugs too. ;-)

> It would be also nice to facilitate Ajax integration (maybe with DWR). I
> believe that it would broaden the users base of this project.

Ajax is already in CVS - DWR 1.0, Prototype 1.4 and Script.aculo.us
1.5 are all included.  Of course, it's up to you to figure out how to
use them. ;-)  I've been meaning to put together some simple howtos,
but haven't had the time.

> I don't understand 100%  what do you mean with:
>
> > 2. Change AppFuse to be modular, similar to how Maven suggests you
> > build projects:
>
> The application is already modular. You mean change in the build process?

It's mainly a structural change, as well as a possible change in the
build process. I've come to realize that the structure in CVS and the
structure that's distributed can be different.

So rather than

src
   - dao
   - service
   - web

It would become modules/src/data and modules/src/web.  I plan on
seeing what the IDEs are most comfortable with in order to make
everyone (command line and IDE users) happy.

Matt

>
> Luciano
>
> Matt Raible wrote:
> > Hello all,
> >
> > The current plan for AppFuse 1.9 is to cram quite a bit of stuff into
> > a single release.  For example, the big "features" I'm planning on
> > implementing are dependency downloading and the ability to use AppFuse
> > as a single appfuse.jar.
> >
> > However, there's quite a bit of stuff on the roadmap:
> >
> > http://issues.appfuse.org/browse/APF?report=com.atlassian.jira.plugin.system.project:roadmap-panel
> >
> > It might make more sense to do something like this:
> >
> > 1. Quit implementing new features and concentrate on fixing bugs in 1.9.
> > 2. Release 1.9.
> > 3. Start 1.9.1 with dependency downloading.
> > 4. Release 1.9.1.
> > 5. Start 1.9.2 with easily-upgradable AppFuse version (appfuse.jar).
> >
> > 1.9.1 will likely include upgrades for WebWork (2.2) and Tapestry (4.0).
> >
> > A couple of other things I'm considering:
> >
> > 1. Change build.xml to be simpler like Equinox - removing pmd,
> > checkstyle, etc. Part of the removal would entail documenting how to
> > add them back in.
> >
> > 2. Change AppFuse to be modular, similar to how Maven suggests you
> > build projects:
> >
> > pom.xml
> > build.xml
> >     - modules
> >         - data (services and daos)
> >         - web
> >
> > Thoughts?
> >
> > Matt
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
> --
> ____________________________
> Luciano Fiandesio
> http://www.lucianofiandesio.com
> IT Consultant
> e: [hidden email]
> gsm BE: ([phone]
> gsm IT: ([phone]
> gsm FI: ([phone]
> ____________________________
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

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

[David Moran]

It is not finding the property files and  the authentication is not working.



David Moran
Vigilant Management Systems
[hidden email]
919-604-3758 (cell)
919-577-0026  (work)

-----Original Message-----
From: Matt Raible [mailto:[hidden email]]
Sent: Tuesday, December 20, 2005 3:46 PM
To: [hidden email]
Subject: Re: [appfuse-user] Appfuse on Resin 2.1.16

What problems are you having?

On 12/20/05, David Moran <[hidden email]> wrote:
>  I'm having trouble getting appfuse to work on resin 2.1.16. I have tried
> the suggestions in the mail archives and the tutorial.   Could someone
send

> me thereconf files and web.xml for a working application.
>
> Thank you
>
>
> David Moran
> Vigilant Management Systems
> [hidden email]
> 919-604-3758 (cell)
> 919-577-0026  (work)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

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




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

[koevet]

Yes, I actually integrated DWR and an Appfuse-based application recently
and it went very well.
What I thought could be part of a next release is a Manager class
exposing some Ajax based services (e.g. the Lookup manager), but a Howto
should maybe do the trick.

Luciano

>>It would be also nice to facilitate Ajax integration (maybe with DWR). I
>>believe that it would broaden the users base of this project.
>
>
> Ajax is already in CVS - DWR 1.0, Prototype 1.4 and Script.aculo.us
> 1.5 are all included.  Of course, it's up to you to figure out how to
> use them. ;-)  I've been meaning to put together some simple howtos,
> but haven't had the time.


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

[felipenasc]

Are you planning on using Maven instead of ANT ?? (of course maven
could use ANT behind the scenes).
I like maven to do configuration management, generate documentation,
download dependencies, etc. When you said "like Maven", I was in doubt
if your going to build something like it, or use it.

AppFuse is GREAT!!!! Tks Matt...

Felipe

2005/12/21, Luciano Fiandesio <[hidden email]>:

> Yes, I actually integrated DWR and an Appfuse-based application recently
> and it went very well.
> What I thought could be part of a next release is a Manager class
> exposing some Ajax based services (e.g. the Lookup manager), but a Howto
> should maybe do the trick.
>
> Luciano
>
> >>It would be also nice to facilitate Ajax integration (maybe with DWR). I
> >>believe that it would broaden the users base of this project.
> >
> >
> > Ajax is already in CVS - DWR 1.0, Prototype 1.4 and Script.aculo.us
> > 1.5 are all included.  Of course, it's up to you to figure out how to
> > use them. ;-)  I've been meaning to put together some simple howtos,
> > but haven't had the time.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

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

[Matt Raible-3]

On 12/21/05, Felipe Nascimento <[hidden email]> wrote:
> Are you planning on using Maven instead of ANT ?? (of course maven
> could use ANT behind the scenes).

No.  I'm planning on using Maven 2's Ant Tasks.  I'd rather offer
choice than require everyong to learn a new build tool.  I have
co-workers that have been very intimate with Maven 2 and their
impression has not been that good.

> I like maven to do configuration management, generate documentation,
> download dependencies, etc. When you said "like Maven", I was in doubt
> if your going to build something like it, or use it.

I'll use parts of it, and ideas from it - and possibly allow Ant or
Maven 2.  We'll see - it's likely to be a tough integration,
especially because I'm aware that AppFuse should be very IDE-friendly.

>
> AppFuse is GREAT!!!! Tks Matt...

Glad you like it - thanks for using it!

Matt

>
> Felipe
>
> 2005/12/21, Luciano Fiandesio <[hidden email]>:
> > Yes, I actually integrated DWR and an Appfuse-based application recently
> > and it went very well.
> > What I thought could be part of a next release is a Manager class
> > exposing some Ajax based services (e.g. the Lookup manager), but a Howto
> > should maybe do the trick.
> >
> > Luciano
> >
> > >>It would be also nice to facilitate Ajax integration (maybe with DWR). I
> > >>believe that it would broaden the users base of this project.
> > >
> > >
> > > Ajax is already in CVS - DWR 1.0, Prototype 1.4 and Script.aculo.us
> > > 1.5 are all included.  Of course, it's up to you to figure out how to
> > > use them. ;-)  I've been meaning to put together some simple howtos,
> > > but haven't had the time.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

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

[Cesidio]

Matt Raible-3 wrote:

This sounds like a good idea.  I think by doing the upgradeable
version - and the modularization, it'll make it easier to create an
appfuse-tiger.jar, like many other projects have been doing.  I think
it's important to keep backwards compatibility rather than making the
leap to JDK 5.  It's my experience that many are still using 1.4.2,
even if they'd rather be using 5.

...

I agree, but the downloading dependencies is part of that.  An ideal
solution IMO is you have a pom.xml that specifies all your
dependencies (including appfuse) and an empty directory structure.

Matt

I don't understand one thing. Let's put the case I need a new relationship in the user object, like User Many-to-Many with Course(a new object that I create). Where do I modify the User object, in the appfuse.jar file? in that case, is it still easy to be upgradable?

[Matt Raible-3]

On 1/6/06, Cesidio (sent by Nabble.com) <[hidden email]> wrote:

>
>
> Matt Raible-3 wrote:
> This sounds like a good idea.  I think by doing the upgradeable
> version - and the modularization, it'll make it easier to create an
> appfuse-tiger.jar, like many other projects have been doing.  I think
> it's important to keep backwards compatibility rather than making the
> leap to JDK 5.  It's my experience that many are still using 1.4.2,
> even if they'd rather be using 5.
>
> Matt I don't understand one thing. Let's put the case I need a new
> relationship in the user object, like User Many-to-Many with Course(a new
> object that I create). Where do I modify the User object, in the appfuse.jar
> file? in that case, is it still easy to be upgradable?

You should be able to subclass org.appfuse.model.User and add this
relationship there.  It's likely there will still be a way to specify
the mapping files - so you could override
/org/appfuse/model/User.hbm.xml with /your/custom/one/User.hbm.xml.

Hopefully there's a way to be smart and automatically override
/org/appfuse/model/*.hbm.xml mappings if you have the same name
(excluding the package).

Matt

> ________________________________
>  View this message in context: Re: AppFuse 1.9
>  Sent from the AppFuse - User forum at Nabble.com.

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