-
Notifications
You must be signed in to change notification settings - Fork 19
Ajax fileupload capabilities #802
Comments
Reported by werpu12 |
Issue-Links: |
@edburns said: |
@edburns said: |
@edburns said: |
@edburns said:
|
@edburns said: |
@edburns said: |
rogerk said: |
ganeshpuri said: |
werpu12 said: I am going to investigate further if setting the request header is possible on |
werpu12 said: The problem really is we currently have two mechanisms, one identifying that it The idea is following, introduce a third type, iframe request, and allow both As for the proposed mechanism. My personal idea is to enqueue an iframe request (see the preliminary snapshot code here http://www.pastebin.org/396667 and As how and when we trigger the mechanism is a little bit unclear to me still, my |
@edburns said: |
@edburns said: |
@edburns said: http://www.jsftoolbox.com/documentation/tomahawk/09-TagReference/tomahawk-inputFileUpload.html |
@edburns said: |
markcolletteice said: It would be nice to collaborate on moving parts of this into JSF, so that everyone's different file upload components could be built on a common infrastructure. One critical issue to us is that we don't follow the pattern of simply sticking the file contents into a temporary byte[] or file, like the other component frameworks do. We allow for either directly writing the file to the end file-system destination that the application specified, or using a callback interface for chunking the file data, without buffering the whole file, to the application, so that it can virus scan the file contents, or re-transmit it to another server via a socket, or write it to a database. So, we'd like the file processing to be custom for the component framework, that way we're not limited by a lowest common denominator handling of file data. http://wiki.icefaces.org/display/ICE/FileEntry |
ngriffin7a said: In my comments there,mentioned that I implemented a solution in the PortletFaces Bridge. It's working quite nicely – no need for Servlet 3.0, no need for a filter. Everything works great. Making this work in a Servlet-based JSF like Mojarra should be a piece of cake. |
tedgoddard said:
|
werpu12 said: So you can define jsf.ajax.request with additional myfaces: {transportType: "iframeRequest"} etc.. options to force the system into an iframe request. We also allow an auto transport option where the system changes from the default xhr level1 into iframe if a multipart file upload situation is detected. The problem with xhr level3 simply is or was the last time I looked at it that most browsers issued multipart requests without length attributes which rendered most fileupload libraries useless (and broke one of the two related specs in that area) But as I see it xhr level3 is a good option if you can support it properly because it also allows some kind of progress notification so if this issue is started we also should opt for xhr level3 optionally. The http header issue was another one. Currently the jsf ajax cycle is determined over custom http header, which is a no go in an iframe scenario because you only can send parameters, this needs to be fixed (and I did an internal fallback in myfaces to fix this but this is currently an implementation detail. the jsf.ajax.response is another issue relatively unrelated, in myfaces we have some internal params which fix some internal issues, like how do you fix the issue of having an update and your original element is detached as well as its parent form. Those kind issues simply have to be taken care of in the official spec then I guess the jsf.ajax.response is really public. |
@edburns said: |
@edburns said: These are the files that differ from the state of the tree when he created that branch. These files were committed in r9162. Index: common/ant/dependencies.xml |
@edburns said: |
File: 20110613-i_spec_802_mods.txt |
@edburns said: |
File: 20111208-i_spec_802-mods.patch |
werpu12 said: |
@edburns said: |
@edburns said: |
robweaver said: Upload widget acts as if the upload is working, but never hits the back end event handler. Reverting to 3.1 with no changes to WAR and the file upload works again. Would be glad to help diagnose this issue. Any target date for the fix, and is there a workaround ? |
@edburns said: Can I ask you please to file this in the GLASSFISH JIRA? I know some multipart upload changes were done in GlassFish 3.1.2 and t's quite possible this has nothing to do with Mojarra JSF implementation. At any rate, it certainly doesn't have anything to do with the spec. http://java.net/jira/browse/GLASSFISH Thanks, |
robweaver said: Apologies for the incorrect entry. |
rogerk said: |
@edburns said: |
File: 20121102-werpu-AjaxFileupload.odt |
@edburns said: |
@arjantijms said: |
rogerk said: |
Marked as fixed on Tuesday, April 30th 2013, 11:42:09 am |
jid1 said: |
@edburns said: Here's the yes part. You can say this:
and it renders correctly:
but the no part is that each of the files in the multiple list is overwritten when the next one is processed. |
@edburns said: |
This issue was imported from java.net JIRA JAVASERVERFACES_SPEC_PUBLIC-802 |
The main issue with the current implementation is, that fileupload the ajax way
is not working properly.
The problem simply is, that fileupload component and multipart form requests
both are a second class citizen in the JEE world and html generally.
There is no way to submit a fileupload via ajax currently, however there is an
iframe based method to do it.
But for that an iframe transport layer is missing, since the current spec only
talks abut queued asynchronous xhr requests.
see http://www.openjs.com/articles/ajax/ajax_file_upload/
for more information....
Environment
Operating System: All
Platform: Macintosh
Affected Versions
[2.0]
The text was updated successfully, but these errors were encountered: