- This topic has 8 replies, 6 voices, and was last updated 8 years, 3 months ago by support-tony.
-
AuthorPosts
-
Alejandro RicoMemberHello everybody;
This should fit in -Success Story- 😀
A couple of weeks ago; I was wondering how to make MyEclipse to Syntax Check my JSPs; I have found that in
Preferences –> MyEclipse –> Editors –> JSP/HTML Editor –> General
is a radio button [which is selected] indicating to Compile JSPs
But even If I put non-sense text in the JSP; there were no indication of the syntax error. (The Code Completion works just Fine!).
Then I’ve Installed LOMBOZ Plugin; and re-configured eclipse to keep MyEclipse as the Default JSP Editor.
And then I’ve got Syntax Checking Working! 🙂
==== Up to This Far goes the Success Story 🙂 ======
That works fine for me, but leave me the question:
Why Eclipse is calling the Lomboz Syntax Check when the Editor used to open the JSPs is MyEclipse JSP Editor?
I have double check that I am actually using the MyEclipse JSP Editor istead of the Lomboz One.
BTW: Im Using MyEclipse 3.0M6
Saludos
Alejandro
Riyad KallaMemberAlejandro,
Can you give us an example of the “nonsense” text that you were typing into the page originally that was not being marked as an error, and then show what Lomboz is marking as an error?This sounds very strange…
Riyad KallaMemberAparently there are some incompatabilities with Lomboz and MyEclipse that could explain why you are seeing this cross-over behavior. Unfortunately this is not a support configuration, and to help avoid any conflicts, I would suggest using the products in separate installations of Eclispe to avoid any further conflicts.
While it might seem great that the current conflict is more accurate error checking, you might run into problems down the road with wizards not working or deployments failing and not be sure why. Our first suggestion would to be to get rid of all conflicting plugins (Lomboz being one of them and XML Buddy/XMen/JBossIDE being others). These conflicts stem from the fact that sometimes our plugins are branches from these open source projects and conflicts occur, and other times its just a functionality conflict (i.e. one plugin will take the file association for a certain file type, and you won’t get the full MyEclipse experience).
Alejandro RicoMemberHello;
I Have made the folowing Test:
Extracted : eclipse-SDK-3.0M6-win32.zip
Installed : EnterpriseWorkbenchInstaller_030700RC2.exe
Copied : templates_es.properties to <MyEclipse-Dir>\plugins\com.genuitec.eclipse.wizards_3.6.200
Run: : eclipse.exe
Checked : MyEclipse Perspective EXISTSCase One
========
Create : New J2EE Web Project
Create : New JSP : One.jsp
Checked : Syntax Check on One.jsp is OK (added garbage; and MyEclipse noticed it)Case Two
========
Create : New Simple Project
Team : Selected TEAM -> Share-Project
Update : TEAM –> Update : get Latest Version
Checked : Opened *any* JSP; add garbage (“asd ad asd ad ad;”)
Checked : There is no message or mark of Syntax Error.After Checking-Out the project from CVS; I have noticed that the option (with Right-Click on the Project Root) MyEclipse –> Add-WebProject-Capabilities is disabled; the I could not test putting that option on.
The reason I have selected Simple-Project is because in this project the directory structure is kinda messy; and I have to set manually where are the source folders and so on.
If I Select Enterprise Application Project; the wizard forces me to define a Web-App and at least One EJB; leaving a differerent directory structure from what the application haves.
Then maybe the question would be:
How can I tell MyEclipse to Perform JSP Syntax Checking if I have started with a Simple Project ?
———–
Sorry for the topic tweak; started from a –Success Story– and ended with one more –Support– issue 😳
Saludos
Alejandro
Scott AndersonParticipantAlejandro,
The example with a simple project won’t work because it is not a java project and not a web project. This basically means that the Java project builder is not active for the project and it is within this build loop that all the syntax checking and validation is performed. Without the builder, nothing can happen.
To get what you want, you really need to develop your JSP’s within a MyEclipse Web project.
Alejandro RicoMemberOk, Thanks!
Saludos
hnoor0066Participantthanks for everything
_______________
NOOR- This reply was modified 8 years, 8 months ago by hnoor0066.
gopinath8940ParticipantAug 27, 2016 8:34:08 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property ‘source’ to ‘org.eclipse.jst.jee.server:Banking’ did not find a matching property.
Aug 27, 2016 8:34:08 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property ‘source’ to ‘org.eclipse.jst.jee.server:payment’ did not find a matching property.
Aug 27, 2016 8:34:08 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server version: Apache Tomcat/8.0.18
Aug 27, 2016 8:34:08 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server built: Jan 23 2015 11:56:07 UTC
Aug 27, 2016 8:34:08 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server number: 8.0.18.0
Aug 27, 2016 8:34:08 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Name: Windows 7
Aug 27, 2016 8:34:08 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Version: 6.1
Aug 27, 2016 8:34:08 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Architecture: amd64
Aug 27, 2016 8:34:08 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Java Home: C:\Program Files\Java\jre1.8.0_101
Aug 27, 2016 8:34:08 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Version: 1.8.0_101-b13
Aug 27, 2016 8:34:08 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Vendor: Oracle Corporation
Aug 27, 2016 8:34:08 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_BASE: C:\Users\Gopinath\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0
Aug 27, 2016 8:34:08 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_HOME: C:\Apache\apache-tomcat-8.0.18
Aug 27, 2016 8:34:08 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dcatalina.base=C:\Users\Gopinath\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0
Aug 27, 2016 8:34:08 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dcatalina.home=C:\Apache\apache-tomcat-8.0.18
Aug 27, 2016 8:34:08 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dwtp.deploy=C:\Users\Gopinath\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps
Aug 27, 2016 8:34:08 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.endorsed.dirs=C:\Apache\apache-tomcat-8.0.18\endorsed
Aug 27, 2016 8:34:08 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Dfile.encoding=Cp1252
Aug 27, 2016 8:34:08 PM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jre1.8.0_101\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:/Program Files/Java/jre1.8.0_101/bin/server;C:/Program Files/Java/jre1.8.0_101/bin;C:/Program Files/Java/jre1.8.0_101/lib/amd64;C:\PROGRA~2\RATIONAL\RATION~1\NUTCROOT\bin;C:\PROGRA~2\RATIONAL\RATION~1\NUTCROOT\bin\x11;C:\PROGRA~2\RATIONAL\RATION~1\NUTCROOT\mksnt;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files (x86)\Rational\common;C:\Program Files (x86)\Rational\ClearQuest;C:\Program Files (x86)\Rational\Rose\TopLink\;C:\Program Files (x86)\Rational\Rational Test;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\eclipse;;.
Aug 27, 2016 8:34:08 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [“http-nio-8080”]
Aug 27, 2016 8:34:09 PM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector
INFO: Using a shared selector for servlet write/read
Aug 27, 2016 8:34:09 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [“ajp-nio-8009”]
Aug 27, 2016 8:34:09 PM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector
INFO: Using a shared selector for servlet write/read
Aug 27, 2016 8:34:09 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 3265 ms
Aug 27, 2016 8:34:09 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Aug 27, 2016 8:34:09 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/8.0.18
Aug 27, 2016 8:34:11 PM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Aug 27, 2016 8:34:12 PM org.apache.jasper.servlet.TldScanner scanJars
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Aug 27, 2016 8:34:12 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [“http-nio-8080”]
Aug 27, 2016 8:34:12 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [“ajp-nio-8009”]
Aug 27, 2016 8:34:12 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 2337 ms
Aug 27, 2016 8:35:35 PM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet [jsp] in context with path [/Banking] threw exception [Unable to compile class for JSP:An error occurred at line: 18 in the jsp file: /contactBean.jsp
Session cannot be resolved to a type
15: props.put(“mail.smtp.auth”, “true”);
16: props.put(“mail.smtp.port”, “465”);
17:
18: Session session1 = Session.getDefaultInstance(props,
19: new javax.mail.Authenticator() {
20: protected PasswordAuthentication getPasswordAuthentication() {
21: return new PasswordAuthentication(“[email protected]”,”hi2hello”);An error occurred at line: 18 in the jsp file: /contactBean.jsp
Session cannot be resolved
15: props.put(“mail.smtp.auth”, “true”);
16: props.put(“mail.smtp.port”, “465”);
17:
18: Session session1 = Session.getDefaultInstance(props,
19: new javax.mail.Authenticator() {
20: protected PasswordAuthentication getPasswordAuthentication() {
21: return new PasswordAuthentication(“[email protected]”,”hi2hello”);An error occurred at line: 19 in the jsp file: /contactBean.jsp
javax.mail.Authenticator cannot be resolved to a type
16: props.put(“mail.smtp.port”, “465”);
17:
18: Session session1 = Session.getDefaultInstance(props,
19: new javax.mail.Authenticator() {
20: protected PasswordAuthentication getPasswordAuthentication() {
21: return new PasswordAuthentication(“[email protected]”,”hi2hello”);
22: }An error occurred at line: 28 in the jsp file: /contactBean.jsp
MimeMessage cannot be resolved to a type
25: //compose message
26: try {
27:
28: MimeMessage message = new MimeMessage(session1);
29: message.setFrom(new InternetAddress(“[email protected]”));
30: message.addRecipient(Message.RecipientType.TO,new InternetAddress(to));
31: message.setSubject(s);An error occurred at line: 28 in the jsp file: /contactBean.jsp
MimeMessage cannot be resolved to a type
25: //compose message
26: try {
27:
28: MimeMessage message = new MimeMessage(session1);
29: message.setFrom(new InternetAddress(“[email protected]”));
30: message.addRecipient(Message.RecipientType.TO,new InternetAddress(to));
31: message.setSubject(s);An error occurred at line: 29 in the jsp file: /contactBean.jsp
InternetAddress cannot be resolved to a type
26: try {
27:
28: MimeMessage message = new MimeMessage(session1);
29: message.setFrom(new InternetAddress(“[email protected]”));
30: message.addRecipient(Message.RecipientType.TO,new InternetAddress(to));
31: message.setSubject(s);
32: message.setText(m);An error occurred at line: 30 in the jsp file: /contactBean.jsp
Message.RecipientType.TO cannot be resolved to a type
27:
28: MimeMessage message = new MimeMessage(session1);
29: message.setFrom(new InternetAddress(“[email protected]”));
30: message.addRecipient(Message.RecipientType.TO,new InternetAddress(to));
31: message.setSubject(s);
32: message.setText(m);
33:An error occurred at line: 30 in the jsp file: /contactBean.jsp
InternetAddress cannot be resolved to a type
27:
28: MimeMessage message = new MimeMessage(session1);
29: message.setFrom(new InternetAddress(“[email protected]”));
30: message.addRecipient(Message.RecipientType.TO,new InternetAddress(to));
31: message.setSubject(s);
32: message.setText(m);
33:An error occurred at line: 35 in the jsp file: /contactBean.jsp
Transport cannot be resolved
32: message.setText(m);
33:
34: //send message
35: Transport.send(message);
36: session.setAttribute(“contact_status”,”true”);
37: response.sendRedirect(“contact.jsp”);
38:An error occurred at line: 40 in the jsp file: /contactBean.jsp
MessagingException cannot be resolved to a type
37: response.sendRedirect(“contact.jsp”);
38:
39:
40: } catch (MessagingException e) {throw new RuntimeException(e);}
41:
42:
43: %>Stacktrace:] with root cause
org.apache.jasper.JasperException: Unable to compile class for JSP:An error occurred at line: 18 in the jsp file: /contactBean.jsp
Session cannot be resolved to a type
15: props.put(“mail.smtp.auth”, “true”);
16: props.put(“mail.smtp.port”, “465”);
17:
18: Session session1 = Session.getDefaultInstance(props,
19: new javax.mail.Authenticator() {
20: protected PasswordAuthentication getPasswordAuthentication() {
21: return new PasswordAuthentication(“[email protected]”,”hi2hello”);An error occurred at line: 18 in the jsp file: /contactBean.jsp
Session cannot be resolved
15: props.put(“mail.smtp.auth”, “true”);
16: props.put(“mail.smtp.port”, “465”);
17:
18: Session session1 = Session.getDefaultInstance(props,
19: new javax.mail.Authenticator() {
20: protected PasswordAuthentication getPasswordAuthentication() {
21: return new PasswordAuthentication(“[email protected]”,”hi2hello”);An error occurred at line: 19 in the jsp file: /contactBean.jsp
javax.mail.Authenticator cannot be resolved to a type
16: props.put(“mail.smtp.port”, “465”);
17:
18: Session session1 = Session.getDefaultInstance(props,
19: new javax.mail.Authenticator() {
20: protected PasswordAuthentication getPasswordAuthentication() {
21: return new PasswordAuthentication(“[email protected]”,”hi2hello”);
22: }An error occurred at line: 28 in the jsp file: /contactBean.jsp
MimeMessage cannot be resolved to a type
25: //compose message
26: try {
27:
28: MimeMessage message = new MimeMessage(session1);
29: message.setFrom(new InternetAddress(“[email protected]”));
30: message.addRecipient(Message.RecipientType.TO,new InternetAddress(to));
31: message.setSubject(s);An error occurred at line: 28 in the jsp file: /contactBean.jsp
MimeMessage cannot be resolved to a type
25: //compose message
26: try {
27:
28: MimeMessage message = new MimeMessage(session1);
29: message.setFrom(new InternetAddress(“[email protected]”));
30: message.addRecipient(Message.RecipientType.TO,new InternetAddress(to));
31: message.setSubject(s);An error occurred at line: 29 in the jsp file: /contactBean.jsp
InternetAddress cannot be resolved to a type
26: try {
27:
28: MimeMessage message = new MimeMessage(session1);
29: message.setFrom(new InternetAddress(“[email protected]”));
30: message.addRecipient(Message.RecipientType.TO,new InternetAddress(to));
31: message.setSubject(s);
32: message.setText(m);An error occurred at line: 30 in the jsp file: /contactBean.jsp
Message.RecipientType.TO cannot be resolved to a type
27:
28: MimeMessage message = new MimeMessage(session1);
29: message.setFrom(new InternetAddress(“[email protected]”));
30: message.addRecipient(Message.RecipientType.TO,new InternetAddress(to));
31: message.setSubject(s);
32: message.setText(m);
33:An error occurred at line: 30 in the jsp file: /contactBean.jsp
InternetAddress cannot be resolved to a type
27:
28: MimeMessage message = new MimeMessage(session1);
29: message.setFrom(new InternetAddress(“[email protected]”));
30: message.addRecipient(Message.RecipientType.TO,new InternetAddress(to));
31: message.setSubject(s);
32: message.setText(m);
33:An error occurred at line: 35 in the jsp file: /contactBean.jsp
Transport cannot be resolved
32: message.setText(m);
33:
34: //send message
35: Transport.send(message);
36: session.setAttribute(“contact_status”,”true”);
37: response.sendRedirect(“contact.jsp”);
38:An error occurred at line: 40 in the jsp file: /contactBean.jsp
MessagingException cannot be resolved to a type
37: response.sendRedirect(“contact.jsp”);
38:
39:
40: } catch (MessagingException e) {throw new RuntimeException(e);}
41:
42:
43: %>Stacktrace:
at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:102)
at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:198)
at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:450)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:361)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:336)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:323)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:570)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:356)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:396)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:340)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:610)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:516)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1086)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:659)
at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:223)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1558)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1515)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Unknown Source)
support-tonyKeymastergopinath8940,
I’m not sure if you’ve accidentally posted a reply to this topic. You’ve provided no information about your issue other than part of a Tomcat log. If you think this is a MyEclipse issue, please raise a new topic on this forum as it is highly unlikely to be similar to the original issue, from 12 years ago and this very old topic will be closed. If you do raise a new topic, please include as much information as possible about your use of MyEclipse (including the MyEclipse build number, the OS used and a full description of the problem).
-
AuthorPosts