Hi at all,
I found a bug which I think is a jsf problem rather than for ExtVal, but since
the code refers to https://issues.apache.org/jira/browse/EXTVAL-102 I would
like you to check it too:
Exception is javax.el.PropertyNotFoundException:
/resources/parts/partbase.xhtml @23,53
Hi,
On my project, we had a strange issue, caused by the way view parameters are
handled.
We had a page like this: (simplified)
?xml version=1.0 encoding=UTF-8?
html xmlns=http://www.w3.org/1999/xhtml;
xmlns:f=http://java.sun.com/jsf/core;
xmlns:h=http://java.sun.com/jsf/html;
hi tom,
i'll have a look at the example.
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2010/7/19 mynewsgro...@arcor.de
Hi at all,
I found a bug which I think is a jsf
Hi,
If you only provide param2, both params will be null in the bean, because
param1 is required and if you don't provide it, validation will fail, and if
validation fails, no value updates will occur. Thus this is the expected
behavior.
Regards,
Jakob
2010/7/19 Jan-Kees van Andel
Hi,
Yeah, I know it's expected from an implementation Point of View, but from a
user's PoV I think it's very confusing and also makes viewParam less useful.
Let me explain why.
When you work according to the JSF 1.x way, you invoke the application in
the Invoke Application phase, which is not
hi tom,
extval tries to initialize input components before they get rendered. so you
see the exception quite early.
i haven't analyzed the details of the example - however, if you deactivate
extval (via vm parameter), you will see the same issue at the next postback.
so you are right - it is not
The Apache MyFaces team is pleased to announce the release of MyFaces
Core 2.0.1.
MyFaces Core is a JavaServer(tm) Faces 2.0 implementation as specified
by JSR-314. MyFaces Core has passed Sun's JSR-314 TCK and is 100%
compliant with the JSR-314 specification.
MyFaces Core 2.0.1 is
7 matches
Mail list logo
