as long as it was clear, the distinction between a form bean missing because
it should be there, and a form bean missing because it was optional. I
would think it might be better as a tag attr, because a form could be shared
with different actions, and it might be sticky if it's optional for some
If they're different projects, wouldn't they have different context roots?
And so would be treated as separate apps? Is this what you meant by
projects? Or did you mean within the same application? I ask because you
only mentioned same JVM, not same application.
-Original Message-
From:
to see it stay in some form somewhere.
Another alternative would be to remove the news and resources pages
completely, with the expectation that, if these pages are valuable to
the Community, then someone in the Community will undertake hosting
them. (I know I would.)
Agreed.
Thanks,
Mike Jasnowski
Greetings,
I was curious if what (if any) particular reason there is that
BaseHanderTag doesn't define getName() and getProperty(), which seemingly
most form tags need. The scenario that's prompted this question is an tag
extension scenario. In a particular instance I want to set the value of
Didn't you just answer your own question?
-Original Message-
From: Zakaria khabot [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2003 11:52 AM
To: Struts Developers List
Subject: XMLEncoder class
Hi
wich package contains the class java.beans.XMLEncoder
thanks
class
i got this error message :
Error: cannot access class java.beans.XMLEncoder; file
java\beans\XMLEncoder.class not found
and I thougth I have to add a (.jar) in the classpath
- Original Message -
From: Mike Jasnowski [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Sent
For some reason the new sidebar shows up left aligned, but at the bottom of
the page in IE 6
-Original Message-
From: Steve Raeburn [mailto:[EMAIL PROTECTED]
Sent: Monday, September 29, 2003 2:54 PM
To: Struts Developers List
Subject: RE: XHTML Web site updates
-Original
I like this idea as well, we've been trying to represent forms as XML also,
not just for bullets you mentioned, but it also enables flexible layout and
presentation, which can be shared across like forms, custom error
placement,etc.. We're running our forms through an XSLT template to render
the
Another interesting aspect is to use templates to drive tag content. I
believe they do something like this in WW2 with their form tags and Velocity
templates. I don't know off-hand what limitations the templating would
impose.
-Original Message-
From: Edgar Dollin [mailto:[EMAIL
Good question, I think someone else has done some similar thinking already:
http://dev2dev.bea.com/codelibrary/code/jsr168_struts.jsp
I haven't used this, nor can I vouch for it. I just remembered seeing it
listed on a web page.
-Original Message-
From: Mete Kural [mailto:[EMAIL
This may be a good time to add an ActionContext interface instead of
passing all these individual pieces. This would also slightly remove the
dependence on Servlet to allow us more flexibility when we look at the
portlet API.
As an outside observer I would like to see something like this added.
Ideally, I believe another class, specified by the ActionForward, should
be responsible for setting up any chrome a particular page may need.
It's the one that knows where the page is (via the path property), and
so it's the one that should be privy to these details.
Not sure if this
I'm not sure if this would satisfy you're request, but you can extend the
forward element to include custom properties, this extension is then named
in the className attribute. You can then locate your forward as usual,
then cast it down to your extension class, and call a setter on it.
Great job guys! Looking forward to more great stuff.
-Original Message-
From: Martin Cooper [mailto:[EMAIL PROTECTED]
Sent: Monday, June 30, 2003 3:39 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: [ANNOUNCEMENT] Struts 1.1 Final released
The Struts team is
-Original Message-
From: Mike Jasnowski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 25, 2003 9:55 AM
To: Struts Users Mailing List
Subject: Form field styling/error reporting - Alternate solution [Long]
Greetings,
The subject of styling form field labels based on the results
/error reporting - Alternate solution
[Long]
-Original Message-
From: Mike Jasnowski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 25, 2003 9:55 AM
To: Struts Users Mailing List
Subject: Form field styling/error reporting - Alternate solution [Long]
The technique centers around the use
Message-
From: DeRose Jonathan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 25, 2003 11:02 AM
To: Struts Developers List
Subject: RE: Form field styling/error reporting - Alternate solution
[Long]
-Original Message-
From: Mike Jasnowski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 25
Agreed,What is also interesting is that the TM2 to Struts matrix/feature
comparison nearly every column
matches Yes. So if this is the case, how can Struts Not have it's act
together?
-Original Message-
From: David Graham [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 11, 2003 12:35 PM
Just curious, in the releaes plan under The plan it has the following
line:
Therefore, the following release plan is proposed for Struts 1.1 Release
Candidate 1:
Should this be Release Candidate 2 ?
If not, sorry for the noise.
Mike
-Original Message-
From: Ted Husted [mailto:[EMAIL
19 matches
Mail list logo
