Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JSP Vaildation Error after import to STS #14

Closed
kdvolder opened this issue May 3, 2013 · 7 comments
Closed

JSP Vaildation Error after import to STS #14

kdvolder opened this issue May 3, 2013 · 7 comments

Comments

@kdvolder
Copy link
Member

kdvolder commented May 3, 2013

We'd like to include PetClinic as a sample app on the STS dashboard.

Unfortunately it has a validation error when I import the current master branch to STS as an m2e project.

This is the error I am getting:

pageContext cannot be resolved inputField.tag
/spring-pet-clinic/src/main/webapp/WEB-INF/tags
line 11
JSP Problem

Any idea what this error means and how to fix it?

It may very well be the problem isn't actually with the App but with the validations or Eclipse classpath. The app seems to deploy just fine to Tc Server in STS despite the error.

@aclement
Copy link

aclement commented May 3, 2013

Kris, you should have asked me about this. It is a known problem, it is already raised in our STS jira and I think Leo discovered it is a bug in some WTP bits and pieces that we are picking up.

@aclement
Copy link

aclement commented May 3, 2013

@michaelisvy
Copy link

Thanks a lot for taking care of it. My only workaround was to disable the relevant Eclipse validators. It seems that there is an Eclipse patch already. Andy, have you had the opportunity to test it?

@aclement
Copy link

aclement commented May 3, 2013

I don't think we have tested that patch yet. We'll try to get to it.

@michaelisvy
Copy link

Just a quick update on that: this Eclipse bug has been resolved in Eclipse Kepler (4.3).

You can download STS 3.3 based on 2 Eclipse distribs: 3.8 (Juno) or 4.3 (Kepler). It has been done that way because Kepler used to be really slow (but it has improved a lot in the past 6 months).

So in order to have this bug fixed, you should download STS 3.3 based on Eclipse 4.3.

If you can't use that version of Eclipse, you still can disable the relevant validators. To do so:

  1. Right click on the spring-petclinic project
  2. Select "Properties"
  3. Validation -> JSP Syntax -> Enable Project specific settings (and you should uncheck one of the options there, I don't remember which one as I'm using Kepler myself)

@naray89k
Copy link

naray89k commented Mar 5, 2015

Hi ..... I would like to deploy this application in Cloud Foundry as a POC for CF implementation.
Could you please give the details steps to Deploy this application in cloud foundry ....

@michaelisvy
Copy link

@naray89k You can just follow this tutorial: https://spring.io/guides/gs/sts-cloud-foundry-deployment/

Regards,
Michael.

dsyer pushed a commit that referenced this issue Nov 21, 2016
Update for changes in github pages
mariusoe pushed a commit to JonasKunz/spring-petclinic that referenced this issue May 11, 2021
mariusoe pushed a commit to JonasKunz/spring-petclinic that referenced this issue May 11, 2021
…ectory

spring-projects#14 Do not fail maven build of the .git directory is missing
dwinchell pushed a commit to dwinchell/spring-petclinic that referenced this issue Sep 27, 2022
* Changed workflow definition to use full workflow

* Changed to point to feature branch for testing

* Renamed job to full

* Moved branch definition back to main
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants