|
In
regards to WL6, although this may not fix anyones particular problems, we
noticed one thing with the beta version we have. Anyting in the /WEB-INF/lib dir
does not automatically become part of the classpath. I assume this is (or was) a
bug with WL6. It works fine in Orion App Server. As per the spec, the
WEB-INF/lib and WEB-INF/classes dirs get included as part of the classpath
automatically, as does the vendor specific /lib dir (if they have it) and I
think the /jdk-dir/ext does too?
After seeing the talk about the API changes, I just downloaded the
latest nightly build (01-23 binary version) and tried to deploy the example
application to WebLogic 5.1 but it failed miserably with all kinds of XML
related errors. I also tried to run the example app on JRun, but this failed
as well (but with minor errors when JSP compiling- related to passing a string
into the setLocale(), setFilter() perhaps also due to XML
parsing?)
Anyway, Struts 0.5 works for me on WL5.1 now on both of my development
PCs so I am going to have to use this for now since I don't have time to
figure out how to make the 1.0 build work. Hopefully this is as simple as
suggested in the previous emails (I looked back a few weeks at the various
threads). Or better yet, maybe my problem is just with my XML parser (I am
using jaxp1.0.1).
If
anyone has successfully deployed the Struts v1.0 example application on
WL5.1 please let me know... I may experiment some more with this next
week.
Thanks,
Bob
Hi,
I'm currently buzy to migrate an application working on Tomcat to
Weblogic 6.0
The problems with the PropertyMessageRessource class is not yet solved,
but Craig confirmed me some days ago that he was working on it.
Anyway, even if that problem still exist, it is possible to use
Struts with webLogic 6.0, by doing the small modifications
in MessageRessourceFactory ( it must be Serializable and de
setPrintWriter must initialize the printWriter to null ).
Otherwise I didn't had others problems ( I don't really know about the
datasource problem, since I'm using an EJB implementation). except for small
context path problems.
Thierry
Thierry Cools
Senior Java Developer
S1 Brussels
Kleine Kloosterstraat, 23
1932 st. Stevens-Woluwe
Belgium
Tel : +32 2 200 43 82
Email : [EMAIL PROTECTED]
----- Original Message -----
Sent: Tuesday, January 23, 2001 4:31
PM
Subject: Struts and Weblogic
6.0
Memo from Nic Hobbs of
PricewaterhouseCoopers
-------------------- Start of message text
--------------------
Hi All,
I know there have been many
threads over the last few months concerning Weblogic
5.1 and Struts and
also WLS 6.0, particularly with respect to the
example
application.
Could someone let me know what the
situation is with this now? I.e. Is there an
intention to make the
example app work on WLS 6.0 and are there any aspects of
struts that
will not work on WLS 6.0 as a result of the serialization issues
(and
where are we with these too!). What is the situation with the change of
the
properties to use XML, properties files and database for
storing
internationalised strings?
Any information would be
gratefully received as we are currently evaluating
using struts but
Weblogic has already been chosen as the target
platform.
TIA,
Nic
--------------------- End of
message text --------------------
The principal place of business
of PricewaterhouseCoopers and its associate
partnerships is 1
Embankment Place, London WC2N 6NN where lists of the
partners' names
are available for inspection. All partners in the
associate
partnerships are authorised to conduct business as agents of,
and all
contracts for services to clients are with,
PricewaterhouseCoopers. The UK
firm of PricewaterhouseCoopers is
authorised by the Institute of Chartered
Accountants in England and
Wales to carry on investment business.
PricewaterhouseCoopers is a
member of the world-wide
PricewaterhouseCoopers
organisation.
----------------------------------------------------------------
The
information transmitted is intended only for the person or entity to
which
it is addressed and may contain confidential and/or privileged
material. Any
review, retransmission, dissemination or other use
of, or taking of any action
in reliance upon, this information by
persons or entities other than the
intended recipient is
prohibited. If you received this in error, please
contact
the sender and delete the material from any
computer.
|
