Skip to main content

[webtier] JSF2 not passing SelectOneMenu items

6 replies [Last post]
Anonymous

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Ed Burns

>>>>> On Wed, 22 Apr 2009 10:44:53 -0700, Ryan Lubke said:

RL> On 4/21/09 2:25 PM, Lincoln Baxter, III wrote:
>> Excellent, thanks! This is good to hear.
RL> I've just committed changes to support the new functionality.

RL> 1. composite:renderUsingPageChildren has been removed.
RL> 2. composite:insertFacet does just what it says now. It
RL> moves the facet of the composite component to the
RL> parent component in which composite:insertFacet is nested
RL> within.
RL> 3. added composite:insertChildren. This tag moves
RL> the children of the composite component to
RL> the component in which composite:insertChildren is
RL> nested within.
RL> 4. added composite:renderFacet. This should be used
RL> when a composite component has a facet that needs
RL> to be displayed (i.e. it's not a facet of a component
RL> within the composite:implementation section).

Ryan, I've added this attribute to .



If true, and there is no such facet present on the top
level component, a TagException must be thrown, containing
the Location, the facet name, and a localized descriptive
error message.

]]>


required
false

boolean

You mentioned on Skype that it would be useful and I agree. Can you
please ensure it gets added to the implementation?

Thanks,

Ed

---------------------------------------------------------------------
To unsubscribe, e-mail: webtier-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: webtier-help@glassfish.dev.java.net

Ryan Lubke

On 4/23/09 2:13 AM, Ed Burns wrote:
>>>>>> On Wed, 22 Apr 2009 10:44:53 -0700, Ryan Lubke said:
>>>>>>
>
> RL> On 4/21/09 2:25 PM, Lincoln Baxter, III wrote:
>
>>> Excellent, thanks! This is good to hear.
>>>
> RL> I've just committed changes to support the new functionality.
>
> RL> 1. composite:renderUsingPageChildren has been removed.
> RL> 2. composite:insertFacet does just what it says now. It
> RL> moves the facet of the composite component to the
> RL> parent component in which composite:insertFacet is nested
> RL> within.
> RL> 3. added composite:insertChildren. This tag moves
> RL> the children of the composite component to
> RL> the component in which composite:insertChildren is
> RL> nested within.
> RL> 4. added composite:renderFacet. This should be used
> RL> when a composite component has a facet that needs
> RL> to be displayed (i.e. it's not a facet of a component
> RL> within the composite:implementation section).
>
> Ryan, I've added this attribute to.
>
>
>
> >

>
>

Iftrue, and there is no such facet present on the top
> level component, aTagException must be thrown, containing
> theLocation, the facet name, and a localized descriptive
> error message.

>
>

]]>
>
>
> required
> false
>
> boolean
>

>
>
> You mentioned on Skype that it would be useful and I agree. Can you
> please ensure it gets added to the implementation?
>
Yep, checked in about an hour ago.
> Thanks,
>
> Ed
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: webtier-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: webtier-help@glassfish.dev.java.net
>
>

[att1.html]

Ed Burns

>>>>> On Sat, 11 Apr 2009 09:16:17 -0700, Ryan Lubke said:

RL> This is the correct behavior. The 'renderUsingPageChildren' renders the
RL> output of a component in
RL> the location referenced by that tag. If the children being referenced
RL> don't have renderers (as selectItems
RL> do not), then no output will be produced.

RL> Currently, and this may change in time for 2.0, there is no way to
RL> re-locate children of a composite
RL> component to a location within the composite component
RL> implementation.

As Ryan said, it did change. I'll publish another Editor's Draft of the
spec to our public area and announce it on my blog.

Ed

---------------------------------------------------------------------
To unsubscribe, e-mail: webtier-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: webtier-help@glassfish.dev.java.net

Lincoln Baxter, III

Excellent, thanks! This is good to hear.

On Tue, 2009-04-21 at 19:04 +0200, Ed Burns wrote:

> >>>>> On Sat, 11 Apr 2009 09:16:17 -0700, Ryan Lubke said:
>
> RL> This is the correct behavior. The 'renderUsingPageChildren' renders the
> RL> output of a component in
> RL> the location referenced by that tag. If the children being referenced
> RL> don't have renderers (as selectItems
> RL> do not), then no output will be produced.
>
> RL> Currently, and this may change in time for 2.0, there is no way to
> RL> re-locate children of a composite
> RL> component to a location within the composite component
> RL> implementation.
>
> As Ryan said, it did change. I'll publish another Editor's Draft of the
> spec to our public area and announce it on my blog.
>
> Ed
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: webtier-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: webtier-help@glassfish.dev.java.net
>
[att1.html]

Ryan Lubke

On 4/21/09 2:25 PM, Lincoln Baxter, III wrote:
> Excellent, thanks! This is good to hear.
I've just committed changes to support the new functionality.

1. composite:renderUsingPageChildren has been removed.
2. composite:insertFacet does just what it says now. It
moves the facet of the composite component to the
parent component in which composite:insertFacet is nested
within.
3. added composite:insertChildren. This tag moves
the children of the composite component to
the component in which composite:insertChildren is
nested within.
4. added composite:renderFacet. This should be used
when a composite component has a facet that needs
to be displayed (i.e. it's not a facet of a component
within the composite:implementation section).

>
> On Tue, 2009-04-21 at 19:04 +0200, Ed Burns wrote:
>> >>>>> On Sat, 11 Apr 2009 09:16:17 -0700, Ryan Lubke> said:
>>
>> RL> This is the correct behavior. The 'renderUsingPageChildren' renders the
>> RL> output of a component in
>> RL> the location referenced by that tag. If the children being referenced
>> RL> don't have renderers (as selectItems
>> RL> do not), then no output will be produced.
>>
>> RL> Currently, and this may change in time for 2.0, there is no way to
>> RL> re-locate children of a composite
>> RL> component to a location within the composite component
>> RL> implementation.
>>
>> As Ryan said, it did change. I'll publish another Editor's Draft of the
>> spec to our public area and announce it on my blog.
>>
>> Ed
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:webtier-unsubscribe@glassfish.dev.java.net
>> For additional commands, e-mail:webtier-help@glassfish.dev.java.net
>>
>>

[att1.html]

lincolnbaxter@gmail.com

Ill try this out tonight, thanks Ryan!

And thanks both for listening to needs of the community :)

-lincoln
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Ryan Lubke

Date: Wed, 22 Apr 2009 10:44:53
To:
Subject: Re: [webtier] JSF2 not passing SelectOneMenu
items

On 4/21/09 2:25 PM, Lincoln Baxter, III wrote:
> Excellent, thanks! This is good to hear.
I've just committed changes to support the new functionality.

1. composite:renderUsingPageChildren has been removed.
2. composite:insertFacet does just what it says now. It
moves the facet of the composite component to the
parent component in which composite:insertFacet is nested
within.
3. added composite:insertChildren. This tag moves
the children of the composite component to
the component in which composite:insertChildren is
nested within.
4. added composite:renderFacet. This should be used
when a composite component has a facet that needs
to be displayed (i.e. it's not a facet of a component
within the composite:implementation section).

>
> On Tue, 2009-04-21 at 19:04 +0200, Ed Burns wrote:
>> >>>>> On Sat, 11 Apr 2009 09:16:17 -0700, Ryan Lubke> said:
>>
>> RL> This is the correct behavior. The 'renderUsingPageChildren' renders the
>> RL> output of a component in
>> RL> the location referenced by that tag. If the children being referenced
>> RL> don't have renderers (as selectItems
>> RL> do not), then no output will be produced.
>>
>> RL> Currently, and this may change in time for 2.0, there is no way to
>> RL> re-locate children of a composite
>> RL> component to a location within the composite component
>> RL> implementation.
>>
>> As Ryan said, it did change. I'll publish another Editor's Draft of the
>> spec to our public area and announce it on my blog.
>>
>> Ed
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:webtier-unsubscribe@glassfish.dev.java.net
>> For additional commands, e-mail:webtier-help@glassfish.dev.java.net
>>
>>

[att1.html]