Donnie Hale wrote:
Donnie comment
I understand that sentiment and, in general, agree with it. I just don't
think the underlying premise of servlet = controller only or servlet =
view only is necessarily valid. I think it's possible to have the
controller and view be decoupled but still run
Apologies to Dan Malks et al. The book is of course called Core J2EE
Patterns ;-0
Ted Husted wrote:
In Core J233 Pattern terms, Struts implements a Service to Worker
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Donnie Hale wrote:
Re: the proposed interface - I'd like to see one, perhaps a base interface
for what you're proposing, which has access to everything for which the
current request isn't needed. And that's most of those elements. That way
all Struts elements that need the non-request-based
Ted Husted wrote:
So, now that 1.0.1 is in the queue, we may want to make some decisions
regarding 1.1.
...
[Tiles,Validator]
The next question is whether David and Cedric are interested in
proposing their components to Taglibs or the Commons, or would prefer to
leave them here. Your
This would be very helpful for me! I'm desigining an application with a
fairly complex internal navigation structure and until the workflow
commons package is in a more complete state I've had to make do with an
ad hoc scheme that has been seriously hindered by the inability of an
action to set
Hi people, I wonder why the PropertyUtils class in
struts does not include the method setMappedProperty.
like in
org.apache.commons.beanutils
Why wasn't this feature implemented? Would it be
difficult?
Greetings and thank you for your great work.
Diego
Hello Matt,
Controling pages look and feel according to users roles is also exactely what I need
and
what I am currently working on.
The solution you suggest is interesting because it is simple and covers most cases.
However I am looking for a solution that
1 - would keep the security
If you were able to patch a copy of ActionServlet, and run them through
some of your use cases, that would help move them along. I could provide
a patched jar based on the nightly build if that would help.
These compile, but haven't been tested:
public ActionForm createActionForm(String
I have actually implemented something along the lines of the custom tags
for my project, although I have to admit IRoled my own security
without learning how to do J2EE security, and now am in the process of
retrofitting.
getcare:security permission=directory
a href=directory/a
The Struts PropertyUtils is now deprecated: all further developement is done
within the commons beanutils project. Future Struts release after 1.0.x will
use the new commons library. If you really want this feature with Struts
1.0.x, see this posting:
Have you guys considered having the html tags output well-formed markup, to make
Struts compatible with xhtml?
i.e. input/ rather than input?
Is there a reason that it doesn't already do this (eg. browser incompat.)?
Thank you,
Bob
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5244.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5244.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5244.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
If the one and only goal is getting Struts to use Velocity templates,
then, yes, a VelocityAction is going work every bit as well as a
VelocityServlet. And maybe that's the way to go. A developer could
choose to either extend it, or maybe just forward to a base
VelocityAction that did what the
It's not a pressing issue.
I'm writing some interface XSL's that perform transformations on HTML forms. Part of
the incentive of choosing XSL over a custom tag library is that I can make them work
with both Struts (which I'm trying to get my team to move to) or regular forms. For
this to
Since I see no reason to define hundreds of different exceptions,
which are very similar in their nature and are handled in a similar way,
I would propose:
*) introduce 2 base exception classes: AppException and RuntimeException
which should support constructors like:
No, the question is entirely independent from velocity. There are
many possibilities to render a view. E.g. Maverick domifies a data
structure and gives it to an XSL transformer, etc. What I was wonder
was simply the WRAPPING of the view helper. To me it seems to be
natural to hide (and make it
Dimitri Valdin wrote:
Since I see no reason to define hundreds of different exceptions,
which are very similar in their nature and are handled in a similar way,
I would propose:
*) introduce 2 base exception classes: AppException and RuntimeException
which should support constructors like:
The standard ActionForward and ActionInclude Actions create a
RequestDispather in the Action, and do call another servlet directly,
without going back to the container.
http://jakarta.apache.org/struts/api-1.0/org/apache/struts/actions/ForwardAction.html
I recently suggested some additional
Couple of comments in-line -
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 03, 2001 3:15 PM
To: Struts Developers List
Subject: Re: Declarative Exception Handling
Dimitri Valdin wrote:
Since I see no reason to define hundreds of different
On Mon, Dec 03, 2001 at 03:29:26PM -0500, Ted Husted wrote:
The standard ActionForward and ActionInclude Actions create a
RequestDispather in the Action, and do call another servlet directly,
without going back to the container.
We're definitely looking at doing something similar as well, so the interest
level is definitely here though we haven't had the chance yet to define an
implementation.
BTW, I noticed that Websphere v4 uses Struts for its Administrator Console!
Does that mean that Websphere could be added to the
Ted,
The stepwise refinement sounds like a reasonable way to go. I've got a good
chunk of one definite piece of that done - a resource repository, which
would implement most of your proposed interface (it has no knowledge of
requests at present); and a config handler, which reads servlet init
I have some code that uses bean:write and the datetime:format tag from
taglibs project. I use it like this:
datetime:format pattern=MM/dd/bean:write name=contractinfo
property=beginDate.time//datetime:format
The bean:write used to print out the number of milliseconds returned by
Hello,
This deals with the Struts Validator, and is a suggestion for a minor
enhancement/extension.
The application I'm working on needs to be able to distinguish between
'fatal' and 'non-fatal' validations (for lack of a better term). Fatal
validations mean that the page should not be
Laine Donlan wrote:
perhaps some time later nobody will remind old perform(), but would
use
new execute() ;-)
OK by me, especially if the controller were somehow smart enough to call
one or the other if both approaches were mixed in the same application
(during a migration period).
I had originally thought we might start posting an ActionResources
object in the request, so it would be there when we started to refactor
the tag extensions, and also for the use of other presentation systems
like Velocity templates. So, for a time, it would really be redundant,
and could just
Ted,
There are a number of public methods on ActionServlet right now like:
addDataSource
addFormBean
addForward
addMapping
Some of them are used in various actions package classes to do things
dynamically. I'm guessing that there are deployed Struts apps out there
which also use these methods
These wouldn't exist as such on the ActionResource interface I
suggested. These are really just shortcuts to the API for the underlying
resources, like
formBeans.addFormBean(formBean);
So, if someone wanted to do them through an ActionResources object, they
could do the same thing
30 matches
Mail list logo
