RE: 1.0 status of MessageBundle and non-serializable application resources

2001-01-10 Thread Matthew Heaton 



I 
tried to get the latest version of struts to run in Weblogic just a day ago and 
ran into non-serializable errors. I made modifications that had been 
suggested in a previous post and everything worked fine, but it doesn't look 
like some of changes made it into the build. The changes I made 
were,

Making 
MessageResourceFactory serializable as well as modifying the setDefaultWriter 
method so it was always set to null.

Making 
sure the following classes were serializable (some were, some 
weren't)

Action
ActionFormBean
ActionFormBeans
ActionForward
ActionForwards
ActionMapping
ActionMappings
ActionServlet

-Matt

  -Original Message-From: Ludwig, Pat 
  [mailto:[EMAIL PROTECTED]]Sent: Wednesday, January 10, 2001 
  1:06 PMTo: Struts-User (E-mail)Subject: 1.0 status of 
  MessageBundle and non-serializable application resources
  hi 
  Craig,
   would you please give a quick report on the status 
  in Struts 1.0 of the proposed change of MessageResources to MessageBundle and 
  conversion of other non-serializable application resources. you had proposed a 
  solution for MessageResources in early December, and i know that a number of 
  changes have been made to 1.0 to rectify other non-serializableproblems. 
  stillthere have been sporadic reports of serialization exceptions with 
  various appservers. will all the changes you proposed be implemented in the 
  1.0 code base? this is really quite an important development issue since it 
  affects a container's ability to re-deploy an application without 
  restarting.
  
  thanks,
  Pat 
  Ludwig

Re: 1.0 status of MessageBundle and non-serializable application resources

2001-01-10 Thread Craig R. McClanahan 

"Craig R. McClanahan" wrote:


 The basic Struts framework no longer creates any non-Serializable servlet
 context attributes.  The new MessageResources implementation was completed
 last week.


As I pointed out in a subsequent message on this thread ... you need to avoid
the use of the data-sources initialization service if your container requires
context attributes to be serializable.  In such cases, the app server will
provide an alternative means (JNDI InitialContext) to gain access to the data
sources you need.

Craig