Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Unable to implement WOOgnl parser in my WO application on WO5.4.

Eclipse Version: Juno Service Release 1

java version: 1.6.0_18

WebObject Version = 5.4.3


Steps I am using to implement WOOgnl Parser:-


1- I have imported WOOgnl.framework in build path

2- I have made following changes to build.properties file

ognl.active = true

ognl.helperFunctions=true

ognl.inlineBindings=true

ognl.parseStandardTags=true


The whole build.properties looks like this:-


#Wed Nov 21 13:06:11 EST 2012

classes.dir=bin

component.inlineBindingPrefix=[

component.inlineBindingSuffix=]

component.wellFormedTemplateRequired=true

customInfoPListContent=

eoAdaptorClassName=

embed.Local=false

embed.Project=false

embed.System=false

ognl.active = true

ognl.helperFunctions=true

ognl.inlineBindings=true

ognl.parseStandardTags=true

principalClass=Application

project.name=Empsoft

project.name.lowercase=empsoft

project.type=application

webXML=false

webXML_CustomContent=


When I am using the above steps i am getting error mentioned below:-


A fatal exception occurred: ognl/PropertyAccessor

java.lang.NoClassDefFoundError: ognl/PropertyAccessor


When I am not importing WOOgnl.framework in my build path the project is running fine but I have to remove all the duplicate entries in Wod file else exception is thrown when I am opening the page from UI.


Please let me know where I am going wrong.


Thanks!!!!



Regards

Mritunjay Kumar

Eclipse JUNO-OTHER, Windows 7

Posted on Dec 27, 2012 1:52 PM

Reply
1 reply

Dec 27, 2012 2:51 PM in response to MritunjayKumarAnr

The ognl properties (ognl.active, ognl.helperFunctions, etc) go in the Properties file in the Resources folder, not in build.properties.


You should rarely have to edit the build.properties file manually. It is edited from eclipse by right clicking on project name and selecting "Properties" from the contextual menu and then editing the settings in WOLips Deployment and WOLips Development. If you are using WOOgnl for inline bindings rather than Apple's inline bindings mechanism then in WOLips Development you should probably change


component.inlineBindingPrefix=[

component.inlineBindingSuffix=]


to


component.inlineBindingPrefix=$

component.inlineBindingSuffix=


so that WOLips validation knows what style inline bindings you are using.


Also I don't understand why you have duplicate entries in wod file.

Unable to implement WOOgnl parser in my WO application on WO5.4.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.