You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by tapestrycn <ta...@yahoo.com.cn> on 2005/07/23 01:31:03 UTC
Re: Is there a bug for dual Select components?Bug still exits!
Bug still exists with following snippet:
<select jwcid="@Select">
<span jwcid="@Foreach" source="ognl:colorsList"
value="ognl:synColor">
<span jwcid="@Option" label="ognl:synColor"
selected="ognl:synSelected"/>
</span>
</select>
<select jwcid="@Select">
<span jwcid="@Foreach" source="ognl:colorsList2"
value="ognl:synColor2">
<span jwcid="@Option" label="ognl:synColor2"
selected="ognl:synSelected2"/>
</span>
</select>
The org.apache.hivemind.ApplicationRuntimeException always thrown with message:
Select components may not be nested.
I'm upgrading my project now,the problem is much more urgent!Can anybody help
me?
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Is there a bug for dual Select components?Bug still exits!
Posted by Nick Westgate <ni...@jellyfish.co.nz>.
Patrick Casey <patcasey <at> adelphia.net> writes:
> The poor guy may very well not be up to that though. If we really
> want tapestry to be useful to inexperienced or "new" developers, then asking
> them to just "tweak" the components themselves isn't the way to go.
Hi Pat. (Damn this gmane interface's top-posting prohibition!)
Of course, your point is valid in the general case.
But when converting a project to a beta release, we
should expect to get our hands dirty, don't you think?
I've only been using Tapestry for a year, but the
component code is actually pretty simple to get into.
Still, I'm not playing with version 4 yet.
> That's the thing that always makes me a little uncomfortable about
> open source communities. As the community matures and gets more and more
> experienced with its own product, it tends to get less welcoming and more
> dismissive of newcomers and their concerns e.g. that's not a bug, it's a
> feature, duh! I mean seriously, try asking *any* question on the Hibernate
> forums and watch the snarking sneers begin. Great product, lousy, insular,
> and arrogant community.
Well, happily this list is quite different, don't you think?
Personally, I try to remember to start every email with a greeting,
and sign off with my name. Even little bits of netiquette like that
can make emails much friendlier.
> I guess what I'm saying is give the guy a break.
Well, I think everyone here has done just that.
I see Robert has just posted some helpful suggestions.
Assuming there are no more new bugs to be found there. ;-)
Cheers,
Nick.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Is there a bug for dual Select components?Bug fixed.
Posted by tapestrycn <ta...@yahoo.com.cn>.
Thanks you
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: Is there a bug for dual Select components?Bug still exits!
Posted by Patrick Casey <pa...@adelphia.net>.
The poor guy may very well not be up to that though. If we really
want tapestry to be useful to inexperienced or "new" developers, then asking
them to just "tweak" the components themselves isn't the way to go. Sure, a
good programmer (or just an intermediate one with good knowledge of
tapestry), can do this, but a good programmer with sufficient time can do
damn near anything (except solve the traveling salesman problem).
That's the thing that always makes me a little uncomfortable about
open source communities. As the community matures and gets more and more
experienced with its own product, it tends to get less welcoming and more
dismissive of newcomers and their concerns e.g. that's not a bug, it's a
feature, duh! I mean seriously, try asking *any* question on the Hibernate
forums and watch the snarking sneers begin. Great product, lousy, insular,
and arrogant community.
I don't think that's specifically what Geoff was trying to do here,
but it's a fear that always lurks in the back of my mind in cases like this.
I'm as guilty of this as anyone, I'm sure, but I still think its something
we should try to look out for.
Ultimately, we can't assume that anyone who uses tapestry is:
A) An experienced java programmer.
B) Familiar with the classic design patterns.
C) Comfortable running ant.
D) Comfortable modifying somebody else's code.
E) Either already aware of, or capable of easily discerning, the
overall code structure of the Tapestry code base.
If we insist on the above as a minimum to be a member of the "club"
then we've just pained tapestry into a corner where it's never going to get
the kind of widespread following we all (I assume) hope it gets.
I guess what I'm saying is give the guy a break.
--- Pat
> -----Original Message-----
> From: news [mailto:news@sea.gmane.org] On Behalf Of Nick Westgate
> Sent: Friday, July 22, 2005 9:33 PM
> To: tapestry-user@jakarta.apache.org
> Subject: Re: Is there a bug for dual Select components?Bug still exits!
>
> Patrick Casey <patcasey <at> adelphia.net> writes:
>
> >
> >
> > Probably because it's frustrating to find a bug (or at least think
> > you've found a bug) and have folks neither confirm, nor deny the bug,
> but
> > instead question why the hell you're doing things a particular way :).
>
> No excuse. Probably 99% of posts like this are not bugs.
> Geoff's question was entirely reasonable, since the example code
> provided did not indicate multiple selections.
>
> Anyway "tapestrycn", you can work around the bug by downloading the source
> for Tapestry, copying the Select component into your project, and making
> your own customised Select component.
>
> Patch the java source as follows:
> protected void cleanupAfterRender(IRequestCycle cycle)
> {
> _rendering = false;
> _selections = null;
>
> cycle.removeAttribute(ATTRIBUTE_NAME);
> }
>
> Cheers,
> Nick.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Is there a bug for dual Select components?Bug still exits!
Posted by Nick Westgate <ni...@jellyfish.co.nz>.
Patrick Casey <patcasey <at> adelphia.net> writes:
>
>
> Probably because it's frustrating to find a bug (or at least think
> you've found a bug) and have folks neither confirm, nor deny the bug, but
> instead question why the hell you're doing things a particular way :).
No excuse. Probably 99% of posts like this are not bugs.
Geoff's question was entirely reasonable, since the example code
provided did not indicate multiple selections.
Anyway "tapestrycn", you can work around the bug by downloading the source
for Tapestry, copying the Select component into your project, and making
your own customised Select component.
Patch the java source as follows:
protected void cleanupAfterRender(IRequestCycle cycle)
{
_rendering = false;
_selections = null;
cycle.removeAttribute(ATTRIBUTE_NAME);
}
Cheers,
Nick.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Is there a bug for dual Select components?Bug still exits!
Posted by Geoff Longman <gl...@gmail.com>.
It is a bug in Tapestry 4. Somewhere along the line a call to
cycle.removeAttribute(ATTRIBUTE_NAME); was dropped in Select.java.
But, Howard has changed/moved things around so much in that class I
don't want to monkey with it.
Add a bug in Jira and paste this message in.
'night all.
Geoff
PS. I never use Select or Option. The only time I needed multiple
selection I created my own component (based on the PropertySelection
code). Easy to do, give it a try.
On 7/23/05, Patrick Casey <pa...@adelphia.net> wrote:
>
> Probably because it's frustrating to find a bug (or at least think
> you've found a bug) and have folks neither confirm, nor deny the bug, but
> instead question why the hell you're doing things a particular way :).
>
> Me: Hi, GM, my car stalls whenever I turn right!
> GM: Why don't you just make 3 lefts?
>
> I haven't a clue if he actually found a bug mind you, but I suspect
> that was the motivation behind his CAPS :).
>
> --- Pat
>
> > -----Original Message-----
> > From: Geoff Longman [mailto:glongman@gmail.com]
> > Sent: Friday, July 22, 2005 8:52 PM
> > To: Tapestry users
> > Subject: Re: Is there a bug for dual Select components?Bug still exits!
> >
> > why are you yelling at me?
> >
> > On 7/22/05, tapestrycn <ta...@yahoo.com.cn> wrote:
> > > PropertySelection doesn't support MULTIPLE selection!
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > >
> > >
> >
> >
> > --
> > The Spindle guy. http://spindle.sf.net
> > Get help with Spindle:
> > http://lists.sourceforge.net/mailman/listinfo/spindle-user
> > Announcement Feed:
> > http://www.jroller.com/rss/glongman?catname=/Announcements
> > Feature Updates: http://spindle.sf.net/updates
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
>
>
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Announcement Feed:
http://www.jroller.com/rss/glongman?catname=/Announcements
Feature Updates: http://spindle.sf.net/updates
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: Is there a bug for dual Select components?Bug still exits!
Posted by Patrick Casey <pa...@adelphia.net>.
Probably because it's frustrating to find a bug (or at least think
you've found a bug) and have folks neither confirm, nor deny the bug, but
instead question why the hell you're doing things a particular way :).
Me: Hi, GM, my car stalls whenever I turn right!
GM: Why don't you just make 3 lefts?
I haven't a clue if he actually found a bug mind you, but I suspect
that was the motivation behind his CAPS :).
--- Pat
> -----Original Message-----
> From: Geoff Longman [mailto:glongman@gmail.com]
> Sent: Friday, July 22, 2005 8:52 PM
> To: Tapestry users
> Subject: Re: Is there a bug for dual Select components?Bug still exits!
>
> why are you yelling at me?
>
> On 7/22/05, tapestrycn <ta...@yahoo.com.cn> wrote:
> > PropertySelection doesn't support MULTIPLE selection!
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> >
> >
>
>
> --
> The Spindle guy. http://spindle.sf.net
> Get help with Spindle:
> http://lists.sourceforge.net/mailman/listinfo/spindle-user
> Announcement Feed:
> http://www.jroller.com/rss/glongman?catname=/Announcements
> Feature Updates: http://spindle.sf.net/updates
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Is there a bug for dual Select components?Bug still exits!
Posted by Geoff Longman <gl...@gmail.com>.
why are you yelling at me?
On 7/22/05, tapestrycn <ta...@yahoo.com.cn> wrote:
> PropertySelection doesn't support MULTIPLE selection!
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Announcement Feed:
http://www.jroller.com/rss/glongman?catname=/Announcements
Feature Updates: http://spindle.sf.net/updates
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Is there a bug for dual Select components?Bug still exits!
Posted by Robert Zeigler <ro...@scazdl.org>.
Here are some options supporting multiple selects:
1) Try using contrib:Palette -- neat component; nice for many things,
slightly pricey on the screen real-estate. :)
2) Try using "SelectMultiple" (available from tassel at:
http://equalitylearning.org/Tassel/app?service=external/ViewComponent&sp=SSelectMultiple)
3) Try writing a custom PropertySelectionRenderer and plugging it into
contrib:MultiplePropertySelection
Robert
tapestrycn wrote:
> PropertySelection doesn't support MULTIPLE selection!
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Is there a bug for dual Select components?Bug still exits!
Posted by tapestrycn <ta...@yahoo.com.cn>.
PropertySelection doesn't support MULTIPLE selection!
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Is there a bug for dual Select components?Bug still exits!
Posted by Geoff Longman <gl...@gmail.com>.
Why don't you use PropertySelection?
Geoff
On 7/22/05, tapestrycn <ta...@yahoo.com.cn> wrote:
> Bug still exists with following snippet:
>
> <select jwcid="@Select">
> <span jwcid="@Foreach" source="ognl:colorsList"
> value="ognl:synColor">
> <span jwcid="@Option" label="ognl:synColor"
> selected="ognl:synSelected"/>
> </span>
> </select>
>
> <select jwcid="@Select">
> <span jwcid="@Foreach" source="ognl:colorsList2"
> value="ognl:synColor2">
> <span jwcid="@Option" label="ognl:synColor2"
> selected="ognl:synSelected2"/>
> </span>
> </select>
>
>
> The org.apache.hivemind.ApplicationRuntimeException always thrown with message:
> Select components may not be nested.
>
> I'm upgrading my project now,the problem is much more urgent!Can anybody help
> me?
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
The Spindle guy. http://spindle.sf.net
Get help with Spindle:
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Announcement Feed:
http://www.jroller.com/rss/glongman?catname=/Announcements
Feature Updates: http://spindle.sf.net/updates
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org