|
Re: dispatcher inside snap not finding path. [message #699415 is a reply to message #699397] |
Thu, 21 July 2011 14:07 |
|
Hi,
The Error you see in the log can be ignored, it's just a INFO level message getting output to system.err by tomcat for some reason, we are looking in to it. You RequestMapping should be fine assuming it comes straight after the mapping for your DispatcherServlet and that comes straight after the Snap path. So in your browser, you should be entering a path like this http://myServer.com:port/hostPath/snapsFilter/snapPath/DispatcherServlet/requestMapping. The snapPath is the one defined in your manifest header.
If this is all correct then check the Snaps filter in the host, it needs to cover all the dispatchers, otherwise the snap won't be able to find your requested view, a jsp for example.
<filter-mapping>
<filter-name>host-filter</filter-name>
<url-pattern>/*</url-pattern>
<dispatcher>INCLUDE</dispatcher>
<dispatcher>FORWARD</dispatcher>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
Let me know it goes,
Thanks, Chris.
------------------------------------------------
Chris Frost, Twitter @cgfrost
Springsource, a divison of VMware.
|
|
|
|
|
|
Re: dispatcher inside snap not finding path. [message #699600 is a reply to message #699512] |
Thu, 21 July 2011 21:42 |
|
Hi,
So we are in Spring MVC now, the message "FrameworkServlet 'standard' : initialization completed in 1714 ms" Simply means it found the context definition for the DispatcherServlet and initialized it with no problems.
The question is why it hasn't found your controllers. If your using annotation based configuration, have you got the correct annotations (@Controller) in place and scanned for the right package to find them as defined in the DispatcherServlet context?
Chris.
------------------------------------------------
Chris Frost, Twitter @cgfrost
Springsource, a divison of VMware.
|
|
|
|
Re: dispatcher inside snap not finding path. [message #702337 is a reply to message #701887] |
Tue, 26 July 2011 08:28 |
|
Your bundle class-path should be set to something like '., ./classes' for web bundles. In the project settings, go to the build information and configure the source directories. At the bottom of that page you can configure the output directory. By default it's 'bin' but we tend to use something like 'target/classes'. I'm not sure how this will affect the build from Eclipse though, we use an external build process to produce our bundles. I suspect it will work as long as your project is both an OSGi bundle project and a WTP 'Dynamic Web Project' then it should all be fine.
------------------------------------------------
Chris Frost, Twitter @cgfrost
Springsource, a divison of VMware.
|
|
|
Powered by
FUDForum. Page generated in 0.03948 seconds