NetBeans Forums
| View previous topic :: View next topic |
| Author |
Message |
Vince Kraemer Posted via mailing list.
|
Posted: Thu Jan 08, 2009 8:31 pm Post subject: Re: NetBeans plugin for GlassFish v3 no longer includes jsf-impl.jar in its Classpath |
|
|
I will investigate.
vbk
Po-Ting Wu wrote:
| Quote: | Hi, Vince,
When using GlassFish v3, JSF framework recently (maybe 1-2 month)
always adds the bundled JSF 1.2 libraries into the new project because
it can't find the JSF jar files from the v3 server classpath! It uses
the API
org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.getDefault().getJ2eePlatform(serverInstanceID).getClasspathEntries()
to check whether the server supports the related class. I believe the
JSP editor also uses this API for this purpose.
Then I found that from the project view, the Libraries for v2 and v3
changed a lot. In v2 the jsf-impl.jar is in the list while in v3 it's
gone. It will affect the designtime that the JSP editor cannot find
the taglib. Though the deployment will still be good.
Any clue for this change? As I understood, both JSF and Struts will be
affected by this change. Should the framework change the searching
scheme? The JSP editor's syntax check and code-completion are also
affected!
Thanks,
Po-Ting
|
|
|
| Back to top |
|
 |
Vince Kraemer Posted via mailing list.
|
Posted: Thu Jan 08, 2009 9:10 pm Post subject: Re: NetBeans plugin for GlassFish v3 no longer includes jsf-impl.jar in its Classpath |
|
|
jsf-impl not in the list of jars: confirmed in the Java EE 6 branch.
it looks like a one line fix... but when I do fix it... I still cannot
create a web app that uses JSF?!?
I keep seeing this in the add frameworks step of the new project wizard
(when I check JSF or Visual JSF)
'' is not valid path for a folder
the next and finish button are also disabled...
Still digging.
vbk
Vince Kraemer wrote:
| Quote: | I will investigate.
vbk
Po-Ting Wu wrote:
| Quote: | Hi, Vince,
When using GlassFish v3, JSF framework recently (maybe 1-2 month)
always adds the bundled JSF 1.2 libraries into the new project
because it can't find the JSF jar files from the v3 server classpath!
It uses the API
org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.getDefault().getJ2eePlatform(serverInstanceID).getClasspathEntries()
to check whether the server supports the related class. I believe the
JSP editor also uses this API for this purpose.
Then I found that from the project view, the Libraries for v2 and v3
changed a lot. In v2 the jsf-impl.jar is in the list while in v3 it's
gone. It will affect the designtime that the JSP editor cannot find
the taglib. Though the deployment will still be good.
Any clue for this change? As I understood, both JSF and Struts will
be affected by this change. Should the framework change the searching
scheme? The JSP editor's syntax check and code-completion are also
affected!
Thanks,
Po-Ting
|
|
|
|
| Back to top |
|
 |
Vince Kraemer Posted via mailing list.
|
Posted: Thu Jan 08, 2009 9:26 pm Post subject: Re: NetBeans plugin for GlassFish v3 no longer includes jsf-impl.jar in its Classpath |
|
|
OK.
the error is because of a validation problem on the second tab...
I wish there was a way to see the field that is causing the error to
appear....
oh well.
vbk
Vince Kraemer wrote:
| Quote: |
jsf-impl not in the list of jars: confirmed in the Java EE 6 branch.
it looks like a one line fix... but when I do fix it... I still cannot
create a web app that uses JSF?!?
I keep seeing this in the add frameworks step of the new project
wizard (when I check JSF or Visual JSF)
'' is not valid path for a folder
the next and finish button are also disabled...
Still digging.
vbk
Vince Kraemer wrote:
| Quote: | I will investigate.
vbk
Po-Ting Wu wrote:
| Quote: | Hi, Vince,
When using GlassFish v3, JSF framework recently (maybe 1-2 month)
always adds the bundled JSF 1.2 libraries into the new project
because it can't find the JSF jar files from the v3 server
classpath! It uses the API
org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.getDefault().getJ2eePlatform(serverInstanceID).getClasspathEntries()
to check whether the server supports the related class. I believe
the JSP editor also uses this API for this purpose.
Then I found that from the project view, the Libraries for v2 and v3
changed a lot. In v2 the jsf-impl.jar is in the list while in v3
it's gone. It will affect the designtime that the JSP editor cannot
find the taglib. Though the deployment will still be good.
Any clue for this change? As I understood, both JSF and Struts will
be affected by this change. Should the framework change the
searching scheme? The JSP editor's syntax check and code-completion
are also affected!
Thanks,
Po-Ting
|
|
|
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You can attach files in this forum You can download files in this forum
|
|