Home » Language IDEs » Java Development Tools (JDT) » JSF app no longer deploys class files
| JSF app no longer deploys class files [message #251203] |
Mon, 04 February 2008 05:49  |
 David M. Karr
Messages: 143
Registered: July 2009 |
Senior Member |
|
|
I seem to have gotten my JSF app in a state where it will no longer deploy
the class files that I've written into the WAR file, either on export or
on automatic deploy to Tomcat.
I had created a dynamic web app with the JSF project facet. It was
basically working, except I was having some specific issues with my JSP
page and its interaction with JSF. I wanted to attach the JSF RI source
(I'm using the Sun 1.2 RI). For some reason that I can't explain, Eclipse
won't let me attach the source for this. Whenever I stored the path and
then clicked OK on the project preferences, I still couldn't see the
source files, and going back into the project properties shows that the
source dir setting was gone.
Anyway, I'm annoyed with that, but that's not even my current problem. I
decided since I would try to remove the JSF project facet and just add the
JSF RI jars as an ordinary library. This produced one bizarre
side-effect. It seemed to remove my source tree from the "Sources"
property settings. I readded it by editing the .classpath file directly,
adding the following line (looking at other projects for this):
<classpathentry kind="src" path="src"/>
I thought this fixed my source files situation for the moment.
Unfortunately, I then discovered that now JSP pages didn't know about my
JSF tag libraries. So, I decided it really needs to have it as a project
facet, so I backtracked on that, removing it as a regular library, then
re-adding it as a project facet.
Unfortunately, it seems like this didn't even help. Even worse, I
discovered that when I deploy the app, it doesn't put my compiled class
files into WEB-INF/classes.
Am I going to have to completely rebuild this application, or is there a
way to do surgery on my .classpath file (or other files) to restore normal
functionality?
I wouldn't mind solving my "original" problem, which is being able to set
the source files path for the JSF implementation.
|
|
| |
| Re: JSF app no longer deploys class files [message #251217 is a reply to message #251203] |
Mon, 04 February 2008 17:02  |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
This question is more likely to get help on the webtools and/or JSF
newsgroups. I've copied them to this response.
David Karr wrote:
> I seem to have gotten my JSF app in a state where it will no longer
> deploy the class files that I've written into the WAR file, either on
> export or on automatic deploy to Tomcat.
>
> I had created a dynamic web app with the JSF project facet. It was
> basically working, except I was having some specific issues with my JSP
> page and its interaction with JSF. I wanted to attach the JSF RI source
> (I'm using the Sun 1.2 RI). For some reason that I can't explain,
> Eclipse won't let me attach the source for this. Whenever I stored the
> path and then clicked OK on the project preferences, I still couldn't
> see the source files, and going back into the project properties shows
> that the source dir setting was gone.
>
> Anyway, I'm annoyed with that, but that's not even my current problem.
> I decided since I would try to remove the JSF project facet and just add
> the JSF RI jars as an ordinary library. This produced one bizarre
> side-effect. It seemed to remove my source tree from the "Sources"
> property settings. I readded it by editing the .classpath file
> directly, adding the following line (looking at other projects for this):
>
> <classpathentry kind="src" path="src"/>
>
> I thought this fixed my source files situation for the moment.
>
> Unfortunately, I then discovered that now JSP pages didn't know about my
> JSF tag libraries. So, I decided it really needs to have it as a
> project facet, so I backtracked on that, removing it as a regular
> library, then re-adding it as a project facet.
>
> Unfortunately, it seems like this didn't even help. Even worse, I
> discovered that when I deploy the app, it doesn't put my compiled class
> files into WEB-INF/classes.
>
> Am I going to have to completely rebuild this application, or is there a
> way to do surgery on my .classpath file (or other files) to restore
> normal functionality?
>
> I wouldn't mind solving my "original" problem, which is being able to
> set the source files path for the JSF implementation.
>
|
|
|
| Re: JSF app no longer deploys class files [message #251221 is a reply to message #251213] |
Mon, 04 February 2008 17:03 |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
David Karr wrote:
> I have no idea how it got into this state, but after recreating the
> application from scratch (just copying the source files over after
> creating the skeleton), I see the differences in the metadata files that
> make the difference. In the
> ".settings/org.eclipse.wst.common.component" file, I needed to have the
> following line:
>
> <wb-resource deploy-path="/WEB-INF/classes" source-path="/src"/>
>
> If this happens again, if it's less practical to recreate the project,
> at least I might be able to fix it by adding this line.
>
> I would think it would be a good idea to document the schemas for these
> metadata files. I couldn't find any documentation on this file, or
> others like it. I'm sure I just didn't know where to look.
>
>
Those files are probably not documented; they're not intended for user
modification as they are internal "state" of the WST tools.
Eric
|
|
| |
| Re: JSF app no longer deploys class files [message #251229 is a reply to message #251221] |
Mon, 04 February 2008 17:31 |
| Eclipse User |
|
|
|
Originally posted by: dcarver.starstandard.org
Eric, I would hope that there is some documentation somewhere about
those files and what they are used for. Regardless if they are intended
for user modification or not, documenting the usage of those files is
important.
>> If this happens again, if it's less practical to recreate the project,
>> at least I might be able to fix it by adding this line.
>>
>> I would think it would be a good idea to document the schemas for
>> these metadata files. I couldn't find any documentation on this file,
>> or others like it. I'm sure I just didn't know where to look.
>>
>>
>
> Those files are probably not documented; they're not intended for user
> modification as they are internal "state" of the WST tools.
>
> Eric
|
|
|
| Re: JSF app no longer deploys class files [message #251250 is a reply to message #251229] |
Mon, 04 February 2008 22:35 |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
David Carver wrote:
> Eric, I would hope that there is some documentation somewhere about
> those files and what they are used for. Regardless if they are intended
> for user modification or not, documenting the usage of those files is
> important.
This is open source - if the WST development team didn't have reason,
motivation, time,...whatever... to document them, someone will have to
either a) open a bug report asking for it, b) do the work and submit it,
or c) both.
>
>>> If this happens again, if it's less practical to recreate the
>>> project, at least I might be able to fix it by adding this line.
>>>
>>> I would think it would be a good idea to document the schemas for
>>> these metadata files. I couldn't find any documentation on this
>>> file, or others like it. I'm sure I just didn't know where to look.
>>>
>>>
>>
>> Those files are probably not documented; they're not intended for user
>> modification as they are internal "state" of the WST tools.
>>
>> Eric
|
|
| |
Goto Forum:
Current Time: Wed Jan 15 06:42:50 GMT 2025
Powered by FUDForum. Page generated in 0.05028 seconds |
] 
Search
Help
Register
Login
Home
