glassfish « Error « JSP-Servlet Q&A





1. glassfish error    stackoverflow.com

SEVERE: javax.naming.NamingException: Lookup failed for 'jdbc:mysql://localhost:3306/sample ' in SerialContext [Root exception is javax.naming.NameNotFoundException: jdbc:mysql:] what to do to rectify? i am running jsp code in netbeans and i am using mysql as ...

2. Diagnosing 404 error issue with servlet (Eclipse and Glassfish 3)    stackoverflow.com

I am in the process of writing a Java web app and am having issues getting my servlet to work properly. This is from my web.xml file:

  <servlet>
    ...

3. Glassfish v2.x CORE5048 error    coderanch.com

I am seeing this error, and have no idea what is causing it. I assume its more of an warning than an error. CORE5048: generated dir is obsolete compared to default-web.xml for application fnfapp; loading from application directory /home/pfarrell/sandbox/bbook/trunk/fnfapp/build/web instead. This takes longer than loading from the generated directory; redeploying the app will recreate the generated directory but is not required. ...

4. Object is not of remote type error in GlassFish v3    coderanch.com

Prasad, I regularly test this way from JUnit running in Eclipse. Below are samples that are working just fine in JBOSS and GlassFish V2. The problem seems to be when attempting to narrow the remote object, but I am away from the laptop where I am having the problem at the moment. I need to see what it is trying to ...

6. Why is Glassfish error page appended to my own JSP error page?    java.net

> Anyway, I have tested plain JSP pages with page > directive errorPage and isErrorPage, and they worked > as expected. I'll check with out JSF expert to see > if JSF does its own error processing and somehow > interferes with JSP errorPage. > > It'd also help if you can provide a simple war that > demonstrates this problem. ...

8. Enums, JSP, setProperty, error, fail, not working (other similar keywords)    java.net

I believed this to be a problem with my EL configuration, which I have since decided that it was not. Jsp is doing a simple, direct injection thing here, while I was expecting it to interpret the text in my attribute as a ValueExpression. This is what is to be expected with the useBean action. If a custom tag with a ...