Hi Robert!
Mike (who commented on the java.lang.Integer etc mapping issue) probably confused int
and Integer (easily done).
Orion has up until now not had a special mapping for Integer & co (it has been
serialized and hence the longvarbinary type).
This has been changed though and they're now supported the way you want them to.
While I'm at it I can bring you up to date with two other issues as well; stateless
session beans are now fully supported (reused etc) and the timeout
bug is gone. The "ghost entity" findByPrimaryKey() bug has also been fixed. Thanks for
your bug-reports (and thanks to all the others who have also
submitted reports), they really help making Orion the top-notch product we all want it
to be.
As for a "sneak preview" one thing that's added in the upcoming version is full EJB
failover. This includes timeouts so if none of the servers (in a server cluster) can
be reached the client waits for a preset time before the call fails. This greatly
improves service availability and so on. A word of warning though - the configuration
files have changed considerably in the next version so we recommend a complete
reinstall (as opposed to the "patch the jars" procedure usually recommended). This is
due to a topology change which will probably lead to some cumbersome (re)learning at
first but will probably benefit most users in the long run.
Somewhat further down the road are features like OR-mapping, full EJB (entity and
session) clustering and graphical configuration/management tools. We're also currently
improving the application-client support.
Have a nice day! :)
/Magnus Stenman, the Orion team
> At 23:21 08.01.00 , Karl Avedal wrote:
>
> Karl,
>
> great to hear. feel much better now (with at least 2 important projects
> being deployed within the next 6 weeks). So we'll keep posting our bug
> reports and questions to the list until the bug tracking system is up and
> wait for the next version (any sneak preview on features?).
>
> Even if I'm becoming a pain in the ass I would still like you to comment on
> one thing I have posted because it is so important to us and probably many
> other people: Are you going to keep your CMP mapping for java types that
> have a corresponding primitive type (e.g. java.lang.Integer) the way it is,
> i.e. to a BLOB type? That way you can never have a database NULL in an
> container-managed database column of type INTEGER, which is something that
> gets you in big trouble in many situations. Although someone else has
> posted it doesn't behave that way (which could indicate, that it is
> jdbc-driver dependent), I can only say that that is what happens
> (autodeployment tries to create a LONGVARBINARY column and mapping to
> INTEGER crashes during runtime with a database exception, something like
> 'invalid type') using orion 0.8.3 with an Oracle 8.0.5 database, which
> should be a common combination. If you suspect ii is driver dependent and
> you don't have Oracle running�, please contact me if I can provide any more
> useful information. btw what setup (OS, databases) do you use for testing?
>
> Thanks for your feedback and again, congratulations on a great product,
>
> Regards,
>
> Robert
>
>
> >Robert,
> >
> >You are right about us being more silent for some time than we want and need
> >to be. I can assure you that this is temporary and (besides the recent
> >holidays) is largely due to the fact of major development and bug fixing
> >being done prior to the release of 1.0. Currently there is no date set for
> >1.0 for a few reasons. There are still bugs that need to be fixed and we are
> >still in discussions with Sun considering the licensing of the Java 2
> >Enterprise Edition brand and compability test suite. The answer still has to
> >be Real Soon Now (TM).
> >
> >To make it easier for you to track what bugs have been fixed and what is
> >still there we have planned to put up a bug tracking system on the site and
> >we hope this will be in place soon to make you get better feedback. We feel
> >confident that serious EJB development works very well with Orion today but
> >we agree that there are bugs that need to be fixed and we are working hard
> >to do so. In the next version coming up soon you will also see some major
> >changes and improvements that we feel will strengthen Orion alot.
> >
> >Until we get the bug tracking system going we will try hard to make sure
> >that we are more visible on this list and comment on bug reports.
> >
> >Regarding source licensing, we currently have no such plans.
> >
> >Best regards,
> >Karl Avedal
> >
>
> (-) Robert Kr�ger
> (-) SIGNAL 7 Gesellschaft f�r Informationstechnologie mbH
> (-) Br�der-Knau�-Str. 79 - 64285 Darmstadt,
> (-) Tel: 06151 665401, Fax: 06151 665373
> (-) [EMAIL PROTECTED], www.signal7.de
>
