Right. I know there has been some talk about creating a Tomahawk JSF
1.2 branch. I don't imagine that Tomahawk would use the commons before
(and if) this happens anyway. Still, it would be nice to make the
migration as painless as possible. :)
Scott
Leonardo Uribe wrote:
On Thu, Jun 19, 2008 at 5:05 PM, Scott O'Bryan <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hey Leonardo,
Let me take a look at this tonight. As you know, I hope to have
the configurator package checked in soon into commons which will
do this as well. Right now it fits Trinidad's requirements pretty
well but I'd like to see how it stacks up to Tomahawk's. In
trinidad I plan to make their existing File object a wrapper when
used with the commons configurator so that the fileupload
components can be interchangeable. If I can address all of
Tomahawk's requirements as well, then you guys can do the same..
Ok thanks!. Long time ago, I take ExternalContextUtils (because
myfaces-commons-utils is for java 1.5) and correct some stuff to make
it compatible with java 1.4 (on tomahawk is on
org.apache.myfaces.tomahawk.util). Definitively it is necessary to do
something with utils, because trinidad 1.0.x is java 1.4, so this
cannot use myfaces-commons utils.
regards
Leonardo Uribe
Scott
Leonardo Uribe wrote:
Hi
I have made some changes (enabled multipart content support
for TomahawkFacesContextWrapper) on tomahawk.
The objective is have a solution of MYFACES-434 Myfaces
Portlet Enhancement.
I have tested this and works fine for me, but the last time
there was some problems doing this, so better advice dev list
about the changes.
I'm enhancing the documentation and adding fileupload support
for portlets.
Suggestions are welcome
regards
Leonardo Uribe
