Hi!
Dan OConnor wrote:
> I think that making a plugin that can edit both ejb-jar and jboss.xml
> is a step in the right direction, in terms of usability. However, this
> process would probably continue every time we added a new set
> of functionality, e.g. o/r mapping info goes in its own xml file and
> the user wants to edit/view it with the jboss info and the
> deployment descriptor info... If we make a combined plugin every
> time, pretty soon there's no point in plugins and we have a
> monolithic configuration application that we need to maintain.
>
> I'd like to suggest a document/view architecture where you can
> dynamically add views (corresponding to plugins) at runtime. Each
> view/plugin could be represented by a tab on the window, for
> example.
>
> Say you're working with a particular EJB jar. When you open it up,
> you get the generic deployment descriptor view that you get now
> with the EJB 1.1 setting. You could choose to dynamically add
> tabs with new views on the EJB jar, such as an object/relational
> mapping view, a "basic" JBoss-specific settings view, an
> "advanced" JBoss-specific settings view, a JMS view, etc.
Yes, this makes sense. Only have to figure out how to do this in a good
UI way.
/Rickardf
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
