Tom Cook wrote:
>
> I think the whole thing is caused by misuse of the file-open dialog
> box. When you want to open an existing ejb-jar.xml you need to select
> the file in this dialog and then change the file type to 'EJB 1.1 XML'
> from it's default, jBoss XML. If you want to edit a jboss.xml or
> jaws.xml you still need to select ejb-jar.xml in the dialog but then
> change the file type to the appropriate type.
>
> This seems kinda counter-intuitive to me.
I agree. Considering how easy-to-use the rest of jBoss is, EJX, while
useful, is difficult to figure out. I must have played with it for an
hour before I got what I wanted out of it...
I think if the interface let you "import" your existing ejb-jar.xml into
a newly created jboss.xml, it would be more clear. Something like:
File>New
<dialog>
Pick jboss.xml from a radio list including ejb-jar.xml, jaws.xml,
jboss.xml.
Select a checkbox that lights up for choices other than ejb-jar.xml
titled "Import ejb-jar.xml".
Select a ejb-jar.xml file with a browse button that lights up for
choices other than ejb-jar.xml.
Click OK.
</dialog>
This pattern could work for cross importing from various files. Perhaps
a super-simple file manager allowing your to work with all three files
at once.
Just some thoughts...
Thanks,
Tim
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
