One example use that I am doing based on the Struts-Chain example:
SoA access (via Hessian and a chain dispatcher) to Apache JackRabit CMS.
W SoA, you can call from any API (Tiles, Portlet, JSTL, JSP, Servlet... any Java..... or non Java, like C++). It's just a call that happens to dispatch and execute remotely.


I may open source, I may not.

I am quite disapointed that people are silent on JSF direction other than the 2 people who did not try it.

.V


Scott Anderson wrote:
Instead of taking the approach of predicting what
developers might want from Struts and JSF in the
future and providing a few potentially unrealistic and
overly simplistic demos, how about identifying a
complete evolutionary or revolutionary sample web
application and/or web service that would be truly
useful to the Struts community. This application,
along with the process of developing it, could be
leveraged to shape what extensions to JSF and what
complementary components from Struts would be worth
investing in, while also serving to demonstrate proper
design patterns and best practices.

In my mind this would not be another "Java Pet Store"
application, but a tool that would be used and
leveraged to expose this evolved platform and/or
development model to developers with little or no
investment on their part. It looks to me like Struts
will be focusing on describing application control and
integration while JSF will be focusing on the
presentation layer. At least this is how I am planning
to leverage the two. It is my belief that successful
web applications will need to become more
customizable, personalizable, *and* more usable while
these application's infrastructure become simplified
from the perspective of both the developer and the
consumer of the application. Integration requirements,
in addition to those related to usability, led me to
conclude that an iterative divide and conquer approach
using standardized portlets held some promise.

With this in mind, my proposal for a useful and
demonstrative application would be the result of
porting/supporting NetBeans' web application
development APIs and relevant visual components to a
JSR 168 portlet suite built on Struts components and
JSF extensions. This suite would form the basis for a
hosted IDE and project manager and could also leverage
the Web Services for Remote Portlets (WSRP) OASIS
standard to provide for project aggregation. I can see
this authoring tool/portal being used to generate more
focused tools and applications, a WAR factory, that in
turn gets used by higher level developers and applied
to more specific problem domains.

I think this group can pull off something like this.

Scott

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com


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



Reply via email to