Re: 2.2.0 and multipart

2014-03-10 Thread Howard W. Smith, Jr.
Leonardo Uribe, see below. I think this is the thread where Karl discussed
his fileUpload issue, and shared a test case (below), too.




On Tue, Mar 4, 2014 at 9:18 AM, Karl Kildén karl.kil...@gmail.com wrote:

 Leonardo Uribe, Thanks for doing a test with this already.

 Everyone, this is how I reproduced it in a test project:


- Cloned Gerhards template
 project:https://github.com/os890/javaweb-cdi-ds-project-template
- Ran with mvn clean install jetty:run -
http://localhost:8080/javaweb-cdi-ds-project-template/helloWorld.xhtml-
 
 Wrote my name and pressed Press Me and it successfully navigated.
- Changed helloWorld.xhtml and added enctype=multipart/form-data to
the form.
- Ran project with mvn clean install jetty:run - it does not work
- Ran project with mvn clean install jetty:run -Pmojarra - works (Note
that mojarra profile is used)


 To conclude with a normal form Gerhards project template works just fine.
 It works fine with mojarra in either case. With Myfaces and
 enctype=multipart/form-data it does not work.

 I tried this several times with the same result.

 Deltaspike and Myfaces is what's in common with my normal stack. No
 Primefaces needed for reproduce

 cheers







 On 4 March 2014 14:58, Karl Kildén karl.kil...@gmail.com wrote:

  Well for me it breaks the form completely. Even if I have only a single
  component h:commandButton/ it's broke. Adding the primefaces parameter
  has no effect. I will try to put a test application together
 
 
  On 4 March 2014 14:17, Leonardo K. Shikida shik...@gmail.com wrote:
 
  Karl
 
  I haven't tested it, but Howard figured out that it may be a primefaces
  problem in their autodetection algorithm
 
  I haven't tested myself yet, but it seems it's just a matter of adding
  this
  parameter explicitly
 
  context-param
  param-nameprimefaces.UPLOADER/param-name
param-valuecommons/param-value
  /context-param
 
  best regards
 
  Leo
 
 
  []
 
  Leo
 
 
  On Tue, Mar 4, 2014 at 4:37 AM, Karl Kildén karl.kil...@gmail.com
  wrote:
 
   Leo,
  
   I have the same problem, What's your status?
  
   cheers
  
  
   On 22 February 2014 02:58, Leonardo K. Shikida shik...@gmail.com
  wrote:
  
Hi
   
Just noticed this thread about tomee, myfacs 2.2.0 and multipart
  request
   
   
   
  
 
 stackoverflow.com/questions/21948228/how-to-get-jsf-file-upload-to-work-on-tomee-1-6
   
does anyone know if between 2.1.13 and 2.2.0, multipart request has
  got
   any
new bug? could not find anything in JIRA
   
the guy who posted the stackoverflow question tested with
   
h:commandButton while I've reproduced the problem just switching
myfaces jars from vanilla tomee 1.6.0 from 2.1.13 to 2.2.0 and using
p:fileUpload
   
[]
   
Leo
   
  
 
 
 



Re: 2.2.0 and multipart

2014-03-10 Thread Karl Kildén
Yes, Also https://issues.apache.org/jira/browse/MYFACES-3865




On 10 March 2014 21:35, Howard W. Smith, Jr. smithh032...@gmail.com wrote:

 Leonardo Uribe, see below. I think this is the thread where Karl discussed
 his fileUpload issue, and shared a test case (below), too.




 On Tue, Mar 4, 2014 at 9:18 AM, Karl Kildén karl.kil...@gmail.com wrote:

  Leonardo Uribe, Thanks for doing a test with this already.
 
  Everyone, this is how I reproduced it in a test project:
 
 
 - Cloned Gerhards template
  project:https://github.com/os890/javaweb-cdi-ds-project-template
 - Ran with mvn clean install jetty:run -
 
 http://localhost:8080/javaweb-cdi-ds-project-template/helloWorld.xhtml-
  
  Wrote my name and pressed Press Me and it successfully navigated.
 - Changed helloWorld.xhtml and added enctype=multipart/form-data to
 the form.
 - Ran project with mvn clean install jetty:run - it does not work
 - Ran project with mvn clean install jetty:run -Pmojarra - works
 (Note
 that mojarra profile is used)
 
 
  To conclude with a normal form Gerhards project template works just fine.
  It works fine with mojarra in either case. With Myfaces and
  enctype=multipart/form-data it does not work.
 
  I tried this several times with the same result.
 
  Deltaspike and Myfaces is what's in common with my normal stack. No
  Primefaces needed for reproduce
 
  cheers
 
 
 
 
 
 
 
  On 4 March 2014 14:58, Karl Kildén karl.kil...@gmail.com wrote:
 
   Well for me it breaks the form completely. Even if I have only a single
   component h:commandButton/ it's broke. Adding the primefaces
 parameter
   has no effect. I will try to put a test application together
  
  
   On 4 March 2014 14:17, Leonardo K. Shikida shik...@gmail.com wrote:
  
   Karl
  
   I haven't tested it, but Howard figured out that it may be a
 primefaces
   problem in their autodetection algorithm
  
   I haven't tested myself yet, but it seems it's just a matter of adding
   this
   parameter explicitly
  
   context-param
   param-nameprimefaces.UPLOADER/param-name
 param-valuecommons/param-value
   /context-param
  
   best regards
  
   Leo
  
  
   []
  
   Leo
  
  
   On Tue, Mar 4, 2014 at 4:37 AM, Karl Kildén karl.kil...@gmail.com
   wrote:
  
Leo,
   
I have the same problem, What's your status?
   
cheers
   
   
On 22 February 2014 02:58, Leonardo K. Shikida shik...@gmail.com
   wrote:
   
 Hi

 Just noticed this thread about tomee, myfacs 2.2.0 and multipart
   request



   
  
 
 stackoverflow.com/questions/21948228/how-to-get-jsf-file-upload-to-work-on-tomee-1-6

 does anyone know if between 2.1.13 and 2.2.0, multipart request
 has
   got
any
 new bug? could not find anything in JIRA

 the guy who posted the stackoverflow question tested with

 h:commandButton while I've reproduced the problem just switching
 myfaces jars from vanilla tomee 1.6.0 from 2.1.13 to 2.2.0 and
 using
 p:fileUpload

 []

 Leo

   
  
  
  
 



Re: 2.2.0 and multipart

2014-03-10 Thread Howard W. Smith, Jr.
Karl, did you see the email below, and did you try that sample, and did
that work for you?



On Tue, Mar 4, 2014 at 10:30 AM, Howard W. Smith, Jr. 
smithh032...@gmail.com wrote:

 wow, okay. :)

 Earlier, Leonardo Uribe mentioned the following:

 I can confirm a simple example using MyFaces 2.2.0 works. See:

 http://jsflive.wordpress.com/2013/04/23/jsf22-file-upload/

 Looking forward to hearing why your/Karl's test case does not work.



 On Tue, Mar 4, 2014 at 10:26 AM, Karl Kildén karl.kil...@gmail.comwrote:

 Removing deltaspike has no effect. / Karl


 On 4 March 2014 16:23, Howard W. Smith, Jr. smithh032...@gmail.com
 wrote:

  Have you reported this to Deltaspike? I wonder what happens when you
  'remove' delta spike from the equation/mix, and see if stuff/stack
 starts
  working. :)
 
 
 
  On Tue, Mar 4, 2014 at 9:55 AM, Karl Kildén karl.kil...@gmail.com
 wrote:
 
   It made no difference for me / Karl
  
  
   On 4 March 2014 15:52, Karl Kildén karl.kil...@gmail.com wrote:
  
Nice spot, In my production environment I changed it but I will test
  that
aspect in the template project
   
   
On 4 March 2014 15:50, Howard W. Smith, Jr. smithh032...@gmail.com
   wrote:
   
On Tue, Mar 4, 2014 at 9:18 AM, Karl Kildén karl.kil...@gmail.com
 
wrote:
   
 Everyone, this is how I reproduced it in a test project:


- Cloned Gerhards template
 project:https://github.com/os890/javaweb-cdi-ds-project-template

   
h,
   
examining the faces-config.xml, i see 2.0 specified instead of 2.1
 (or
2.2).
   
faces-config version=2.0
xmlns=http://java.sun.com/xml/ns/javaee;
xmlns:xi=http://www.w3.org/2001/XInclude;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd;
   
/faces-config
   
   
When MyFaces 2.2 was released, i don't think I saw any mention of a
'requirement' to update faces-config, accordingly, but it would be
  nice
   to
know if faces-config.xml has to be updated with '2.2' or 2.1.
   
   
   
  
 





Re: 2.2.0 and multipart

2014-03-10 Thread Karl Kildén
Howard,

No that sample does not work for me. The details are in the jira.


On 10 March 2014 21:47, Howard W. Smith, Jr. smithh032...@gmail.com wrote:

 Karl, did you see the email below, and did you try that sample, and did
 that work for you?



 On Tue, Mar 4, 2014 at 10:30 AM, Howard W. Smith, Jr. 
 smithh032...@gmail.com wrote:

  wow, okay. :)
 
  Earlier, Leonardo Uribe mentioned the following:
 
  I can confirm a simple example using MyFaces 2.2.0 works. See:
 
  http://jsflive.wordpress.com/2013/04/23/jsf22-file-upload/
 
  Looking forward to hearing why your/Karl's test case does not work.
 
 
 
  On Tue, Mar 4, 2014 at 10:26 AM, Karl Kildén karl.kil...@gmail.com
 wrote:
 
  Removing deltaspike has no effect. / Karl
 
 
  On 4 March 2014 16:23, Howard W. Smith, Jr. smithh032...@gmail.com
  wrote:
 
   Have you reported this to Deltaspike? I wonder what happens when you
   'remove' delta spike from the equation/mix, and see if stuff/stack
  starts
   working. :)
  
  
  
   On Tue, Mar 4, 2014 at 9:55 AM, Karl Kildén karl.kil...@gmail.com
  wrote:
  
It made no difference for me / Karl
   
   
On 4 March 2014 15:52, Karl Kildén karl.kil...@gmail.com wrote:
   
 Nice spot, In my production environment I changed it but I will
 test
   that
 aspect in the template project


 On 4 March 2014 15:50, Howard W. Smith, Jr. 
 smithh032...@gmail.com
wrote:

 On Tue, Mar 4, 2014 at 9:18 AM, Karl Kildén 
 karl.kil...@gmail.com
  
 wrote:

  Everyone, this is how I reproduced it in a test project:
 
 
 - Cloned Gerhards template
  project:
 https://github.com/os890/javaweb-cdi-ds-project-template
 

 h,

 examining the faces-config.xml, i see 2.0 specified instead of
 2.1
  (or
 2.2).

 faces-config version=2.0
 xmlns=http://java.sun.com/xml/ns/javaee;
 xmlns:xi=http://www.w3.org/2001/XInclude;
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
 http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd;

 /faces-config


 When MyFaces 2.2 was released, i don't think I saw any mention
 of a
 'requirement' to update faces-config, accordingly, but it would
 be
   nice
to
 know if faces-config.xml has to be updated with '2.2' or 2.1.



   
  
 
 
 



Re: 2.2.0 and multipart

2014-03-04 Thread Leonardo K. Shikida
Karl

I haven't tested it, but Howard figured out that it may be a primefaces
problem in their autodetection algorithm

I haven't tested myself yet, but it seems it's just a matter of adding this
parameter explicitly

context-param
param-nameprimefaces.UPLOADER/param-name
  param-valuecommons/param-value
/context-param

best regards

Leo


[]

Leo


On Tue, Mar 4, 2014 at 4:37 AM, Karl Kildén karl.kil...@gmail.com wrote:

 Leo,

 I have the same problem, What's your status?

 cheers


 On 22 February 2014 02:58, Leonardo K. Shikida shik...@gmail.com wrote:

  Hi
 
  Just noticed this thread about tomee, myfacs 2.2.0 and multipart request
 
 
 
 stackoverflow.com/questions/21948228/how-to-get-jsf-file-upload-to-work-on-tomee-1-6
 
  does anyone know if between 2.1.13 and 2.2.0, multipart request has got
 any
  new bug? could not find anything in JIRA
 
  the guy who posted the stackoverflow question tested with
 
  h:commandButton while I've reproduced the problem just switching
  myfaces jars from vanilla tomee 1.6.0 from 2.1.13 to 2.2.0 and using
  p:fileUpload
 
  []
 
  Leo
 



Re: 2.2.0 and multipart

2014-03-04 Thread Karl Kildén
Well for me it breaks the form completely. Even if I have only a single
component h:commandButton/ it's broke. Adding the primefaces parameter
has no effect. I will try to put a test application together


On 4 March 2014 14:17, Leonardo K. Shikida shik...@gmail.com wrote:

 Karl

 I haven't tested it, but Howard figured out that it may be a primefaces
 problem in their autodetection algorithm

 I haven't tested myself yet, but it seems it's just a matter of adding this
 parameter explicitly

 context-param
 param-nameprimefaces.UPLOADER/param-name
   param-valuecommons/param-value
 /context-param

 best regards

 Leo


 []

 Leo


 On Tue, Mar 4, 2014 at 4:37 AM, Karl Kildén karl.kil...@gmail.com wrote:

  Leo,
 
  I have the same problem, What's your status?
 
  cheers
 
 
  On 22 February 2014 02:58, Leonardo K. Shikida shik...@gmail.com
 wrote:
 
   Hi
  
   Just noticed this thread about tomee, myfacs 2.2.0 and multipart
 request
  
  
  
 
 stackoverflow.com/questions/21948228/how-to-get-jsf-file-upload-to-work-on-tomee-1-6
  
   does anyone know if between 2.1.13 and 2.2.0, multipart request has got
  any
   new bug? could not find anything in JIRA
  
   the guy who posted the stackoverflow question tested with
  
   h:commandButton while I've reproduced the problem just switching
   myfaces jars from vanilla tomee 1.6.0 from 2.1.13 to 2.2.0 and using
   p:fileUpload
  
   []
  
   Leo
  
 



Re: 2.2.0 and multipart

2014-03-04 Thread Karl Kildén
Leonardo Uribe, Thanks for doing a test with this already.

Everyone, this is how I reproduced it in a test project:


   - Cloned Gerhards template
project:https://github.com/os890/javaweb-cdi-ds-project-template
   - Ran with mvn clean install jetty:run -
   http://localhost:8080/javaweb-cdi-ds-project-template/helloWorld.xhtml-
Wrote my name and pressed Press Me and it successfully navigated.
   - Changed helloWorld.xhtml and added enctype=multipart/form-data to
   the form.
   - Ran project with mvn clean install jetty:run - it does not work
   - Ran project with mvn clean install jetty:run -Pmojarra - works (Note
   that mojarra profile is used)


To conclude with a normal form Gerhards project template works just fine.
It works fine with mojarra in either case. With Myfaces and
enctype=multipart/form-data it does not work.

I tried this several times with the same result.

Deltaspike and Myfaces is what's in common with my normal stack. No
Primefaces needed for reproduce

cheers







On 4 March 2014 14:58, Karl Kildén karl.kil...@gmail.com wrote:

 Well for me it breaks the form completely. Even if I have only a single
 component h:commandButton/ it's broke. Adding the primefaces parameter
 has no effect. I will try to put a test application together


 On 4 March 2014 14:17, Leonardo K. Shikida shik...@gmail.com wrote:

 Karl

 I haven't tested it, but Howard figured out that it may be a primefaces
 problem in their autodetection algorithm

 I haven't tested myself yet, but it seems it's just a matter of adding
 this
 parameter explicitly

 context-param
 param-nameprimefaces.UPLOADER/param-name
   param-valuecommons/param-value
 /context-param

 best regards

 Leo


 []

 Leo


 On Tue, Mar 4, 2014 at 4:37 AM, Karl Kildén karl.kil...@gmail.com
 wrote:

  Leo,
 
  I have the same problem, What's your status?
 
  cheers
 
 
  On 22 February 2014 02:58, Leonardo K. Shikida shik...@gmail.com
 wrote:
 
   Hi
  
   Just noticed this thread about tomee, myfacs 2.2.0 and multipart
 request
  
  
  
 
 stackoverflow.com/questions/21948228/how-to-get-jsf-file-upload-to-work-on-tomee-1-6
  
   does anyone know if between 2.1.13 and 2.2.0, multipart request has
 got
  any
   new bug? could not find anything in JIRA
  
   the guy who posted the stackoverflow question tested with
  
   h:commandButton while I've reproduced the problem just switching
   myfaces jars from vanilla tomee 1.6.0 from 2.1.13 to 2.2.0 and using
   p:fileUpload
  
   []
  
   Leo
  
 





Re: 2.2.0 and multipart

2014-03-04 Thread Howard W. Smith, Jr.
On Tue, Mar 4, 2014 at 8:58 AM, Karl Kildén karl.kil...@gmail.com wrote:

 Well for me it breaks the form completely.


interesting. please clarify this statement... breaks the form completely.


 Even if I have only a single component h:commandButton/ it's broke.


i'm definitely interested in seeing this h:form and h:commandbutton (and
p:fileUpload) xhtml syntax.


Adding the primefaces parameter has no effect. I will try to put a test
 application together


Karl,

Below is my xhtml, which is PrimeFaces 3.x FileUpload syntax. The following
code worked with PrimeFaces 3.x (and PrimeFaces 4.0.x and MyFaces 2.1.13),
but it stopped working when I added MyFaces 2.2 to my PrimeFaces 4.0.x
project/app.

h:form id=fileUploadForm enctype=multipart/form-data
p:panel header=Upload attachment
p:fileUpload value=#{orderDocumentBean.uploadedFile}
mode=simple /
p:commandLink value=Upload File ajax=false
onclick=displayLoadingImage(true)

 actionListener=#{orderDocumentBean.uploadAttachment()}/
/p:panel
/h:form

Once I specified 'commons' for PrimeFaces uploader context param in web.xml
(after upgrading to Apache commons fileupload 1.3 JAR), the xhtml 'above'
started working again.


Re: 2.2.0 and multipart

2014-03-04 Thread Karl Kildén
Hi Howard,

This is the complete markup you wanted to see:

h:form id=mainForm enctype=multipart/form-data
h:commandButton value=Press me
action=#{helloWorld.send}/br/
/h:form

Note that I reproduced it in a project that does not include Primefaces
(described in my latest email). When I press the submit nothing happens.
It's as if I wrote onclick=return false;

cheers


On 4 March 2014 15:23, Howard W. Smith, Jr. smithh032...@gmail.com wrote:

 On Tue, Mar 4, 2014 at 8:58 AM, Karl Kildén karl.kil...@gmail.com wrote:

  Well for me it breaks the form completely.


 interesting. please clarify this statement... breaks the form completely.


  Even if I have only a single component h:commandButton/ it's broke.


 i'm definitely interested in seeing this h:form and h:commandbutton (and
 p:fileUpload) xhtml syntax.


 Adding the primefaces parameter has no effect. I will try to put a test
  application together
 

 Karl,

 Below is my xhtml, which is PrimeFaces 3.x FileUpload syntax. The following
 code worked with PrimeFaces 3.x (and PrimeFaces 4.0.x and MyFaces 2.1.13),
 but it stopped working when I added MyFaces 2.2 to my PrimeFaces 4.0.x
 project/app.

 h:form id=fileUploadForm enctype=multipart/form-data
 p:panel header=Upload attachment
 p:fileUpload value=#{orderDocumentBean.uploadedFile}
 mode=simple /
 p:commandLink value=Upload File ajax=false
 onclick=displayLoadingImage(true)

  actionListener=#{orderDocumentBean.uploadAttachment()}/
 /p:panel
 /h:form

 Once I specified 'commons' for PrimeFaces uploader context param in web.xml
 (after upgrading to Apache commons fileupload 1.3 JAR), the xhtml 'above'
 started working again.



Re: 2.2.0 and multipart

2014-03-04 Thread Howard W. Smith, Jr.
On Tue, Mar 4, 2014 at 9:18 AM, Karl Kildén karl.kil...@gmail.com wrote:

 Everyone, this is how I reproduced it in a test project:


- Cloned Gerhards template
 project:https://github.com/os890/javaweb-cdi-ds-project-template


h,

examining the faces-config.xml, i see 2.0 specified instead of 2.1 (or 2.2).

faces-config version=2.0
xmlns=http://java.sun.com/xml/ns/javaee;
xmlns:xi=http://www.w3.org/2001/XInclude;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd;

/faces-config


When MyFaces 2.2 was released, i don't think I saw any mention of a
'requirement' to update faces-config, accordingly, but it would be nice to
know if faces-config.xml has to be updated with '2.2' or 2.1.


Re: 2.2.0 and multipart

2014-03-04 Thread Karl Kildén
Nice spot, In my production environment I changed it but I will test that
aspect in the template project


On 4 March 2014 15:50, Howard W. Smith, Jr. smithh032...@gmail.com wrote:

 On Tue, Mar 4, 2014 at 9:18 AM, Karl Kildén karl.kil...@gmail.com wrote:

  Everyone, this is how I reproduced it in a test project:
 
 
 - Cloned Gerhards template
  project:https://github.com/os890/javaweb-cdi-ds-project-template
 

 h,

 examining the faces-config.xml, i see 2.0 specified instead of 2.1 (or
 2.2).

 faces-config version=2.0
 xmlns=http://java.sun.com/xml/ns/javaee;
 xmlns:xi=http://www.w3.org/2001/XInclude;
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
 http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd;

 /faces-config


 When MyFaces 2.2 was released, i don't think I saw any mention of a
 'requirement' to update faces-config, accordingly, but it would be nice to
 know if faces-config.xml has to be updated with '2.2' or 2.1.



Re: 2.2.0 and multipart

2014-03-04 Thread Karl Kildén
It made no difference for me / Karl


On 4 March 2014 15:52, Karl Kildén karl.kil...@gmail.com wrote:

 Nice spot, In my production environment I changed it but I will test that
 aspect in the template project


 On 4 March 2014 15:50, Howard W. Smith, Jr. smithh032...@gmail.comwrote:

 On Tue, Mar 4, 2014 at 9:18 AM, Karl Kildén karl.kil...@gmail.com
 wrote:

  Everyone, this is how I reproduced it in a test project:
 
 
 - Cloned Gerhards template
  project:https://github.com/os890/javaweb-cdi-ds-project-template
 

 h,

 examining the faces-config.xml, i see 2.0 specified instead of 2.1 (or
 2.2).

 faces-config version=2.0
 xmlns=http://java.sun.com/xml/ns/javaee;
 xmlns:xi=http://www.w3.org/2001/XInclude;
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
 http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd;

 /faces-config


 When MyFaces 2.2 was released, i don't think I saw any mention of a
 'requirement' to update faces-config, accordingly, but it would be nice to
 know if faces-config.xml has to be updated with '2.2' or 2.1.





Re: 2.2.0 and multipart

2014-03-04 Thread Howard W. Smith, Jr.
Have you reported this to Deltaspike? I wonder what happens when you
'remove' delta spike from the equation/mix, and see if stuff/stack starts
working. :)



On Tue, Mar 4, 2014 at 9:55 AM, Karl Kildén karl.kil...@gmail.com wrote:

 It made no difference for me / Karl


 On 4 March 2014 15:52, Karl Kildén karl.kil...@gmail.com wrote:

  Nice spot, In my production environment I changed it but I will test that
  aspect in the template project
 
 
  On 4 March 2014 15:50, Howard W. Smith, Jr. smithh032...@gmail.com
 wrote:
 
  On Tue, Mar 4, 2014 at 9:18 AM, Karl Kildén karl.kil...@gmail.com
  wrote:
 
   Everyone, this is how I reproduced it in a test project:
  
  
  - Cloned Gerhards template
   project:https://github.com/os890/javaweb-cdi-ds-project-template
  
 
  h,
 
  examining the faces-config.xml, i see 2.0 specified instead of 2.1 (or
  2.2).
 
  faces-config version=2.0
  xmlns=http://java.sun.com/xml/ns/javaee;
  xmlns:xi=http://www.w3.org/2001/XInclude;
  xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
  http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd;
 
  /faces-config
 
 
  When MyFaces 2.2 was released, i don't think I saw any mention of a
  'requirement' to update faces-config, accordingly, but it would be nice
 to
  know if faces-config.xml has to be updated with '2.2' or 2.1.
 
 
 



Re: 2.2.0 and multipart

2014-03-04 Thread Karl Kildén
Removing deltaspike has no effect. / Karl


On 4 March 2014 16:23, Howard W. Smith, Jr. smithh032...@gmail.com wrote:

 Have you reported this to Deltaspike? I wonder what happens when you
 'remove' delta spike from the equation/mix, and see if stuff/stack starts
 working. :)



 On Tue, Mar 4, 2014 at 9:55 AM, Karl Kildén karl.kil...@gmail.com wrote:

  It made no difference for me / Karl
 
 
  On 4 March 2014 15:52, Karl Kildén karl.kil...@gmail.com wrote:
 
   Nice spot, In my production environment I changed it but I will test
 that
   aspect in the template project
  
  
   On 4 March 2014 15:50, Howard W. Smith, Jr. smithh032...@gmail.com
  wrote:
  
   On Tue, Mar 4, 2014 at 9:18 AM, Karl Kildén karl.kil...@gmail.com
   wrote:
  
Everyone, this is how I reproduced it in a test project:
   
   
   - Cloned Gerhards template
project:https://github.com/os890/javaweb-cdi-ds-project-template
   
  
   h,
  
   examining the faces-config.xml, i see 2.0 specified instead of 2.1 (or
   2.2).
  
   faces-config version=2.0
   xmlns=http://java.sun.com/xml/ns/javaee;
   xmlns:xi=http://www.w3.org/2001/XInclude;
   xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
   xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
   http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd;
  
   /faces-config
  
  
   When MyFaces 2.2 was released, i don't think I saw any mention of a
   'requirement' to update faces-config, accordingly, but it would be
 nice
  to
   know if faces-config.xml has to be updated with '2.2' or 2.1.
  
  
  
 



Re: 2.2.0 and multipart

2014-03-04 Thread Howard W. Smith, Jr.
wow, okay. :)

Earlier, Leonardo Uribe mentioned the following:

I can confirm a simple example using MyFaces 2.2.0 works. See:

http://jsflive.wordpress.com/2013/04/23/jsf22-file-upload/

Looking forward to hearing why your/Karl's test case does not work.



On Tue, Mar 4, 2014 at 10:26 AM, Karl Kildén karl.kil...@gmail.com wrote:

 Removing deltaspike has no effect. / Karl


 On 4 March 2014 16:23, Howard W. Smith, Jr. smithh032...@gmail.com
 wrote:

  Have you reported this to Deltaspike? I wonder what happens when you
  'remove' delta spike from the equation/mix, and see if stuff/stack starts
  working. :)
 
 
 
  On Tue, Mar 4, 2014 at 9:55 AM, Karl Kildén karl.kil...@gmail.com
 wrote:
 
   It made no difference for me / Karl
  
  
   On 4 March 2014 15:52, Karl Kildén karl.kil...@gmail.com wrote:
  
Nice spot, In my production environment I changed it but I will test
  that
aspect in the template project
   
   
On 4 March 2014 15:50, Howard W. Smith, Jr. smithh032...@gmail.com
   wrote:
   
On Tue, Mar 4, 2014 at 9:18 AM, Karl Kildén karl.kil...@gmail.com
wrote:
   
 Everyone, this is how I reproduced it in a test project:


- Cloned Gerhards template
 project:https://github.com/os890/javaweb-cdi-ds-project-template

   
h,
   
examining the faces-config.xml, i see 2.0 specified instead of 2.1
 (or
2.2).
   
faces-config version=2.0
xmlns=http://java.sun.com/xml/ns/javaee;
xmlns:xi=http://www.w3.org/2001/XInclude;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd;
   
/faces-config
   
   
When MyFaces 2.2 was released, i don't think I saw any mention of a
'requirement' to update faces-config, accordingly, but it would be
  nice
   to
know if faces-config.xml has to be updated with '2.2' or 2.1.
   
   
   
  
 



Re: 2.2.0 and multipart

2014-03-03 Thread Leonardo K. Shikida
Hi Howard

thanks for the answer

except for the primefaces.UPLOADER thing, I was using FU 1.3 already and
the primefaces file upload filter.

the difference is that I use PF4 community

I've also noticed from the manual that this parameter is optional (page 192)

(...)
FileUpload engine on the server side can either be servlet 3.0 or commons
fileupload. PrimeFaces
selects the most appropriate uploader engine by detection and it is
possible to force one or the other
usign an optional configuration param.
context-param
param-nameprimefaces.UPLOADER/param-name
param-valueauto|native|commons/param-value
/context-param
(...)

I'm gonna try setting the parameter explicitly, maybe it's a primefaces
detection problem.

thanks!

Leo


[]

Leo


On Sun, Mar 2, 2014 at 8:36 PM, Howard W. Smith, Jr. smithh032...@gmail.com
 wrote:

 On Tue, Feb 25, 2014 at 10:20 AM, Howard W. Smith, Jr. 
 smithh032...@gmail.com wrote:

  +1 thanks Leonardo for informing the user list about this issue. I am
  using MyFaces 2.2 (and/via TomEE 1.6.1 snapshot) with my JSF web
  application, and I confirmed this bug/issue too in my app. PrimeFaces 4.x
  (simple) fileUpload is no longer working. :(
 
  maybe, it can/should be confirmed if MyFaces 2.2 (basic/simple)
 fileUpload
  works as designed/expected. i have not tested that though/yet.
 

 okay, this evening, I spent some time with this.

 1. I searched google for

 site:forum.primefaces.org fileupload 2.2

 2. found the following on PrimeFaces forum

 http://forum.primefaces.org/viewtopic.php?f=3t=31210

 3. which referenced the following (solution seemed to be too much)


 http://stackoverflow.com/questions/17204355/glassfish-4-jsf-2-2-and-primefaces-fileuploadevent-not-working-together/17363970#17363970

 4. which referenced the following as a related link,


 http://stackoverflow.com/questions/20316773/primefaces-4-0-fileupload-works-with-mojarra-2-2-but-not-myfaces-2-2?rq=1

 5. the answer below, motivated me to upgrade from apache commons fileupload
 1.2.2 to 1.3

 http://stackoverflow.com/a/20347508/933054

 6. and then I looked at PrimeFaces 4.0 user guide, and recognized something
 'new' that could be specified in web.xml. So, I added the following to my
 web.xml,

 context-param
 param-nameprimefaces.UPLOADER/param-name
 param-valuecommons/param-value
 /context-param

 and finally, PrimeFaces (Elite) 4.0.x works with MyFaces 2.2.

 7. as per PrimeFaces 4.0 user guide, I already had the following (FYI,
 below is required if 'commons' fileupload is used)

 !-- PrimeFaces FileUpload Filter --
 filter
 filter-namePrimeFaces FileUpload Filter/filter-name

 filter-classorg.primefaces.webapp.filter.FileUploadFilter/filter-class
 /filter
 filter-mapping
 filter-namePrimeFaces FileUpload Filter/filter-name
 servlet-nameFaces Servlet/servlet-name
 /filter-mapping



Re: 2.2.0 and multipart

2014-03-03 Thread Howard W. Smith, Jr.
On Mar 3, 2014 7:33 AM, Leonardo K. Shikida shik...@gmail.com wrote:

 Hi Howard

 thanks for the answer

You're welcome, Leonardo.


 except for the primefaces.UPLOADER thing, I was using FU 1.3 already and
 the primefaces file upload filter.

FileUpload 1.3, alone, did not solve the issue for me.


 the difference is that I use PF4 community

 I've also noticed from the manual that this parameter is optional (page
192)

 (...)
 FileUpload engine on the server side can either be servlet 3.0 or commons
 fileupload. PrimeFaces
 selects the most appropriate uploader engine by detection and it is
 possible to force one or the other
 usign an optional configuration param.
 context-param
 param-nameprimefaces.UPLOADER/param-name
 param-valueauto|native|commons/param-value
 /context-param
 (...)

 I'm gonna try setting the parameter explicitly, maybe it's a primefaces
 detection problem.

That's where I think the issue is. Auto detection is failing. That's why I
set to Commons, and then it started working.


 thanks!

 Leo


 []

 Leo


 On Sun, Mar 2, 2014 at 8:36 PM, Howard W. Smith, Jr. 
smithh032...@gmail.com
  wrote:

  On Tue, Feb 25, 2014 at 10:20 AM, Howard W. Smith, Jr. 
  smithh032...@gmail.com wrote:
 
   +1 thanks Leonardo for informing the user list about this issue. I am
   using MyFaces 2.2 (and/via TomEE 1.6.1 snapshot) with my JSF web
   application, and I confirmed this bug/issue too in my app. PrimeFaces
4.x
   (simple) fileUpload is no longer working. :(
  
   maybe, it can/should be confirmed if MyFaces 2.2 (basic/simple)
  fileUpload
   works as designed/expected. i have not tested that though/yet.
  
 
  okay, this evening, I spent some time with this.
 
  1. I searched google for
 
  site:forum.primefaces.org fileupload 2.2
 
  2. found the following on PrimeFaces forum
 
  http://forum.primefaces.org/viewtopic.php?f=3t=31210
 
  3. which referenced the following (solution seemed to be too much)
 
 
 
http://stackoverflow.com/questions/17204355/glassfish-4-jsf-2-2-and-primefaces-fileuploadevent-not-working-together/17363970#17363970
 
  4. which referenced the following as a related link,
 
 
 
http://stackoverflow.com/questions/20316773/primefaces-4-0-fileupload-works-with-mojarra-2-2-but-not-myfaces-2-2?rq=1
 
  5. the answer below, motivated me to upgrade from apache commons
fileupload
  1.2.2 to 1.3
 
  http://stackoverflow.com/a/20347508/933054
 
  6. and then I looked at PrimeFaces 4.0 user guide, and recognized
something
  'new' that could be specified in web.xml. So, I added the following to
my
  web.xml,
 
  context-param
  param-nameprimefaces.UPLOADER/param-name
  param-valuecommons/param-value
  /context-param
 
  and finally, PrimeFaces (Elite) 4.0.x works with MyFaces 2.2.
 
  7. as per PrimeFaces 4.0 user guide, I already had the following (FYI,
  below is required if 'commons' fileupload is used)
 
  !-- PrimeFaces FileUpload Filter --
  filter
  filter-namePrimeFaces FileUpload Filter/filter-name
 
 
filter-classorg.primefaces.webapp.filter.FileUploadFilter/filter-class
  /filter
  filter-mapping
  filter-namePrimeFaces FileUpload Filter/filter-name
  servlet-nameFaces Servlet/servlet-name
  /filter-mapping
 


Re: 2.2.0 and multipart

2014-03-03 Thread Karl Kildén
Leo,

I have the same problem, What's your status?

cheers


On 22 February 2014 02:58, Leonardo K. Shikida shik...@gmail.com wrote:

 Hi

 Just noticed this thread about tomee, myfacs 2.2.0 and multipart request


 stackoverflow.com/questions/21948228/how-to-get-jsf-file-upload-to-work-on-tomee-1-6

 does anyone know if between 2.1.13 and 2.2.0, multipart request has got any
 new bug? could not find anything in JIRA

 the guy who posted the stackoverflow question tested with

 h:commandButton while I've reproduced the problem just switching
 myfaces jars from vanilla tomee 1.6.0 from 2.1.13 to 2.2.0 and using
 p:fileUpload

 []

 Leo



Re: 2.2.0 and multipart

2014-03-02 Thread Howard W. Smith, Jr.
On Tue, Feb 25, 2014 at 10:20 AM, Howard W. Smith, Jr. 
smithh032...@gmail.com wrote:

 +1 thanks Leonardo for informing the user list about this issue. I am
 using MyFaces 2.2 (and/via TomEE 1.6.1 snapshot) with my JSF web
 application, and I confirmed this bug/issue too in my app. PrimeFaces 4.x
 (simple) fileUpload is no longer working. :(

 maybe, it can/should be confirmed if MyFaces 2.2 (basic/simple) fileUpload
 works as designed/expected. i have not tested that though/yet.


okay, this evening, I spent some time with this.

1. I searched google for

site:forum.primefaces.org fileupload 2.2

2. found the following on PrimeFaces forum

http://forum.primefaces.org/viewtopic.php?f=3t=31210

3. which referenced the following (solution seemed to be too much)

http://stackoverflow.com/questions/17204355/glassfish-4-jsf-2-2-and-primefaces-fileuploadevent-not-working-together/17363970#17363970

4. which referenced the following as a related link,

http://stackoverflow.com/questions/20316773/primefaces-4-0-fileupload-works-with-mojarra-2-2-but-not-myfaces-2-2?rq=1

5. the answer below, motivated me to upgrade from apache commons fileupload
1.2.2 to 1.3

http://stackoverflow.com/a/20347508/933054

6. and then I looked at PrimeFaces 4.0 user guide, and recognized something
'new' that could be specified in web.xml. So, I added the following to my
web.xml,

context-param
param-nameprimefaces.UPLOADER/param-name
param-valuecommons/param-value
/context-param

and finally, PrimeFaces (Elite) 4.0.x works with MyFaces 2.2.

7. as per PrimeFaces 4.0 user guide, I already had the following (FYI,
below is required if 'commons' fileupload is used)

!-- PrimeFaces FileUpload Filter --
filter
filter-namePrimeFaces FileUpload Filter/filter-name

filter-classorg.primefaces.webapp.filter.FileUploadFilter/filter-class
/filter
filter-mapping
filter-namePrimeFaces FileUpload Filter/filter-name
servlet-nameFaces Servlet/servlet-name
/filter-mapping


Re: 2.2.0 and multipart

2014-02-25 Thread Werner Punz

Am 22.02.14 02:58, schrieb Leonardo K. Shikida:

Hi

Just noticed this thread about tomee, myfacs 2.2.0 and multipart request

stackoverflow.com/questions/21948228/how-to-get-jsf-file-upload-to-work-on-tomee-1-6

does anyone know if between 2.1.13 and 2.2.0, multipart request has got any
new bug? could not find anything in JIRA

the guy who posted the stackoverflow question tested with

h:commandButton while I've reproduced the problem just switching
myfaces jars from vanilla tomee 1.6.0 from 2.1.13 to 2.2.0 and using
p:fileUpload

[]

Leo

Hi this could be a new bug, we introduced a fileupload handling with JSF 
2.2 (the h:inputFile tag) maybe the normal multipart request handling 
was broken by the extensions done in this area the best bet is to file a 
bugreport in the myfaces bugtracker 
https://issues.apache.org/jira/browse/MYFACES


Werner






Re: 2.2.0 and multipart

2014-02-25 Thread Howard W. Smith, Jr.
On Tue, Feb 25, 2014 at 3:20 AM, Werner Punz werner.p...@gmail.com wrote:

 Am 22.02.14 02:58, schrieb Leonardo K. Shikida:

  Hi

 Just noticed this thread about tomee, myfacs 2.2.0 and multipart request

 stackoverflow.com/questions/21948228/how-to-get-jsf-file-
 upload-to-work-on-tomee-1-6

 does anyone know if between 2.1.13 and 2.2.0, multipart request has got
 any
 new bug? could not find anything in JIRA

 the guy who posted the stackoverflow question tested with

 h:commandButton while I've reproduced the problem just switching
 myfaces jars from vanilla tomee 1.6.0 from 2.1.13 to 2.2.0 and using
 p:fileUpload

 []

 Leo

  Hi this could be a new bug, we introduced a fileupload handling with JSF
 2.2 (the h:inputFile tag) maybe the normal multipart request handling was
 broken by the extensions done in this area the best bet is to file a
 bugreport in the myfaces bugtracker https://issues.apache.org/
 jira/browse/MYFACES

 Werner


 +1 thanks Leonardo for informing the user list about this issue. I am
using MyFaces 2.2 (and/via TomEE 1.6.1 snapshot) with my JSF web
application, and I confirmed this bug/issue too in my app. PrimeFaces 4.x
(simple) fileUpload is no longer working. :(

maybe, it can/should be confirmed if MyFaces 2.2 (basic/simple) fileUpload
works as designed/expected. i have not tested that though/yet.


Re: 2.2.0 and multipart

2014-02-25 Thread Leonardo K. Shikida
Thanks
Em 25/02/2014 12:20, Howard W. Smith, Jr. smithh032...@gmail.com
escreveu:

 On Tue, Feb 25, 2014 at 3:20 AM, Werner Punz werner.p...@gmail.com
 wrote:

  Am 22.02.14 02:58, schrieb Leonardo K. Shikida:
 
   Hi
 
  Just noticed this thread about tomee, myfacs 2.2.0 and multipart request
 
  stackoverflow.com/questions/21948228/how-to-get-jsf-file-
  upload-to-work-on-tomee-1-6
 
  does anyone know if between 2.1.13 and 2.2.0, multipart request has got
  any
  new bug? could not find anything in JIRA
 
  the guy who posted the stackoverflow question tested with
 
  h:commandButton while I've reproduced the problem just switching
  myfaces jars from vanilla tomee 1.6.0 from 2.1.13 to 2.2.0 and using
  p:fileUpload
 
  []
 
  Leo
 
   Hi this could be a new bug, we introduced a fileupload handling with
 JSF
  2.2 (the h:inputFile tag) maybe the normal multipart request handling was
  broken by the extensions done in this area the best bet is to file a
  bugreport in the myfaces bugtracker https://issues.apache.org/
  jira/browse/MYFACES
 
  Werner
 
 
  +1 thanks Leonardo for informing the user list about this issue. I am
 using MyFaces 2.2 (and/via TomEE 1.6.1 snapshot) with my JSF web
 application, and I confirmed this bug/issue too in my app. PrimeFaces 4.x
 (simple) fileUpload is no longer working. :(

 maybe, it can/should be confirmed if MyFaces 2.2 (basic/simple) fileUpload
 works as designed/expected. i have not tested that though/yet.



Re: 2.2.0 and multipart

2014-02-25 Thread Leonardo Uribe
Hi

I can confirm a simple example using MyFaces 2.2.0 works. See:

http://jsflive.wordpress.com/2013/04/23/jsf22-file-upload/

I think the problem is caused by some kind of incompatibility from
primefaces p:fileUpload. h:inputFile relies on servlet 3.0 spec, but
p:fileUpload could still use the filter approach, so you need to put a
filter on top of faces servlet to handle the multipart request.

Theoretically, nothing has changed, or at least at first view I cannot
see a problem in MyFaces besides the issues we have already fixed, so
2.2.0 should not have any problem.

It could be great if you can provide an example webapp showing the
problem, so we can take a look with the debugger and see if there is a
problem from primefaces or from myfaces. For now the evidence I have
suggest MyFaces is ok.

regards,

Leonardo Uribe

2014-02-25 10:36 GMT-05:00 Leonardo K. Shikida shik...@gmail.com:
 Thanks
 Em 25/02/2014 12:20, Howard W. Smith, Jr. smithh032...@gmail.com
 escreveu:

 On Tue, Feb 25, 2014 at 3:20 AM, Werner Punz werner.p...@gmail.com
 wrote:

  Am 22.02.14 02:58, schrieb Leonardo K. Shikida:
 
   Hi
 
  Just noticed this thread about tomee, myfacs 2.2.0 and multipart request
 
  stackoverflow.com/questions/21948228/how-to-get-jsf-file-
  upload-to-work-on-tomee-1-6
 
  does anyone know if between 2.1.13 and 2.2.0, multipart request has got
  any
  new bug? could not find anything in JIRA
 
  the guy who posted the stackoverflow question tested with
 
  h:commandButton while I've reproduced the problem just switching
  myfaces jars from vanilla tomee 1.6.0 from 2.1.13 to 2.2.0 and using
  p:fileUpload
 
  []
 
  Leo
 
   Hi this could be a new bug, we introduced a fileupload handling with
 JSF
  2.2 (the h:inputFile tag) maybe the normal multipart request handling was
  broken by the extensions done in this area the best bet is to file a
  bugreport in the myfaces bugtracker https://issues.apache.org/
  jira/browse/MYFACES
 
  Werner
 
 
  +1 thanks Leonardo for informing the user list about this issue. I am
 using MyFaces 2.2 (and/via TomEE 1.6.1 snapshot) with my JSF web
 application, and I confirmed this bug/issue too in my app. PrimeFaces 4.x
 (simple) fileUpload is no longer working. :(

 maybe, it can/should be confirmed if MyFaces 2.2 (basic/simple) fileUpload
 works as designed/expected. i have not tested that though/yet.



2.2.0 and multipart

2014-02-21 Thread Leonardo K. Shikida
Hi

Just noticed this thread about tomee, myfacs 2.2.0 and multipart request

stackoverflow.com/questions/21948228/how-to-get-jsf-file-upload-to-work-on-tomee-1-6

does anyone know if between 2.1.13 and 2.2.0, multipart request has got any
new bug? could not find anything in JIRA

the guy who posted the stackoverflow question tested with

h:commandButton while I've reproduced the problem just switching
myfaces jars from vanilla tomee 1.6.0 from 2.1.13 to 2.2.0 and using
p:fileUpload

[]

Leo