RE: Getting ready for Struts 2.1.1

[Giovanni Azua]

hi dusty,

I am also trying to do the same i.e. get the AppFuse basic/module 2.0.2 to
work with Struts 2.1.2

I think your Date/Time converter resolution below is not correct. I ported
couple of apps from Struts 2.0.x to Struts 2.1.x and to port the Date/Time
conversion you need to NOT use the custom converter i.e. delete the
xwork-conversion.properties and delete all Date and Time conversion
implementations. Then make sure to change your actions to use Date type
property, the conversion will be handled transparently for you by Struts
2.1.x

I am not completely sure but I think the UI components implemented in
AppFuse will need rework i.e. extract the new freemarker templates from
Struts 2.1.x and re-apply the theme changes. Since Struts 2.1.x the ajax
theme was moved into the dojo plugin there might be other issues because of
this.

Is there any progress on upgrading to Struts 2.1.x? What's the svn URL
you're working on? Maybe we could join forces on this...

Please find porting Struts 2.0.x to 2.1.x troubleshooting notes here:
http://cwiki.apache.org/S2WIKI/troubleshooting-guide-migrating-from-struts-2
0x-to-21x.html

Best regards,
Giovanni


On Mar 22, 2008, at 10:27 PM, dusty wrote:
>
> The first item is a package change in xwork for TypeConversionException.  
>
>It was //import com.opensymphony.xwork2.util.TypeConversionException;
>but now its
>import com.opensymphony.xwork2.conversion.TypeConversionException;
> RE: Getting ready for Struts 2.1.1



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

[Frans Thamura-3]

On Sat, May 24, 2008 at 6:17 PM, Giovanni Azua <[hidden email]> wrote:

hi dusty,

I am also trying to do the same i.e. get the AppFuse basic/module 2.0.2 to
work with Struts 2.1.2

is Struts 2.1.2 stable enough to be used?

F

[Giovanni Azua]

Some javascript/style in this post has been disabled (why?)

http://www.nabble.com/-RESULT--Struts-2.1.2-test-build-p17454192.html

 

---

From: Frans Thamura [mailto:[hidden email]]
Sent: Sunday, May 25, 2008 2:47 AM
To: [hidden email]
Subject: Re: [appfuse-dev] RE: Getting ready for Struts 2.1.1

 

 

On Sat, May 24, 2008 at 6:17 PM, Giovanni Azua <[hidden email]> wrote:

hi dusty,

I am also trying to do the same i.e. get the AppFuse basic/module 2.0.2 to
work with Struts 2.1.2

is Struts 2.1.2 stable enough to be used?

F

[dusty]

After thinking/coding/reading for a while I think the more interesting  
task is:  Retool Appfuse to be one or more Struts2 plugins based on  
various higher level app patterns.  (Appfuse Facebook, Appfuse  
Employee DB, Appfuse Blog, Appfuse Basic LDAP, Appfuse Basic Crowd)

This all comes from the fact, that I have been wanting to refactor the  
Appfuse web layer for Struts.  One of the interesting aspects of  
Appfuse is that it works pretty much the same across all it's web  
frameworks.  It does so with some lowest common denominator  
abstractions that can be ported and look and work the same across  
frameworks.  I have picked my tool(s): Struts2 and Ruby On Rails when  
I want to pretend I am young again.   I know Spring MVC, JSF, etc but  
I have no desire to build significant apps on those platforms.  Its  
not because they suck and Struts2 rules, it is because I know Struts2  
the best, I am most efficient there and it provides everything I need  
to build great webapps (Lets not devolve to a framework debate).  So,  
I would rather have a more Struts2-specific web stack, that really  
leverages conventions born and raised there.  The nice thing about the  
Struts2 web stack is that it is complemented nicely by Appfuse's data/
service layer, since unlike Grails or Rails, Struts2 has no data or  
service layer.

So in my mind, its time to fork Appfuse for the Struts2 followers and  
try to implement the following:
* Refactored Data/Service layer
    ** Favor GenericDao + basic search functions, Add generic  
DataDictionary for managing lists of values or value/key pairs,  
Manager impl only where necessary for transactions across multiple  
DAOs, no XFire web service included, favor Hibernate
* Refactor User/Role actions to be RESTful style.  Much easier to  
follow a create/update/show/index.... set of actions/views for a User  
resource and another for Profile resource than a single method that  
tries to figure out where it was called from and what it is supposed  
to do...Let the URI and Spring Security handle that
* Basic CRUD and Parent/Child action/view patterns -- "scaffolding"
* Update the Struts2 action testing harness to use a better  
implementation that can do things like execute the interceptor stack  
or just call the method directly.
* Remove a lot of the extra weight and let users add stuff through  
tutorials or generators -- Clickstream, Reload, Cache Flush
* Create a LDAP version with modified User management actions
* Create a Crowd version with modified User management actions
* Create a "generator" so I can do appfuse:gen controller xxx and get  
xxxController (Struts2 action), show(), edit(), index(), etc methods  
and the stub view files (index.jsp, etc) in /WEB-INF/pages/xxx/.

The end result is a Struts2 plugin that provides basic Hibernate/Model  
services as well as basic security/user management infrastructure for  
Struts2-based applications.  If you were at JavaOne you would have  
seen that there is a HUGE interest in Struts2 and this would help a  
lot.  But Struts2 has its warts:  The basic "getting-started-how-to"  
space there is a little lacking.  Also, there is a lot of code churn  
and debate surrounding the REST plugin and Convention vs. Codebehind  
vs. Smart-URLs vs. Whatever Else Someone Wrote configuration  
plugins.    I like the REST plugin but its missing some important  
parts and it depends on the Codebehind plugin which is not really  
favored in the Struts2 community.  What I think all this means is that  
we do what I have done recently...design and implement your Struts2  
app RESTfully, follow conventions for configuration and when the REST  
+ Config plugin dust settles, refactor as necessary.  For example,  
UserController.index() is supposed to produce a JSON result for a  
JQuery table.  Without the plugin our URL would be http://appufse.org/admin/users/index.html 
  and with the plugin it would be {GET}http://appfuse.org/admin/ 
users.  Also, instead of configuring a JSON result in your XML for the  
action you could request a JSON implementation of the action's model,  
in this case a list of users.




On May 24, 2008, at 4:17 AM, Giovanni Azua wrote:

> hi dusty,
>
> I am also trying to do the same i.e. get the AppFuse basic/module  
> 2.0.2 to
> work with Struts 2.1.2
>
> I think your Date/Time converter resolution below is not correct. I  
> ported
> couple of apps from Struts 2.0.x to Struts 2.1.x and to port the  
> Date/Time
> conversion you need to NOT use the custom converter i.e. delete the
> xwork-conversion.properties and delete all Date and Time conversion
> implementations. Then make sure to change your actions to use Date  
> type
> property, the conversion will be handled transparently for you by  
> Struts
> 2.1.x
>
> I am not completely sure but I think the UI components implemented in
> AppFuse will need rework i.e. extract the new freemarker templates  
> from
> Struts 2.1.x and re-apply the theme changes. Since Struts 2.1.x the  
> ajax
> theme was moved into the dojo plugin there might be other issues  
> because of
> this.
>
> Is there any progress on upgrading to Struts 2.1.x? What's the svn URL
> you're working on? Maybe we could join forces on this...
>
> Please find porting Struts 2.0.x to 2.1.x troubleshooting notes here:
> http://cwiki.apache.org/S2WIKI/troubleshooting-guide-migrating-from-struts-2
> 0x-to-21x.html
>
> Best regards,
> Giovanni
>
>
> On Mar 22, 2008, at 10:27 PM, dusty wrote:
>>
>> The first item is a package change in xwork for  
>> TypeConversionException.
>>
>> It was //import com.opensymphony.xwork2.util.TypeConversionException;
>> but now its
>> import com.opensymphony.xwork2.conversion.TypeConversionException;
>> RE: Getting ready for Struts 2.1.1
>
>
>
> ---------------------------------------------------------------------
> 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]

I'd like to support this effort however I can. If it makes things
easier, I can create a branch and add committers to work on it.

Matt

On Sun, May 25, 2008 at 12:56 PM, Dustin Pearce <[hidden email]> wrote:

> After thinking/coding/reading for a while I think the more interesting task
> is:  Retool Appfuse to be one or more Struts2 plugins based on various
> higher level app patterns.  (Appfuse Facebook, Appfuse Employee DB, Appfuse
> Blog, Appfuse Basic LDAP, Appfuse Basic Crowd)
>
> This all comes from the fact, that I have been wanting to refactor the
> Appfuse web layer for Struts.  One of the interesting aspects of Appfuse is
> that it works pretty much the same across all it's web frameworks.  It does
> so with some lowest common denominator abstractions that can be ported and
> look and work the same across frameworks.  I have picked my tool(s): Struts2
> and Ruby On Rails when I want to pretend I am young again.   I know Spring
> MVC, JSF, etc but I have no desire to build significant apps on those
> platforms.  Its not because they suck and Struts2 rules, it is because I
> know Struts2 the best, I am most efficient there and it provides everything
> I need to build great webapps (Lets not devolve to a framework debate).  So,
> I would rather have a more Struts2-specific web stack, that really leverages
> conventions born and raised there.  The nice thing about the Struts2 web
> stack is that it is complemented nicely by Appfuse's data/service layer,
> since unlike Grails or Rails, Struts2 has no data or service layer.
>
> So in my mind, its time to fork Appfuse for the Struts2 followers and try to
> implement the following:
> * Refactored Data/Service layer
>   ** Favor GenericDao + basic search functions, Add generic DataDictionary
> for managing lists of values or value/key pairs, Manager impl only where
> necessary for transactions across multiple DAOs, no XFire web service
> included, favor Hibernate
> * Refactor User/Role actions to be RESTful style.  Much easier to follow a
> create/update/show/index.... set of actions/views for a User resource and
> another for Profile resource than a single method that tries to figure out
> where it was called from and what it is supposed to do...Let the URI and
> Spring Security handle that
> * Basic CRUD and Parent/Child action/view patterns -- "scaffolding"
> * Update the Struts2 action testing harness to use a better implementation
> that can do things like execute the interceptor stack or just call the
> method directly.
> * Remove a lot of the extra weight and let users add stuff through tutorials
> or generators -- Clickstream, Reload, Cache Flush
> * Create a LDAP version with modified User management actions
> * Create a Crowd version with modified User management actions
> * Create a "generator" so I can do appfuse:gen controller xxx and get
> xxxController (Struts2 action), show(), edit(), index(), etc methods and the
> stub view files (index.jsp, etc) in /WEB-INF/pages/xxx/.
>
> The end result is a Struts2 plugin that provides basic Hibernate/Model
> services as well as basic security/user management infrastructure for
> Struts2-based applications.  If you were at JavaOne you would have seen that
> there is a HUGE interest in Struts2 and this would help a lot.  But Struts2
> has its warts:  The basic "getting-started-how-to" space there is a little
> lacking.  Also, there is a lot of code churn and debate surrounding the REST
> plugin and Convention vs. Codebehind vs. Smart-URLs vs. Whatever Else
> Someone Wrote configuration plugins.    I like the REST plugin but its
> missing some important parts and it depends on the Codebehind plugin which
> is not really favored in the Struts2 community.  What I think all this means
> is that we do what I have done recently...design and implement your Struts2
> app RESTfully, follow conventions for configuration and when the REST +
> Config plugin dust settles, refactor as necessary.  For example,
> UserController.index() is supposed to produce a JSON result for a JQuery
> table.  Without the plugin our URL would be
> http://appufse.org/admin/users/index.html and with the plugin it would be
> {GET}http://appfuse.org/admin/users.  Also, instead of configuring a JSON
> result in your XML for the action you could request a JSON implementation of
> the action's model, in this case a list of users.
>
>
>
>
> On May 24, 2008, at 4:17 AM, Giovanni Azua wrote:
>
>> hi dusty,
>>
>> I am also trying to do the same i.e. get the AppFuse basic/module 2.0.2 to
>> work with Struts 2.1.2
>>
>> I think your Date/Time converter resolution below is not correct. I ported
>> couple of apps from Struts 2.0.x to Struts 2.1.x and to port the Date/Time
>> conversion you need to NOT use the custom converter i.e. delete the
>> xwork-conversion.properties and delete all Date and Time conversion
>> implementations. Then make sure to change your actions to use Date type
>> property, the conversion will be handled transparently for you by Struts
>> 2.1.x
>>
>> I am not completely sure but I think the UI components implemented in
>> AppFuse will need rework i.e. extract the new freemarker templates from
>> Struts 2.1.x and re-apply the theme changes. Since Struts 2.1.x the ajax
>> theme was moved into the dojo plugin there might be other issues because
>> of
>> this.
>>
>> Is there any progress on upgrading to Struts 2.1.x? What's the svn URL
>> you're working on? Maybe we could join forces on this...
>>
>> Please find porting Struts 2.0.x to 2.1.x troubleshooting notes here:
>>
>> http://cwiki.apache.org/S2WIKI/troubleshooting-guide-migrating-from-struts-2
>> 0x-to-21x.html
>>
>> Best regards,
>> Giovanni
>>
>>
>> On Mar 22, 2008, at 10:27 PM, dusty wrote:
>>>
>>> The first item is a package change in xwork for TypeConversionException.
>>>
>>> It was //import com.opensymphony.xwork2.util.TypeConversionException;
>>> but now its
>>> import com.opensymphony.xwork2.conversion.TypeConversionException;
>>> RE: Getting ready for Struts 2.1.1
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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]
>
>

--
http://raibledesigns.com

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

[dusty]

I was afraid you would say that....You mean you don't already have it  
done?   I have a Struts2 Appfuse app field stripped down to just the  
bare essentials.   I will take a crack at getting the foundation in  
place.  Then we can get it on a branch.

-D

On May 27, 2008, at 8:55 AM, Matt Raible wrote:

> I'd like to support this effort however I can. If it makes things
> easier, I can create a branch and add committers to work on it.
>
> Matt
>
> On Sun, May 25, 2008 at 12:56 PM, Dustin Pearce <[hidden email]
> > wrote:
>> After thinking/coding/reading for a while I think the more  
>> interesting task
>> is:  Retool Appfuse to be one or more Struts2 plugins based on  
>> various
>> higher level app patterns.  (Appfuse Facebook, Appfuse Employee DB,  
>> Appfuse
>> Blog, Appfuse Basic LDAP, Appfuse Basic Crowd)
>>
>> This all comes from the fact, that I have been wanting to refactor  
>> the
>> Appfuse web layer for Struts.  One of the interesting aspects of  
>> Appfuse is
>> that it works pretty much the same across all it's web frameworks.  
>> It does
>> so with some lowest common denominator abstractions that can be  
>> ported and
>> look and work the same across frameworks.  I have picked my  
>> tool(s): Struts2
>> and Ruby On Rails when I want to pretend I am young again.   I know  
>> Spring
>> MVC, JSF, etc but I have no desire to build significant apps on those
>> platforms.  Its not because they suck and Struts2 rules, it is  
>> because I
>> know Struts2 the best, I am most efficient there and it provides  
>> everything
>> I need to build great webapps (Lets not devolve to a framework  
>> debate).  So,
>> I would rather have a more Struts2-specific web stack, that really  
>> leverages
>> conventions born and raised there.  The nice thing about the  
>> Struts2 web
>> stack is that it is complemented nicely by Appfuse's data/service  
>> layer,
>> since unlike Grails or Rails, Struts2 has no data or service layer.
>>
>> So in my mind, its time to fork Appfuse for the Struts2 followers  
>> and try to
>> implement the following:
>> * Refactored Data/Service layer
>>  ** Favor GenericDao + basic search functions, Add generic  
>> DataDictionary
>> for managing lists of values or value/key pairs, Manager impl only  
>> where
>> necessary for transactions across multiple DAOs, no XFire web service
>> included, favor Hibernate
>> * Refactor User/Role actions to be RESTful style.  Much easier to  
>> follow a
>> create/update/show/index.... set of actions/views for a User  
>> resource and
>> another for Profile resource than a single method that tries to  
>> figure out
>> where it was called from and what it is supposed to do...Let the  
>> URI and
>> Spring Security handle that
>> * Basic CRUD and Parent/Child action/view patterns -- "scaffolding"
>> * Update the Struts2 action testing harness to use a better  
>> implementation
>> that can do things like execute the interceptor stack or just call  
>> the
>> method directly.
>> * Remove a lot of the extra weight and let users add stuff through  
>> tutorials
>> or generators -- Clickstream, Reload, Cache Flush
>> * Create a LDAP version with modified User management actions
>> * Create a Crowd version with modified User management actions
>> * Create a "generator" so I can do appfuse:gen controller xxx and get
>> xxxController (Struts2 action), show(), edit(), index(), etc  
>> methods and the
>> stub view files (index.jsp, etc) in /WEB-INF/pages/xxx/.
>>
>> The end result is a Struts2 plugin that provides basic Hibernate/
>> Model
>> services as well as basic security/user management infrastructure for
>> Struts2-based applications.  If you were at JavaOne you would have  
>> seen that
>> there is a HUGE interest in Struts2 and this would help a lot.  But  
>> Struts2
>> has its warts:  The basic "getting-started-how-to" space there is a  
>> little
>> lacking.  Also, there is a lot of code churn and debate surrounding  
>> the REST
>> plugin and Convention vs. Codebehind vs. Smart-URLs vs. Whatever Else
>> Someone Wrote configuration plugins.    I like the REST plugin but  
>> its
>> missing some important parts and it depends on the Codebehind  
>> plugin which
>> is not really favored in the Struts2 community.  What I think all  
>> this means
>> is that we do what I have done recently...design and implement your  
>> Struts2
>> app RESTfully, follow conventions for configuration and when the  
>> REST +
>> Config plugin dust settles, refactor as necessary.  For example,
>> UserController.index() is supposed to produce a JSON result for a  
>> JQuery
>> table.  Without the plugin our URL would be
>> http://appufse.org/admin/users/index.html and with the plugin it  
>> would be
>> {GET}http://appfuse.org/admin/users.  Also, instead of configuring  
>> a JSON
>> result in your XML for the action you could request a JSON  
>> implementation of
>> the action's model, in this case a list of users.
>>
>>
>>
>>
>> On May 24, 2008, at 4:17 AM, Giovanni Azua wrote:
>>
>>> hi dusty,
>>>
>>> I am also trying to do the same i.e. get the AppFuse basic/module  
>>> 2.0.2 to
>>> work with Struts 2.1.2
>>>
>>> I think your Date/Time converter resolution below is not correct.  
>>> I ported
>>> couple of apps from Struts 2.0.x to Struts 2.1.x and to port the  
>>> Date/Time
>>> conversion you need to NOT use the custom converter i.e. delete the
>>> xwork-conversion.properties and delete all Date and Time conversion
>>> implementations. Then make sure to change your actions to use Date  
>>> type
>>> property, the conversion will be handled transparently for you by  
>>> Struts
>>> 2.1.x
>>>
>>> I am not completely sure but I think the UI components implemented  
>>> in
>>> AppFuse will need rework i.e. extract the new freemarker templates  
>>> from
>>> Struts 2.1.x and re-apply the theme changes. Since Struts 2.1.x  
>>> the ajax
>>> theme was moved into the dojo plugin there might be other issues  
>>> because
>>> of
>>> this.
>>>
>>> Is there any progress on upgrading to Struts 2.1.x? What's the svn  
>>> URL
>>> you're working on? Maybe we could join forces on this...
>>>
>>> Please find porting Struts 2.0.x to 2.1.x troubleshooting notes  
>>> here:
>>>
>>> http://cwiki.apache.org/S2WIKI/troubleshooting-guide-migrating-from-struts-2
>>> 0x-to-21x.html
>>>
>>> Best regards,
>>> Giovanni
>>>
>>>
>>> On Mar 22, 2008, at 10:27 PM, dusty wrote:
>>>>
>>>> The first item is a package change in xwork for  
>>>> TypeConversionException.
>>>>
>>>> It was //import  
>>>> com.opensymphony.xwork2.util.TypeConversionException;
>>>> but now its
>>>> import com.opensymphony.xwork2.conversion.TypeConversionException;
>>>> RE: Getting ready for Struts 2.1.1
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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]
>>
>>
>
>
>
> --
> http://raibledesigns.com
>
> ---------------------------------------------------------------------
> 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]

[Musachy Barroso]

I am not an Appfuse user myself (or Struts 2 for that matter), but this sounds really cool, I would definitely help out with such an effort.

[dusty]

Thanks Musachy!  I have been a little sidetracked.  Its summer time  
and I am on the board of my kids swim team and there is way more drama  
than I need right now.  ;-)  I think we can house this under the  
Appfuse roof since its really a branch of that code base.  If we can  
get some wiki space I can start laying some things out so people can  
just take chunks and implement.

Matt,  Do you have a particular starting page you want us to use?  Or  
should we just hang a page and then create children pages as necessary  
from there?

-D


On Jun 3, 2008, at 1:00 PM, Musachy Barroso wrote:

>
> I am not an Appfuse user myself (or Struts 2 for that matter), but  
> this
> sounds really cool, I would definitely help out with such an effort.
> --
> View this message in context: http://www.nabble.com/RE%3A-Getting-ready-for-Struts-2.1.1-tp17446803s2369p17632203.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]
>

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

[Matt Raible-3]

On Tue, Jun 3, 2008 at 3:11 PM, Dustin Pearce <[hidden email]> wrote:
> Thanks Musachy!  I have been a little sidetracked.  Its summer time and I am
> on the board of my kids swim team and there is way more drama than I need
> right now.  ;-)  I think we can house this under the Appfuse roof since its
> really a branch of that code base.  If we can get some wiki space I can
> start laying some things out so people can just take chunks and implement.
>
> Matt,  Do you have a particular starting page you want us to use?  Or should
> we just hang a page and then create children pages as necessary from there?

I could create a new space do to stuff. How about ASP for AppFuse
Struts Plugin? Another thing I was thinking about is going ahead and
calling it AppFuse 3, with the main objective being moving AppFuse
features back into the web frameworks. I'd love to something like
AppFuse supported by all the major players.

Either way, I'd be happy to create a new space for you - just let me
know the name and key.

Matt

>
> -D
>
>
> On Jun 3, 2008, at 1:00 PM, Musachy Barroso wrote:
>
>>
>> I am not an Appfuse user myself (or Struts 2 for that matter), but this
>> sounds really cool, I would definitely help out with such an effort.
>> --
>> View this message in context:
>> http://www.nabble.com/RE%3A-Getting-ready-for-Struts-2.1.1-tp17446803s2369p17632203.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]
>>
>
>
>
> ---------------------------------------------------------------------
> 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]

[hyuan]

Some javascript/style in this post has been disabled (why?)

Hi Matt,
 
You might be interested in using this strategy, described in the following link, to manage the implementation of new features in SVN. Maybe it will be easier for you to have more people get involved.
http://www.infoq.com/articles/agile-version-control
 
Anthony

> Date: Tue, 3 Jun 2008 15:56:19 -0600
> From: [hidden email]
> To: [hidden email]
> Subject: Re: [appfuse-dev] Getting ready for Struts 2.1.1
>
> On Tue, Jun 3, 2008 at 3:11 PM, Dustin Pearce <[hidden email]> wrote:
> > Thanks Musachy! I have been a little sidetracked. Its summer time and I am
> > on the board of my kids swim team and there is way more drama than I need
> > right now. ;-) I think we can house this under the Appfuse roof since its
> > really a branch of that code base. If we can get some wiki space I can
> > start laying some things out so people can just take chunks and implement.
> >
> > Matt, Do you have a particular starting page you want us to use? Or should
> > we just hang a page and then create children pages as necessary from there?
>
> I could create a new space do to stuff. How about ASP for AppFuse
> Struts Plugin? Another thing I was thinking about is going ahead and
> calling it AppFuse 3, with the main objective being moving AppFuse
> features back into the web frameworks. I'd love to something like
> AppFuse supported by all the major players.
>
> Either way, I'd be happy to create a new space for you - just let me
> know the name and key.
>
> Matt
>
> >
> > -D
> >
> >
> > On Jun 3, 2008, at 1:00 PM, Musachy Barroso wrote:
> >
> >>
> >> I am not an Appfuse user myself (or Struts 2 for that matter), but this
> >> sounds really cool, I would definitely help out with such an effort.
> >> --
> >> View this message in context:
> >> http://www.nabble.com/RE%3A-Getting-ready-for-Struts-2.1.1-tp17446803s2369p17632203.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]
> >>
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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]
>

---

Windows Live Writer，支持离线撰写博客内容，随时随地想写就写。 立即使用！

[David Whitehurst]

Guys:

I am offering my hands for the LDAP and Crowd piece of this.  I am
doing a CAS implementation and SSO and security have always been my
interest.

If I understand the previous threads here, AppFuse would be an
Identity Management application that just worked with Crowd? (CAS) Or,
does Crowd do have the admin for the user management already?  I
haven't looked at it yet.

David

On 6/3/08, yuanhang <[hidden email]> wrote:

> Hi Matt,
>
> You might be interested in using this strategy, described in the following
> link, to manage the implementation of new features in SVN. Maybe it will be
> easier for you to have more people get involved.
> http://www.infoq.com/articles/agile-version-control
>
> Anthony
>
> > Date: Tue, 3 Jun 2008 15:56:19 -0600
> > From: [hidden email]
> > To: [hidden email]
> > Subject: Re: [appfuse-dev] Getting ready for Struts 2.1.1
>
> >
> > On Tue, Jun 3, 2008 at 3:11 PM, Dustin Pearce <[hidden email]>
> wrote:
> > > Thanks Musachy! I have been a little sidetracked. Its summer time and I
> am
> > > on the board of my kids swim team and there is way more drama than I
> need
> > > right now. ;-) I think we can house this under the Appfuse roof since
> its
> > > really a branch of that code base. If we can get some wiki space I can
> > > start laying some things out so people can just take chunks and
> implement.
> > >
> > > Matt, Do you have a particular starting page you want us to use? Or
> should
> > > we just hang a page and then create children pages as necessary from
> there?
> >
> > I could create a new space do to stuff. How about ASP for AppFuse
> > Struts Plugin? Another thing I was thinking about is going ahead and
> > calling it AppFuse 3, with the main objective being moving AppFuse
> > features back into the web frameworks. I'd love to something like
> > AppFuse supported by all the major players.
> >
> > Either way, I'd be happy to create a new space for you - just let me
> > know the name and key.
> >
> > Matt
> >
> > >
> > > -D
> > >
> > >
> > > On Jun 3, 2008, at 1:00 PM, Musachy Barroso wrote:
> > >
> > >>
> > >> I am not an Appfuse user myself (or Struts 2 for that matter), but this
> > >> sounds really cool, I would definitely help out with such an effort.
> > >> --
> > >> View this message in context:
> > >>
> http://www.nabble.com/RE%3A-Getting-ready-for-Struts-2.1.1-tp17446803s2369p17632203.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]
> > >>
> > >
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > 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]
> >
>
>
> ________________________________
> Windows Live Writer，支持离线撰写博客内容，随时随地想写就写。 立即使用！

[Matt Raible-3]

Crowd has user management built in. Here's a tutorial on how to
integrate AppFuse with Crowd:

http://raibledesigns.com/rd/entry/integrate_appfuse_with_crowd_in

Matt

On Wed, Jun 4, 2008 at 6:16 AM, David Whitehurst <[hidden email]> wrote:

> Guys:
>
> I am offering my hands for the LDAP and Crowd piece of this.  I am
> doing a CAS implementation and SSO and security have always been my
> interest.
>
> If I understand the previous threads here, AppFuse would be an
> Identity Management application that just worked with Crowd? (CAS) Or,
> does Crowd do have the admin for the user management already?  I
> haven't looked at it yet.
>
> David
>
> On 6/3/08, yuanhang <[hidden email]> wrote:
>> Hi Matt,
>>
>> You might be interested in using this strategy, described in the following
>> link, to manage the implementation of new features in SVN. Maybe it will be
>> easier for you to have more people get involved.
>> http://www.infoq.com/articles/agile-version-control
>>
>> Anthony
>>
>> > Date: Tue, 3 Jun 2008 15:56:19 -0600
>> > From: [hidden email]
>> > To: [hidden email]
>> > Subject: Re: [appfuse-dev] Getting ready for Struts 2.1.1
>>
>> >
>> > On Tue, Jun 3, 2008 at 3:11 PM, Dustin Pearce <[hidden email]>
>> wrote:
>> > > Thanks Musachy! I have been a little sidetracked. Its summer time and I
>> am
>> > > on the board of my kids swim team and there is way more drama than I
>> need
>> > > right now. ;-) I think we can house this under the Appfuse roof since
>> its
>> > > really a branch of that code base. If we can get some wiki space I can
>> > > start laying some things out so people can just take chunks and
>> implement.
>> > >
>> > > Matt, Do you have a particular starting page you want us to use? Or
>> should
>> > > we just hang a page and then create children pages as necessary from
>> there?
>> >
>> > I could create a new space do to stuff. How about ASP for AppFuse
>> > Struts Plugin? Another thing I was thinking about is going ahead and
>> > calling it AppFuse 3, with the main objective being moving AppFuse
>> > features back into the web frameworks. I'd love to something like
>> > AppFuse supported by all the major players.
>> >
>> > Either way, I'd be happy to create a new space for you - just let me
>> > know the name and key.
>> >
>> > Matt
>> >
>> > >
>> > > -D
>> > >
>> > >
>> > > On Jun 3, 2008, at 1:00 PM, Musachy Barroso wrote:
>> > >
>> > >>
>> > >> I am not an Appfuse user myself (or Struts 2 for that matter), but this
>> > >> sounds really cool, I would definitely help out with such an effort.
>> > >> --
>> > >> View this message in context:
>> > >>
>> http://www.nabble.com/RE%3A-Getting-ready-for-Struts-2.1.1-tp17446803s2369p17632203.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]
>> > >>
>> > >
>> > >
>> > >
>> > >
>> ---------------------------------------------------------------------
>> > > 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]
>> >
>>
>>
>> ________________________________
>> Windows Live Writer，支持离线撰写博客内容，随时随地想写就写。 立即使用！
>

--
http://raibledesigns.com

[dusty]

If only Crowd worked with Struts2 the way the tutorial described.  If  
you want to use Crowd with Appfuse you are going to run into a few  
problems, depending on your setup.

If you are Struts2 and Pre-Spring Security then you only have the  
problem of applicationContext-CrowdClient.xml in the crowd jar  
referencing an old xwork library and breaking things.  You can create  
a copy of this Spring config file in your local classpath with the  
reference to the interceptor (you don't need it) or you can rebuild  
Crowd after you download the source once you have edited  
ApplicationContext-CrowdClient.xml.  The second option is rather  
drastic and I am sure that Atlassian is going to have that worked out  
in a dot release soon.

Secondly, if you are using Spring Security 2 then you will have to  
download and rebuild the Crowd source because as of 1.4 it still  
references the Acegi libraries.

Crowd is a GREAT user management system, and with it I have no local  
Appfuse App user admin section.  When you are using pure LDAP or the  
local database then you will need a local User Management system.  It  
depends on your AuthenticationProvider.  There are three basic  
modes...Local (current appfuse), delegated authentication (ldap), full  
delegation (crowd).  In all three modes we want our users and our own  
code to reference users through the Spring Security context.  This  
makes it much more flexible and portable.

I am excited about all the interest!

-D

On Jun 4, 2008, at 3:43 PM, Matt Raible wrote:

> Crowd has user management built in. Here's a tutorial on how to
> integrate AppFuse with Crowd:
>
> http://raibledesigns.com/rd/entry/integrate_appfuse_with_crowd_in
>
> Matt
>
> On Wed, Jun 4, 2008 at 6:16 AM, David Whitehurst <[hidden email]
> > wrote:
>> Guys:
>>
>> I am offering my hands for the LDAP and Crowd piece of this.  I am
>> doing a CAS implementation and SSO and security have always been my
>> interest.
>>
>> If I understand the previous threads here, AppFuse would be an
>> Identity Management application that just worked with Crowd? (CAS)  
>> Or,
>> does Crowd do have the admin for the user management already?  I
>> haven't looked at it yet.
>>
>> David
>>
>> On 6/3/08, yuanhang <[hidden email]> wrote:
>>> Hi Matt,
>>>
>>> You might be interested in using this strategy, described in the  
>>> following
>>> link, to manage the implementation of new features in SVN. Maybe  
>>> it will be
>>> easier for you to have more people get involved.
>>> http://www.infoq.com/articles/agile-version-control
>>>
>>> Anthony
>>>
>>>> Date: Tue, 3 Jun 2008 15:56:19 -0600
>>>> From: [hidden email]
>>>> To: [hidden email]
>>>> Subject: Re: [appfuse-dev] Getting ready for Struts 2.1.1
>>>
>>>>
>>>> On Tue, Jun 3, 2008 at 3:11 PM, Dustin Pearce <[hidden email]
>>>> >
>>> wrote:
>>>>> Thanks Musachy! I have been a little sidetracked. Its summer  
>>>>> time and I
>>> am
>>>>> on the board of my kids swim team and there is way more drama  
>>>>> than I
>>> need
>>>>> right now. ;-) I think we can house this under the Appfuse roof  
>>>>> since
>>> its
>>>>> really a branch of that code base. If we can get some wiki space  
>>>>> I can
>>>>> start laying some things out so people can just take chunks and
>>> implement.
>>>>>
>>>>> Matt, Do you have a particular starting page you want us to use?  
>>>>> Or
>>> should
>>>>> we just hang a page and then create children pages as necessary  
>>>>> from
>>> there?
>>>>
>>>> I could create a new space do to stuff. How about ASP for AppFuse
>>>> Struts Plugin? Another thing I was thinking about is going ahead  
>>>> and
>>>> calling it AppFuse 3, with the main objective being moving AppFuse
>>>> features back into the web frameworks. I'd love to something like
>>>> AppFuse supported by all the major players.
>>>>
>>>> Either way, I'd be happy to create a new space for you - just let  
>>>> me
>>>> know the name and key.
>>>>
>>>> Matt
>>>>
>>>>>
>>>>> -D
>>>>>
>>>>>
>>>>> On Jun 3, 2008, at 1:00 PM, Musachy Barroso wrote:
>>>>>
>>>>>>
>>>>>> I am not an Appfuse user myself (or Struts 2 for that matter),  
>>>>>> but this
>>>>>> sounds really cool, I would definitely help out with such an  
>>>>>> effort.
>>>>>> --
>>>>>> View this message in context:
>>>>>>
>>> http://www.nabble.com/RE%3A-Getting-ready-for-Struts-2.1.1-tp17446803s2369p17632203.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]
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>> ---------------------------------------------------------------------
>>>>> 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]
>>>>
>>>
>>>
>>> ________________________________
>>> Windows Live Writer，支持离线撰写博客内容，随时随地
>>> 想写就写。 立即使用！
>>
>
>
>
> --
> http://raibledesigns.com

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