Which version of Seam are you using?
I don't really understand why you are trying to achieve? Isn't it the inputstream null because there is nothing to read (or the inputstream was already consumed by JSF)? Are you posting data to this URL? Isn't then better to read the data from a byte array?
If you think that the SeamFilter is the problem you can disable it with @BypassInterceptors on your Bean.
I'm using Seam 2.1.1.GA on Sun App. Server 9.x and I've already tried to read from a byte array and disabled the Seam Filter in web.xml but that didn't work either.
However, when I copy paste the code from the XmlReader component into a Servlet or a Filter, then the inputstream is not empty or null (thus I can read ther content).
Anyway, I'm gonna give the @BypassInterceptors on my bean a try and if that doesn't work, I guess I'm gonna use a Filter.
@BypassInterceptors is also not working.
I ended up by using a Filter (a la Seam way), which reads the request, returns it into a String and puts in the request again (setAttribute). Then I forward the request to the bean by calling chain.doFilter().
This is a workaround and it works, but it's a shame that I can't read the inputstream directly from my bean. That would've bean a much nicer solution.
i'm running in the same problem, too. While building a seam bridge to another servlet application, it is nessecary that this application can read the request.inputStream.
so for now, i will go the same way like serkan, but i also like to suggest to modify org.jboss.seam.web.multipartFilter in a way, that one can access the input data later, after this filter reads all the stuff.
switch to RestEasy , it is a perfect match and can be defined as a Seam component giving you basically access to all Seam components .
Hi, I think have the same problem, but i dont understand your workaround? Can you post some code?
thanks in advance