Portlet instance component ref requires '/' application name prefix when automatic app. name discovery is used. --------------------------------------------------------------------------------------------------------------- Key: JBPORTAL-737 URL: http://jira.jboss.com/jira/browse/JBPORTAL-737 Project: JBoss Portal Issue Type: Bug Security Level: Public(Everyone can see) Components: Documentation, Portal Core Reporter: Tuomas Kiviaho Assigned To: Roy Russo Priority: Minor Fix For: 2.4 Final I'd like get rid of delete jboss-app.xml and let the deployment decide the application name, because that's currently the only information used from the file. If I don't have the xml in place all of the portlet instances will be undeployed. I can see from the database when manually creating a portlet instance that for some reason a '/' before application name has appeared. When I change the *-object.xml file to have '/' as prefix for every component-ref the portlet instances are deployed, but if I recover the jboss-app.xml and use this new app. naming the result is again undeployment. There is no mentioning about such side effect in documentation <http://docs.jboss.org/jbportal/v2.2/reference-guide/en/html/xmldescriptor... Could the component-ref app name part be automatically discovered when undeclared (cases when *-object.xml and portlet.xml reside in same web application) to reduce hard-to-discover couplings between configuration files.