I was fixing a bug on this screen that's when I found out the problem on
the calendar component. I believe this screen was implemented by Nitya
to begin with, in consultation with Sankara in IEC. I can check with
Anissa, and see whether we've to redo this screen to support unknown
event types, and I want Sankara to confirm whether unknown types are
supported. I'm cutting, and pasting the two lines from
https://glassfish.dev.java.net/javaee5/selfmanagement/selfmanagementhome.html
"An event triggers the action to be executed. A set of events are
provided by default with the glassfish and user could extend the events
by using JMX Notification mechanism".
The above line indicates to me that users could extend events. If we've
to redo this screen to support unknown event typest, it's not difficult
to do. We've to provide a properties table for users to add properties
as name/value pairs.
thx
Senthil
Bill Shannon wrote:
> Senthil Chidambaram wrote:
>
>> Bill Shannon wrote:
>>
>>> 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?
>>
>>
>> You can't add a new type in the current screen flow. GUI is
>> implemented for the six supported types.
>
>
> First you say I can add a new type and then you say I can't.
> No wonder I'm confused!!! :-)
>
> Did you implement the GUI assuming there would never be any other
> event types?
>
> Or do you plan to completely redo the GUI in the future to support an
> open ended set of event types?
>
> Was it faster or easier to implement a GUI for six built-in types than
> to implement a GUI for an extensible set of types?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>