Senthil Chidambaram wrote:
> The six supported event types by GF can be extended. This is what the
> document says, and that's how GUI is implemented. Sankara has to confirm
> this.
If the DTD only allows the six types, how can I add a new type?
>> If the six event types are primitive, it would make sense for the
>> admin GUI to have specific knowledge of each event type.
>
> Yes, GUI has this knowledge, and that's how the current screen flow is
> for the selected event type when you create a management rule.
What does the GUI do for an unknown event type for which it has no
specific knowledge? How would it know (for example) to display a
calendar component for a string valued property?
>> If the six event types are just a set of events that happened to be
>> delivered with GlassFish, and a user could add other event types, I
>> would hope that the admin GUI would be more open-ended and handle
>> all event types - the six above or user-written - identically.
>>
>> In the latter case, I don't understand how the admin GUI knows to
>> display a string valued property using a calendar component.
>
> Hmm... We don't have an issue here, bcz we've the knowledge of the six
> supported event types. Again, if Sankara feels the other way, we've to
> redo this screen flow completely.
Again, what about event types you don't have knowledge of?
>> And back to the original issue...
>>
>> If we can't remove the pattern property (because the calendar component
>> doesn't support it) because we already delivered the Timer event in
>> GlassFish V1 and removing the pattern would be an incompatible change,
>> and we can't fix the calendar component to accept a pattern, then it
>> seems that we're stuck with not being able to use the calendar component.
>
> Yes, and No. With AJAX in place we can still make use of calendar
> component, some more work though :-) . When user types in the pattern we
> can make an AJAX request to the server, and re-render the calendar
> component again with the specified pattern. Sounds simple :-) , I'll see
> how best I can deliver here. Ken said, he'll also help me to implement
> this, so hopefully we can deliver this screen again with calendar
> component.
Does the calendar component just have the effect of typing in the date
string for you? If you choose the date in the calendar component, can
it use the pattern to format the date string that it's going to enter
for you?