[
https://issues.jboss.org/browse/JBIDE-12646?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich commented on JBIDE-12646:
-----------------------------------------------
Finally, it seems I have found what the problem is.
First, we check if type exists in Java project, either in sources or as a binary, in
libraries. That is ok, it cannot go wrong.
Then, if type is not found, we check if the pre-compiled class is located in the output
folder. That was done for the case of a project that has no sources and classes do not
exist in Eclipse Java project but are copied to output. And since we cannot look up for
the type, we just check
{code}
new File(pathToFile).isFile()
{code}
This works fine in Linux but it must go wrong in OS case-insensitive to file names, like
Windows and Mac OS X. [~xcoulon], could you please confirm that you work in such an OS?
web.xml servlet-name validation is not case-sensitive
-----------------------------------------------------
Key: JBIDE-12646
URL:
https://issues.jboss.org/browse/JBIDE-12646
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml/html source editing
Affects Versions: 4.0.0.Alpha1
Reporter: Xavier Coulon
Assignee: Viacheslav Kabanovich
Fix For: LATER
Attachments: JBIDE-12646 - Wi-Fi.m4v, ServletNameValidation.png
[Using the HTML5 sample project generated from Central]
I'm adding a servlet declaration in the web.xml file but the web.xml editor does not
report a warning when the servlet name case is wrong:
{code}
<servlet-mapping>
<servlet-name>org.jboss.tools.example.html5.rest.JaxrsActivator</servlet-name>
<url-pattern>/hello/*</url-pattern>
</servlet-mapping>
{code}
In the example above, the class name should be JaxRsActivator, not JaxrsActivator.
On the other hand, it properly reports a warning when a letter is missing in the
classname.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira