-
1. Re: tomahawk extension filter and seam fileUpload
shane.bryzak Feb 10, 2007 2:42 AM (in response to milesif)This is because the tomahawk extensions filter wraps the request with its own request wrapper if it's a multipart request. I could get the file upload control to do some reflection gymnastics to unwrap the request if that's the case... let me see what I can do about it.
-
2. Re: tomahawk extension filter and seam fileUpload
shane.bryzak Feb 10, 2007 2:49 AM (in response to milesif)I've committed a change to CVS that should work around this issue. It would be great if you could try it out and let me know if it works or not.
-
3. Re: tomahawk extension filter and seam fileUpload
gavin.king Feb 10, 2007 3:03 AM (in response to milesif)So, Shane was being very nice and helpful, as is his nature. Unfortunately my nature is to be the guy who says "no" to things and pisses everyone off and I've nixed this change. I won't let the Seam codebase become more complex due to workarounds for problems with Tomahawk. The trouble with workarounds like this is that they break everytime Tomahawk internal implementation changes, and thus create a maintainence nightmare for us.
Sorry. -
4. Re: tomahawk extension filter and seam fileUpload
shane.bryzak Feb 10, 2007 3:05 AM (in response to milesif)And just to follow up, I strongly recommend that you look for some alternative to using tomahawk. As a general rule, Seam/tomahawk compatibility is not a priority and there may be other issues in the future for which there will be no easy workaround.
-
5. Re: tomahawk extension filter and seam fileUpload
ffischer Feb 10, 2007 3:12 PM (in response to milesif)Shane,
can you be a bit more precise on the alternatives on using tomahawk? What are you guys using?
Regards,
Frank"shane.bryzak@jboss.com" wrote:
And just to follow up, I strongly recommend that you look for some alternative to using tomahawk. As a general rule, Seam/tomahawk compatibility is not a priority and there may be other issues in the future for which there will be no easy workaround. -
6. Re: tomahawk extension filter and seam fileUpload
shane.bryzak Feb 10, 2007 5:18 PM (in response to milesif)Both ADF/Trinidad and ICEFaces provide a tree control, I believe.
-
7. Re: tomahawk extension filter and seam fileUpload
seto Feb 11, 2007 10:41 AM (in response to milesif)I'm trouble in it, because of the extended datatable providing the newspaper table format. Exploring the ADF and ICEFACES, I found no replacement of the extended datatable.
-
8. Re: (O/T) tomahawk extension filter and seam fileUpload
kukeltje Feb 11, 2007 12:24 PM (in response to milesif)I'll switch to icefaces as soon as someone shows me a working conversation switching, theme switching, a tabswithcing that does show the tab that is selected in one workspace/conversation also in the next workspace AND correct way of configuring all this with facelets. I've had a lot more problems with icefaces than I'd like and a lot less with tomahawk. I do like you guys promoting icefaces, but make them realize that it is a major requirement to have an open issue system up and running... (it is not even on their list on how to build a community)
-
9. Re: tomahawk extension filter and seam fileUpload
gavin.king Feb 11, 2007 12:49 PM (in response to milesif)The icefaces guys have told me that they will have an open JIRA installation available sometime next month.
For now, you can report issues in the "ICE Faces Integration" component in the Seam JIRA (which they are monitoring). -
10. Re: tomahawk extension filter and seam fileUpload
seto Feb 11, 2007 11:26 PM (in response to milesif)So to use the newspaper table, I have to change the newspaper table tag to seam to use? It's so unreasonable.
-
11. Re: tomahawk extension filter and seam fileUpload
gavin.king Feb 12, 2007 12:46 AM (in response to milesif)What is "unreasonable" is that Tomahawk uses a servlet filter to accomplish things that should not require use of such a blunt instrument. There is zero reason why components like a treeview or a table should require a servlet filter to operate. Such things are perfectly able to be implemented using standard JSF mechanisms. In fact, that is exactly why the JSF specification exists!
So if you want to complain, please complain on the MyFaces list! -
12. Re: tomahawk extension filter and seam fileUpload
milesif Feb 12, 2007 4:11 AM (in response to milesif)Sorry for my late reply. I switched back to the tomahawk upload control. I tried to use icefaces (I really like it), but I had problems and no time to solve them.....
I will try them out nex time ;-) and switch to ADF/IceFaces.
Anyway, many thanks to everybody, especially to Shane.
ciao Francesco
PS: and many thanks to "the guy who says no" too. -
13. Re: tomahawk extension filter and seam fileUpload
seto Feb 12, 2007 6:32 AM (in response to milesif)Sorry for my impolite reply. I just get caught by the feature my project needed. It's the newspaper table component. Absoulutely I love Seam and I'm trying my best to make surroundings use Seam while many of Chinese use Spring. I just want the Seam to be perfect to support various feature.
-
14. Re: tomahawk extension filter and seam fileUpload
costeen21 Feb 15, 2007 12:34 PM (in response to milesif)Gavin,
I switched from Tomahawk to IceFaces partly based on your recommendation (see http://www.jboss.com/index.html?module=bb&op=viewtopic&t=95328).
Seam is an awesome product. IceFaces is a good product. Using the products together I've had to do more trial and error programming than desired. I've had some struggles, but the products work much better together with the last few releases of each product. Overall, I've been amazed at how fast Seam and IceFaces have been sending out releases.
I've been waiting to implement the IceFaces file upload component until some of the issues were worked out. Seam has come out with their own file upload component. So now Seam has decided that getting the IceFaces file upload component working with Seam is not a priority (see http://jira.jboss.org/jira/browse/JBSEAM-676 ).
This is great, except I can't get Seam's file upload component it to work with IceFaces which again is what you recommend (I'm trying to get Seam's file upload to work on an IceFaces Tab and/or Popup panel).
I feel like if Seam is going to recommend IceFaces that either 1) Seam should work with the IceFaces file upload or 2) the file upload component that comes with Seam should work with IceFaces. At least one of these two options needs to be a priority, Otherwise, I kind of feel like you've left me out to dry. I hope I'm not coming across as ungrateful because Seam is a great product and I really appreciate all of the Seam's work and how fast you and the team respond to forum issues. I just think one of these items should be a priority.