Yeah, I haven't had time to read the spec since May '01.. I wanted to
use this to construct faces on web services, but it was so tied to
HTTP.. I needed something that would work within Swing as well. I hope
this has changed since then.. It would be handy to have this support
from IE/Mozilla to
This will probably be handled by JavaServer Faces.
David
From: V. Cekvenich [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: OT - XFORMS Tag:
Date: Wed, 13 Nov 2002 07:58:55 -0500
One day form processing will be done like this:
1. XForms
I'm still unclear on the direction we should take here. I'd like to hear
from other committers :-).
Thanks,
Dave
From: Martin Cooper [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: Re: [VOTE] How to implement XHMTL
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=14506.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
No you can't do that with bean:write. If you want a specific property,
specify the property in the html:messages tag and only messages with that
key will be itereated over.
-Original Message-
From: Michael Delamere [mailto:home;michael-delamere.de]
Sent: Wednesday, November 13, 2002
I agree with Martin that you can't ignore people using jsp:include. I prefer
his option B because then it allows someone to use the xhtml support in the
other tags without forcing them to use html:html. They would have to set
the attribute themselves and assume the risks that go along with making
Hi,
thanks for your reply. I just wanted to add that I havent actually
tried adding the property attribute to the bean:write tag yet, so the
problem still remains...
Regards,
Michael
-Original Message-
From: Hal Deadman [mailto:hal.deadman;Tallan.com]
Sent: Mittwoch, 13. November
The ChainAction was intended to be another option for users in defining
their actions in the struts-config. User's are not forced to chain actions
together in each ActionMapping. For this reason in lieu of a Custom Reqeust
Processor, we decided to use the existing Struts Action architecture to
whisperDon't bother drawing a ballot up - these guys don't use it!
They're all like thinking outside the box and adding options to it,
dude! ... and there's that one fellow who is always saying put your
code where your mouth is - we only vote on code - while standing there
with a wild, Clint
-Original Message-
From: Craig R. McClanahan [mailto:craigmcc;apache.org]
The presumption of storing the outer xhtml setting
(independent of *how*
you do so) is to let the included page automatically adapt to
the outer
page's choice - presumably, that lets you use the same
What if we did this:
1. Store a boolean in the request under Globals.XHTML_KEY
2. html:html xhtml=true would set the boolean to true
3. html:xhtml (new tag) would set the boolean to true
4. People could manually set the request attribute if they choose and
realize potential problems.
This
Forgot this:
5. Tags nested in html:html xhtml=false will not be rendered in xhtml
regardless of any other settings.
Dave
From: David Graham [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: [VOTE] How to implement XHMTL support
Date:
On Wed, 13 Nov 2002, David Graham wrote:
What would html:isXhtml/ do?
This would be the way Craig was seeking for an included page to tell its
own Struts tags whether to render XHTML or plain HTML. It would set a
*page* context attribute, which the subsequent tags on that page would
check.
husted 2002/11/13 11:16:41
Modified:contrib/scaffold/src/java/org/apache/struts/scaffold
BaseForm.java
Log:
+ BaseForm: Add convenience methods for testing for required fields
and if a field representing a value is zero or blank.
Revision Changes
Martin Cooper wrote:
On Wed, 13 Nov 2002, David Graham wrote:
What would html:isXhtml/ do?
This would be the way Craig was seeking for an included page to tell its
own Struts tags whether to render XHTML or plain HTML. It would set a
*page* context attribute, which the subsequent tags on
Ok, I think I agree with the non-body tag setting a page scoped attribute.
I really like the style of html:xhtml/ over html:isXhtml/. The is
part indicates that it's a question rather than stating that we're using
xhtml.
Regardless, I'll get the changes in soon so people can start playing
On Wed, 13 Nov 2002, Eddie Bush wrote:
big-snip/
If the outermost document is meant to enforce XHTML, how can an included
piece *not* conform to XHTML and the entire document still be XHTML? I
... feel like we're attempting to over-design - but maybe I'm just
showing my own ignorance
On Wed, 13 Nov 2002, David Graham wrote:
Ok, I think I agree with the non-body tag setting a page scoped attribute.
I really like the style of html:xhtml/ over html:isXhtml/. The is
part indicates that it's a question rather than stating that we're using
xhtml.
I'm not that fussed about
Martin Cooper wrote:
On Wed, 13 Nov 2002, Eddie Bush wrote:
big-snip/
If the outermost document is meant to enforce XHTML, how can an included
piece *not* conform to XHTML and the entire document still be XHTML? I
... feel like we're attempting to over-design - but maybe I'm just
showing my
Neither am I. Absolutely correct naming is almost impossible, it's just
a good goal. If you can't make it perfect, the documentation should
take you the rest of the way. Make sure that the documentation for the
html and xhtml tags refer to each other. A boilerplate comment
about this in each
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=14524.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
The future of the struts html tags is unclear. JavaServer Faces will
largely replace their functionality. I just wanted to get simple xhtml
support into Struts now because it's a requirement on some projects. It's
easy enough to setup xhtml with the current nightly builds and enhancements
HI,
we (the Tomcat dev team) are experiencing some problem with Struts 1.0.2
and Xerces 2.2.0 in Tomcat. When starting Tomcat, a wrong exception is
thrown (see below). Is somedoby aware of a similar problem? I'm trying
to produce a smaller test case for the Xerces-J team (they will not fix
This is not a bug. It's part of the XML specification.
http://www.w3.org/TR/REC-xml#sec-comments
-Original Message-
From: Jeanfrancois Arcand [mailto:jfarcand;apache.org]
we (the Tomcat dev team) are experiencing some problem with
Struts 1.0.2
and Xerces 2.2.0 in Tomcat. When
Have you looked for -- within comments in the xml files your parsing? The
error seems pretty clear.
David
From: Jeanfrancois Arcand [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Struts 1.0.2 + Xerces 2.2.0
Date: Tue, 12 Nov 2002
Just be sure to be seated if you ever decide to give IDEA IntelliJ a try
if you get that excited about measley little import cleanup :))
Don't get me wrong, Eclipse is cool and the price is nice. But
IntelliJ thats where its at :)
James Mitchell wrote:
I must admit. Since the hoopla a
Eclipse +1 because of the price. Netbeans is to big.
I use Eclipse with VIM.org. VIM.org (vi) does GUI XHTML and JSP, and
anytime I am confused and need javac. Both run in XWindows.
And only thing better than InteliJ is Omnicore CodeGuide!
geek:joke: Anyone who disagrees with this must be
Yes, I've run into this too -- in my struts config files :-) If you
remove the unneeded -- this error should vanish. Examine all comments
for occurences of -- which do not belong (ie. do not occur at the
start or end of the comment).
Ex: Change anything like !-- Foo -- Bar -- to !-- Foo Bar
Hi,
A Dimecres 13 Novembre 2002 20:45, Martin Cooper va escriure:
On Wed, 13 Nov 2002, Eddie Bush wrote:
big-snip/
If the outermost document is meant to enforce XHTML, how can an included
piece *not* conform to XHTML and the entire document still be XHTML? I
... feel like we're
The developer must make a choice between html and xhtml. This choice is
minor as xhtml is compatible with current browsers. Included jsps should
not be influenced by the includer file; they must decide if they're xhtml or
html. That's the point behind the html:xhtml tag, to tell struts html
Hi,
A Dimecres 13 Novembre 2002 23:06, David Graham va escriure:
The developer must make a choice between html and xhtml. This choice is
minor as xhtml is compatible with current browsers. Included jsps should
not be influenced by the includer file; they must decide if they're xhtml
or
Unfortunalty, the file doesn't contains any --. The file is
web-jsptaglibrary_1_2.dtd
http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd
and this is there since at least 1 year :-( Only Xerces 2.2 fail, not
Xerces 2.0.1, 2.0.2, 2.1.0 and Crimson.
I will have to ping the Xerces guys
--
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=14535.
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=14535.
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=14535.
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=14535.
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=14535.
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=14535.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
38 matches
Mail list logo
