This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 232326 - WARNING: Context path from ServletContext: differs from path from bundle:
Summary: WARNING: Context path from ServletContext: differs from path from bundle:
Status: RESOLVED INVALID
Alias: None
Product: javaee
Classification: Unclassified
Component: Web Project (show other bugs)
Version: 7.3.1
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: David Konecny
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-06 17:24 UTC by raed3bsi
Modified: 2016-01-16 05:13 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
I WANT TO CREATE A JMS APPLICATION FOR THIS IN THE CONSOLE I WANT TO CREATE A NEW JMS FACTORY CONNECTION, BUT IT SAYS JAVA.CLASS.LANG.RUNTIMEEXCEPTION (5.02 KB, text/plain)
2016-01-16 05:13 UTC, harsh.gupta
Details

Note You need to log in before you can comment on or make changes to this bug.
Description raed3bsi 2013-07-06 17:24:18 UTC

    
Comment 1 raed3bsi 2013-07-06 17:59:17 UTC
when running any web application, I always got the following error:
WARNING: Context path from ServletContext:/example differs from path from bundle: example.
That cause actionListeners not called from any implicitly returned form (a form that retrieved as ajax response).
Comment 2 David Konecny 2013-07-07 21:29:52 UTC
This sounds like a problem in your own application and not a NetBeans IDE defect. If I misunderstood you please provide steps to perform in the NetBeans IDE to reproduce the defect and what is expected behaviour. Thx.
Comment 3 Sylnsr 2013-07-17 21:37:34 UTC
I too have experienced this exact issue. My project was working before with no issues whatsoever then one day I came back to the project; tried to run it in debug mode (so that I could see what a client was passing to the web service) and it would no longer deploy. I do note however that this seems to be an issue with the Glassfish 4 server. My project is located here: https://github.com/sylnsr/docx4j-ws
Comment 4 Sylnsr 2013-07-17 22:43:55 UTC
I resolved my issue. I am using Intelli-J. I checked the project settings and found the issue there. The project always used to was when the Artifact Type was set to WAR Exploded. For some reason is was set to WAR (not exploded). I switched it back to Exploded and the app deployed fine. I suspect that you are using Glassfish and that your Netbeans project configuration may have the same issue (just guessing).

For the record, this is a horrible red herring that Glassfish4 throws.

(In reply to comment #3)
> I too have experienced this exact issue. My project was working before with no
> issues whatsoever then one day I came back to the project; tried to run it in
> debug mode (so that I could see what a client was passing to the web service)
> and it would no longer deploy. I do note however that this seems to be an issue
> with the Glassfish 4 server. My project is located here:
> https://github.com/sylnsr/docx4j-ws
Comment 5 Sylnsr 2013-07-17 22:47:12 UTC
Correction: The particular application referenced run when the Artifact Type is "JavaEE Application: Exploded"

(In reply to comment #4)
> I resolved my issue. I am using Intelli-J. I checked the project settings and
> found the issue there. The project always used to was when the Artifact Type
> was set to WAR Exploded. For some reason is was set to WAR (not exploded). I
> switched it back to Exploded and the app deployed fine. I suspect that you are
> using Glassfish and that your Netbeans project configuration may have the same
> issue (just guessing).
> 
> For the record, this is a horrible red herring that Glassfish4 throws.
> 
> (In reply to comment #3)
> > I too have experienced this exact issue. My project was working before with no
> > issues whatsoever then one day I came back to the project; tried to run it in
> > debug mode (so that I could see what a client was passing to the web service)
> > and it would no longer deploy. I do note however that this seems to be an issue
> > with the Glassfish 4 server. My project is located here:
> > https://github.com/sylnsr/docx4j-ws
Comment 6 David Konecny 2013-07-23 00:00:07 UTC
(In reply to comment #4)
> I suspect that you are
> using Glassfish and that your Netbeans project configuration may have the same
> issue (just guessing).

AFAICT, NetBeans deploy project in exploded form. But it should be relatively simple to narrow this issue down to a reproducible test case.

Btw. is there an issue filed for GF server in their bugzilla? Could you add a link here to the issue if you know it? Thanks.
Comment 7 bugmenot1 2013-07-25 14:57:48 UTC
I got rid of the message by removing the leading slash from the context root (defined in glassfish-web.xml in a simple web application or in application.xml in an EAR).

Source for the log entry is RealmAdapter.getAppContextID(final ServletContext servletContext): https://java.net/projects/glassfish/sources/svn/content/trunk/main/appserver/security/webintegration/src/main/java/com/sun/web/security/RealmAdapter.java
Comment 8 harsh.gupta 2016-01-16 05:13:54 UTC
Created attachment 158152 [details]
I WANT TO CREATE A JMS APPLICATION FOR THIS IN THE CONSOLE I WANT TO CREATE A NEW JMS FACTORY CONNECTION, BUT IT SAYS JAVA.CLASS.LANG.RUNTIMEEXCEPTION