I'm not 100% positive how EJX works but from what I can tell you /always/ open
ejb-jar.xml, and the filter that you choose determines the options presented
to you.
If this is a correct statement, I believe a more appropriate user interface
would be one of the following:
1) Give the user all possible options
2) Give the user 3 tabs, EJB 1.1, JAWS, EJB + Jboss that each contain their
own respective configuration options.
I tend toward #2.
Another problem w/ the interface is the "Action" button. It needs to be more
prominently displayed as a button, so some type of border might be useful.
Also, when no actions exist maybe gray it out.
Just some possibilities..
Louis
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Dan OConnor
> Sent: Wednesday, October 18, 2000 10:36 AM
> To: jBoss
> Subject: RE: [jBoss-User] Confused about ejx
>
>
> At a former job I once had a tool that needed to work with two
> configuration files and an ODBC connection at the same time. I
> built an "open wizard" that presented three successive screens
> with a "next" button at the bottom.
>
> We could do something similar with EJX in situations where
> multiple files were required. So, if you only wanted to work with an
> ejb-jar.xml, you'd just open it. But if you wanted to work with a
> jboss.xml file, you'd be presented with a multi-page dialog that first
> asked the name of the jboss.xml file, and then asked for the
> associated ejb-jar.xml file.
>
> What do you guys think of this approach?
>
> -Dan
>
>
> On 18 Oct 00, at 10:26, Louis R. Marascio wrote:
>
> > Aye, extremely counter-intuitive and very confusing for the first
> time user.
> > It took me 2 days to figure out that I /wasn't/ going insane and
> that I didn't
> > have some crazy, old deprecated version of EJX. Alas, I finally
> figured out
> > the trick and the steps that I had to go through to get some use
> out of the
> > tool. Its now very handy :).
> >
> > Someone should probably write up a document about this.. maybe an
> EJX first
> > time user's guide?
> >
> > Louis
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]]On Behalf Of Tom Cook
> > > Sent: Wednesday, October 18, 2000 3:58 AM
> > > To: jBoss
> > > Subject: Re: [jBoss-User] Confused about ejx
> > >
> > >
> > > 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.
> > >
> > > Tom
> > >
> > > Rickard Oberg writes:
> > > > Hi!
> > > >
> > > > > 1. ejb-jar.xml opens in EJX, but seems to be missing primary key
> > > > > specifications for the beans. Also, the Actions menu in EJX only
> > > > > displays one choice: Add JNDI Name Prefix. Is the implementation
> > > > > incomplete (e.g. missing primary key stuff and others
> stuff?) How do
> > > > > you add things like environment, ejb, and resource references
> > > to a bean?
> > > > > Where are the Actions menu options to add these things?
> > > >
> > > > You seem to be referring to the jBoss editor, not the
> EJB-JAR.xml editor.
> > > > Make sure you choose the right file filter!
> > > >
> > > > > 2. When I tried to open the bank test's jaws.xml or
> jboss.xml, I get a
> > > > > null pointer exception. Here's a sample stack trace...
> > > > >
> > > > > java.lang.NullPointerException
> > > > > at
> com.dreambean.ejx.editor.EJX$2.actionPerformed(EJX.java:94)
> > > >
> > > > Don't have the source available right now so I can't check. Can
> > > you add this
> > > > to bugzilla?
> > > >
> > > > > 3. A side issue, but does anyone know how I can easily
> reformat the xml
> > > > > produced by ejx so it is properly formatted? As indicated
> above, I'm
> > > > > using NT.
> > > >
> > > > What is the formatting issue? EJX uses an XML parser to
> > > read/write files so
> > > > we're pretty much stuck with how it does it.
> > > >
> > > > regards,
> > > > Rickard
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > --------------------------------------------------------------
> > > > To subscribe: [EMAIL PROTECTED]
> > > > To unsubscribe: [EMAIL PROTECTED]
> > > > Problems?: [EMAIL PROTECTED]
> > > >
> > >
> > >
> > > --
> > > --------------------------------------------------------------
> > > To subscribe: [EMAIL PROTECTED]
> > > To unsubscribe: [EMAIL PROTECTED]
> > > Problems?: [EMAIL PROTECTED]
> > >
> >
> >
> >
> > --
> > --------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> > Problems?: [EMAIL PROTECTED]
> >
>
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
