| Re: JSF app no longer deploys class files [message #475404] |
Mon, 04 February 2008 12:03  |
Eclipse User |
|
|
|
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 #475530 is a reply to message #475407] |
Mon, 04 February 2008 17:35  |
| Eclipse User |
|
|
|
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
|
|
|
|
| Re: JSF app no longer deploys class files [message #616505 is a reply to message #475404] |
Mon, 04 February 2008 12:12 |
| Eclipse User |
|
|
|
The problem with amazing tools like Eclipse is that sometimes they don't
work properly. If the plugin somehow gets the internal state confused,
unless I know the hidden information about the structure of these files,
my only recourse is to just start over. If the structure of these files
was documented in a reasonable place, I'd at least have a chance of being
able to fix it without having to start over. If I make a mistake and the
result doesn't work, I'm no worse off than I was in the first place.
|
|
|
| Re: JSF app no longer deploys class files [message #616509 is a reply to message #475404] |
Mon, 04 February 2008 12: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 #617106 is a reply to message #475407] |
Mon, 04 February 2008 17:35 |
| Eclipse User |
|
|
|
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
|
|
|
|
Powered by
FUDForum. Page generated in 0.04376 seconds
Home