Re: Stumped with nested iterator and nested link

[Arron Bates]

There was an inconsistency as to how the options were handled in the 
basic link tag's logic which broke the nested extension thereof.
This has been fixed up to be done in a more pessimistic fashion, and now 
available in the jars on my site ( http://www.keyboardmonkey.com/struts 
), or the next nightly build.

To mark it up as you'll need it...
my link thang

my link thang

The first will leave the name of the parameter as the value of paramId 
and take the value from the nested bean property specified 
"paramProperty". The second version, the proeprty value relates to a 
bean property that will refer to a java.util.Map collection that will 
place the key and value pairs into the URL.

Hopefully this will solve the issue. You will need to get new version of 
the tag though. Probably the quickest way is from my site.


Arron.


CyberZombie wrote:

> Arron Bates wrote:
>
>> [ ...cut... ]
>>
>> The nested tags as of mid Jan (nightly build and separate jars) are 
>> able to reference the current parent directly using the "this/" or 
>> "./" properties (same thing, just allowing for different tastes). Any 
>> property with "/" on the end will be treated as a parent reference. 
>> If you use anything else eg "somethingElse/" it will also be treated 
>> as a relative reference and step back through the last parent and 
>> reference the parent object before it.
>>
>> This allows you to write out the String value of the current parent 
>> object, and various other uses like being able to write out a 
>> collection of Strings etc.
>
>
> I guess I just am having a "lack-of-understanding" problem with 
> regards to nested:link then.  When I use the "this/", I still can't 
> get the HREF to be correctly generated.  Given the following:
>
>
>
>
>
>
>
> What is the proper combination (or incantation) of attributes that 
> will append to the page link the query "?transactionKey=1001" (or 
> whatever the current iteration value for 
> transaction.getTransactionKey() is)?
>
>>> Note:  Manipulating the Collection as an Array (IMHO) is not a good 
>>> solution -- and the nested iterator is already pointing at the 
>>> current transaction. 
>>
>>
>>
>> What do you mean by this exactly?...
>
>
> Not really sure any more -- yesterday was a LONG day (as today will be 
> as well...)
>
>
>
> -- 
> To unsubscribe, e-mail:   
> 
> For additional commands, e-mail: 
> 
>
>



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Stumped with nested iterator and nested link

[CyberZombie]

Arron Bates wrote:

> [ ...cut... ]
>
> The nested tags as of mid Jan (nightly build and separate jars) are 
> able to reference the current parent directly using the "this/" or 
> "./" properties (same thing, just allowing for different tastes). Any 
> property with "/" on the end will be treated as a parent reference. If 
> you use anything else eg "somethingElse/" it will also be treated as a 
> relative reference and step back through the last parent and reference 
> the parent object before it.
>
> This allows you to write out the String value of the current parent 
> object, and various other uses like being able to write out a 
> collection of Strings etc.

I guess I just am having a "lack-of-understanding" problem with regards 
to nested:link then.  When I use the "this/", I still can't get the HREF 
to be correctly generated.  Given the following:







What is the proper combination (or incantation) of attributes that will 
append to the page link the query "?transactionKey=1001" (or whatever 
the current iteration value for transaction.getTransactionKey() is)?

>> Note:  Manipulating the Collection as an Array (IMHO) is not a good 
>> solution -- and the nested iterator is already pointing at the 
>> current transaction. 
>
>
> What do you mean by this exactly?...

Not really sure any more -- yesterday was a LONG day (as today will be 
as well...)



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Stumped with nested iterator and nested link

[Arron Bates]

CyberZombie wrote:

> I have a Collection...

[ ...cut... ]

The nested tags as of mid Jan (nightly build and separate jars) are able 
to reference the current parent directly using the "this/" or "./" 
properties (same thing, just allowing for different tastes). Any 
property with "/" on the end will be treated as a parent reference. If 
you use anything else eg "somethingElse/" it will also be treated as a 
relative reference and step back through the last parent and reference 
the parent object before it.

This allows you to write out the String value of the current parent 
object, and various other uses like being able to write out a collection 
of Strings etc.

> Note:  Manipulating the Collection as an Array (IMHO) is not a good 
> solution -- and the nested iterator is already pointing at the current 
> transaction. 

What do you mean by this exactly?...


Arron.


--
To unsubscribe, e-mail:   
For additional commands, e-mail: