As per our analysis..We don't think that the Select works when embedded
inside a component with the "value" attribute of the select as generic Enum
type.
To recreate this, create a component with Select. While including this
component in other pages, pass the Enum to this component. Now try to a
> model="literal:Red,Green,Blue"/> //Line 6
>
> - From the parent pages, we include our editselectfield.tml as shown below:
> fieldType="relationship" lable="Status" addDesc="Add your relationship
> status"/>
> Where relationship is Enum :
> public enum Relationship {
> RS1, RS2,
Hi Howard,
Thanks for your advice.
As per your advice, I changed the model to literal type but still the same.
Further, I attached Tapestry source code(5.2.1) along my debug path and
found that the enumClass.getEnumConstants() at line #41 of EnumSelectModel
class was returning NULL only for the
Make sure you enum type is not in a controlled package, such as
x.y.z.components or x.y.z.pages.
On Tue, Jan 25, 2011 at 12:29 PM, Howard Lewis Ship wrote:
> Very odd:
>
> @SuppressWarnings("unchecked")
>
> SelectModel defaultModel()
>
> {
>
> Class valueType = resources.getBo
Very odd:
@SuppressWarnings("unchecked")
SelectModel defaultModel()
{
Class valueType = resources.getBoundType("value");
if (valueType == null)
return null;
if (Enum.class.isAssignableFrom(valueType))
return new EnumSelectModel(val
It's in the stack trace:
Caused by: org.apache.tapestry5.ioc.internal.util.TapestryException [at
classpath:com/skyecandy/components/EditSelectField.tml, line 6]
at
org.apache.tapestry5.internal.structure.ComponentPageElementImpl.invoke(ComponentPageElementImpl.java:993)
at
org.apache.
Hi,
This is the second issue that we are facing while migrating from Tapestry
5.1.0.5 to Tapestry 5.2.4. To add to your information, we are using
Hibernate 3.6, Hibernate Search 3.3, Spring 3.0.5, Tapestry Spring Security
3.0
Could any one of you please share your experience in solving this is
