Rickard, great job! My bean now deploys, with the same code and ejb-jar.xml
file I have been using, with no luck, until now. Thats great!
Reguarding JAWS.XML, how little can I get away with specifying in this
file? I would like to be able to specify just my finder methods, or
whatever else I think I need. If I have a jaws.xml file, need it be
complete, or will it use defaults for anything I don't specify?
Thanks!
Jim
--On Tuesday, May 30, 2000 8:47 PM +0200 Rickard �berg <[EMAIL PROTECTED]>
wrote:
> Hey
>
> It's been a busy day in jBoss hacking land. I have made substantial
> updates to jBoss 2.0, which are now in CVS.
>
> There are too many updates to name them separately, but here are the
> highlights:
> * I have begun adding comments to the source code, mainly the EJB
> container codebase. In doing this I have also cleaned it up
> substantially (such as making sure all the plugins are managed
> appropriately, adding sanity checks, etc.). From now on I will try to
> comment in the source as I write instead :-) But it's been good to go
> over the "old" source and clean it up codewise.
>
> * The EJX GUI has been revamped. I have taken the first steps towards
> extracting the GUI from the model, but it's not quite done yet. Anyway,
> it should look nicer and be easier to work with now.
>
> * Defaults to configuration have been done (Marc had done most of it
> already though). You can now (get this!) download the Pet Store from Sun
> and deploy the EJB part of it out of the box! :-) Whoa!! Of course this
> doesn't mean that much since stateful sessions and BMP isn't done yet,
> and the mail sessions are impossible to do by defaults, but still. Major
> improvement.
>
> * More EJBObject methods are handled in the proxy, such as hashCode and
> isIdentical. This takes away many server roundtrips and should speed up
> any apps that use these methods a lot.
>
> * The transaction manager have been fixed somewhat. There's a new JMX
> service that manages it, and binds it in JNDI for others to use.
>
> * The AutoDeployer have been fixed. If the deployment fails the
> autodeployer should be able to keep on working.
>
> * There's a cool new option in the jBoss configuration: call logging.
> Set it to true and all calls to EJB's will be logged. Slows down the
> performance, but can be crucial for development and testing.
>
> Well, that's about it (plus about 50+ minor changes). If there aren't
> any major bugs found as a result of this update, I propose that a new
> binary is created. Heck, this crap is almost usable now :-)
>
> over 'n out,
> Rickard
>
> --
> Rickard �berg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
