saving information in a request in jsf

I am new to jsf. I would like to know how to pass informatioin between requests. I am able to pass the object in one direction, but never can get it to make a 'round trip'. For instance, I can pass from jsp to my backing bean OR from backing bean to jsp, but For Some reason it never makes it from jsp to backing bean and back to the jsp(and vice versa).
In the jsf-jsp im using
<% request.setAttribute("objName", obj) %>

In the backing bean I use:
o = (obj)request.getAttribute("objName");
then I get the facescontext, obtain the request, and put the object back into the request using setAttribute once again.

When I check the object in my jsp its null!! Am I missing something? Is there a better way to do this using JSF framework? I should mention, that I dont want to put the Object in the session I only want it to live for a certain amount of time AND I dont want to the responsibility of having to manage removal of these objects from session....anyone have any ideas??

TSS Interop Blog at JavaOne: .NET 3.0 dances with Sun Glassfish

At the JavaOne Conference, Harold Carr, Lead Architect and Arun Gupta, Evangelist at Sun, gave a presentation showing integration between .NET 3.0 and Sun Glassfish applications using Web Services Interoperability Technology, code named Tango.

In the presentation, Carr and Gupta gave a demonstration of how it was possible to use a Microsoft Excel application as a client to post data to a back end server with which a legacy client running on Unix could interact.

Carr said that before the implementation of WSIT, these kinds of features were somewhat limited. The basic Java APIs for XML Web Services (JAX-WS) is specific to HTTP. Glassfish introduces Meta-Data Exchange (MEX), which enables Java and Windows server applications to communicate via multiple channels, such as InfiniBand within the data center.

The WSIT capabilities introduce support for a variety of Web service protocols for improving the integration of applications across the Windows and Java server platforms. WSIT actually consists of a number of Web specifications including WS-Reliable Messaging, WS-Secure, and WS-Trust.

http://tssblog.techtarget.com/index.php/xmlweb-services/tango-day-at-javaone-net-30-dances-with-sun-glassfish/

Occasional XSLT for Experienced Software Developers

Although using XSLT to process XML is increasingly common, most developers still use it only occasionally—and often treat it as just another procedural language. But that's not the best way to use XSLT. Learn how to simplify and improve your XSLT processing using event-driven and declarative techniques from DevX in "Occasional XSLT for Experienced Software Developers."

Spring news roundup

Matt Raible posted a summary of 6 important Spring related news items / article which came out last week, incase you missed them.

Read Spring News Roundup.

Patrick Lightbody: It's the tools, stupid!

In "It's the tools, stupid!, " Patrick Lightbody says: "Patrick Peak came to the conclusion that the main benefit Ruby brings to the table over Java is in the area of the development workflow. This is very true and, in my opinion, is the heart of the Rails vs J2EE/Java/WebWork/Whatever argument. The key thing is, in fact, not Rails, but Ruby. And that's OK."

Part of his summary:
Developer productivity is not to be dismissed lightly. Ruby has a leg up on Java right now because it is inherently a better language. But it is far from a better platform right now, which is unfortunate. So the question is: Which will happen first? Will Ruby get the tools, or will Java get its act together and catch up to Ruby? One, if not both, are bound to happen soon, and no matter what the developers will win.

Message-driven POJOs revisited

Craig Walls has written a sequel to hi Message Driven Pojo's entry. Reacting to questions about the validity of referring to the MDP as a "POJO" because it still must implement javax.jms.MessageListener, this time, with James Strachan's help, Craig shows how to achieve MDPs with pure POJOs (not requiring any external interfaces of any kind).

Read Message-driven POJOs revisited

Longing for an Integrated Maintenance Environment

John Reynolds, in "Longing for an Integrated Maintenance Environment," blogs about life from the IT side as opposed to life on the development side, and how the two have different requirements.