You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by David Wynter <da...@roamware.co.uk> on 2003/10/01 16:53:32 UTC
HELP?: Looking for VelocityPage.vm?
Hi,
I have traced through the masses of init and assembler stuff in T2.3 to try
to find out why it is trying to find VelocityPage.vm when it does not in
previous versions. What i found is that it all look legitimate. With
services.VelocityService.template.extension=vm
services.VelocityService.default.page=VelocityPage
services.VelocityService.default.screen=VelocityScreen
services.VelocityService.default.layout=RoleBasedLayout
services.VelocityService.default.navigation=VelocityNavigation
services.VelocityService.default.error.screen = VelocityErrorScreen
services.VelocityService.default.layout.template = Default.vm
in your TR.props the init constructs a defaultPage value on line 776 of
Turbine.java. This is then used by the assemblers to find the page. It calls
down through stuff until BaseTemplateMapper.getDefaultName(String template).
So in theBaseTemplateMapper method it takes my "Login.vm" string and takes
the extension off it and adds this to the end of the value set in
"services.VelocityService.default.page" - result "VelocityPage.vm" in the
defaultPage. Clearly it is never going to find a class called
"org.apache.turbine.modules.VelocityPage.vm" so it fails.
I cannot understand how this ever worked and am more confused than ever.
Does anyone understand how this is supposed to work and can they explain it
in simple terms? I am using the T2.3 release code and am on JDK 1.4.1_01 and
W2K.
Thanks
David
> -----Original Message-----
> From: David Wynter [mailto:david@roamware.co.uk]
> Sent: 29 September 2003 12:30
> To: Turbine-User
> Subject: Looking for VelocityPage.vm?
>
>
> Hi,
>
> I have the Velocity service configuration as in the example
> TR.props in the
> distribution with T2.3. The RoleBasedLayout overrides the path used for
> finding layout, navigations and screens based on the role,
> something simple
> that has worked for 2 years now, I don't believe it is the problem.
>
> services.VelocityService.template.extension=vm
> services.VelocityService.default.page=VelocityPage
> services.VelocityService.default.screen=VelocityScreen
> services.VelocityService.default.layout=RoleBasedLayout
> services.VelocityService.default.navigation=VelocityNavigation
> services.VelocityService.default.error.screen = VelocityErrorScreen
> services.VelocityService.default.layout.template = Default.vm
>
> The error I get is:
>
> ...
> [DEBUG] DefaultTurbineRunData - -Returning default Charset of ISO-8859-1
> [DEBUG] PageLoader - -Loading Page VelocityPage.vm from the
> Assembler Broker
> [DEBUG] JavaPageFactory - -Class Fragment is VelocityPage.vm
> [DEBUG] JavaPageFactory - -Trying
> com.roamware.rwtransform.modules.pages.VelocityPage.vm
> [DEBUG]
> JavaPageFactory - -com.roamware.rwtransform.modules.pages.VelocityPage.vm:
> Not found
> [DEBUG] JavaPageFactory - -Trying
> org.apache.turbine.modules.pages.VelocityPage.vm
> [DEBUG] JavaPageFactory -
> -org.apache.turbine.modules.pages.VelocityPage.vm:
> Not found
> [DEBUG] JavaPageFactory - -Returning: null
> [ERROR] Turbine - -Turbine.handleException:
> <java.lang.ClassNotFoundException:
>
> Requested Page not found: VelocityPage.vm
> Turbine looked in the following modules.packages path:
> [com.roamware.rwtransform.modules, org.apache.turbine.modules]
> >java.lang.ClassNotFoundException:
>
> Requested Page not found: VelocityPage.vm
> Turbine looked in the following modules.packages path:
> [com.roamware.rwtransform.modules, org.apache.turbine.modules]
>
> at
> org.apache.turbine.modules.PageLoader.getInstance(PageLoader.java:207)
> at org.apache.turbine.modules.PageLoader.exec(PageLoader.java:136)
> at org.apache.turbine.Turbine.doGet(Turbine.java:796)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
>
> Why is it looking for VelocityPage.vm? I can understand it would use
> VelocityPage.class but I have never had VelocityPage.vm ever? It refers to
> VelocityPage.vm as a Class Fragment, which doesn't make sense? I could not
> find anything specifically on this problem in the archives. Lots of layout
> related problems, but not looking for VelocityPage.vm problems.
>
> Ideas?
>
> David Wynter
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
RE: HELP?: Looking for VelocityPage.vm?
Posted by Eric Pugh <ep...@upstate.com>.
All of those have default values, so it probably is the mix...
Eric
> -----Original Message-----
> From: David Wynter [mailto:david@roamware.co.uk]
> Sent: Wednesday, October 01, 2003 5:38 PM
> To: Turbine Users List
> Subject: RE: HELP?: Looking for VelocityPage.vm?
>
>
> Well, a solution of sorts.
>
> If I comment out the following:
>
> #services.TemplateService.mapper.page.class =
> org.apache.turbine.services.template.mapper.DirectTemplateMapper
> #services.TemplateService.mapper.screen.class =
> org.apache.turbine.services.template.mapper.ClassMapper
> #services.TemplateService.mapper.layout.class =
> org.apache.turbine.services.template.mapper.ClassMapper
> #services.TemplateService.mapper.navigation.class =
> org.apache.turbine.services.template.mapper.ClassMapper
> #services.TemplateService.mapper.layout.template.class =
> org.apache.turbine.services.template.mapper.LayoutTemplateMapper
> #services.TemplateService.mapper.screen.template.class =
> org.apache.turbine.services.template.mapper.ScreenTemplateMapper
> #services.TemplateService.mapper.navigation.template.class =
> org.apache.turbine.services.template.mapper.DirectTemplateMapper
>
> It works. Go figure. I never had this section in the earlier
> TR.props? Maybe
> it is a mix of old and new ways of doing things.
>
> David
>
>
> > -----Original Message-----
> > From: David Wynter [mailto:david@roamware.co.uk]
> > Sent: 01 October 2003 16:08
> > To: Turbine Users List
> > Subject: RE: HELP?: Looking for VelocityPage.vm?
> >
> >
> > Hi,
> >
> > I left off some key details below. The place that it uses
> defaultPage to
> > look for a class of that name is between lines 114 and 126 of
> > JavaBaseFactory.java.
> >
> > David
> >
> > > -----Original Message-----
> > > From: David Wynter [mailto:david@roamware.co.uk]
> > > Sent: 01 October 2003 15:54
> > > To: Turbine Users List
> > > Subject: HELP?: Looking for VelocityPage.vm?
> > >
> > >
> > > Hi,
> > >
> > > I have traced through the masses of init and assembler stuff in
> > > T2.3 to try
> > > to find out why it is trying to find VelocityPage.vm when
> it does not in
> > > previous versions. What i found is that it all look
> legitimate. With
> > >
> > > services.VelocityService.template.extension=vm
> > > services.VelocityService.default.page=VelocityPage
> > > services.VelocityService.default.screen=VelocityScreen
> > > services.VelocityService.default.layout=RoleBasedLayout
> > > services.VelocityService.default.navigation=VelocityNavigation
> > > services.VelocityService.default.error.screen =
> VelocityErrorScreen
> > > services.VelocityService.default.layout.template = Default.vm
> > >
> > > in your TR.props the init constructs a defaultPage value
> on line 776 of
> > > Turbine.java. This is then used by the assemblers to find the
> > > page. It calls
> > > down through stuff until BaseTemplateMapper.getDefaultName(String
> > > template).
> > > So in theBaseTemplateMapper method it takes my "Login.vm"
> > string and takes
> > > the extension off it and adds this to the end of the value set in
> > > "services.VelocityService.default.page" - result
> > "VelocityPage.vm" in the
> > > defaultPage. Clearly it is never going to find a class called
> > > "org.apache.turbine.modules.VelocityPage.vm" so it fails.
> > >
> > > I cannot understand how this ever worked and am more
> confused than ever.
> > >
> > > Does anyone understand how this is supposed to work and can they
> > > explain it
> > > in simple terms? I am using the T2.3 release code and am on JDK
> > > 1.4.1_01 and
> > > W2K.
> > >
> > > Thanks
> > >
> > > David
> > >
> > > > -----Original Message-----
> > > > From: David Wynter [mailto:david@roamware.co.uk]
> > > > Sent: 29 September 2003 12:30
> > > > To: Turbine-User
> > > > Subject: Looking for VelocityPage.vm?
> > > >
> > > >
> > > > Hi,
> > > >
> > > > I have the Velocity service configuration as in the example
> > > > TR.props in the
> > > > distribution with T2.3. The RoleBasedLayout overrides the
> > path used for
> > > > finding layout, navigations and screens based on the role,
> > > > something simple
> > > > that has worked for 2 years now, I don't believe it is
> the problem.
> > > >
> > > > services.VelocityService.template.extension=vm
> > > > services.VelocityService.default.page=VelocityPage
> > > > services.VelocityService.default.screen=VelocityScreen
> > > > services.VelocityService.default.layout=RoleBasedLayout
> > > > services.VelocityService.default.navigation=VelocityNavigation
> > > > services.VelocityService.default.error.screen =
> VelocityErrorScreen
> > > > services.VelocityService.default.layout.template = Default.vm
> > > >
> > > > The error I get is:
> > > >
> > > > ...
> > > > [DEBUG] DefaultTurbineRunData - -Returning default Charset of
> > ISO-8859-1
> > > > [DEBUG] PageLoader - -Loading Page VelocityPage.vm from the
> > > > Assembler Broker
> > > > [DEBUG] JavaPageFactory - -Class Fragment is VelocityPage.vm
> > > > [DEBUG] JavaPageFactory - -Trying
> > > > com.roamware.rwtransform.modules.pages.VelocityPage.vm
> > > > [DEBUG]
> > > > JavaPageFactory -
> > > -com.roamware.rwtransform.modules.pages.VelocityPage.vm:
> > > > Not found
> > > > [DEBUG] JavaPageFactory - -Trying
> > > > org.apache.turbine.modules.pages.VelocityPage.vm
> > > > [DEBUG] JavaPageFactory -
> > > > -org.apache.turbine.modules.pages.VelocityPage.vm:
> > > > Not found
> > > > [DEBUG] JavaPageFactory - -Returning: null
> > > > [ERROR] Turbine - -Turbine.handleException:
> > > > <java.lang.ClassNotFoundException:
> > > >
> > > > Requested Page not found: VelocityPage.vm
> > > > Turbine looked in the following modules.packages path:
> > > > [com.roamware.rwtransform.modules,
> org.apache.turbine.modules]
> > > > >java.lang.ClassNotFoundException:
> > > >
> > > > Requested Page not found: VelocityPage.vm
> > > > Turbine looked in the following modules.packages path:
> > > > [com.roamware.rwtransform.modules,
> org.apache.turbine.modules]
> > > >
> > > > at
> > > >
> org.apache.turbine.modules.PageLoader.getInstance(PageLoader.java:207)
> > > > at
> org.apache.turbine.modules.PageLoader.exec(PageLoader.java:136)
> > > > at org.apache.turbine.Turbine.doGet(Turbine.java:796)
> > > > at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> > > > at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> > > >
> > > > Why is it looking for VelocityPage.vm? I can understand
> it would use
> > > > VelocityPage.class but I have never had VelocityPage.vm ever?
> > > It refers to
> > > > VelocityPage.vm as a Class Fragment, which doesn't make sense?
> > > I could not
> > > > find anything specifically on this problem in the archives.
> > > Lots of layout
> > > > related problems, but not looking for VelocityPage.vm problems.
> > > >
> > > > Ideas?
> > > >
> > > > David Wynter
> > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> turbine-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail:
> turbine-user-help@jakarta.apache.org
> > > >
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> turbine-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail:
> turbine-user-help@jakarta.apache.org
> > >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> turbine-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
RE: HELP?: Looking for VelocityPage.vm?
Posted by David Wynter <da...@roamware.co.uk>.
Well, a solution of sorts.
If I comment out the following:
#services.TemplateService.mapper.page.class =
org.apache.turbine.services.template.mapper.DirectTemplateMapper
#services.TemplateService.mapper.screen.class =
org.apache.turbine.services.template.mapper.ClassMapper
#services.TemplateService.mapper.layout.class =
org.apache.turbine.services.template.mapper.ClassMapper
#services.TemplateService.mapper.navigation.class =
org.apache.turbine.services.template.mapper.ClassMapper
#services.TemplateService.mapper.layout.template.class =
org.apache.turbine.services.template.mapper.LayoutTemplateMapper
#services.TemplateService.mapper.screen.template.class =
org.apache.turbine.services.template.mapper.ScreenTemplateMapper
#services.TemplateService.mapper.navigation.template.class =
org.apache.turbine.services.template.mapper.DirectTemplateMapper
It works. Go figure. I never had this section in the earlier TR.props? Maybe
it is a mix of old and new ways of doing things.
David
> -----Original Message-----
> From: David Wynter [mailto:david@roamware.co.uk]
> Sent: 01 October 2003 16:08
> To: Turbine Users List
> Subject: RE: HELP?: Looking for VelocityPage.vm?
>
>
> Hi,
>
> I left off some key details below. The place that it uses defaultPage to
> look for a class of that name is between lines 114 and 126 of
> JavaBaseFactory.java.
>
> David
>
> > -----Original Message-----
> > From: David Wynter [mailto:david@roamware.co.uk]
> > Sent: 01 October 2003 15:54
> > To: Turbine Users List
> > Subject: HELP?: Looking for VelocityPage.vm?
> >
> >
> > Hi,
> >
> > I have traced through the masses of init and assembler stuff in
> > T2.3 to try
> > to find out why it is trying to find VelocityPage.vm when it does not in
> > previous versions. What i found is that it all look legitimate. With
> >
> > services.VelocityService.template.extension=vm
> > services.VelocityService.default.page=VelocityPage
> > services.VelocityService.default.screen=VelocityScreen
> > services.VelocityService.default.layout=RoleBasedLayout
> > services.VelocityService.default.navigation=VelocityNavigation
> > services.VelocityService.default.error.screen = VelocityErrorScreen
> > services.VelocityService.default.layout.template = Default.vm
> >
> > in your TR.props the init constructs a defaultPage value on line 776 of
> > Turbine.java. This is then used by the assemblers to find the
> > page. It calls
> > down through stuff until BaseTemplateMapper.getDefaultName(String
> > template).
> > So in theBaseTemplateMapper method it takes my "Login.vm"
> string and takes
> > the extension off it and adds this to the end of the value set in
> > "services.VelocityService.default.page" - result
> "VelocityPage.vm" in the
> > defaultPage. Clearly it is never going to find a class called
> > "org.apache.turbine.modules.VelocityPage.vm" so it fails.
> >
> > I cannot understand how this ever worked and am more confused than ever.
> >
> > Does anyone understand how this is supposed to work and can they
> > explain it
> > in simple terms? I am using the T2.3 release code and am on JDK
> > 1.4.1_01 and
> > W2K.
> >
> > Thanks
> >
> > David
> >
> > > -----Original Message-----
> > > From: David Wynter [mailto:david@roamware.co.uk]
> > > Sent: 29 September 2003 12:30
> > > To: Turbine-User
> > > Subject: Looking for VelocityPage.vm?
> > >
> > >
> > > Hi,
> > >
> > > I have the Velocity service configuration as in the example
> > > TR.props in the
> > > distribution with T2.3. The RoleBasedLayout overrides the
> path used for
> > > finding layout, navigations and screens based on the role,
> > > something simple
> > > that has worked for 2 years now, I don't believe it is the problem.
> > >
> > > services.VelocityService.template.extension=vm
> > > services.VelocityService.default.page=VelocityPage
> > > services.VelocityService.default.screen=VelocityScreen
> > > services.VelocityService.default.layout=RoleBasedLayout
> > > services.VelocityService.default.navigation=VelocityNavigation
> > > services.VelocityService.default.error.screen = VelocityErrorScreen
> > > services.VelocityService.default.layout.template = Default.vm
> > >
> > > The error I get is:
> > >
> > > ...
> > > [DEBUG] DefaultTurbineRunData - -Returning default Charset of
> ISO-8859-1
> > > [DEBUG] PageLoader - -Loading Page VelocityPage.vm from the
> > > Assembler Broker
> > > [DEBUG] JavaPageFactory - -Class Fragment is VelocityPage.vm
> > > [DEBUG] JavaPageFactory - -Trying
> > > com.roamware.rwtransform.modules.pages.VelocityPage.vm
> > > [DEBUG]
> > > JavaPageFactory -
> > -com.roamware.rwtransform.modules.pages.VelocityPage.vm:
> > > Not found
> > > [DEBUG] JavaPageFactory - -Trying
> > > org.apache.turbine.modules.pages.VelocityPage.vm
> > > [DEBUG] JavaPageFactory -
> > > -org.apache.turbine.modules.pages.VelocityPage.vm:
> > > Not found
> > > [DEBUG] JavaPageFactory - -Returning: null
> > > [ERROR] Turbine - -Turbine.handleException:
> > > <java.lang.ClassNotFoundException:
> > >
> > > Requested Page not found: VelocityPage.vm
> > > Turbine looked in the following modules.packages path:
> > > [com.roamware.rwtransform.modules, org.apache.turbine.modules]
> > > >java.lang.ClassNotFoundException:
> > >
> > > Requested Page not found: VelocityPage.vm
> > > Turbine looked in the following modules.packages path:
> > > [com.roamware.rwtransform.modules, org.apache.turbine.modules]
> > >
> > > at
> > > org.apache.turbine.modules.PageLoader.getInstance(PageLoader.java:207)
> > > at org.apache.turbine.modules.PageLoader.exec(PageLoader.java:136)
> > > at org.apache.turbine.Turbine.doGet(Turbine.java:796)
> > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> > >
> > > Why is it looking for VelocityPage.vm? I can understand it would use
> > > VelocityPage.class but I have never had VelocityPage.vm ever?
> > It refers to
> > > VelocityPage.vm as a Class Fragment, which doesn't make sense?
> > I could not
> > > find anything specifically on this problem in the archives.
> > Lots of layout
> > > related problems, but not looking for VelocityPage.vm problems.
> > >
> > > Ideas?
> > >
> > > David Wynter
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
RE: HELP?: Looking for VelocityPage.vm?
Posted by David Wynter <da...@roamware.co.uk>.
Hi,
I left off some key details below. The place that it uses defaultPage to
look for a class of that name is between lines 114 and 126 of
JavaBaseFactory.java.
David
> -----Original Message-----
> From: David Wynter [mailto:david@roamware.co.uk]
> Sent: 01 October 2003 15:54
> To: Turbine Users List
> Subject: HELP?: Looking for VelocityPage.vm?
>
>
> Hi,
>
> I have traced through the masses of init and assembler stuff in
> T2.3 to try
> to find out why it is trying to find VelocityPage.vm when it does not in
> previous versions. What i found is that it all look legitimate. With
>
> services.VelocityService.template.extension=vm
> services.VelocityService.default.page=VelocityPage
> services.VelocityService.default.screen=VelocityScreen
> services.VelocityService.default.layout=RoleBasedLayout
> services.VelocityService.default.navigation=VelocityNavigation
> services.VelocityService.default.error.screen = VelocityErrorScreen
> services.VelocityService.default.layout.template = Default.vm
>
> in your TR.props the init constructs a defaultPage value on line 776 of
> Turbine.java. This is then used by the assemblers to find the
> page. It calls
> down through stuff until BaseTemplateMapper.getDefaultName(String
> template).
> So in theBaseTemplateMapper method it takes my "Login.vm" string and takes
> the extension off it and adds this to the end of the value set in
> "services.VelocityService.default.page" - result "VelocityPage.vm" in the
> defaultPage. Clearly it is never going to find a class called
> "org.apache.turbine.modules.VelocityPage.vm" so it fails.
>
> I cannot understand how this ever worked and am more confused than ever.
>
> Does anyone understand how this is supposed to work and can they
> explain it
> in simple terms? I am using the T2.3 release code and am on JDK
> 1.4.1_01 and
> W2K.
>
> Thanks
>
> David
>
> > -----Original Message-----
> > From: David Wynter [mailto:david@roamware.co.uk]
> > Sent: 29 September 2003 12:30
> > To: Turbine-User
> > Subject: Looking for VelocityPage.vm?
> >
> >
> > Hi,
> >
> > I have the Velocity service configuration as in the example
> > TR.props in the
> > distribution with T2.3. The RoleBasedLayout overrides the path used for
> > finding layout, navigations and screens based on the role,
> > something simple
> > that has worked for 2 years now, I don't believe it is the problem.
> >
> > services.VelocityService.template.extension=vm
> > services.VelocityService.default.page=VelocityPage
> > services.VelocityService.default.screen=VelocityScreen
> > services.VelocityService.default.layout=RoleBasedLayout
> > services.VelocityService.default.navigation=VelocityNavigation
> > services.VelocityService.default.error.screen = VelocityErrorScreen
> > services.VelocityService.default.layout.template = Default.vm
> >
> > The error I get is:
> >
> > ...
> > [DEBUG] DefaultTurbineRunData - -Returning default Charset of ISO-8859-1
> > [DEBUG] PageLoader - -Loading Page VelocityPage.vm from the
> > Assembler Broker
> > [DEBUG] JavaPageFactory - -Class Fragment is VelocityPage.vm
> > [DEBUG] JavaPageFactory - -Trying
> > com.roamware.rwtransform.modules.pages.VelocityPage.vm
> > [DEBUG]
> > JavaPageFactory -
> -com.roamware.rwtransform.modules.pages.VelocityPage.vm:
> > Not found
> > [DEBUG] JavaPageFactory - -Trying
> > org.apache.turbine.modules.pages.VelocityPage.vm
> > [DEBUG] JavaPageFactory -
> > -org.apache.turbine.modules.pages.VelocityPage.vm:
> > Not found
> > [DEBUG] JavaPageFactory - -Returning: null
> > [ERROR] Turbine - -Turbine.handleException:
> > <java.lang.ClassNotFoundException:
> >
> > Requested Page not found: VelocityPage.vm
> > Turbine looked in the following modules.packages path:
> > [com.roamware.rwtransform.modules, org.apache.turbine.modules]
> > >java.lang.ClassNotFoundException:
> >
> > Requested Page not found: VelocityPage.vm
> > Turbine looked in the following modules.packages path:
> > [com.roamware.rwtransform.modules, org.apache.turbine.modules]
> >
> > at
> > org.apache.turbine.modules.PageLoader.getInstance(PageLoader.java:207)
> > at org.apache.turbine.modules.PageLoader.exec(PageLoader.java:136)
> > at org.apache.turbine.Turbine.doGet(Turbine.java:796)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> >
> > Why is it looking for VelocityPage.vm? I can understand it would use
> > VelocityPage.class but I have never had VelocityPage.vm ever?
> It refers to
> > VelocityPage.vm as a Class Fragment, which doesn't make sense?
> I could not
> > find anything specifically on this problem in the archives.
> Lots of layout
> > related problems, but not looking for VelocityPage.vm problems.
> >
> > Ideas?
> >
> > David Wynter
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org