smithproject.org

Hello,

I've decided to use the smithproject for my webapp and enjoyed the easy install with jetty on windows during development. The time to deploy is near and I'm thinking of using Sun Web Server 7.x. Anybody got it up and running on it? What are the steps? I tried to deploy the *.war using the admin webapp, here's the error that I'm getting when I try to access the smith IDE admin

java.lang.NullPointerException at
com.youngculture.smith.engine.servlets.ApplicationServices.findSmithJarPath(ApplicationServices.java:153) at
com.youngculture.smith.engine.servlets.ApplicationServices.<init>(ApplicationServices.java:132) at
com.youngculture.smith.engine.servlets.ApplicationServices.createApplicationServices(ApplicationServices.java:93)
at com.youngculture.smith.engine.servlets.Admin.init(Admin.java:126) at

org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1165) at

org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:819) at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:184) at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:255) at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:18

at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:586) at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:556) at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:187) at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:586) at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:556) at
com.sun.webserver.connector.nsapi.NSAPIProcessor.service(NSAPIProcessor.java:160)

Got it!

Somehow in the Sun Server Environment the code in :
com.youngculture.smith.engine.servlets.ApplicationServices.findSmithJarPath(ApplicationServices.java:153

String encodedUrl = getClass().getResource("").toString();

does not include the .jar name that it needs.

I had to change it to

String encodedUrl = getClass().getResource("ApplicationServices.class").toString();
and now it works!

I also forgot to check for the JAVA_HOME env var. Once that was set the admin webpage came up and running. I'll do my testing now and will report if I find any other problems.

cheers!

case closed...ron..

Hi ron,

thanks for the post!

[edit]

The line:

Code:

String encodedUrl = getClass().getResource("").toString();

returns something like this:

Code:

 Java Server:
 file:/C:/server/domains/domain1/generated/jsp/j2ee-modules/smith/loader/com/youngculture/smith/engine/servlets
 
 Jetty & Tomcat:
 jar:file:/C:/smith-bin-windows-1.3b4/wwwroot/WEB-INF/lib/smith-1.3b4.jar!/com/youngculture/smith/engine/servlets/

So, to get path to the smith jar file on Java Server, a resource inside the jar needs to be specified. It makes no difference on Jetty and Tomcat.

Ron, thanks again, this will be fixed in the next build.