on 05-06-2011 5:25 AM
Hi experts,
I'm no expert in this area and doing some quick code tweaks in a PAR file but have hit some error on com.sapportals.portal.prt.servlets_jsp.server.jsp.ParseException: java.lang.ClassNotFoundException for com.<abc>.pct.<def>.taglib.collection.IterateCollectionFiltered. This class was referenced in a tld file in the taglib folder as follows:
<tag>
<name>iterateCollectionFiltered</name>
<tagclass>com.<abc>.pct.<def>.taglib.collection.IterateCollectionFiltered</tagclass>
<body-content>JSP</body-content>
...
I presume from the error that tt's not able to find the class. Where is it trying to find the class? Within the PAR application? Or another application in the Portal?
Thanks,
ZM
Hi Prashant,
Added the jar files, and also added the location of the Jar files in the Java Build Path and deployed but unfortunately still hitting the same error.
Thanks,
ZM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Prashant,
Appreciate the prompt response. I've saved it as a par file and extracted with winrar as u stated, but it doesn't have "portal-inf" that seems to only appear if you open it using NWDS. It only shows the following folders when using winrar. And I couldnt find the jar file either. Only found core.ar, api.jar, core.src.jar, api.src.jar.
META-INF
jsp
lib
private
srclib.api
srclib.core
taglib
work
Thanks,
ZM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
1. Are you modifying an already running par file or creating a new on?
2. The taglib which is being referenced, has it been deployed on the server on which you are trying to run this par
3. Post the content of portalapp.xml and the the way the taglib is being referenced in the JSP
Thanks
Prashant
Hi Prashant,
1. We've upgraded some third party components and these new files do not contain our customizations. Thus I'm modifying the latest components with our customizations that I've gotten from their older version.
2. The tld file is in the taglib folder which is within the PAR file itself.
3. portalxml:
<?xml version="1.0" encoding="utf-8"?>
<application>
<application-config>
<property name="Vendor" value="<vendorabc>"/>
<property name="SecurityArea" value="<abc>"/>
<property name="SecurityZone" value="This_Application"/>
<property name="SharingReference" value="ApplicationA, ApplicationB, ApplicationC, com.sap.netweaver.bc.rf, com.sap.portal.usermanagement, com.sap.netweaver.bc.util, com.sap.km.cm.service, com.sap.km.cm.repository.service.base,com.sap.portal.navigation.navigationtaglibrary"/>
<property name="SharingReference" value="com.sap.portal.htmlb"/>
</application-config>
<components>
<component name="calledByABC">
<component-config>
<property name="SafetyLevel" value="no_safety"/>
</component-config>
<component-profile>
<property name="ABCTagLibrary" value="/SERVICE/ApplicationB/taglib/easyiViewAccess.tld"/>
<property name="ABCRenderingTagLibrary" value="/SERVICE/ApplicationA/taglib/webContentRendering.tld"/>
<property name="ABCRenderingTagLibrary" value="/SERVICE/This_Application/taglib/bhpContentRendering.tld"/>
<property name="easyWCMKeyLandingPageTagLibrary" value="/SERVICE/ApplicationA/taglib/keyLandingPage.tld"/>
<property name="SAPNavigationTagLibrary" value="/SERVICE/com.sap.portal.navigation.navigationtaglibrary/taglib/TagLibrary.tld"/>
<property name="EPCFLevel" value="0"/>
<property name="ComponentType" value="jspnative"/>
<property name="JSP" value="default"/>
</component-profile>
</component>
<component name="xmlformpreview">
<component-config>
<property name="SafetyLevel" value="no_safety"/>
<property name="ClassName" value="This_Application.xmlformpreview"/>
</component-config>
<component-profile>
<property name="AuthScheme" value="anonymous"/>
</component-profile>
</component>
</components>
<services>
<service name="CustomerAddonsRegistration">
<service-config>
<property name="className" value="This_Application.registration.CustomerAddonsRegistration"/>
<property name="startup" value="true"/>
</service-config>
</service>
</services>
</application>
Thanks,
ZM
This problem is coming because when you import the parfile in NWDS the jar files are not automatically imported.
Follow the steps below
1. Extract the par file using winrar or winzip.
2. In folder PORTAL-INF\private\lib you will find the required jar file
3. Manually import this jar file in NWDS.
4. Rebuild, Export and deploy the [ar file.
Revert if you face any issues.
Thanks
Prashant
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.