Re: [S2.1] Dojo plugin tree problem

2008-01-30 Thread Jeromy Evans
Al, There is indeed a related bug, but the issue is only realized when the head tag CANNOT be processed within the current page context. (eg. within a fragment loaded via XHR) https://issues.apache.org/struts/browse/WW-2398 regards, Jeromy Evans Musachy Barroso wrote: you are missing sd:he

Re: [struts-dev] [S2.1] One Step On.... the Dojo plugin tree problem

2008-01-30 Thread Dale Newfield
Dale Newfield wrote: A previous example has a three character solution: https://issues.apache.org/struts/browse/WW-2383 , for this one it appears that a single "!" may be sufficient. Excerpted from : If th

Re: [struts-dev] [S2.1] One Step On.... the Dojo plugin tree problem

2008-01-30 Thread Dale Newfield
Al Sutton wrote: OK, it would appear that if any node in the tree has a null for the value of the child property the following error is reported by FreeMarker; This is really another example of a broader problem with many of the .ftl templates in the struts2 codebase. A previous example has a

Re: [struts-dev] [S2.1] Dojo plugin tree problem

2008-01-30 Thread Dale Newfield
Al Sutton wrote: Now I've got to work out why I'm getting the following error in sitemesh; I think I saw similar exceptions from sitemesh when an earlier component dumped an exception into the stream in a non-valid xml manner. My first suggestion would be to turn off sitemesh and see if a di

[S2.1] One Step On.... the Dojo plugin tree problem

2008-01-30 Thread Al Sutton
OK, it would appear that if any node in the tree has a null for the value of the child property the following error is reported by FreeMarker; Expression stack.findValue(parameters.childCollectionProperty.toString()) is undefined on line 24, column 8 in template/ajax/treenode-include.ftl. The

Re: [S2.1] Dojo plugin tree problem

2008-01-30 Thread Al Sutton
Bingo :). Now I've got to work out why I'm getting the following error in sitemesh; java.lang.ArrayIndexOutOfBoundsException: -1 com.opensymphony.module.sitemesh.html.HTMLProcessor$1.currentBuffer(HTMLProcessor.java:74) com.opensymphony.module.sitemesh.html.State.handleText(State.java:64) com.

Re: [S2.1] Dojo plugin tree problem

2008-01-30 Thread Musachy Barroso
you are missing sd:head on the page. musachy On Jan 30, 2008 12:50 PM, Al Sutton <[EMAIL PROTECTED]> wrote: > I think I've found a problem in the dojo plugin but I'd like someone to > double check I'm not doing anything whacky before raising a JIRA ticket. > > I've got a webapp with the latest sn

Re: [S2.1] Dojo plugin tree problem

2008-01-30 Thread Al Sutton
I'm hugely in favour of that, but it still won't fix our autoboxing problem (if it is one) :). Al. - Original Message - From: "Martin Cooper" <[EMAIL PROTECTED]> To: "Struts Developers List" Sent: Wednesday, January 30, 2008 5:54 PM Subject: Re: [S2.1] Dojo plugin tree problem On

Re: [S2.1] Dojo plugin tree problem

2008-01-30 Thread Martin Cooper
On Jan 30, 2008 9:50 AM, Al Sutton <[EMAIL PROTECTED]> wrote: > I think I've found a problem in the dojo plugin but I'd like someone to > double check I'm not doing anything whacky before raising a JIRA ticket. One of the Dojo devs pinged me the other day to "remind" me that we're still using Do

[S2.1] Dojo plugin tree problem

2008-01-30 Thread Al Sutton
I think I've found a problem in the dojo plugin but I'd like someone to double check I'm not doing anything whacky before raising a JIRA ticket. I've got a webapp with the latest snapshots of core and dojo plugin. I also have a jsp with; <[EMAIL PROTECTED] prefix="sd" uri="/struts-dojo-tags"%

Re: Examples and summaries in wiki via snippet plugin

2008-01-30 Thread Ted Husted
+1 My suggestion would be to retain technically complete but minimalistic Javadocs, and link from the Javadoc to the wikidoc (and also link from the wikidoc to the Javadoc). The underlying goal is to single-source the documentation, and avoid cutting-and-pasting between assets. One way to single-

Examples and summaries in wiki via snippet plugin

2008-01-30 Thread Philip Luppens
Hi all, I agree the snippet macro is quite useful to keep for example attributes for tags in sync with the documentation in the wiki. However, using that same technique to include a summary and/or examples seems to be less fitting. It's often hard to write good and well formatted samples in the j