Yes.
It looks like the $content in not getting into the context. The turbine log shows an 
app exception while parting a simple xml (shown below). But this works on Tomcat, so I 
thought it might be a  Xerces issue. Weblogic has its own parser, so I grabed the 
xerces.jar from the Tomcat and put it before the weblogic.jar in the classpath, but 
WLS will not boot with this old version.

any clues?


---menu.xml-----
<menu>
<item name="SYSCRZ"  permission=""  />
<item name="ADMIN"  permission=""  />
<item name="CONTROL"  permission=""  />
</menu>

----part of MYFRAM.properties
services.MenuService.builder.xml.class=com.sonda.bancos.SONDAframe.services.menu.builder.xml.XMLBuilder^M
services.MenuService.builder.xml.group=xml^M
services.MenuService.builder.xml.root=10000^M
services.MenuService.builder.xml.startingLevel=1^M
services.MenuService.builder.xml.path=/WEB-INF/conf^M
services.MenuService.builder.xml.file=menu.xml^M

---turbine.log-----
<Jan 23, 2003 5:14:09 PM CLST> <Info> <HTTP> <101047> 
<[ServletContext(id=7236255,name=siscob,context-path=/siscob)] siscob: Turbine: 
Completed HTTP initialization of services>
[Thu Jan 23 17:14:10 CLST 2003] -- ERROR -- Cannot parse 
file:/home/bea/user_projects/bconosur/applications/siscob/WEB-INF/conf/menu.xml
        Exception:  java.lang.NullPointerException
        Stack Trace follows:
        java.lang.NullPointerException
        at 
com.sonda.bancos.SONDAframe.services.menu.builder.xml.MenuReader.startElement(MenuReader.java:153)
        at org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1376)
        at 
org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValidator.java:1122)
        at 
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanner.java:1858)
        at 
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XMLDocumentScanner.java:1234)
        at 
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:381)
        at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:952)
        at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:991)
        at com.sonda.bancos.SONDAframe.util.SAXHandler.parse(SAXHandler.java:61)
        at 
com.sonda.bancos.SONDAframe.services.menu.builder.xml.MenuReader.readMenu(MenuReader.java:100)
        at 
com.sonda.bancos.SONDAframe.services.menu.builder.xml.XMLBuilder.rebuild(XMLBuilder.java:72)
        at 
com.sonda.bancos.SONDAframe.services.menu.builder.BaseBuilder.build(BaseBuilder.java:137)
        at 
com.sonda.bancos.SONDAframe.services.menu.renderer.JoustRenderer.render(JoustRenderer.java:72)
        at 
com.sonda.bancos.SONDAframe.services.menu.SONDAframeMenuService.renderBuilderGroup(SONDAframeMenuService.java:311)
        at 
com.sonda.bancos.SONDAframe.services.menu.SONDAframeMenuService.renderBuilderGroup(SONDAframeMenuService.java:211)
        at 
com.sonda.bancos.SONDAframe.services.menu.SONDAframeMenu.renderBuilderGroup(SONDAframeMenu.java:106)
        at com.sonda.bancos.SONDAframe.modules.layouts.Index.doBuild(Index.java:48)
        at org.apache.turbine.modules.Layout.build(Layout.java:91)
        at org.apache.turbine.modules.LayoutLoader.exec(LayoutLoader.java:123)
        at org.apache.turbine.modules.pages.DefaultPage.doBuild(DefaultPage.java:166)
        at org.apache.turbine.modules.Page.build(Page.java:90)
        at org.apache.turbine.modules.PageLoader.exec(PageLoader.java:123)
        at org.apache.turbine.Turbine.doGet(Turbine.java:447)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at 
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
        at 
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
        at 
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
        at 
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
        at 
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
        at 
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
        at 
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)


---------- Original Message ----------------------------------
From: "Quinton McCombs" <[EMAIL PROTECTED]>
Reply-To: "Turbine Users List" <[EMAIL PROTECTED]>
Date:  Thu, 23 Jan 2003 17:04:41 -0600

>Are you seeing any error messages in your turbine.log?  It looks like the $content 
>tool is not being put into the context.
>
>> -----Original Message-----
>> From: rmadariaga [mailto:[EMAIL PROTECTED]]
>> Sent: Thursday, January 23, 2003 4:20 PM
>> To: [EMAIL PROTECTED]
>> Subject: turbine/velocity on Weblogic Server
>>
>>
>>
>> Hello users.
>> I am in a desperate need of migrating a Tomcat 3.1 + Turbine
>> 2.1 + velocity 1.2 application to Weblogic server 7.01.
>>
>> Moving the webapp was no problem, only slight changes.
>> But for some reason, the .VM files are not being interpreted
>> by WSL. On the browser, it shows the vm file content. For example:
>>
>> ## ## $Id: Menu.vm,v 1.6 2001/08/10 16:05:14 me Exp $ ##
>> $page.setTitle("Navegaci�n")
>> $page.getTitle()
>>
>> looks like html tags are run ok because gifs are shown.
>>
>> velocity log looks ok:
>>
>> Thu Jan 23 09:58:28 CLST 2003   [info] Velocity successfully started.
>> Thu Jan 23 09:58:33 CLST 2003   [info] ResourceManager :
>> found screens/Index.vm with loader
>> org.apache.velocity.runtime.resource.loader.FileResourceLoader
>> Thu Jan 23 09:58:33 CLST 2003   [info] ResourceManager :
>> found layouts/Index.vm with loader
>> org.apache.velocity.runtime.resource.loader.FileResourceLoader
>>
>> So, as you can see: The '$' variables and methods dont get
>> replaced in the .VM files, so looks like the browser does not
>> interpret the code. Please look at the web access log in WLS
>> at the end of this mail. Lines like: "GET
>> /siscob/templates/screens/$content.getURI( HTTP/1.1" 404 1277
>> tell me that the '$' is realy not working.
>>
>> So I thought it was a mime type problem, but Tomcat does not
>> have VM files defined. I did it anyways on WLS but still
>> does'nt work. I also tried putting the original jars before
>> the weblogic.jar, but I got the same luck or worst.
>>
>> Please help.
>>
>>
>> Sorry if this is html mail but I am at client installations
>> and have no other way. Thank you
>>
>> Ricardo
>>
>> -----WLS access.log-----
>> 192.168.1.186 - - [23/Jan/2003:10:04:04 -0300] "GET
>> /siscob/images/menu/ns_doc.gif HTTP/1.1" 304 0 192.168.1.186
>> - - [23/Jan/2003:10:04:04 -0300] "GET
>> /siscob/images/menu/win/blank.gif HTTP/1.1" 304 0
>> 192.168.1.186 - - [23/Jan/2003:10:04:04 -0300] "GET
>> /siscob/templates/screens/menu.vm HTTP/1.1" 304 0
>> 192.168.1.186 - - [23/Jan/2003:10:04:04 -0300] "GET
>> /siscob/templates/screens/button.vm HTTP/1.1" 304 0
>> 192.168.1.186 - - [23/Jan/2003:10:04:04 -0300] "GET
>> /siscob/templates/screens/home.vm HTTP/1.1" 304 0
>> 192.168.1.186 - - [23/Jan/2003:10:04:04 -0300] "GET
>> /siscob/templates/screens/title.vm HTTP/1.1" 304 0
>> 192.168.1.186 - - [23/Jan/2003:10:04:04 -0300] "GET
>> /siscob/templates/screens/$content.getURI( HTTP/1.1" 404 1277
>> 192.168.1.186 - - [23/Jan/2003:10:04:05 -0300] "GET
>> /siscob/templates/screens/$content.getURI('templates/js/SFbase
>> .js') HTTP/1.1" 404 1277 192.168.1.186 - -
>> [23/Jan/2003:10:04:05 -0300] "GET
>> /siscob/templates/screens/$content.getURI( HTTP/1.1" 404 1277
>> 192.168.1.186 - - [23/Jan/2003:10:04:05 -0300] "GET
>> /siscob/templates/screens/$content.getURI('templates/js/SFkeys
>> .js') HTTP/1.1" 404 1277 192.168.1.186 - -
>> [23/Jan/2003:10:04:05 -0300] "GET
>> /siscob/templates/screens/$content.getURI( HTTP/1.1" 404 1277
>> 192.168.1.186 - - [23/Jan/2003:10:04:06 -0300] "GET
>> /siscob/templates/screens/$content.getURI('templates/js/SFmenu
>> .js') HTTP/1.1" 404 1277 192.168.1.186 - -
>> [23/Jan/2003:10:04:06 -0300] "GET
>> /siscob/templates/screens/$content.getURI( HTTP/1.1" 404 1277
>> 192.168.1.186 - - [23/Jan/2003:10:04:06 -0300] "GET
>> /siscob/templates/screens/$content.getURI('templates/js/SFkeys
>> .js') HTTP/1.1" 404 1277 192.168.1.186 - -
>> [23/Jan/2003:10:04:06 -0300] "GET
>> /siscob/templates/screens/$content.getURI('templates/js/SFbase
>> .js') HTTP/1.1" 404 1277 192.168.1.186 - -
>> [23/Jan/2003:10:04:06 -0300] "GET
>> /siscob/templates/screens/$content.getURI('templates/js/SFkeys
>> .js') HTTP/1.1" 404 1277 192.168.1.186 - -
>> [23/Jan/2003:10:04:06 -0300] "GET
>> /siscob/templates/screens/$content.getURI('templates/js/SFform
>> at.js') HTTP/1.1" 404 1277 192.168.1.186 - -
>> [23/Jan/2003:10:04:06 -0300] "GET
>> /siscob/templates/screens/$content.getURI('templates/js/SFutil
>> .js') HTTP/1.1" 404 1277 192.168.1.186 - -
>> [23/Jan/2003:10:04:06 -0300] "GET /siscob/images/logo3.gif
>> HTTP/1.1" 304 0
>>
>>
>>
>> ________________________________________________________________
>> Sent via the KillerWebMail system at omegacl.cl
>>
>>
>>
>>
>>
>>
>> --
>> To unsubscribe, e-mail:
>> <mailto:turbine-user-> [EMAIL PROTECTED]>
>> For
>> additional commands,
>> e-mail: <mailto:[EMAIL PROTECTED]>
>>
>>
>
>--
>To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>



________________________________________________________________
Sent via the KillerWebMail system at omegacl.cl






--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to