Using BaseComponent Question?

[Stanczak Group <ju...@stanczakgroup.com>]

I need a little guidance here. I have a component I'm creating that's 
using the BaseComponent. This component has a PropertySelection 
component in it that submits on change. The reason for this is I have to 
load in the new child classes for that selected Parent then load those 
children into the PropertySelection component so another selection can 
be made. What I'm doing in creating a category selection component that 
will work it's way down the category tree as a user makes a selection. 
While leaving a trail of likes back to the parent categories. Just like 
a path on a web site. The problem I have is I have to values, the 
parameter that is set by the PropertySelection component when submitted, 
and the value I need to update to the page using my component. What this 
involves it checking to see if the PropertySelection's set value is null 
and if it's not then update the value that's returned to the page using 
my component. So my question is where should this logic go? What should 
I override or what interface should I implement?

Another issue with the PropertySelection component submitting on change 
is that the form is submitted and if you don't fill in the required 
fields first you get the warning messages. This is not a huge problem, 
but it would be nice if the component could submit only it's values 
without submitting the whole form. Now if your going to say then put the 
component in it's own form, I have. The problem there is if the user 
does fill in the form first, when they make a selection to the 
PropertySelection component and it submits then their form info is not 
recorded and it get lost. Any suggestions here would be great thanks.

-- 
Justin Stanczak
Stanczak Group
812-735-3600

"All that is necessary for the triumph of evil is that good men do nothing."
Edmund Burke

..________...............__.................
./  _____/..____..._____/..|_..____...____....
/...\..____/.__.\./....\...__\/.._.\./._..\....
\....\_\..\..___/|...|..\..|.(..<_>.|.<_>..)....
.\______../\___.._\__|../__|..\____/.\____/......
........\/.....\/.....\/..........................


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org

Re: Using BaseComponent Question?

[Stanczak Group <ju...@stanczakgroup.com>]

Well I figured out the interface, duh. Started back tracking and 
realized I simply could use the PageRenderListener for this. Now I just 
have the problem where the form submits each time a new category is 
selected. The only way I can figure this could be fixed is with client 
side javascript. But seeing this is categories the can grow quite large 
I'm not sure that's an option. Ajax would probably fix it. Anyone have 
suggestions on this?

Stanczak Group wrote:

> I need a little guidance here. I have a component I'm creating that's 
> using the BaseComponent. This component has a PropertySelection 
> component in it that submits on change. The reason for this is I have 
> to load in the new child classes for that selected Parent then load 
> those children into the PropertySelection component so another 
> selection can be made. What I'm doing in creating a category selection 
> component that will work it's way down the category tree as a user 
> makes a selection. While leaving a trail of likes back to the parent 
> categories. Just like a path on a web site. The problem I have is I 
> have to values, the parameter that is set by the PropertySelection 
> component when submitted, and the value I need to update to the page 
> using my component. What this involves it checking to see if the 
> PropertySelection's set value is null and if it's not then update the 
> value that's returned to the page using my component. So my question 
> is where should this logic go? What should I override or what 
> interface should I implement?
>
> Another issue with the PropertySelection component submitting on 
> change is that the form is submitted and if you don't fill in the 
> required fields first you get the warning messages. This is not a huge 
> problem, but it would be nice if the component could submit only it's 
> values without submitting the whole form. Now if your going to say 
> then put the component in it's own form, I have. The problem there is 
> if the user does fill in the form first, when they make a selection to 
> the PropertySelection component and it submits then their form info is 
> not recorded and it get lost. Any suggestions here would be great thanks.
>

-- 
Justin Stanczak
Stanczak Group
812-735-3600

"All that is necessary for the triumph of evil is that good men do nothing."
Edmund Burke

..________...............__.................
./  _____/..____..._____/..|_..____...____....
/...\..____/.__.\./....\...__\/.._.\./._..\....
\....\_\..\..___/|...|..\..|.(..<_>.|.<_>..)....
.\______../\___.._\__|../__|..\____/.\____/......
........\/.....\/.....\/..........................


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org