[OT] JSP 2.0 tag files and expressions

[Laurie Harper]

Sorry for the off-topic post but I'm sure someone here will be able to 
tell me what's going on with this... I'm trying to use the JSTL forEach 
tag in a tag file invoked by another tag file and I'm getting an error. 
Here's an example piece of JSP:

  
v: ${v}
  
That works fine in a JSP. It works fine in a tag file invoked from a 
JSP. But if the tag file is invoked from another tag file, I get the 
error "According to TLD or attribute directive in tag file, attribute 
end does not accept any expressions." I can use the expression language 
in other places (e.g. outside of custom tags) though.

Is this a limitation of tag files or of Tomcat's implementation of them? 
Or am I just doing something wrong? If it's a limitation of the JSP spec 
and/or Tomcat, is there a work-around? Otherwise tag files are about to 
become a whole lot less useful to me... :-(

L.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OT] JSP 2.0 tag files and expressions

[Laurie Harper]

You summed it up perfectly. And that test case works for me too. As does 
my own now. I've no idea what I changed between last night and now, but 
everything's now fine! I'm glad of that but I hate mystery bugs...

L.
Kris Schneider wrote:
This worked on TC 5.0.28:
/WEB-INF/tags/tag1.tag:
---
<%@ tag body-content="empty" %>
<%@ taglib prefix="tags" tagdir="/WEB-INF/tags/" %>

/WEB-INF/tags/tag2.tag:
---
<%@ tag body-content="empty" %>
<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core"; %>

v: ${v}

tagfile.jsp:

<%@ taglib prefix="tags" tagdir="/WEB-INF/tags/" %>





Which generated:

    
    v: 0
v: 1
v: 2
v: 3
v: 4


Is that what you were trying to do?
Quoting Laurie Harper <[EMAIL PROTECTED]>:

Sorry for the off-topic post but I'm sure someone here will be able to 
tell me what's going on with this... I'm trying to use the JSTL forEach 
tag in a tag file invoked by another tag file and I'm getting an error. 
Here's an example piece of JSP:

  
v: ${v}
  
That works fine in a JSP. It works fine in a tag file invoked from a 
JSP. But if the tag file is invoked from another tag file, I get the 
error "According to TLD or attribute directive in tag file, attribute 
end does not accept any expressions." I can use the expression language 
in other places (e.g. outside of custom tags) though.

Is this a limitation of tag files or of Tomcat's implementation of them? 
Or am I just doing something wrong? If it's a limitation of the JSP spec 
and/or Tomcat, is there a work-around? Otherwise tag files are about to 
become a whole lot less useful to me... :-(

L.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Struts boooks: remommendations?

[Laurie Harper]

I'm looking for a good book on Struts, but there seem to be a number of 
choices... Choice is all well and good, but i need some selection 
criteria :-) I'm looking for a book that has comprehensive coverage of 
Struts, is up-to-date, and which focuses on Struts (not a book on web 
application development that happens to talk about Struts along the way, 
for example).

So, what do people recommend? What books have you found most useful in 
that context? From the sample chapters on line it seems like Struts in 
Action may be a good choice but I don't know how up-to-date it is.

Suggestions appreciated :)

L.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

validaton and i18n

[Laurie Harper]

I've finally managed to get the Struts Validator working, thanks to the 
sample chapter on it from Struts in Action. I'm having one small problem 
still, though. When validation fails, I get a blank alery popup.

Looking at the generated Javascript the problem appears to be that the 
message strings aren't populated:

function required () {
 this.aa = new Array("email", "", new Function ("varName", 
"this.mask=/^([!#\\$%&'\\*\\+\\-\\.\\/0-9=\\?A-Z\\^\\x5E_`a-z\\{\\|\\}~]+)@(([0-9a-zA-Z]([0-9a-zA-Z-]*[0-9a-zA-Z])?)(\\.[0-9a-zA-Z]([0-9a-zA-Z-]*[0-9a-zA-Z])?)+)$/; 
 return this[varName];"));
 this.ab = new Array("password", "", new Function ("varName", " 
return this[varName];"));
}

The message keys are defined in the validation.xml file, I think correctly:






mask
^([!#\$%&'\*\+\-\.\/0-9=\?A-Z\^\x5E_`a-z\{\|\}~]+)@(([0-9a-zA-Z]([0-9a-zA-Z-]*[0-9a-zA-Z])?)(\.[0-9a-zA-Z]([0-9a-zA-Z-]*[0-9a-zA-Z])?)+)$







The message resources are defined and, indeed, I can see in the Struts 
debug log that they're being looked up when the form is rendered:

L4J 2004-03-31 19:52:00,945 DEBUG PropertyMessageResources 
getMessage(en_US,errors.required)

L4J 2004-03-31 19:52:00,946 DEBUG PropertyMessageResources 
getMessage(en_US,logon.error.password.missing)
L4J 2004-03-31 19:52:00,946 DEBUG PropertyMessageResources loadLocale(en_US)
L4J 2004-03-31 19:52:00,946 DEBUG PropertyMessageResources 
getMessage(en_US,errors.required)
L4J 2004-03-31 19:52:00,957 DEBUG PropertyMessageResources 
getMessage(en_US,logon.error.email.missing)

They just never get pushed to the page. Here's what I'm using to get the 
form validation in my JSP:

  

...
What have I missed?

Thanks,

L.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tricky configuration?

[Laurie Harper]

Another option might be to use two URL mappings: *.do and /users/*. 
Would that get you what you want?


L.

amol k wrote:


There are several ways to make this transparent to the user!  I can


send details if >you don't know how?

Do send details if you can.
Something like what Martin is suggesting looks like one way.

Thanks.


On 6/3/05, Ray Madigan <[EMAIL PROTECTED]> wrote:


Why are you making your users type in the action anyway.  Why don't you mask
this so they don't know how you implemented it.  There are several ways to
make this transparent to the user!  I can send details if you don't know
how?



-Original Message-
From: amol k [mailto:[EMAIL PROTECTED]
Sent: Friday, June 03, 2005 11:50 AM
To: Struts Users Mailing List
Subject: Re: Tricky configuration?




Why not just map  /do/* to the action servlet insted of *.do


http://myserver/Login.do to http://myserver/do/Login, etc is not an issue
but
Making the users type http://myserver/do/user/blahblah instead of
http://myserver/user/blahblah is a usability issue.
(will have to ultimately do that if there's no other option but I want
to avoid /do before user/blahblah as far as possible)



On 6/3/05, Rick Reumann <[EMAIL PROTECTED]> wrote:


Why not just map

/do/* to the action servlet insted of *.do

Then all of these would go through Struts..

http://myserver/do/Login
http://myserver/do/Logout
http://myserver/do/user/blahblah

This obviously wouldn't go through struts..

http://myserver/pages/blahblah.jsp

amol k wrote the following on 6/3/2005 2:39 PM:


Here is what I am trying to achieve:

http://myserver/Login.do --> (maps to) LoginAction
http://myserver/Logout.do --> (maps to) LogoutAction
http://myserver/user/blahblah --> UserPageAction (notice that there is
no .do in this case. blahblah can be replaced by anything at runtime)

http://myserver/pages/blahblah.jsp --> not handled by ActionServlet


(obviously)


I am trying various combinations in web.xml and struts-config.xml
(including configuring /user as a module) but havent yet found a
decent solution.
Any thoughts?

Thanks in advance.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Rick

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Nested properties in DynaActionForm

[Laurie Harper]

I'm probably missing something really obvious but I've been fiddling 
about with this for a while now. Maybe someone can spot what I'm doing 
wrong...


I'm using DynaActionForms in my Struts app and I'd like to be able to 
reference a property like this:


  

I tried a form declaration like this:

  

  

but I get an error during request processing that 'iterationLength' is 
not a valid property. So then I tried:


  

  

Struts appears to be trying to cope with this:

DEBUG [http8080-Processor24] org.apache.commons.beanutils.BeanUtils - 
setProperty(DynaActionForm[dynaClass=ProjectEdit,startDate=,owner=,mode=,description=,iterationLength={},endDate=,status=,name=,doSave=], 
iterationLength.time, [1])
DEBUG [http8080-Processor24] org.apache.commons.beanutils.BeanUtils - 
  Target bean = {}
DEBUG [http8080-Processor24] org.apache.commons.beanutils.BeanUtils - 
  Target name = time


So it's getting the empty map as the target bean on which to set a 
property 'time'. But when I fetch the map from the form in my action, 
it's empty.


Is there a way to do this? The reason I want to be able to write the 
property as "iterationLength.time", rather than collapsing it to 
'iterationLengthTime' or something is for consistency with when I'm 
accesing the same property in other beans which aren't dynamically 
generated.


Thanks,

L.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DynaActionForm / BeanUtils usage issue

[Laurie Harper]

Code in a unit test:

  DyanActionForm form = new DynaActionForm();
  BeanUtils.copyProperties(bean, form);

This results in a NullPointerException when BeanUtils calls 
form.getDynaClass().getProperties() (or something like that).


BeanUtils is expecting dynaClass to be set, but DynaActionFrom gives me 
no way to set it, unless I create a sub-class. I had to single step 
through the BeanUtils code to figure out what was causing the NPE 
(complicated by the fact that BeanUtils 1.7.0 has an incorrect version 
listed in it's manifest :=( ).


DynaActionFrom should probably either be abstract or provide a setter 
for dynaClass, given that it's currently impossible to create a valid 
instance without sub-classing.


I'll file a bug report against BeanUtils to use guards around uses of 
getDynaClass() if we can't agree a way to ensure it's unnessesary. Can 
Struts do one of the following:


- make DynaActionForm abstract
- make the default constuctor require an initialization value for dynaClass

I'm guessing the answer is no (for backwards compatibility reasons, 
although maybe not if a DynaActionFrom w/out dynaClass set is always 
invalid). In that case BeanUtils will need to be fixed.


Ugly way to spend an evening, this :-)

L.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Nested properties in DynaActionForm

[Laurie Harper]

But I set up iterationLength as a HashMap; I thought BeanUtils could 
handle maps, so it'd do getIterationLength.get("time"). Perhaps I'm 
mixing up BeanUtils and JSTL semantics.


L.

Hubert Rabago wrote:

Nested properties with DynaActionForms actually require you to nest
objects.  :)  Using a property name like "iterationLength.time" would
be like saying "getIterationLength().getTime()", and this is what
BeanUtils would try to do.

Hubert

On 6/7/05, Laurie Harper <[EMAIL PROTECTED]> wrote:


I'm probably missing something really obvious but I've been fiddling
about with this for a while now. Maybe someone can spot what I'm doing
wrong...

I'm using DynaActionForms in my Struts app and I'd like to be able to
reference a property like this:

  

I tried a form declaration like this:

  

  

but I get an error during request processing that 'iterationLength' is
not a valid property. So then I tried:

  

  

Struts appears to be trying to cope with this:

DEBUG [http8080-Processor24] org.apache.commons.beanutils.BeanUtils -
setProperty(DynaActionForm[dynaClass=ProjectEdit,startDate=,owner=,mode=,description=,iterationLength={},endDate=,status=,name=,doSave=],
iterationLength.time, [1])
DEBUG [http8080-Processor24] org.apache.commons.beanutils.BeanUtils -
  Target bean = {}
DEBUG [http8080-Processor24] org.apache.commons.beanutils.BeanUtils -
  Target name = time

So it's getting the empty map as the target bean on which to set a
property 'time'. But when I fetch the map from the form in my action,
it's empty.

Is there a way to do this? The reason I want to be able to write the
property as "iterationLength.time", rather than collapsing it to
'iterationLengthTime' or something is for consistency with when I'm
accesing the same property in other beans which aren't dynamically
generated.

Thanks,

L.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Test whether an application resource is empty

[Laurie Harper]

Try:

  ">
...
  

where 'name' is the name of the attribute your resource bundle is stored 
under.


L.

Chris Loschen wrote:


Hi Wendy,

Thank you very much for your reply.

Yes, I also thought that I could test the key, then check to see if the
value was empty. But just how to do it is eluding me. I think part of
the problem might be this:

USAGE NOTE - If you use another tag to create the body content (e.g.
bean:write), that tag must return a non-empty String. An empty String
equates to an empty body or a null String, and a new scripting variable
cannot be defined as null. Your bean must return a non-empty String, or
the define tag must be wrapped within a logic tag to test for an empty
or null value.

(from the Struts User Guide for bean:define at
http://struts.apache.org/userGuide/struts-bean.html#define).

I'm trying to do something like









	 


But it's failing (I think) because the bean:message returns an empty
String. I would wrap it in a logic tag as suggested, but if I could do
that, I'd just use the same logic for my logic:notEmpty tag instead. So
finding a way to take that value and assign that to a variable which I
can then test to see whether or not it's empty is what I'm trying to do.

It was not my idea to add all of these empty i18n values: the i18n team
did it. If I can't find a way to make this idea work, that's my
alternate path. If that's the road I need to take, I can do it -- I was
just hopeful I could do this a little more elegantly.

Thanks for your input. Any further ideas?

Chris

-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 09, 2005 11:52 AM

To: Struts Users Mailing List
Subject: Re: Test whether an application resource is empty

From: "Chris Loschen" <[EMAIL PROTECTED]>

Quick synopsis: I have localized i18n messages defined in my tiles 
definitions which are sometimes empty. I need to test that the value 
associated with a given key is not empty before I proceed with further



processing. I can test that the key is non-empty, but I haven't yet 
figured out how to test the same thing for the value.



If you can test the key, then it would seem that removing the empty
messages would solve the problem.  Why are the empty ones there in the
first place?
Can you get rid of them?

--
Wendy Smoak


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





___
Siebel
IT'S ALL ABOUT THE CUSTOMER
Visit www.siebel.com

This e-mail message is for the sole use of the intended recipient(s) and 
contains confidential and/or privileged information belonging to Siebel 
Systems, Inc. or its customers or partners. Any unauthorized review, use, 
copying, disclosure or distribution of this message is strictly prohibited. If 
you are not an intended recipient of this message, please contact the sender by 
reply e-mail and destroy all soft and hard copies of the message and any 
attachments. Thank you for your cooperation.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Test whether an application resource is empty

[Laurie Harper]

You want to use the name of the attribute the resource bundle is stored 
under, not the name of the properties file. You're not specifying it in 
your Struts config so you want the following:


  
...
  

L.

Chris Loschen wrote:

Thanks Laurie,

I tried to set it up this way, but wasn't able to make it work. My
struts-config file defines the message-resources parameter like so:



So I tried putting that in, and also tried some variants like
org.apache.struts.ApplicationResources and
org.apache.struts.util.MessageResources in code like this:





	 


But it always returned false, even if there was a value for the key, so
I apparently set up something wrong.

I did get it working using the alternate path, however -- I set up a new
tile in the tiles-defs file which was defined as a zero-length file in
the default case and a small JSP for those cases where I had directions.
The calling JSP looks like this:






And the inserted tile (when I insert a non-zero-length file) looks like
this:

<%
String directionsKey = (String)
request.getAttribute("directionToUserKey");
%>



That is working ok, though of course I don't have the flexibility of
having a value for some locales and no value for other locales. That's
not terribly important.

By the way, just for my own learning: I initially tried to put the
attribute in page scope, but I kept getting a null value: is page scope
specific to a particular JSP (I would have thought that was tile
scope...), or should it be available throughout the sub-elements of a
given page? It works when I use request scope instead, but is that what
is required here?

Thanks again for everyone's help!

Chris Loschen

-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Laurie Harper
Sent: Thursday, June 09, 2005 7:07 PM
To: user@struts.apache.org
Subject: Re: Test whether an application resource is empty

Try:

   ">
 ...
   

where 'name' is the name of the attribute your resource bundle is stored
under.

L.

Chris Loschen wrote:



Hi Wendy,

Thank you very much for your reply.

Yes, I also thought that I could test the key, then check to see if 
the value was empty. But just how to do it is eluding me. I think part




of the problem might be this:

USAGE NOTE - If you use another tag to create the body content (e.g.
bean:write), that tag must return a non-empty String. An empty String 
equates to an empty body or a null String, and a new scripting 
variable cannot be defined as null. Your bean must return a non-empty 
String, or the define tag must be wrapped within a logic tag to test 
for an empty or null value.


(from the Struts User Guide for bean:define at 
http://struts.apache.org/userGuide/struts-bean.html#define).


I'm trying to do something like











But it's failing (I think) because the bean:message returns an empty 
String. I would wrap it in a logic tag as suggested, but if I could do



that, I'd just use the same logic for my logic:notEmpty tag instead. 
So finding a way to take that value and assign that to a variable 
which I can then test to see whether or not it's empty is what I'm


trying to do.

It was not my idea to add all of these empty i18n values: the i18n 
team did it. If I can't find a way to make this idea work, that's my 
alternate path. If that's the road I need to take, I can do it -- I 
was just hopeful I could do this a little more elegantly.


Thanks for your input. Any further ideas?

Chris

-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 09, 2005 11:52 AM
To: Struts Users Mailing List
Subject: Re: Test whether an application resource is empty

From: "Chris Loschen" <[EMAIL PROTECTED]>

Quick synopsis: I have localized i18n messages defined in my tiles 
definitions which are sometimes empty. I need to test that the value 
associated with a given key is not empty before I proceed with further



processing. I can test that the key is non-empty, but I haven't yet 
figured out how to test the same thing for the value.



If you can test the key, then it would seem that removing the empty 
messages would solve the problem.  Why are the empty ones there in the




first place?
Can you get rid of them?

--
Wendy Smoak





___
Siebel
IT'S ALL ABOUT THE CUSTOMER
Visit www.siebel.com

This e-mail message is for the sole use of the intended recipient(s) and 
contains confidential and/or privileged information belonging to Siebel 
Systems, Inc. or its customers or partners. Any unauthorized review, use, 
copying, disclosure or distribution of this message is strictly prohibited. If 
you are not an intended recipient of this message, please contact the sen

Re: Adding parameter to local forwards

[Laurie Harper]

If a redirect rather than a forward is acceptable, you can also look at 
ActionRedirect (new in 1.2.7).


ActionForward fwd = mapping.findForward(...);
ActionRedirect ar = new ActionRedirect(fwd);
ar.addParameter("name", f.getString("name"));
return ar;

L.

Michael Jouravlev wrote:


Something like this:

ActionForward af = mapping.findForward("showParentForm");
return new ActionForward(
  actionForward.getName(),
  actionForward.getPath() + "?drawing_id=24",
  actionForward.getRedirect()
);

You must create a new instance of ActionForward, you cannot change
existing one, since it is frozen.

Michael.

On 6/10/05, Yuniar Setiawan <[EMAIL PROTECTED]> wrote:


Hi all, I have a configuration like this one below:



now inside the SubmitDrawingUploadAction class usually i just need the
following statement to forward to DrawingUpdate.do :
return mapping.findForwards("showParentForm");
the question is, what if I want to add extra parameter?? so it would be
forwarded into DrawingUpdate.do?drawing_id=24
how can I add that 'drawing_id' parameter from inside
SubmitDrawingUploadAction class


?



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [OT] using JSTL with escapeXML="false" for preview HTML

[Laurie Harper]

What's an 'html special space char'?

Lixin Chu wrote:


Hi,
I am trying to preview a piece of html content. but the c:out with
escapeXML=false can not handle space char correctly.

is there an easy way to replace the '  ' with html special space char ?

thanks
lixin



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [HELP]onchange in the tag

[Laurie Harper]

Leandro_Dorileo/[EMAIL PROTECTED] wrote:
onchange="javascript:form.action='value="myFormBean.myProperty"/>';form.submit();">


You can't nest JSP custom tags like that. If you can use JSTL, this will 
work:


  

If you can't use JSTL you'll have to resort to a runtime expression:

  

HTH,

L.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Test whether an application resource is empty

[Laurie Harper]

Doh, I'm an idiot! :-( What I suggested is like trying to call getFoo() 
on the resource bundle bean, where 'Foo' is what ever 
<%=directionToUserKey.toString()%> evaluates to. Clearly not what's 
needed. The following works for me:




using Struts bean/logic


Just replace 'errors.cancel' with '<%=directionToUserKey.toString()%>' 
and you should be set.


Sorry for the confusion,

L.

Chris Loschen wrote:

Thanks again, Laurie, but for some reason it still returns false every
time, even if there is something under that key.  I'm pretty sure I
followed your directions exactly:







Although I did have to pull the key back out of the request in my second
tile -- do I have to do that here as well? I may have to give up for
now, since I have it working the other way, but I'm still curious what I
did wrong.

Chris 


-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Laurie Harper
Sent: Friday, June 10, 2005 2:49 PM
To: user@struts.apache.org
Subject: Re: Test whether an application resource is empty

You want to use the name of the attribute the resource bundle is stored
under, not the name of the properties file. You're not specifying it in
your Struts config so you want the following:

   
 ...
   

L.

Chris Loschen wrote:


Thanks Laurie,

I tried to set it up this way, but wasn't able to make it work. My 
struts-config file defines the message-resources parameter like so:




So I tried putting that in, and also tried some variants like 
org.apache.struts.ApplicationResources and 
org.apache.struts.util.MessageResources in code like this:





		key="<%=directionToUserKey.toString()%>"/>



But it always returned false, even if there was a value for the key, 
so I apparently set up something wrong.


I did get it working using the alternate path, however -- I set up a 
new tile in the tiles-defs file which was defined as a zero-length 
file in the default case and a small JSP for those cases where I had


directions.


The calling JSP looks like this:






And the inserted tile (when I insert a non-zero-length file) looks 
like

this:

<%
String directionsKey = (String)
request.getAttribute("directionToUserKey");
%>



That is working ok, though of course I don't have the flexibility of 
having a value for some locales and no value for other locales. That's




not terribly important.

By the way, just for my own learning: I initially tried to put the 
attribute in page scope, but I kept getting a null value: is page 
scope specific to a particular JSP (I would have thought that was tile



scope...), or should it be available throughout the sub-elements of a 
given page? It works when I use request scope instead, but is that 
what is required here?


Thanks again for everyone's help!

Chris Loschen

-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Laurie Harper
Sent: Thursday, June 09, 2005 7:07 PM
To: user@struts.apache.org
Subject: Re: Test whether an application resource is empty

Try:

  ">
...
  

where 'name' is the name of the attribute your resource bundle is 
stored under.


L.

Chris Loschen wrote:




Hi Wendy,

Thank you very much for your reply.

Yes, I also thought that I could test the key, then check to see if 
the value was empty. But just how to do it is eluding me. I think part




of the problem might be this:

USAGE NOTE - If you use another tag to create the body content (e.g.
bean:write), that tag must return a non-empty String. An empty String 
equates to an empty body or a null String, and a new scripting 
variable cannot be defined as null. Your bean must return a non-empty 
String, or the define tag must be wrapped within a logic tag to test 
for an empty or null value.


(from the Struts User Guide for bean:define at 
http://struts.apache.org/userGuide/struts-bean.html#define).


I'm trying to do something like











But it's failing (I think) because the bean:message returns an empty 
String. I would wrap it in a logic tag as suggested, but if I could do



that, I'd just use the same logic for my logic:notEmpty tag instead. 
So finding a way to take that value and assign that to a variable 
which I can then test to see whether or not it's empty is what I'm


trying to do.


It was not my idea to add all of these empty i18n values: the i18n 
team did it. If I can't find a way to make this idea work, that's my 
alternate path. If that's the road I need to take, I can do it -- I 
was just hopeful I could do this a little more elegantly.


Thanks for your input. Any further ideas?

Chris

-Original Mess

Re: Test whether an application resource is empty

[Laurie Harper]

Chris Loschen wrote:

As I understand it, this would return the error only if there are no
messages at all in the application resource, which is not at all likely
in this context. We're testing whether a particular application resource
(that is, a particular key-value pair in the application resource file)
is empty, not the whole file. 


No, it should return the error only if the resource named resource 
string exists. The key is the 'special' property name 'message(foo)', 
which translates into 'messages.getMessage("foo").


For me, if 'foo' is a valid message key I get the body of the 
 tag displayed; if 'foo' is not defined in my resource 
bundle, I don't.



That said, I still didn't get the results I had hoped for with the new
version either, unfortunately. I didn't get any errors, but it returned
true even when the value was empty. For example, when I had an
application resource key set up like so:

module.admin.manageHierarchy.businessStruc.add.directionToUser=


Hmm, I hadn't tried that; I just tested it and it worked for me.


And my JSP code is set up like this:


 
 
 

It returns notEmpty as true, because I get this in the page:

 

I presume it must be testing that the key exists and is non-zero-length
rather than testing the value. Oh well.


That's odd. Here's a copy/paste of my test, which works as expected:



test 1



property="message(errors.cancel.missing)">

test 2


<% String foo = "errors.cancel.missing"; %>


test 3


That gives me a single paragraph, 'test 1'. Works whether 
'errors.cancel.missing' is actually missing, or defined with an empty 
value as in your example.


If it doesn't work for you I'm out of ideas! :-/

L.



Chris

-Original Message-
From: Nitish Kumar [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 13, 2005 12:54 AM

To: 'Struts Users Mailing List'
Subject: RE: Test whether an application resource is empty




I dont understand some things here, If the application resource is empty
above code would throw this error, "Define tag cannot set a null value".


So how does this code helps in checking wether an application resouce is
empty?

Am I missing some thing here? or may be the subject is misleading.. 



Thanks and Regards,
Nitish Kumar
Tavant Technologies Ltd
Bangalore


-Original Message-
From: Laurie Harper [mailto:[EMAIL PROTECTED]
Sent: Sunday, June 12, 2005 6:30 AM
To: user@struts.apache.org
Subject: Re: Test whether an application resource is empty


Doh, I'm an idiot! :-( What I suggested is like trying to call getFoo()
on the resource bundle bean, where 'Foo' is what ever
<%=directionToUserKey.toString()%> evaluates to. Clearly not what's
needed. The following works for me:

 
 
 using Struts bean/logic
 

Just replace 'errors.cancel' with '<%=directionToUserKey.toString()%>' 
and you should be set.


Sorry for the confusion,

L.

Chris Loschen wrote:


Thanks again, Laurie, but for some reason it still returns false every



time, even if there is something under that key.  I'm pretty sure I 
followed your directions exactly:





		key="<%=directionToUserKey.toString()%>"/>



Although I did have to pull the key back out of the request in my 
second tile -- do I have to do that here as well? I may have to give 
up for now, since I have it working the other way, but I'm still 
curious what I did wrong.


Chris

-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Laurie Harper
Sent: Friday, June 10, 2005 2:49 PM
To: user@struts.apache.org
Subject: Re: Test whether an application resource is empty

You want to use the name of the attribute the resource bundle is 
stored under, not the name of the properties file. You're not 
specifying it in your Struts config so you want the following:


  
...
  

L.

Chris Loschen wrote:



Thanks Laurie,

I tried to set it up this way, but wasn't able to make it work. My 
struts-config file defines the message-resources parameter like so:




So I tried putting that in, and also tried some variants like 
org.apache.struts.ApplicationResources and 
org.apache.struts.util.MessageResources in code like this:





		key="<%=directionToUserKey.toString()%>"/>



But it always returned false, even if there was a value for the key, 
so I apparently set up something wrong.


I did get it working using the alternate path, however -- I set up a 
new tile in the tiles-defs file which was defined as a zero-length 
file in the default case and a small JSP for those cases where I had


directions.



The calling JSP loo

Re: Test whether an application resource is empty

[Laurie Harper]

What you're missing is the next line of code which performs the test. 
The define just makes the resource bundle available. As long as you have 
at least one message resource bundle defined in struts-config.xml the 
line you quote won't fail.


L.

Nitish Kumar wrote:




I dont understand some things here, If the application resource is empty
above code would throw this error,
"Define tag cannot set a null value". 


So how does this code helps in checking wether an application resouce is
empty?

Am I missing some thing here? or may be the subject is misleading.. 



Thanks and Regards,
Nitish Kumar
Tavant Technologies Ltd
Bangalore


-Original Message-
From: Laurie Harper [mailto:[EMAIL PROTECTED]
Sent: Sunday, June 12, 2005 6:30 AM
To: user@struts.apache.org
Subject: Re: Test whether an application resource is empty


Doh, I'm an idiot! :-( What I suggested is like trying to call getFoo() 
on the resource bundle bean, where 'Foo' is what ever 
<%=directionToUserKey.toString()%> evaluates to. Clearly not what's 
needed. The following works for me:


 
 
 using Struts bean/logic
 

Just replace 'errors.cancel' with '<%=directionToUserKey.toString()%>' 
and you should be set.


Sorry for the confusion,

L.

Chris Loschen wrote:


Thanks again, Laurie, but for some reason it still returns false every
time, even if there is something under that key.  I'm pretty sure I
followed your directions exactly:







Although I did have to pull the key back out of the request in my second
tile -- do I have to do that here as well? I may have to give up for
now, since I have it working the other way, but I'm still curious what I
did wrong.

Chris 


-----Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Laurie Harper
Sent: Friday, June 10, 2005 2:49 PM
To: user@struts.apache.org
Subject: Re: Test whether an application resource is empty

You want to use the name of the attribute the resource bundle is stored
under, not the name of the properties file. You're not specifying it in
your Struts config so you want the following:

  
...
  

L.

Chris Loschen wrote:



Thanks Laurie,

I tried to set it up this way, but wasn't able to make it work. My 
struts-config file defines the message-resources parameter like so:




So I tried putting that in, and also tried some variants like 
org.apache.struts.ApplicationResources and 
org.apache.struts.util.MessageResources in code like this:





		key="<%=directionToUserKey.toString()%>"/>



But it always returned false, even if there was a value for the key, 
so I apparently set up something wrong.


I did get it working using the alternate path, however -- I set up a 
new tile in the tiles-defs file which was defined as a zero-length 
file in the default case and a small JSP for those cases where I had


directions.



The calling JSP looks like this:






And the inserted tile (when I insert a non-zero-length file) looks 
like

this:

<%
String directionsKey = (String)
request.getAttribute("directionToUserKey");
%>



That is working ok, though of course I don't have the flexibility of 
having a value for some locales and no value for other locales. That's




not terribly important.

By the way, just for my own learning: I initially tried to put the 
attribute in page scope, but I kept getting a null value: is page 
scope specific to a particular JSP (I would have thought that was tile



scope...), or should it be available throughout the sub-elements of a 
given page? It works when I use request scope instead, but is that 
what is required here?


Thanks again for everyone's help!

Chris Loschen

-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Laurie Harper
Sent: Thursday, June 09, 2005 7:07 PM
To: user@struts.apache.org
Subject: Re: Test whether an application resource is empty

Try:

 ">
   ...
 

where 'name' is the name of the attribute your resource bundle is 
stored under.


L.

Chris Loschen wrote:





Hi Wendy,

Thank you very much for your reply.

Yes, I also thought that I could test the key, then check to see if 
the value was empty. But just how to do it is eluding me. I think part




of the problem might be this:

USAGE NOTE - If you use another tag to create the body content (e.g.
bean:write), that tag must return a non-empty String. An empty String 
equates to an empty body or a null String, and a new scripting 
variable cannot be defined as null. Your bean must return a non-empty 
String, or the define tag must be wrapped within a logic tag to test 
for an empty or null value.


(from the Struts User Guide for bean:define at 
http://struts.apache.org/userGuide/struts-bean.html#define).


I

Wildcard action paths

[Laurie Harper]

I didn't get any response to this last time so I'm asking again... :-)

I'd like to replace URLs like this:

  /Sections/Subsections/?section=Section1&subsection=SubSection1

with URLs like this:

  /Sections/Section1/Subsections/Subsection1

An action mapping like this will match that URL:

  

The problem is, there's then no way to get what the wildcards matched in 
the view (JSP). For reasons discussed elsewhere I don't want to put a 
different action in front of each view, so I need a more general solution.


I'd like to sub-class ForwardAction and put the wildcard matches from 
the URL into a map which can then go into request context. But how can I 
pass the matches *into* the action? I can't user the 'parameter' 
attribute since it's already used to specify where to forward to.


I thought about this:

  

  

But the wildcard URL matching stops working if I do that and anyway I 
don't think dereferencing the matches would work in that context.


So, any other suggestions? The only thing I can think of right now is 
overloading 'parameter', something like


  parameter=".tiles.mytile;section={1},subsection={2}"

and doing the necessary fixup in my action class. Can anyone suggest 
anything better?


L.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wildcard action paths

[Laurie Harper]

Van wrote:

The problem is, there's then no way to get what the wildcards matched in
the view (JSP). For reasons discussed elsewhere I don't want to put a
different action in front of each view, so I need a more general solution.


This seems so obvious to me that I'm probably missing something about
your requirements. Why can't you access the
HttpServleRequest.getRequestURI() method and then process the returned
URI string in your subclass of the Struts ForwardAction? The execute
method for an Action class gets the incoming request object as one of
the parameters. Your subclass can process the URI for the section and
subsection values and set them as request attributes. For that matter,
the request object is available to your JSP pages as well:

  http://tinyurl.com/9jn4d

Of course, you would have to write scriptlet logic or define a JSP
custom tag to encapsulate the logic to parse for the
section/subsection values in order to handle it directly in the JSPs.
All easily doable though. I'm just not seeing what the problem is
here.


The problem with that approach is duplication of information: you have 
to know the URL structure in the action / tag / whatever that does the 
URL parsing, as well as in struts-config.xml. And I don't need a single 
pattern, there would be a number of them, so the URL parsing would 
quickly get messy.


L.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wildcard action paths

[Laurie Harper]

Michael Jouravlev wrote:

On 6/13/05, Laurie Harper <[EMAIL PROTECTED]> wrote:


I didn't get any response to this last time so I'm asking again... :-)

I'd like to replace URLs like this:

  /Sections/Subsections/?section=Section1&subsection=SubSection1

with URLs like this:

  /Sections/Section1/Subsections/Subsection1



You don't want to solve this with mod_rewrite, do you?


No, I don't want to require Apache.

L.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wildcard action paths

[Laurie Harper]

Van wrote:
> Okay. So maybe this isn't the only wildcard mapping you will have.

Still, you could have one SectionAction class for this particular
wildcard mapping. That would be a vast improvement over status quo.

How many different wildcard mappings do you have in this application?


Almost every page will be delivered through a wild-carded action path. 
We're talking a few tens of patterns with varying amounts of similarity.



You could pass one request parameter that indicated which wildcard
pattern was involved. If you don't want to have branching logic, you
could even make this additional request parameter be a property name
and store in your application properties file the regular expression
to use against the incoming request URL to pull out the matching
wildcard values. That should scale generally to any number of
different wildcard mappings using a single Action class that was
driven by these regular expressions coming from your application
properties file.


That's still multiplying the number of places the patterns must be 
stored and processed, and since Struts already does everything I want 
except (apparently) a way to pass the results along that seems like a 
bad idea.


Looks like my original approach (overloading 'parameter') will have to do.

L.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wildcard action paths

[Laurie Harper]

I ended up writing an action which let me do this:

  

The action splits the parameter, builds a map from the name=value pairs 
and sticks it in request scope then resets parameter. Except it doesn't; 
ActionMapping.setParameter() throws a runtime exception, so I have to 
painfully construct a duplicate with the updated 'parameter' value (or 
wrap it in a proxy, which would be a lot better than the 14 lines of 
mNew.setFoo(mapping.getFoo()) I have now!


Ugh. I wish this wasn't so messy :-(

L.

Don Brown wrote:

To add to your original solution:  write your own subclass of
ActionConfig which overrides getParameter() to return the tiles-needed
part of the parameter attribute.  Additional methods will let you
retrieve other parts.  This way, your Action doesn't have to know
about parsing; it can pull clean values out of the ActionConfig
subclass.

Anyways, I know what you mean about this being difficult.  The
set-property seems like a perfect solution, until you realize it is
processed by digester at deploytime, not request-time like the
parameter attribute.  I think the lack of the ability to pass multiple
request-time values to the Action is a serious deficiency in Struts
right now.

Don

On 6/15/05, Laurie Harper <[EMAIL PROTECTED]> wrote:


Van wrote:
> Okay. So maybe this isn't the only wildcard mapping you will have.


Still, you could have one SectionAction class for this particular
wildcard mapping. That would be a vast improvement over status quo.

How many different wildcard mappings do you have in this application?


Almost every page will be delivered through a wild-carded action path.
We're talking a few tens of patterns with varying amounts of similarity.



You could pass one request parameter that indicated which wildcard
pattern was involved. If you don't want to have branching logic, you
could even make this additional request parameter be a property name
and store in your application properties file the regular expression
to use against the incoming request URL to pull out the matching
wildcard values. That should scale generally to any number of
different wildcard mappings using a single Action class that was
driven by these regular expressions coming from your application
properties file.


That's still multiplying the number of places the patterns must be
stored and processed, and since Struts already does everything I want
except (apparently) a way to pass the results along that seems like a
bad idea.

Looks like my original approach (overloading 'parameter') will have to do.

L.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Wildcard action paths

[Laurie Harper]

Don, that absolutely rocks, you're the man! :-) Really, that's exactly 
what I expected and wanted to do in the config file, and that code 
snipet makes things even cleaner. You've just given me the means to 
collapse an ugly hack into a nice, clean, properly encapsulated solution.


Thank you for that. Is this in CVS head, or posted as a patch somewhere?

L.

Don Brown wrote:

Ok, but even if that is what she was wanting, it could still use the
same struts config syntax I pointed out:


   
   
  ...


Then in PathInfoForwardAction:

for (Iterator i = mapping.getProperties().entrySet().iterator();
i.hasNext(); ) {
  Map.Entry entry = (Map.Entry)i.next();
  String key = (String)entry.getKey();
  String value = (String)entry.getValue();
  ...
}

In this way, you still have the clean configuration, and still your
Action can take any number of parameters and do something with them.

Don

On 6/17/05, Van <[EMAIL PROTECTED]> wrote:


On 6/17/05, Don Brown <[EMAIL PROTECTED]> wrote:


Ok, what about this:

I added the ability to pass multiple request-time values to the Action
using the ActionConfig properties.  This means, in your case, your
struts config would look like:


  
  
 ...


In your PathInfoForwardAction, you can now access those values using:
... = mapping.getProperty("foo");
... = mapping.getProperty("bar");


You may have missed that this is only one of 10 or more different
wildcard action mappings in Laurie's application. At least, that is my
understanding now. So, there are different foo/bar names for some of
them and Laurie wanted *one* action to process them all. Of course,
this approach can still work even with that more general requirement
like so:


  
 ...


In your PathInfoForwardAction, you can now extract your wildcard mapping info:

... = mapping.getProperty("wildcards");
// Then split it up into the separate wildcard mapping segments
// with no assumptions about what the foo/bar names will be.
...

-Van
--
- Mike "Van" Riper
 [EMAIL PROTECTED]



Thanks for bringing this up as it has been a problem of mine that I
haven't revisited since before properties were added to ActionConfig
by Joe I believe.  Hopefully this should make things more simple and
straightforward.

Don

On 6/17/05, Laurie Harper <[EMAIL PROTECTED]> wrote:


I ended up writing an action which let me do this:

  

The action splits the parameter, builds a map from the name=value pairs
and sticks it in request scope then resets parameter. Except it doesn't;
ActionMapping.setParameter() throws a runtime exception, so I have to
painfully construct a duplicate with the updated 'parameter' value (or
wrap it in a proxy, which would be a lot better than the 14 lines of
mNew.setFoo(mapping.getFoo()) I have now!

Ugh. I wish this wasn't so messy :-(

L.

Don Brown wrote:


To add to your original solution:  write your own subclass of
ActionConfig which overrides getParameter() to return the tiles-needed
part of the parameter attribute.  Additional methods will let you
retrieve other parts.  This way, your Action doesn't have to know
about parsing; it can pull clean values out of the ActionConfig
subclass.

Anyways, I know what you mean about this being difficult.  The
set-property seems like a perfect solution, until you realize it is
processed by digester at deploytime, not request-time like the
parameter attribute.  I think the lack of the ability to pass multiple
request-time values to the Action is a serious deficiency in Struts
right now.

Don

On 6/15/05, Laurie Harper <[EMAIL PROTECTED]> wrote:



Van wrote:


Okay. So maybe this isn't the only wildcard mapping you will have.



Still, you could have one SectionAction class for this particular
wildcard mapping. That would be a vast improvement over status quo.

How many different wildcard mappings do you have in this application?


Almost every page will be delivered through a wild-carded action path.
We're talking a few tens of patterns with varying amounts of similarity.




You could pass one request parameter that indicated which wildcard
pattern was involved. If you don't want to have branching logic, you
could even make this additional request parameter be a property name
and store in your application properties file the regular expression
to use against the incoming request URL to pull out the matching
wildcard values. That should scale generally to any number of
different wildcard mappings using a single Action class that was
driven by these regular expressions coming from your application
properties file.


That's still multiplying the number of places the patterns must be
stored and processed, and since Struts already does everything I want
except (apparently) a way to pass the results along that seems like a
bad idea.

Looks like my original approach (overloading 'parameter') will have to do.

L.





---

Re: HTML file generated by JSP is truncated...why?...Please help!...source attached

[Laurie Harper]

You're running into a limitation of the JVM I think. Java classes can 
only have a maximum of 64Kb (?) data heap. If you have a very large JSP, 
the generated Java source will contain enough string data to exceed 
that. In my last job our application had one JSP that was sufficiently 
large and complex to run into this. Quite often the JVM would actually 
crash when Tomcat tried to compile the JSP!


If that is indeed the problem, you should be able to solve it sections 
in separate files and re-assembling them with includes in the original JSP.


L.

O. Oke wrote:


Thank you all.

Source code attached and also below.

Please note that it appears to be a maximum number of
xters problem; I am saying this because when I deleted
some blank lines from my JSP source, more HTML code
was  generated.  The problem is that I do not know
where this size is set.

Nevertheless, the source code are as follows:

JSP
===
<%@ page language="java"%>
<%@ taglib uri="/WEB-INF/struts-html.tld"
prefix="html" %>
<%@ taglib uri="/WEB-INF/struts-logic.tld"
prefix="logic" %>
<%@ taglib uri="/WEB-INF/struts-bean.tld"
prefix="bean" %>

">  
 
	


  

  

  

  
   size="20" maxlength="20"> 

 
key="fieldLabel.transferred_on"/> 

  
  
  
   http://localhost/moneyTrans/pages/jsp/reports/repsLOV.jsp',
550, 550, document.forms[0].userRole.value);"
property="collectn_rep_id"  size="10" maxlength="20"
disabled="true"> 


  


 
key="fieldLabel.rep_emp"/> 




  
  

  
  
  
  

  
  
  
  
  
  
  
key="fieldLabel.from_currency"/>
  
  
  
  
  

  
  
  
  
  
  
 
key="fieldLabel.exchange_rate"/> 
   onchange="document.forms[0].exchange_rate.value =

getExchangeRates(document.forms[0].from_country.value
+ document.forms[0].to_country.value);">




  
   disabled="true"> 



  

  
  





  
  
  
  




  
   size="12" maxlength="22" disabled="true">



 
key="fieldLabel.payable_amount"/> 
   size="22" maxlength="22"> 

  
  
  
   size="28" maxlength="40"> 


  


  

  

  
   size="20" maxlength="20" disabled="true">




  
   size="22" maxlength="22"> 

  
 


  
http://localhost/moneyTrans/pages/jsp/reports/payOutPointsLOV.jsp',
550, 550 );"/>

  
   size="30" maxlength="30"> 

 
key="fieldLabel.payout_addr_code"/> 
   size="10" maxlength="10"> 

  
  
  
   size="10" maxlength="10"> 

 
key="fieldLabel.payout_rep_branch_id"/> 
   maxlength="2"> 
  

  
  
   http://localhost/moneyTrans/pages/jsp/reports/sendersLOV.jsp',
550, 550 );" property="sender_id"  size="28"
maxlength="30" disabled="true"> 
 


  
   size="20" maxlength="20"> 


  
   size="20" maxlength="20"> 

  
   
  
key="fieldLabel.sender_id_type"/>
  
  
  


  
   size="12" maxlength="22" disabled="true">



  
  		  
  
key="fieldLabel.status"/>
  
  
  
  
  
  
   size="22" maxlength="22"> 

 
key="fieldLabel.bene_fname"/> 
   size="20" maxlength="20"> 


  
   size="20" maxlength="20"> 
  
 
key="fieldLabel.bene_id_type"/> 

  
  
  
   size="20" maxlength="20"> 


  
   size="20" maxlength="20"> 

 
key="fieldLabel.updated_by"/> 
   size="20" maxlength="20"> 

  
  
  
   size="20" maxlength="20"> 

 
key="fieldLabel.cancelled_by"/> 
   size="20" maxlength="20"> 


  
   size="20" maxlength="20"> 

  
  
  

  
  
   
  



  Save
  Register
Transfer
  Query
Mode
  Get
Transfer
  Delete
Transfer
  


























name="enableFields">
   type="text/javascript">