Presumably this is based on 1.5.4?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of sana
> Sent: Wednesday, 27 March 2002 2:05 PM
> To: Orion-Interest
> Subject: OC4J 9.0.3
>
>
> Hi,
>
> Oracle released OC4J 9.0.3 Developer Preview.
>
> http:
I will be out of the office starting 03/26/2002 and will not return until
04/08/2002.
I will respond to your message when I return.
Hi,
Oracle released OC4J 9.0.3 Developer Preview.
http://otn.oracle.com/tech/java/oc4j/content_preview.html
It supports most of J2EE 1.3 features.
http://otn.oracle.com/tech/java/oc4j/htdocs/oc4j-feature-list.html
Regards,
sana
__
Do You Ya
I have discovered a strange bug with orion after enabling "Content Advisor"
in both IE 5.5 and 6.0. The problem is that the default.jsp is being
executed after every request, causing a "duplicate" erroneous request.
I have created a simple test to duplicate the problem. I tested 1.5.2 and
1.5.4
At 12:17 PM 3/25/2002, you wrote:
>Hi,
>does anyone know when Orion will be 100% EJB 2.0 compatible including
>local/remote inerfaces EJB-QL ...
>
>Michael
I would just be happy with the JMS working correctly, have the JMS message
types don't work at all!
This includes most of the really ne
sans ejb-ql, 1.5.4 is compatible.
I understand from some Oracle types that ejb-ql will be out later this
summer.
many-many is broken in 1.5.4, but Magnus et al indicate its fixed in
bugzilla for 1.5.5
regards,
the elephantwalker
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMA
Seems the original went missing, again.
> -Original Message-
> From: Geoff Soutter [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, 26 March 2002 3:46 PM
> To: 'Orion Interest List'
> Cc: [EMAIL PROTECTED]
> Subject: FYI/PATCH: Log4j bug masks part of Orion's stack traces
>
>
> Hi there,
>
At this point, Orion does support local/remote interfaces, CMP/CMR, etc (The
experimental Orion
1.5.4), with some bugs they are still working out (many-to-many CMR for instance).
EJB-QL isn't in
there yet - don't know when it will be. You may try contacting Ironflare directly for
more concise
i