03-09-06 01:50 AM
<p>Running xmlaccess often gives cryptic errors. However, we are using xmlac
cess to deploy and assign access to the portlets successfully. There are som
e sample xmlaccess input files under <wp-root>\doc\xml-access. </p><p>
***************************
****************************************
***********<br />DESCRIPTION: 1)uid
in <web-ap/> tag should match uid attribute of portlet-app in portlet.
xml<br />2)uid in <portlet-app/> tag should match uid attribute of con
crete-portlet-app in portle
t.xml<br />3)name in <portlet/> tag must match content of portlet-name
subtag of concrete-portlet in portlet.xml **************************
****************************************
************<br /> <br /> <
portal action="locate&
quot;><br /> <web-app action="update" active="true"
; uid="com.rins.ordering.OrderingPortlet.c07e224550"><br />
<br /> <url>file:///$server_root$/installableApps/OrderingSystem.w
ar</url></p><p> <
portlet-app action="update" active="true" uid="com.
rins.ordering.OrderingPortlet.c07e224550.1"><br /> <portlet act
ion="update" active="true" name="Ordering" un
iquename="PX_Ordering&
quot;><br /> </portlet><br /> </portlet-app> <br /> <br
/> </portlet-app> <br /> <br /> </web-app><br /> </po
rtal></p><p>Make sure your WAR file is copied into installableApps.<br />
Note: We are using this to
deploy IBM portlets and I would think it should be same for JSR168 portlet a
pp also. </p>
[ Post a follow-up to this message ]
|