thanks elephant walker ...
its really good to get some news that orion is still moving forward
-----Original Message-----
From: The elephantwalker [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 4 September 2001 1:09 PM
To: Orion-Interest
Subject: bug fixes
Group,
Although 1.5.2 and oc4j 1.0.2.2.0 aren't exactly the same, the new
release
of oc4j (1.0.2.2.1) has several bug fixes that may be fixed in the next
version of Orion. OC4J 1.0.2.2.1 came out on August 17.
Here's a list of bug fixes in 1.0.2.2.1 (from the oc4j readme file).
Regards,
the elephantwalker
OC4J fixes in 9iAS 1.0.2.2.1
=============================
1853961 - RMI tunneling through HTTP
Two EJBs could not communicate through a firewall using
standard RMI HTTP-tunneling. The program would get the
initial context, but the lookup operation would fail.
This has been fixed in release 1.0.2.2.1.
1851047 - Compilation error when exclusive-write-access=false
EJB deployment failed when setting exclusive-write-access
to false in orion-ejb-jar.xml. The problem has been fixed
in this release.
1904888 - Constructor for bean throws CreateException
Bean Constructor throwing CreateException caused EJB
deployment to fail. This problem has also been fixed in
release 1.0.2.2.1.
1910155 - The session bean reference was still available after
runtime exception during a transaction.
1929873 - MessageLogger Demo broken
The demo has been fixed. It also includes a readme.txt
that outline configuration steps to run the demo.
1826744 - NLS: RequestDispatcher's path query string doesn't take
multi-byte characters.
This has been fixed in release 1.0.2.2.1.
Query string containing multi-byte characters can be
passed to included/forwarded pages.
1806219 - NLS: request.getLocales() doesn't parse the
accept-language correctly
The problem has been fixed and accept-language is
correctly parsed in this release(1.0.2.2.1)
1806193 - NLS: response.getCharacterEncoding() always returns
ISO-8859-1
The locale was disregarded and
response.getCharacterEncoding always returned ISO-8859-1.
1806276 - NLS: response.setContentType() has no effect on JspWriter
encoding
The character set attribute was not being picked up when
using request.setContentType. This has been fixed in this
release(1.0.2.2.1).
1910946 - JspWriter does not print "NULL", when a null object is
passed to print()
1911268 - JspWriter flush() did not actually flush buffer to client
1913403 - NLS: request.setCharacterEncoding() did not reset parsed
parameters
1808513 - NLS: Servlet engine doesn't support Thai encoding TIS-620
When using the IANA name of Thai character set (TIS-620)
PrintWriter used to return UnsupportedEncodingException error.
This problem has been fixed in this release(1.0.2.2.1)
1913863 - NLS: response.sendError() doesn't display multi-byte message
correctly
1883653 - usertransaction.setTransactionTimeout() did not function.
Fixed in this release(1.0.2.2.1)
1883670 - OC4J did not throw NotSupportedException when starting new
transaction before commit or rollback of current transaction
1937950 - Session cookie wasn't secure enough
This has been fixed in this release(1.0.2.2.1) by cookies
being
atleast 128 bits and using strong cryptography.
