Hi!
> 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.
Of course.
> 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.
Yes, I will try to make it more failure resistant. However, it is a bit
strange that these errors occur, because the way the XML import works is
that it applies the found elements on the structure, instead of explicitly
saying "I need this in the XML". So, it should not break from too little
XML. Nevertheless, I will see if I can make this even more true for this
iteration.
> 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.
Excellent! I will probably try to make a transfer feature which understands
the old format, but writes only the new format.
regards,
Rickard
