Hmm...I agree with your premise that there are two types of JSF
integration use cases:
1. The JSf app that wants some action-driven pages
2. The Struts 2 app that wants to use JSF components
However, I don't see why both aren't serviced by the existing code
today. To meet use case #1, you c
I've been talking with the DTDDo[1] developers, and they've done some
work on a Maven 2 plugin for it.
Since Tiles 2 is in the sandbox, it's the easiest place to experiment.
:) I've added the config to the tiles-core pom, and re-published the
site. Here's the generated output:
http://struts.a
My take on this conversation is there are two main viewpoints:
1. Simple convention that uses existing action mapper and wildcards
2. Elaborate convention that uses new action mapper and probably configuration
provider
and really, I think implementing both is worth considering. We provide a
Heh - well, that's how this was implemented in the first place. I wrote my own
ActionMapper. My point is that I have seen a lot of success with a combination
of ActionMapper+Convention-based-configuration, and I think we should really
think about pushing this to a broader set of users.
I think
> OK, I've been lurking on this list for some time, so
> nobody here knows me,
> but I do want to weigh in on this issue on Jason's
> side. I'm relatively new
> to WebWork, using it for a new Web application
> project started in March. I
> was responsible for evaluating the various frameworks
> ava
> Ted, while I have no opinion on case, I can say that
> my comments in these threads has been driven entirely
> from real world experience. This URL:
>
> https://struts.hostedqa.com/project/7/session/suite/li
> st
>
> Maps, via conventions, to
> com.hostedqa.action.project.session.suite.ListActi
OK, I've been lurking on this list for some time, so nobody here knows me,
but I do want to weigh in on this issue on Jason's side. I'm relatively new
to WebWork, using it for a new Web application project started in March. I
was responsible for evaluating the various frameworks available, then
set
Ted, while I have no opinion on case, I can say that my comments in these
threads has been driven entirely from real world experience. This URL:
https://struts.hostedqa.com/project/7/session/suite/list
Maps, via conventions, to com.hostedqa.action.project.session.suite.ListAction
So there, now
I've been working with the Struts2 JSF Integration and I wanted to run a few
ideas past the development community.
First, I would like to give a high level description of the functionality
that I see as being desirable as well as why I believe it to be so.
Second, I would like to give a descript
As an excuse, I first have learned German at school (which I don't
understand anymore) and latter English. Maybe I'll buy a "improve your
english in 24h" CD ?
Gareth Evans a écrit :
Mines not great and it's my first language!
Nicolas De Loof wrote:
Oops,
I'll realy have to improve my eng
Mines not great and it's my first language!
Nicolas De Loof wrote:
Oops,
I'll realy have to improve my english ;-)
Apache Wiki a écrit :
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Struts Wiki"
for change notification.
The following page has been changed by Ga
Oops,
I'll realy have to improve my english ;-)
Apache Wiki a écrit :
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Struts Wiki" for change
notification.
The following page has been changed by GarethEvans:
http://wiki.apache.org/struts/StrutsAndSpring
> We can be rigid and consistent in the conventions
> that we use with our
> own examples, but the nature of wildcards implies
> that people could
> adopt other conventions, whether we like it or not.
> :)
>
> And, the nice thing about people being able to adopt
> their own
> conventions is that i
> On 8/3/06, Jason Carreira
> Ted didn't say deprecate. Ted said that it didn't
> seem like a best
> practice, in the same way that chaining actions is
> not a best
> practice. Mainly because it goes against the grain of
> the "advanced"
> features like type converters, localization, and
> especia
Hi list!
Today I am going to take the train to spend my 2-weeks holidays in my
homeland, so I will not be able to read the list that much (maybe just a
look every now and then :-) ).
Anyway before going away for a while, I would like to hear from you a
concept that came into my mind.
Everything
On 8/3/06, Jason Carreira <[EMAIL PROTECTED]> wrote:
If it looks like the stuff Don was showing before, then it's looking too
complex.
Either explicit configuration or easy but rigid conventions... not configurable
conventions
;-)
We can be rigid and consistent in the conventions that we use
On 8/3/06, Patrick Lightbody <[EMAIL PROTECTED]> wrote:
Don and I talked in-depth about using wildcards to do the style of conventions
I am
talking about, and we found that it would require a much more complex
implementation of
wildcards. Don, can you add to that?
Why not focus on starting w
On 8/3/06, Jason Carreira <[EMAIL PROTECTED]> wrote:
Either way, you're still talking about multiple aliases for one class, which is
what Ted was
saying we should deprecate.
Ted didn't say deprecate. Ted said that it didn't seem like a best
practice, in the same way that chaining actions is n
18 matches
Mail list logo
