I need to render an image which is persisted in an entity ejb.

After looking at the docs and source code of Tapestry, as far as I
see, the simplest approach seems to be making an implementation of
IAsset that looks for the appropiate image from the
data access layer and returns it from the getResourceAsStream()
method.

Could this work?

I have some questions about this.

Which is the life cycle of the IAsset implementations?
This question raise at the point of making an implementation which
takes some parameters in the constructor (parameters that gives the
implementor a reference to the data access layer and info for looking
for the correct image).

Apparently, this parameters should be encoded in the URL in buildURL()
and parsed to extract them back in getResourceAsStream() from
cycle.getServiceParameters() so at this point the instance variables
initialized in the constructor and used in buildURL() are expected to
have the same values or is this a new instance of the implementor?

How the AssetService connects back to this IAsset implementation to
ask the getResourceAsStream() method for the appropiate data?

mmm... I'm lost.

-- 
Saludos,
 Pablo                          mailto:[EMAIL PROTECTED]

"The only thing that interferes with my learning is my education."
Albert Einstein





-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer

Reply via email to