use of Jboss-web,Jboss-app,Jboss-portlet config files

[portalgeek]

Hi,

In one of the portlet samples, i down-loaded from PortletSwap.com (iframe portlet) has following files:

1. Jboss-web 2.Jboss-app 3. Jboss-portlet
4. *-object.xml 5. portlet.xml 6.web.xml 7. portlet-instances.xml

Jboss-web is empty.

<?xml version="1.0"?>
<jboss-web>
</jboss-web>

Jboss-app

<jboss-app>
 <app-name>iframe</app-name>
</jboss-app>

Jboss-portlet

<portlet-app>
 <portlet>
 <portlet-name>IFramePortlet</portlet-name>
 </portlet>
</portlet-app>

Are these config files generated in prior version like 2.2 and now not needed ? Or there is any other use ? Please throw some light.

thanks

[peterj]

The jboss-web.xml file is empty because the typical information (conetxt) is not used. You can omit the file and the portlet still works fine.

The jboss-app.xml file simply supplies a nice app name for the portlet. Otherwise the app name ends up being something like "/iframe". But you will never notice this unless you look at the Instances list in the Administration Portlet.

The jboss-portlet.xml file is described in section 6.1.3 of the Reference Guide that comes with Portal 2.4. Uusually you don't need this file, and given the current contents, I think it can be omitted.