Aaron Mulder <[EMAIL PROTECTED]> wrote:
> Now that I have a bit of a better understanding of the whole
>deployment process for jBoss, EJX is growing on me. While the open
>process still makes little sense to me for individual XML files, it worked
>great on a JAR as a whole. And now that I've been through the whole
>deployment twice, I think I've figured out where all the critical
>right-mouse functions live. I'll back off from my earlier stance of utter
>confusion - I think next time I deploy something it'll be quick and
>painless.
I agree that EJX has improved immensely over the last few weeks.
> However, in the interest of first-timers everywhere, I'll
>contribute a couple observations toward future EJX revisions:
>
> - Please, please don't make me select ejb-jar.xml when you're actually
>going to edit jboss.xml or jaws.xml. I fought that one for a *while*.
>
Please add your comments to Bug #4 in Bugzilla.
> - Let's put all the commands in the same place, whether on a menu or a
>right-mouse or in buttons or whatever. It's quite frustrating when you
>discover critical functions by accident while clicking around in
>frustration.
>
> - I would definitely support a unified editing interface, rather than
>repeatedly closing and reopening the ssame file or JAR.
>
> - It's simple, but let's remember the last directory opened and default
>to that on the next open/save. My files are never in the same directory
>as ejx.jar.
Take a look at Bug 78, and possibly 77, and add any comments you see
fit.
>
> - Can we make it clear somehow what names are JNDI names and what names
>are arbitrary? I was never sure.
>
> - Let's use drop-downs everywhere we possibly can. The most irksome
>omission to me is the container configuration type ("Default Stateless
>SessionBean", etc).
It would be good if you could add specific comments to Bugzilla - it's a
much better collective memory for bugs/improvements than the mail list,
and it supports focused discussion of specific issues.
Justin
>
>Aaron
>
>
--
Justin Forder
