Hi Rickard!
Two comments from me:
a) I would like to be able to keep an existing jaws.xml file like it is.
For example _I_ only specify the non standard tables with jaws.xml and
let the container do the rest for all other tables. I'd like to be able
to keep it that way.
b) I had a really hard time/some trouble lately with loading older
jboss.xml files. There were some fields missing which crashed EJX. Also
starting with an empty file and adding a container configuration
inserted some empty fields (class specification for passivation ?). When
trying to reload the newly generated jboss.xml EJX crashed because the
name of the class was missing. Please take care of such Exceptions in
the future. If it would be possible to work with what EJX was able to
read in so far, that would be really great.
The next time I have some spare time I will setup that "Upgrade"
section, which I mentioned earlier, somehere on the website. Special
notes for how to upgrade the .xml files could go there too.
Cheers,
Tobias
Rickard �berg wrote:
>
> All,
>
> I'm about halfway through the EJX metadata rewrite. All is going well,
> and the results are pretty cool.
>
> For your amusement I have taken a little screenshot of the new GUI:
> http://dreambean.com/download/rickard/ejx.gif
>
> Note the following:
> * Since there is now only one EJX plugin there are no more confusing
> "New" dialogs: when you edit a document you always load and save all 3
> (EJB,JBoss,JAWS), but the JBoss and JAWS files are optional on "Open".
> * Since all three plugins are integrated you can now edit type mappings
> and container configurations and all that in one UI, which is handy.
> * The "Action" menu bar has been removed (people never really found it).
> Instead there is a toolbar with the possible actions. This takes more
> space, but hopefully it will be ok anyway.
> * The GenericCustomizer has a new subclass called
> CompactGenericCustomizer (shown in screenshot) which presents the info
> in a more compact way. This should allow people with lower resolutions
> to use it more easily.
> * The Swing icon collection is used. Looks good :-)
> * Each logical entity (such as a "session" or a "cmp field") has tabs
> for each type of XML file. If a particular type don't care about a
> logical entity (JAWS doesn't care about sessions for example) then it
> will have no tab for that type.
> * During load and store all three types of XML is loaded/stored.
>
> In other words, a heck of a lot better than the current iteration.
>
> If you guys have any other pet peeves that you want me to fix in EJX
> while I'm at it, let me know.
>
> /Rickard
>
> --
> Rickard �berg
>
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
