You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Jeff Painter <pa...@kiasoft.com> on 2003/12/04 15:00:06 UTC
continuing saga with 2.3.1
Well, I came in this morning and reread the services howto for 2.3 and
went back to work on my tr.props
according to the 2.3 howto
If you request e.g. the template screen
"about,directions,Driving.vm" then the following class names are searched
(on the module search path):
* 1. about.directions.Driving <- direct matching the template to the class name
* 2. about.directions.Default <- matching the package, class name is Default
* 3. about.Default <- stepping up in the package hierarchy, looking for Default
* 4. Default <- Class called "Default" without package
* 5. VelocityScreen <- The class configured by the Service (VelocityService) to use
I find that from the code I checked out yesterday, it gets to level 4 and
stops. If a default does not exist, it is not traversing on up the tree to
VelocityScreen. So I just created
org.mycomp.newapp.modules.layouts.Default -> extends o.a.t.m.layouts.VelocityOnlyLayout
org.mycomp.newapp.modules.scrrens.Default -> extends o.a.t.m.screens.VelocityScreen
there is no other code in these classes other than extending the ones I
wished to be the default
and everything worked... I'm not sure if there is a problem with my
properties or if the class loader is just stopping if it doesn't find an
exact class named Default.java
That is what it appears at the moment.
I don't know enough yet about how the template service actually works
behind the scenes to do any more useful debugging than that.
this is what the log file is saying
.
.
2003-12-04 08:45:30,272 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.template.mapper.ClassMapper - classPackage is now:
2003-12-04 08:45:30,272 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.template.mapper.ClassMapper - Looking for Default
2003-12-04 08:45:30,272 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.modules.ScreenLoader - Loading Screen Default from the Assembler Broker
2003-12-04 08:45:30,272 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - Class Fragment is Default
2003-12-04 08:45:30,272 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - Trying org.apache.turbine.modules.screens.Default2003-12-04 08:45:30,278
[Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - org.apache.turbine.modules.screens.Default: Not found
2003-12-04 08:45:30,278 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - Trying org.apache.turbine.flux.modules.screens.Default
2003-12-04 08:45:30,280 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - org.apache.turbine.flux.modules.screens.Default: Not found
2003-12-04 08:45:30,280 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - org.apache.turbine.flux.modules.screens.Default:Not found
2003-12-04 08:45:30,280 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - Trying org.mycompany.newapp.modules.screens.Default
2003-12-04 08:45:30,282 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - org.mycompany.newapp.modules.screens.Default: Not found
2003-12-04 08:45:30,282 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - Returning: null
2003-12-04 08:45:30,282 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.template.mapper.ClassMapper - Returning default
2003-12-04 08:45:30,282 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.modules.ScreenLoader - Loading Screen VelocityScreen from the Assembler Broker
2003-12-04 08:45:30,282 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - Class Fragment is VelocityScreen
now it says org.mycompany.newapp.modules.screens.Default does not exist in
the log file even though I know I just put it there, recompiled and
restarted and then it does render my screen, but without the actual
Default.java in there it is croaking at that point and not pulling the
VelocityScreen class
any ideas?
--
Regards,
Jeffery Painter
- --
painter@kiasoft.com http://kiasoft.com
PGP FP: 9CE8 83A2 33FA 32B1 0AB1 4E62 E4CB E4DA 5913 EFBC
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/qEQE5Mvk2lkT77wRAnMJAJ9vJ6qOkg/mvqqIpz7troCEQJ8bFACglu/U
YNXabx7DZOV2Hd9LwSTmGpY=
=dWiu
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: continuing saga with 2.3.1
Posted by Jeff Painter <pa...@kiasoft.com>.
On Thu, 4 Dec 2003, Jeff Painter wrote:
>
> I must still be tired... ignore the comments about not loading my own
> Default screen... that part did work correctly, I didn't have a
> modules.screens.Default
>
> I had put in modules.pages.Default and modules.layout.Default
>
> It is just croaking on not being able to load the default layout and the
> default page.
>
> Default screen is working.
>
> Thanks
luckily I found Martin's tdk 2.3 he worked on back in Sep.
http://jakarta.apache.org/~mpoeschl/tdk-2.3-20030905.tar.gz
I will see if I can merge the work he did with what I've been hacking on
and see if I can get this together
--
Regards,
Jeffery Painter
- --
painter@kiasoft.com http://kiasoft.com
PGP FP: 9CE8 83A2 33FA 32B1 0AB1 4E62 E4CB E4DA 5913 EFBC
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/qEQE5Mvk2lkT77wRAnMJAJ9vJ6qOkg/mvqqIpz7troCEQJ8bFACglu/U
YNXabx7DZOV2Hd9LwSTmGpY=
=dWiu
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: continuing saga with 2.3.1
Posted by Jeff Painter <pa...@kiasoft.com>.
I must still be tired... ignore the comments about not loading my own
Default screen... that part did work correctly, I didn't have a
modules.screens.Default
I had put in modules.pages.Default and modules.layout.Default
It is just croaking on not being able to load the default layout and the
default page.
Default screen is working.
Thanks
On Thu, 4 Dec 2003, Jeff Painter wrote:
>
> Well, I came in this morning and reread the services howto for 2.3 and
> went back to work on my tr.props
>
> according to the 2.3 howto
>
> If you request e.g. the template screen
> "about,directions,Driving.vm" then the following class names are searched
> (on the module search path):
>
> * 1. about.directions.Driving <- direct matching the template to the class name
> * 2. about.directions.Default <- matching the package, class name is Default
> * 3. about.Default <- stepping up in the package hierarchy, looking for Default
> * 4. Default <- Class called "Default" without package
> * 5. VelocityScreen <- The class configured by the Service (VelocityService) to use
>
> I find that from the code I checked out yesterday, it gets to level 4 and
> stops. If a default does not exist, it is not traversing on up the tree to
> VelocityScreen. So I just created
>
> org.mycomp.newapp.modules.layouts.Default -> extends o.a.t.m.layouts.VelocityOnlyLayout
> org.mycomp.newapp.modules.scrrens.Default -> extends o.a.t.m.screens.VelocityScreen
>
> there is no other code in these classes other than extending the ones I
> wished to be the default
>
> and everything worked... I'm not sure if there is a problem with my
> properties or if the class loader is just stopping if it doesn't find an
> exact class named Default.java
>
> That is what it appears at the moment.
>
> I don't know enough yet about how the template service actually works
> behind the scenes to do any more useful debugging than that.
>
> this is what the log file is saying
>
> .
> .
> 2003-12-04 08:45:30,272 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.template.mapper.ClassMapper - classPackage is now:
> 2003-12-04 08:45:30,272 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.template.mapper.ClassMapper - Looking for Default
> 2003-12-04 08:45:30,272 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.modules.ScreenLoader - Loading Screen Default from the Assembler Broker
> 2003-12-04 08:45:30,272 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - Class Fragment is Default
> 2003-12-04 08:45:30,272 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - Trying org.apache.turbine.modules.screens.Default2003-12-04 08:45:30,278
> [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - org.apache.turbine.modules.screens.Default: Not found
> 2003-12-04 08:45:30,278 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - Trying org.apache.turbine.flux.modules.screens.Default
> 2003-12-04 08:45:30,280 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - org.apache.turbine.flux.modules.screens.Default: Not found
> 2003-12-04 08:45:30,280 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - org.apache.turbine.flux.modules.screens.Default:Not found
> 2003-12-04 08:45:30,280 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - Trying org.mycompany.newapp.modules.screens.Default
> 2003-12-04 08:45:30,282 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - org.mycompany.newapp.modules.screens.Default: Not found
> 2003-12-04 08:45:30,282 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - Returning: null
> 2003-12-04 08:45:30,282 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.template.mapper.ClassMapper - Returning default
> 2003-12-04 08:45:30,282 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.modules.ScreenLoader - Loading Screen VelocityScreen from the Assembler Broker
> 2003-12-04 08:45:30,282 [Ajp13Processor[11009][4]] DEBUG org.apache.turbine.services.assemblerbroker.util.java.JavaScreenFactory - Class Fragment is VelocityScreen
>
--
Regards,
Jeffery Painter
- --
painter@kiasoft.com http://kiasoft.com
PGP FP: 9CE8 83A2 33FA 32B1 0AB1 4E62 E4CB E4DA 5913 EFBC
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/qEQE5Mvk2lkT77wRAnMJAJ9vJ6qOkg/mvqqIpz7troCEQJ8bFACglu/U
YNXabx7DZOV2Hd9LwSTmGpY=
=dWiu
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org