Skip to main content

Deployment issue after computer upgrade

7 replies [Last post]
bakarirum
Offline
Joined: 2005-07-07

I have a project that is using jMaki in NetBeans. I saved this code off and then copied over the entire project to a new computer with a new install of NetBeans. I then made sure the appropriate jMaki module was installed in NetBeans. I then cleaned and built the application and deployed it. When I try to access a page that is using a jMaki widget, I am getting the following error. What I am missing?

<br />
HTTP Status 500 - </p>
<p>--------------------------------------------------------------------------------</p>
<p>type Exception report</p>
<p>message </p>
<p>description The server encountered an internal error () that prevented it from fulfilling this request.</p>
<p>exception </p>
<p>org.apache.jasper.JasperException: The absolute uri: <a href="http://jmaki/v1.0/jsp" title="http://jmaki/v1.0/jsp">http://jmaki/v1.0/jsp</a> cannot be resolved in either web.xml or the jar files deployed with this application<br />
	org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:51)<br />
	org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:409)<br />
	org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:116)<br />
	org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:315)<br />
	org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:148)<br />
	org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:420)<br />
	org.apache.jasper.compiler.Parser.parseDirective(Parser.java:476)<br />
	org.apache.jasper.compiler.Parser.parseElements(Parser.java:1426)<br />
	org.apache.jasper.compiler.Parser.parse(Parser.java:133)<br />
	org.apache.jasper.compiler.ParserController.doParse(ParserController.java:216)<br />
	org.apache.jasper.compiler.ParserController.parse(ParserController.java:103)<br />
	org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:167)<br />
	org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)<br />
	org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)<br />
	org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)<br />
	org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)<br />
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:317)<br />
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)<br />
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)<br />
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)<br />
	org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:390)<br />
	org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:694)<br />
	org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:665)<br />
	org.apache.jsp.index_jsp._jspService(index_jsp.java:93)<br />
	org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)<br />
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)<br />
	org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393)<br />
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)<br />
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)<br />
	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)<br />
	org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:390)</p>
<p>note The full stack trace of the root cause is available in the Apache Tomcat/6.0.14 logs.<br />

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
bakarirum
Offline
Joined: 2005-07-07

Plugin number 1.6.13.

We cannot upgrade due to previous mentioned issues.

And, yes, now that the application is deployed properly those files are in the DIST. However, I cannot verify if there were there before I deployed the "simple test application" mentioned in post 2 of this thread.

gmurray71
Offline
Joined: 2003-07-31

Hi Bakairum,

jMaki in Netbeans uses a reference to the jar resources used by jMaki.

What you can do is add them to your WEB-INF/lib

The two files you need are the org.json-0.0.2.jar and ajax-wrapper-comp-1.8.1.jar

Find them in the download:

https://ajax.dev.java.net/servlets/ProjectDocumentList?folderID=7943&exp...

The link you what is :

jmaki-java-1.8.1.zip

In the zip there is a /jmaki/lib directory under which you will find the jar files you need.

I would also suggest updating your web apps /resources/jmaki.js and /resources/jmaki-min.js with the /jmaki/scripts/jmaki.js

jdz99
Offline
Joined: 2008-11-07

I get the same error as above when manually deploying a webapp to a tomcat 5.0.28

It runs on 6.0.18 no problem.

Can I use jmaki 1.8.1 with Tomcat 5.0.28?

If so how?

Thanks,
Jim

jdz99
Offline
Joined: 2008-11-07

I installed Tomcat 5.5.7 and get the same error,

557 supports Servlet 2.4 JSP 2.0

gmurray71
Offline
Joined: 2003-07-31

Hi,

This question has come up a few time. The older 5.x (pre 5.5) versions of Tomcat have issues locating tag lib TLD files that are embedded in jar files.

You can easily fix this by downloading the latest jmaki.tld from:

https://ajax.dev.java.net/source/browse/*checkout*/ajax/ws/jmaki/shared/...

and copy it to your WEB-INF/ directory. Then you can put the following entry in your web.xml:



http://jmaki/v1.0/jsp
/WEB-INF/jmaki.tld

There is more on this topic here:

http://wiki.metawerx.net/Wiki.jsp?page=Web.xml.TagLibLocation

Please let us know if this doesn't work for you.

-Greg

bakarirum
Offline
Joined: 2005-07-07

There is definitely an issue in the NetBeans module. However, I simply created a new Web Application and imported the jMaki framework. I then dragged a jMaki widget into application and deployed it. Once I did that, the other application started working.

As info.

gmurray71
Offline
Joined: 2003-07-31

In the libraries that get included in your web app (e.g. WEB-INF/lib/) do you see a:

ajax-wrapper-comp-1.8.x.jar

and a:

org.json-0.0.2.jar

Also what version of Netbeans / jMaki Plugin are you using?

-Greg