It would be hard for us to figure out anything without any description
of what really happens. Do you have an exception stack trace?
You could really help yourself out by setting this up in a JPDA debugger
and really tracking exactly what happens at the point of the error (and
before).
After you upgraded from 1.1b3 to 1.1rc1, did you clear out your web
container work directory? There were numerous changes to the
JavaBeans mapping from JSP attributes to class properties. If it didn't
regenerate the servlet, it won't work.
-Original Message-
From: Derek Richardson
You said ContestForm has a categories property. Your reference in
the JSP says that ContestForm has a map property, which has a
categories property. Which is it? If the former, your reference
would just be ${ContestForm.categories}.
-Original Message-
From: awc [mailto:[EMAIL
Ok, in that case your original syntax was correct. I don't know why it
isn't working. I assume you mean by does not work that the variable
appears to be empty, and not that you're getting exceptions.
If I were you, I would be stepping through this code in your debugger.
Set breakpoints on your
Yeah, ok, now I remember. The collection attribute of the options
tag is just the NAME of the bean which represents the collection. There
is no way to specify an EL expression for that which represents the
collection itself. This would have been a good place for Struts-EL to
have a minor
-Original Message-
From: LUCERO,DENNIS (HP-Boise,ex1) [mailto:[EMAIL PROTECTED]
Hello
I am trying to do this:
html:button property= someButton
onClick=doSomething(%=somedynamicvariable%) Do Something
/html:button
Basically trying to pass a dynamic variable as arg to java
You're missing an important point about the JSTL tags. The tags that
store information into variables don't put them into scriptlet
variables, they put them into scoped variables, which are just HashMap
entries. If you use fmt:formatDate to store a formatted date into
currentdate, you can't
If you ever need to get older versions of files in the distribution, you
can always find it through the cvsweb links on the main Jakarta site.
Just navigate to the project and file that you want, and you can see all
of the file revisions, along with the version tags that indicate what
releases
You have single quotes wrapping single quotes. Make either the inner or
outer quotes be double quotes. I assume you're not really referencing
the xxx attribute?
-Original Message-
From: Ray Madigan [mailto:[EMAIL PROTECTED]
My application generates detailed Exceptions in the
Yes, Struts 1.1 changes (wrt Struts 1.0.2) where you specify the
application properties file. After your action-mappings element, put
something like the following:
message-resources parameter=resources.application /
-Original Message-
From: k [mailto:[EMAIL PROTECTED]
Sent: Monday,
In general, it's useful if you provide the entire stacktrace, including
the root cause.
-Original Message-
From: Mervin Williams [mailto:[EMAIL PROTECTED]
Every time my application encounters the ActionErrors isEmpty()
message,
a Servlet Exception occurs. I simply replaced the old
How about telling us what not working means? What exactly happens?
What do you see and what did you expect to see?
-Original Message-
From: Chen, Gin [mailto:[EMAIL PROTECTED]
I am trying to use target in Struts 1.1b3
I have:
html:form action=/calendar method=post
Expression scriptlets have to be the entire attribute value, not just a
portion of it. Change the value of the property attribute to (don't
forget the wrapping single quotes):
'%= locationroomValue( + (String)mapEntry.getKey() + ) %'
-Original Message-
From: Huw Jones [mailto:[EMAIL
-Original Message-
From: alexj [mailto:[EMAIL PROTECTED]
Sent: Friday, February 28, 2003 3:34 PM
To: Struts Users Mailing List
Subject: [struts-el] What's the benefits ?
I didn't find the benefits of the use of jstl extention.
Who can explain me the benefits ?
You would be
And that before example wasn't even using scriptlets, which makes it
even harder to read and follow (especially for HTML designers).
-Original Message-
From: alexj [mailto:[EMAIL PROTECTED]
Sent: Friday, February 28, 2003 3:55 PM
To: Struts Users Mailing List
Subject: Re: [struts-el]
You just do it :) . Look over the Struts User Guide, including the API
pages. In the select tag, you'll see an onchange attribute.
-Original Message-
From: Richard Raquepo [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 27, 2003 4:54 PM
To: Struts Users Mailing List
Subject: do
-Original Message-
From: Jason Vinson [mailto:[EMAIL PROTECTED]
For some reason, I am not catching on to the idea of beans in the
request.
Here's my code:
request.setAttribute(caseInfo, theCase);
theForm.setCaseInfo(theCase);
I assume the previous code is in an action, and the
Gee, I wonder if specifying a roles value of dummy (a nonexistent
role name) would do this. I don't know if a non-redirect forward from
an action to an action would go through the RequestProcessor. I have a
feeling it wouldn't. If this works, I have a feeling it's a fortunate
accident.
Yes, it's reported, and I see the problem, and I'll be fixing that
tonight.
-Original Message-
From: Dan Tran [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 25, 2003 9:14 AM
To: Struts Users Mailing List
Subject: Re: NPE, webapp broken after moving to 1.1-rc1
I ran to the same
Show us where you're putting queuesName into request scope.
-Original Message-
From: Jason Vinson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 25, 2003 10:12 AM
To: Struts Users Mailing List
Subject: Re: RE: bean:write issues... or a better solution
I tried this in my page
al
ue());
cboQueue.moveNext();
}
theForm.setQueuesName(theQueues);
---Original Message---
From: Karr, David [EMAIL PROTECTED]
Show us where you're putting queuesName into request scope.
-Original Message-
From: Jason Vinson [mailto:[EMAIL PROTECTED]
Sent
Don't you mean address[index](street) instead of
address[index]{street} (parens instead of braces)?
-Original Message-
From: Mathias, Merlyn [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 25, 2003 11:02 AM
To: 'Struts Users Mailing List'
Subject: RE: Maps and Nested Properties
JSP tags are only meaningful when translating JSP pages. If you have
JSP tags embedded in javascript code, then the javascript code has to be
present inline in the page, or included from an include directive.
The latter is probably your best bet for sharing this code (make sure
it's an include
Prepare to get a bunch of responses saying the same thing: You're
heading down the wrong path. Your ActionForms should be simple
containers, and should not be connecting to your business logic or your
session. Use the business logic in your Action class to manipulate and
coordinate these
You can't nest custom tags in the attribute values of custom tags.
If you're using the JSTL, you might consider using Struts-EL, which is a
contrib library in the Struts distribution. If you use that, your
example would look like this:
campaign:list id=campaign
TR bgcolor=#CC
One thing that I've been seeing a bit is that upgrading a tag library
does not necessarily force retranslation of JSP pages. This is critical
in this case. Many EL tags had the names of the attribute setter
methods changed, but which are mapped back to the original attribute
through a BeanInfo
Ok, that's useful information, especially the fact that the same thing
happens with the non-el tags (so it wasn't me :) ). It would really be
useful if you could step through this in the debugger and try to see
what's happening, starting at the (expected) call to the attribute
setter in the form
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
In a different message, David wrote:
It would really be useful if you could step through this in the
debugger
and try to see
what's happening, starting at the (expected) call to the attribute
setter
in the form tag
This has been talked about somewhat recently, but the first issue is
that Struts no longer uses those config parameters in the web.xml file
to configure debug output. It uses commons-logging, and under that,
whichever logging system that is either available or configured.
-Original
Well, they're not there for convenience, as the exercise app won't
work without them. I certainly haven't modified them, either. You can
use those copies, or copies you got from elsewhere. I haven't specified
any particular version of the reference implementation, and I really
don't know what
... and the form bean will have a name property, and you will remove
the value attribute from your html:text element.
-Original Message-
From: Jarnot Voytek Contr AU HQ/SC
[mailto:[EMAIL PROTECTED]]
If you want to stick to the generally accepted Struts best-practices,
you
will never
I'm afraid I haven't gotten my act together and written a friendly
document about this. It's sort of a funny thing. I mean, if you know
Struts, and you know JSTL, well, think Chocolate and Peanut Butter.
Except for knowing which tags have been ported (as described in the
README.txt file),
-Original Message-
From: Alvarado, Juan (c) [mailto:[EMAIL PROTECTED]]
Can anyone tell me how I can prepend the context path to the following
example:
html-el:button property=userAction onclick=goLink('%=
request.getContextPath() %/resultsAction.do?userAction=Modify
-Original Message-
From: Arnesen, Geir [mailto:[EMAIL PROTECTED]]
I manage to get it up running with the classes are deployed inside a
jar, - but when compiling the action-classes to .class files in the
WEB-INF/classes
I get this error message when starting the application inside
-Original Message-
From: Rachel [mailto:[EMAIL PROTECTED]]
Hi
Does anyone have, or know of a simple example or tutorial for
accessing
mysql data with Struts?
I'm building a simple application using Struts with Tiles and need to
be
able to retrieve articles from mySQL. I'm an
-Original Message-
From: rajiv ahuja [mailto:[EMAIL PROTECTED]]
Hi
I am trying to use logic:equal tag to check whether a bean property is
equal
to another bean property or not. I am getting following error
cannot resolve the synmbol: setValue(currentVar) location EqualTag
First of all, you should set a non-empty package for your class.
Certain things won't work correctly if you try to use the default
package. Second, you have to have an import for your class in the
JSP, using a page directive with an import attribute, perhaps like
this (also showing a good
-Original Message-
From: otisg [mailto:[EMAIL PROTECTED]]
I am trying to make use of ActionError(s)
and messages defined in resource files, but
instead of an appropriate error message I
get something like
???en_US.amp.error.invalidLogin???
I know why I get the resource key
At end.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
I have been struggling in vain to use the html:link tag with
multiple
parameters. I know you're supposed to use a java.util.Map to hold the
parameters, since there could be any number of them, but the
You're obviously using the JSTL, so it might be more convenient to use
Struts-EL, which became available in 1.1b3. Once you do that (assuming
you have the correct taglib directive), you would change html:text to
html-el:text, and your sample reference to ${isReadOnly} would work.
As described in
I don't know whether you did this in any of your earlier notes, but how
about describing exactly what went wrong, including specific error
messages and stack traces, and showing us your relevant source files?
-Original Message-
From: Daniel E. Morrison [mailto:[EMAIL PROTECTED]]
Sent:
LogonForm.java looks fine and all the configuration looks
fine. Looks like it can't find the bean?
Thanks,
Dan
Karr, David wrote:
I don't know whether you did this in any of your earlier notes, but
how
about describing exactly what went wrong, including specific error
messages and stack traces
Show your exact source and exactly how you're getting this error
message. What web container and version are you using?
-Original Message-
From: Vinay [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 31, 2003 10:20 AM
To: Struts Users Mailing List
Subject: fieldset tag in HTML
Has
I have a feeling that both could be interpreted as correct, but we could
use some other opinions on this. I wrote the first one, so I'll update
it if this discussion points out a better way to say this.
On your quandary with iterating over a collection of String objects,
instead of beans, it's
Not quite.
The value of the value attribute is used directly. If you set it to
abc, then the text field will display abc. So, you would probably
use '%= aString %'.
If you have indexed=true, that does the work of adding the brackets
and array index to your resulting request parameter, you
I don't know for certain whether it will work with WL 5.1, but Struts
does not require a servlet 2.3 compliant container. As it is currently
defined, it can work in a servlet 2.2 container.
-Original Message-
From: Jason Vinson [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 29,
If you're using Struts and JSTL, you might as well use Struts-EL, so you
could do the following:
fmt:formatDate value=${employeeForm.dateOfBrith}
pattern=dd/MMM/ var=formattedBirthDate/
html-el:text property=employee.dateOfBirthText
value=${formattedBirthDate}/
Gee, I haven't been paying much attention to this issue, but that looks
like there could be some synergy with the JSTL EL engine. You could
easily handle expressions like that in the EL.
-Original Message-
From: James Turner [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 30, 2003
As others have said, it means run-time expression. Specifically, it
means the value CAN be specified by a JSP expression scriptlet
(beginning with %=). Ironically, calling it a run-time expression
is now a little too general, because the JSTL allows us to evaluate
values at run-time, but
A custom tag attribute can only use an expression scriptlet if the
attribute specification in the tag library descriptor has a value of
true for the rtexprvalue attribute.
This is not the default, because some attributes of some tags will not
work if an expression scriptlet is used to specify
attribute set with rtexprvaluetrue/rtexprvalue. But I
found
that using an expression scriptlet was inconsistent. It would work for
some
tags and not for others. Has anyone else experienced that?
-Original Message-
From: Karr, David [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 29, 2003
The welcome page of a web application has to be a physical file, and
not the path to a Struts action, so the common convention for making
sure every real page is fronted by an action is to have the index.jsp
welcome page immediately do a forward (and nothing else) to a main
action.
-Original
You'd have to show your specific code, showing your TLD entries, and
most of the JSP page.
-Original Message-
From: Jayaraman Dorai [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 29, 2003 1:51 PM
To: Struts Users Mailing List
Subject: RE: what does RT Expr mean
In the custom tag I
The indexId attribute of logic:iterate allows you to specify a name
of a scriptlet variable to create, to hold the current iteration index.
It assumes this variable is not created anywhere else. It's not
intended to be used to specify the starting index of your iteration, if
that's what you were
Looks like a bug to me. I'm not familiar with that code, but it looks
like the isAssignableFrom is trying to only use an existing attribute
as the ActionForm if it's of the correct type (or subtype) of the
specified ActionForm type. The result of the second return is that it
will use that
Just return null from your execute method.
-Original Message-
From: Murphy, Todd [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 2:50 PM
To: [EMAIL PROTECTED]
Subject: Must an Action forward to another JSP or servlet?
I am trying to render output as a PDF from a byte array.
This might work better for you:
logic:present name=details scope=request
bean:write name=details property=value/
/logic:present
-Original Message-
From: Khalid K. [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 24, 2003 1:21 PM
To: [EMAIL PROTECTED]
Subject: logic tag and %= %
It's certainly good that they're using 1.1, but somewhat unfortunate
that they stopped at b2. There were numerous fixes put in after b2,
including the entire Struts-EL contribution. Hopefully they can upgrade
their support pretty quickly.
-Original Message-
From: Hajratwala, Nayan (N.)
Note that you will get this message if the count of name, value, and
body is != 1. The message sounds like it's saying you have more than
one of them, but in truth you could get the error if you had none of
them. I'm going to guess that beanName is empty or null.
-Original Message-
In general, Struts applications will use prepare actions to prepare
the data for a form, and process actions to process the submitted data
for a form. In your prepare action code, you'll interface with your
business logic to obtain the required data, then populate fields of a
bean, probably in
That seems like a weird name to use, but it might work. You really
should just be executing this in the debugger so you can see exactly
what is happening.
-Original Message-
From: Adel [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 23, 2003 1:05 PM
To: [EMAIL PROTECTED]
Subject: Re:
-
From: Karr, David [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 23, 2003 3:48 PM
To: Struts Users Mailing List
Subject: RE: HOWTO pre-populate forms with data, then update ?
In general, Struts applications will use prepare actions to prepare
the data for a form, and process actions
For other's benefit, that only applies for the ActionForm class
associated with the Action in the action-mapping. If your prepare
action is associated with a different form bean, then that won't be
what you want.
However, you can have your prepare action and process action
action-mappings use
What the heck does that mean? Struts is a framework which facilitates
the building of browser-based applications in a way that enhances their
maintainability. It's perfectly applicable, probably more so, for
building inward or outward facing service applications.
-Original Message-
Assuming you're using the execute method instead of the perform
method, you can technically avoid having a try/catch block at all
(because execute throws Exception). You would then define an
exception element in your struts-config that specifies how to handle
exceptions of that type (or base
You can do this with the Struts-EL library, which is part of the Struts distribution.
Using this, your tag could look like this:
html-el:link forward='${menuOpt[forward]}' target='${menuOpt[target]}'/
The Struts-EL library uses the JSTL expression language engine for evaluating
attribute
library with the JSTL expression language evaluation engine.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Everybody is talking about struts-el. Is it part of
struts.jar? where can I
find the doc for it?
-Original Message-
From: Karr, David
It appears that there's some problem getting to your message resources or your Struts
configuration, I'm not sure. Can you upgrade to a newer stable version of Tomcat?
-Original Message-
From: Fabrice BLANQUART [mailto:[EMAIL PROTECTED]]
Hi,
I am using Netbeans 3.4 and I try to
We'd need to see the JSP page that is generating this error, or at least
the relevant parts of it. Also show us the form bean code.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
I'm embarassed to ask this question, but I've tried everything thing I
can think
Despite that being a good idea, it has no relevance. It doesn't matter
how the bean methods are implemented, or the names or case of the
variables. The signatures are all that matters.
-Original Message-
From: Richard Yee [mailto:[EMAIL PROTECTED]]
Your member variable names should
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 27, 2002 9:00 AM
To: Struts Users Mailing List
Subject: Re: No getter method available...
[EMAIL PROTECTED] wrote:
Karr, David wrote:
We'd need to see the JSP page that is generating this
error
Unfortunately, the only thing that is really clear about this is the code (AFAICS).
The default exception handler will put the exception into request scope under the key
symbol Globals.EXCEPTION_KEY, which is the string
org.apache.struts.action.EXCEPTION.
-Original Message-
From:
ExceptionHandler to do this?
Jerry
-Original Message-
From: Karr, David [mailto:[EMAIL PROTECTED]]
Unfortunately, the only thing that is really clear about this
is the code (AFAICS). The default exception handler will put
the exception into request scope under the key
The property represented in your ActionForm is geoZoneID, not
geozoneID. You have to make sure your case references match.
-Original Message-
From: David Rothschadl [mailto:[EMAIL PROTECTED]]
Hello,
I have created the action form that contains the getter
method for a property
You can't use EL expressions with the base Struts tag library. They will only work if
you're using the contributed Struts-EL tag library, from the contrib directory.
You'll have to make sure your taglib directive specifies the correct TLD, and you'll
probably want to use a different prefix
Let's see. Is this inside a valid form element? Do you have the
ActionServlet set with a load-on-startup element?
-Original Message-
From: usha [mailto:[EMAIL PROTECTED]]
Hi
can anybody know why i am getting the following error
i am using struts-html tag like this
Note that using the EL (JSTL expression language, with Struts-EL and
JSTL) is not really script. It's considered a good idea to avoid
using runtime JSP expression scriptlets, which these are not. If you
don't use either Struts-EL or the JSTL, it's difficult to do this sort
of thing without using
We would need to see more of your real JSP code, including the taglib directives, and
not just a simulated copy, but the real code.
-Original Message-
From: Dan Tran [mailto:[EMAIL PROTECTED]]
Hi,
I have this code
snippet
html-el:submit value=${action} /
/snippet
The
.
Question, how do I pick up the a property within my form?
ie html-el:submit value=${myform.var}
Thanks
- Original Message -
From: Karr, David [EMAIL PROTECTED]
We would need to see more of your real JSP code, including the taglib
directives, and not just a simulated
You need to have an html:form element. It needs to encapsulate your
select and submit elements. It needs to specify your action path.
Look at the struts-exercise-taglib and numerous other examples for
building a form with form elements.
-Original Message-
From: [EMAIL PROTECTED]
Hi
The first one is closer, but you leave off the .properties part, and just leave the
basename. Make sure the case of the file matches.
-Original Message-
From: JONATHAN PHILIP HOLLOWAY [mailto:[EMAIL PROTECTED]]
Could somebody please tell me whether I can use the following:
Well, normally Struts-EL is part of the nightly build. We're currently having an
unknown problem that is causing it to be missing from the nightly build. The
nightlies from 12/7 and before have it, and also on 12/15, but we appear to have lost
it again on 12/16.
Now, on the documentation
As other people have described, the arg0 attribute is taken as a literal value, or
as a scriptlet value. It isn't interpreted as a bean property.
This is a good reason to use Struts-EL and the JSTL. Your example would look like
this, using Struts-EL:
logic-el:iterate id=item
That appears to be the correct structure. Make sure you get the names correct. Also
note that Tomcat's jspc generates the web.xml excerpt, you shouldn't have to write
this by hand.
-Original Message-
From: Billy Ng [mailto:[EMAIL PROTECTED]]
So, should I do this?
web.xml
No, you cannot. However, it appears that you're trying to do i18n here.
Don't do this in your form bean properties, do it in your resource
properties. That is, store a single symbol value in your form bean, but
store different display values in your properties file based on the
locale.
It just can't find your Action class. Verify that you've put the Action
class into your WAR file properly.
-Original Message-
From: Nathan Pitts [mailto:[EMAIL PROTECTED]]
Hi all,
OK I've got Struts In Action and I'm ready for action!
Unfortunately, my web
app isn't. For
Sorry. Read the JavaBeans specification. A JavaBeans property has only
one type. It's unfortunate that it's not easy to diagnose mistakes in
following the JavaBeans specification. You often get unintelligible
errors like you got.
-Original Message-
From: Sash Sash [mailto:[EMAIL
In Struts tags, the property attribute maps to the HTML name attribute.
-Original Message-
From: Andy Kriger [mailto:[EMAIL PROTECTED]]
I would like to set the HTML name attribute of an input element (e.g.
image). The name attribute in Struts html-tag land refers
to the form bean
I know this is confusing. I think the problem might be that you don't have an indexed
setter on TimeProofFormBean for the element property.
-Original Message-
From: Michael Olszynski [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 12, 2002 8:58 AM
To: [EMAIL PROTECTED]
Subject:
This is the two starting caps rule. I don't know exactly how this translates, as I
try to avoid this situation. Change your property name (in both places) so that the
second character is NOT a capital. I believe this will solve this problem, at least
that part.
-Original Message-
Note that rtexprvalues have to be the ENTIRE attribute value, not just a
portion, so your examples like header-%=countryCode% can't work like
that. If you still wanted to use rtexprvalues, you'd have to use
something like '% header- + countryCode %'.
A cleaner solution is probably to use the
The most important documentation is the JSTL specification. Struts-EL
is very simple. It just uses the JSTL EL engine for evaluating
attribute values. You can get information about the JSTL specification
at http://java.sun.com/products/jsp/jstl/.
-Original Message-
From: Paul
I think I found the problem in the latest code base. Adding styleId to
html-el:image required one more change that I didn't think of. I had to uncomment
the use of the styleId attribute in the BeanInfo class. I've submitted a fix which
will hopefully be in tonight's build (if the problem
: Help! StrutsL-EL error (HTML tag)
Karr, David wrote:
I think I found the problem in the latest code base.
Adding styleId to html-el:image required one more change
that I didn't think of. I had to uncomment the use of the
styleId attribute in the BeanInfo class. I've submitted
You've already figured out most of it. If you use an rtexprvalue, the entire value
needs to be an rtexprvalue, not just a portion. If you use the JSTL, or Struts-EL (or
anything that uses the JSTL EL engine for attribute values), then this sort of thing
gets easier to do, as you can easily
Do you have cvs installed on your local box? Go to a shell prompt and type cvs
--version. If it reports the version of the Concurrent Versions System, then you
should be able to type that entire command line at your prompt.
If you don't get that output, then you should install a version of
No idea. This is the second time in the last month or so this has happened, and I
don't think I ever knew why it happened the first time. It will be fixed.
-Original Message-
From: Hohlen, John [mailto:[EMAIL PROTECTED]]
It looks as the JSTL implementation Struts-EL libraries
First of all, questions like this are better asked on the struts-user list. This
list is for issues related to the internal development of the Struts framework, not
how to use it.
I would guess you would be looking for the Validator framework, which is a standard
part of Struts (and has
It's because of the indexed attribute on tags inside the logic:iterate element.
That won't work (I believe) with c:forEach.
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 05, 2002 1:31 PM
To: 'Struts Users Mailing List'
Subject: Question
If it's possible at all, you might try the first few nightly builds that included
Struts-EL. I know the first one won't work very well, as I made some major mistakes
in the first commit. It was a few days before I got it mostly right. Whether this
(combining 1.1b2 with a nightly struts-el)
101 - 200 of 380 matches
Mail list logo