I can confirm that I used c:forEach erroneously.
Myfaces 2.2.3 running great for me now
cheers
On 13 March 2014 16:27, Leonardo Uribe lu4...@gmail.com wrote:
Hi
@Karl I think your problem should be something different. I closed
MYFACES-3869, since we have positive confirmation that the
Hi all,
Tried 2.2.2-20140313.024403-5
Duplicate id problems are still present. I have tried for a while now to
create a simple sample but I am unsuccessful so far.
On 12 March 2014 15:48, Karl Kildén karl.kil...@gmail.com wrote:
Hi Howard,
Leo found and fixed the
On Thu, Mar 13, 2014 at 7:34 AM, Karl Kildén karl.kil...@gmail.com wrote:
Tried 2.2.2-20140313.024403-5
Duplicate id problems are still present. I have tried for a while now to
create a simple sample but I am unsuccessful so far.
+1 thanks Karl for the report.
Hi
@Karl I think your problem should be something different. I closed
MYFACES-3869, since we have positive confirmation that the fix done
works, but we need to analyze your problem and check if there is an
error in MyFaces or not.
We need more information than just the stack trace. MyFaces
Following up,
Karl, are you still waiting on Leonardo to trigger a snapshot build? With
all that has been discussed here, is it likely that tomee + myfaces 2.2.x
(snapshot) is a 'go' for you? :)
fingers crossed... :)
On Tue, Mar 11, 2014 at 4:19 AM, Karl Kildén karl.kil...@gmail.com wrote:
Hi Howard,
Leo found and fixed the enctype=multipart/form-data. It's basically up
to the Servlet Container to do the job now when the Faces Servlet is
annotated correctly. Thanks a lot to everyone who helped me with that
issue. Regarding the duplicate id problems, I did not get enough time to
OK, if enctype is not supported for post (except when fileUpload component
is present) it could be my headache then. If I have a fileupload or not
depends on include logic etc. This is somewhat a legacy so I can probably
rework it in the future.
I assume any build time logic that could
Karl, does this fix your issue and or meet your requirements? Looking
forward to your response. I'm sure others are, too. :-)
Can you refactor your code, so it is not dependent on c:forEach? Maybe
Leonardo can advise on that, too.
On Mar 9, 2014 9:24 PM, Leonardo Uribe lu4...@gmail.com wrote:
Hi Howard,
If someone proposed a fix for me I must have missed it, so no my issues are
still not resolved unfortunately. I don't think it's possible to write it
in another fashion.
Problem #1: enctype=multipart/form-data not working. Not sure if anyone
tried the demo app I linked in the jira but
response inline,
On Mon, Mar 10, 2014 at 2:43 PM, Karl Kildén karl.kil...@gmail.com wrote:
Hi Howard,
If someone proposed a fix for me I must have missed it, so no my issues are
still not resolved unfortunately. I don't think it's possible to write it
in another fashion.
Leonardo's
Hi
2014-03-10 14:13 GMT-05:00 Howard W. Smith, Jr. smithh032...@gmail.com:
response inline,
On Mon, Mar 10, 2014 at 2:43 PM, Karl Kildén karl.kil...@gmail.com wrote:
Hi Howard,
If someone proposed a fix for me I must have missed it, so no my issues are
still not resolved unfortunately. I
Ah the new release, yes I tried it asap it did not fix my issue.
Regarding the duplicated id issue that I think could be related to
c:forEach, No idea what the problem is but it works fine with mojarra and
just as fine with myfaces 2.1.x. The construct in that app is special so it
is up to me to
Hi Leo,
Upgraded to 2.2.1 today (or was it yesterday?) and had problems. Removed
org.apache.myfaces.STRICT_JSF_2_FACELETS_COMPATIBILITY and many problems
went away. Much later discovered more problems but it's just me and my
silly app until I have proof :-)
I totally agree that c:forEach was
Hi Karl
2014-03-10 15:15 GMT-05:00 Karl Kildén karl.kil...@gmail.com:
Hi Leo,
Upgraded to 2.2.1 today (or was it yesterday?) and had problems. Removed
org.apache.myfaces.STRICT_JSF_2_FACELETS_COMPATIBILITY and many problems
went away. Much later discovered more problems but it's just me and
Hi, Im sure others know better but here's my story as early adopter.
I am -1 against adoption if you use c:forEach because it's been rewritten
or greatly improved upon somehow. As a consequence I was blocked by
MYFACES-3853 https://issues.apache.org/jira/browse/MYFACES-3853 for a
while. As a fix
I found 2.2 to be very stable, almost a drop in replacement for 2.1.
Using the new file upload feature of JSF 2.2 was straightforward for me. I had
a hard time with Faces Flows, but Leonardo and the others kindly helped and
fixed a few bugs - I still have to test that it is ok.
I expected many
On Sun, Mar 9, 2014 at 5:20 PM, Ludovic Pénet l.pe...@senat.fr wrote:
I found 2.2 to be very stable, almost a drop in replacement for 2.1.
+1
I was using MyFaces 2.1.13 prior using MyFaces 2.2.0 (final), and MyFaces
2.2.0 seems just as stable as 2.1.13 is/was. I'm very pleased/satisfied
with
Hi
@MYFACES-3865 It was fixed in 2.2.1, and the artifacts will be released
in no time. The fix for c:forEach was really complex and painful, but it
was finally done and the result is the best option we will have. Finally
we have a proper solution that will work in complex cases and will
allow all
18 matches
Mail list logo
