[
https://issues.apache.org/jira/browse/MYFACES-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18053000#comment-18053000
]
Werner Punz edited comment on MYFACES-4718 at 1/20/26 8:09 AM:
---------------------------------------------------------------
Yes the original mechanism was done via iframes, seriously, Formdata came
rather late, IE was the last browser to introduce it, I think with IE8 or so,
before that you had to use IFrames!
When the original code was written, there was no FormData on the IE so I had to
support both, I think originally I just had IFrames and then I added FormData.
To keep the rest of the codebase leaner I abstracted it away via a factory
method which delivered me an abstraction which had similar methods to FormData
for both the IFrame and FormData.
And this factory method for whatever reason seems to fail (while it has worked
in the past reasonably well)
The new codebase never has supported iframes to begin with, at that point in
time when I wrote it with the goal of maintainability and on newer browser
standards, this was the first thing I did not even consider to add! (the second
one was classical dom lookup without query api. but even there I added a
functional pattern on top because this makes the queries and subsequent
handling leaner)
was (Author: werpu):
Yes the original mechanism was done via iframes, seriously, Formdata came
rather late, IE was the last browser to introduce it, I think with IE8 or so,
before that you had to use IFrames!
When the original code was written, there was no FormData on the IE so I had to
support both, I think originally I just had IFrames and then I added FormData.
To keep the rest of the codebase leaner I abstracted it away via a factory
method which delivered me an abstraction which had similar methods to FormData
for both the IFrame and FormData.
And this factory method for whatever reason seems to fail (while it has worked
in the past reasonably well)
The new codebase never has supported iframes to begin with, at that point in
time when I wrote it with the goal of trying to keep it maintainable and on
newer browser standards, this was the first thing I did not even consider to
add! (the second one was classical dom lookup without query api)
> Uncaught TypeError: this._getMultipartReqClass(...) is not a constructor
> ------------------------------------------------------------------------
>
> Key: MYFACES-4718
> URL: https://issues.apache.org/jira/browse/MYFACES-4718
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 3.0.3
> Reporter: Volodymyr Siedlecki
> Assignee: Werner Punz
> Priority: Major
> Fix For: 3.0.4
>
>
>
> When uploading a file via ajax, the following exception is encountered:
> {code:java}
> Uncaught TypeError: this._getMultipartReqClass(...) is not a constructor
> multipartQueuedPost
> http://localhost:9080/JSF22InputFile/jakarta.faces.resource/jsf.js.jsf?ln=jakarta.faces&stage=Development:8827
> request
> http://localhost:9080/JSF22InputFile/jakarta.faces.resource/jsf.js.jsf?ln=jakarta.faces&stage=Development:9493
> request
> http://localhost:9080/JSF22InputFile/jakarta.faces.resource/jsf.js.jsf?ln=jakarta.faces&stage=Development:10281
> onchange http://localhost:9080/JSF22InputFile/AjaxFileUploadTest.jsf:1
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
