| (jspf fragment) was not found at expected path - Adding external [message #687563] |
Wed, 22 June 2011 18:35  |
 Dale 
Messages: 6
Registered: July 2009 |
Junior Member |
|
|
Rather than turning off jspf validation, I'd rather try and get WTP to "see" some jsp's that are part of a core web application that is not in my project, but is in the final build.
Yeah, so I've got two builds I do. One is the auto build that Eclipse does, and the other is an Apache Ant script that unpacks a core bunch of files, then follows that step with writing files out of my project. So the resulting build folder has more than what's in my project.
That all works pretty good, except that I get tons of "(jspf fragment) was not found at expected path" errors. Since the core files don't change at all, I would like to set those up somehow so that the jsp validator could "see" them.
In other words, is it possible for me to put the external jsp files somewhere, then configure the jsp validator to recognize that these files, although not in (project)/WEB-INF/web/blahblah (where it expects them), are really in this external location?
--Dale--
|
|
|
|
| Re: (jspf fragment) was not found at expected path - Adding external [message #689166 is a reply to message #687563] |
Mon, 27 June 2011 02:53  |
|
On 6/22/2011 2:35 PM, Dale wrote:
> In other words, is it possible for me to put the external jsp files
> somewhere, then configure the jsp validator to recognize that these
> files, although not in (project)/WEB-INF/web/blahblah (where it expects
> them), are really in this external location?
No, not without really diving into the
..settings/org.eclipse.wst.common.component file and declaring where
everything actually does come from. The JSP Validators will respect its
contents.
--
Nitin Dahyabhai
Eclipse WTP Source Editing and JSDT
IBM Rational
_
Nitin Dahyabhai
Eclipse Web Tools Platform
|
|
|
|
|
| Re: (jspf fragment) was not found at expected path - Adding external [message #689622 is a reply to message #689536] |
Tue, 28 June 2011 02:29 |
|
On 6/27/2011 3:30 PM, Dale wrote:
> Nitin, Thanks for the reply. I don't mind digging around in a
> configuration file, but there seems to be not enough information from
> what you wrote to guide me.
>
> When I look at that configuration file, there's only 3 bits of info in
> there, and two have to do with a "classes" (Java, not jsp). The only
> other is the context root. It doesn't allow me to put in a fully
> qualified file path the context root. And even if I put the fully
> qualified path directly into the config text file, it still does not see
> the jsp's from the build path.
>
> So could you be more specific about how one would make changes to allow
> the validator to see the external jsp path?
Unfortunately I'm not an expert on how you author that file by hand as
I've only seen it accessed through APIs, and really only know that the
JSP validator will make use of its contents. As you probably saw,
however, multiple paths from the the project can be deployed to the same
location on the server. You might want to do some experimentation with
linked resources (the Advanced section in the New File and New Folder
wizard) and how specifically you can set up the deployment.
--
Nitin Dahyabhai
Eclipse WTP Source Editing and JSDT
IBM Rational
_
Nitin Dahyabhai
Eclipse Web Tools Platform
|
|
|
|
|
| Re: (jspf fragment) was not found at expected path - Adding external [message #690618 is a reply to message #689837] |
Wed, 29 June 2011 20:33 |
|
On 6/28/2011 9:22 AM, Greg Amerson wrote:
> Thanks for the info Nitin. Do you have any idea if it is possible to add
> additional web content through this file where it will validated/indexed
> but it will not be deployed?
I do not know, but why should it be web content, then?
--
Nitin Dahyabhai
Eclipse WTP Source Editing and JSDT
IBM Rational
_
Nitin Dahyabhai
Eclipse Web Tools Platform
|
|
|
|
|
Powered by
FUDForum. Page generated in 7.53332 seconds
] 
Search
Help
Register
Login
Home
