I am sorry - i guess i was not very clear. i am just concerned about how to
query Bugzilla in order to only get bugs with no available patches. If we had a
standard (say, keyword 'PATCH' or 'HAS_PATCH') for bugs with an available
patch, then we can do more focussed queries.
Would be especially
+1
IMHO, we are talking about View - [Protocol] - Controller layers.
We have taglibs for the View and Actions for the Controller. logic:redirect and
logic:forward are definitely an encroachment of the view on controller domain.
In an ideal world we should just take them out. Barring which
--- Martin Cooper [EMAIL PROTECTED] wrote:
1) All of the tags in the logic taglib relate to flow control. There are two
sets - conditionals and 'goto's
Not true
- conditionals relate to layout and display (i.e. View)
- gotos send control out of the current file (i.e. Control)
2) If we
--- Martin Cooper [EMAIL PROTECTED] wrote:
Conditionals relate to whatever the developer wants them to relate to. They
are in no way limited to layout and display. I can just as easily use a
conditional tag to control (sic) a SQL update as I can to determine whether
or not to show someone's
Hi,
Is it a standard (at least within jakarta) to prefix the bugs with patches
available with a [PATCH]? Any ideas w.r.t creating a status called Has Patch?
I ask because there are quite a few bugs in the commons which have no
indication about available patches. I guess the commiters can finish
Hey, this is great! Do you plan to contribute this?
I would love to, but don't know how to go about it... esp. packaging the xsl,
css files.
Also, maybe you could help me with something similar that I've been
wanting to do. ...
Think I get the gist of it. Dont think i can do it in xsl. Will
Hi,
I have put together an ant task with accompanying XSL files etc, which generate
javadoc-like documentation for the taglibs (uses the current struts-xxx.xml
files).
The docs are available at http://mohankishore.tripod.com/struts-docs/ Just
wanted to run it by the community to see if it feels
+1
I guess this approach satisfies both the requirements of (1) Having quicker
core releases (2) having all-in-one packages easy to use.
But IMHO there should be a conscious effort to separate the development/release
cycles for the two...
--- David Graham [EMAIL PROTECTED] wrote:
Which is why
Would recommend a whitepaper/guidelines doc from the core tag developers, so
that we have certain patterns to follow for future tag development...
--- David Graham [EMAIL PROTECTED] wrote:
It is a fact. You can do the math yourself to verify. Tomcat pooling did
not break the tags; the tags
Theres an 'major' open bug regarding failure of 'required' Integer fields. I
think this discussion kind of closes it...
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17156
regards,
Mohan.
--- Craig R. McClanahan [EMAIL PROTECTED] wrote:
On Wed, 26 Feb 2003 [EMAIL PROTECTED] wrote:
Was having the same problem myself.
The trivial solution is to type in 'cvs diff -u XXX' in the command window.
But, the better solution is to create a file called .cvsrc in the directory you
store your cvs password file. This file should have the line 'diff -u'. Now,
when you invoke 'diff' from
16916 nested:write using incorrect bean
This is probably serious enough to block 1.1. I don't know enough about it
to fix it though.
I had submitted a patch - it had fixed the immediate problem reported. But, I
guess there is a broader impact of tag-handler reuse which has to be looked
for.
: [EMAIL PROTECTED]
Mohan Kishore
732 Marlin Ave, Apt 4
Foster City, CA 94404
[EMAIL PROTECTED]
-
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
Hi,
Was looking at the the JSP spec (also posted in the mailing list some time back):
All properties of a tag handler instance exposed as attributes will be initialized by
the container using the appropriate setter methods before the instance can be used to
perform the action methods. It is
, for interpreting the
patterns. And the $P is interpreted differently - in forwardURL, we add a leading '/'
if needed, and we dont do the same in pageURL... just wanted to bring it up - dunno if
its a bug...
Mohan Kishore
732 Marlin Ave, Apt 4
Foster City, CA 94404
[EMAIL PROTECTED
As Craig says, the static state doesnt affect Serialization. When deserialized, the
static state will be effectively borrowed from the JVM it is running in.
As the classes concerned (abstract class ModuleConfigFactory, and interface
ModuleConfig) do not have any instance state, we can just mark
/?page=features/junkmail
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Mohan Kishore
732 Marlin Ave, Apt 4
Foster City, CA 94404
[EMAIL PROTECTED
I noticed that there is no overview diagram in the User Guide. Is that a concious design decision? Am attaching an image which might be used for the same...
MohanDo you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now-
The attachment might be a problem. My mistake - should have provided a URL instead.
Can be accessed at http://www.mycgiserver.com/~mohankishore/work/java/struts/step1.html
Mohan
Mohan Kishore [EMAIL PROTECTED] wrote:
I noticed that there is no overview diagram in the User Guide
. But,
none of the commons-logging versions (1.0, 1.0.1,1.0.2) seem to support this signature
(they have a release() method...).
Have a perfect build after I commented the line out...
regards,
Mohan.
Mohan Kishore
732 Marlin Ave, Apt 4
Foster City, CA 94404
[EMAIL PROTECTED
20 matches
Mail list logo
