Sorry, you were pipped to the post !
cheers,
John.
Jochen Zink <[EMAIL PROTECTED]>
05/11/2007 09:47
Please respond to
user@geronimo.apache.org
To
user@geronimo.apache.org
cc
Subject
Re: MyFaces 1.1.5 and Geronimo 2.0.2
Thanks for all your answers.
We came to the decision, that
I got an NPE when I tried using the 1.1 impl in an webapp with the
1.2 api classes inherited from jee-specs. But I suspect that was due
to the classloader configuration rather than a backwards
compatibility problem. Certain JSF factory methods can return null
when the api and impl are in
mailinglist
for that ;)
Thanks for your help!
Regards
Jochen
> -Ursprüngliche Nachricht-
> Von: user@geronimo.apache.org
> Gesendet: 03.11.07 18:39:37
> An: user@geronimo.apache.org
> Betreff: Re: MyFaces 1.1.5 and Geronimo 2.0.2
>
> I think we could move the myf
I think we could move the myfaces non-overrideable classes into the
myfaces-builder default environment attribute. This would mean that
if you turn off the myfaces-deployer we wouldn't try to deploy your
jsf stuff as per javaee 5, and you shouldn't need to use hidden-
classes to avoid the m
I'm running into this issue too and it doesn't seem to care about the
J2EE version of the app being deployed. Shouldn't the behavior be that
this only happens if the app in question is a JEE5 app ? Is there a
check in the code to branch around the additions to the plan for JSF
related stuff ? Unl
The minimal assembles don't contain the myfaces components but they
do contain the jee-specs component. The jee-specs component is a
parent of all webapps and includes the JSF 1.2 apis in its
classpath. I provided instructions in another email for one way to
work around this since Joch
Starting with Java EE 5 the JSF classes are provided by the web
container. The spec says that the JSF classes should not be included
in the web application archive. When Geronmio deploys a webapp it
automatically merges this setting into webapp's deployment plan:
java.
On 11/1/07, David Jencks <[EMAIL PROTECTED]> wrote:
>
> Paul may have more info, but my understanding is that for javaee
> compliance we need to, by default, support myfaces 1.2 and ignore any
> attempt to use earlier/other jsf implementations.
>
> You might be able to disable this support by turni
Paul may have more info, but my understanding is that for javaee
compliance we need to, by default, support myfaces 1.2 and ignore any
attempt to use earlier/other jsf implementations.
You might be able to disable this support by turning off the myfaces
and myfaces-deployer modules in confi
Hello all,
I try to deploy a JSF-Webapplication which depends on myfaces 1.1.5. This
Application runs successfully under Tomcat 6.
Know, I want deploy this application under Geronimo 2.0.2. With exactly the
same WAR file, nothing is happen. No Error Messages and no HTML Page is shown
in the br
10 matches
Mail list logo
