[roy.russo]

Roy, frankly that sort of answer makes it hard for folks like me to give serious consideration to using your portal product, and JBoss products in general, for development on behalf of my customers. I'm not doing a school project here...

-Dave

The descriptors are explained in the documentation. I took time out of my schedule to draw a pretty picture to help you understand their relation to one another and posted it in the wiki.

If you can't figure out how to deploy a portlet and tie it to specific portal instance after reading the above docs, you have 3 options:

1. Sign a support agreement with JBoss, Inc.
2. Look thru the code. It is OS, after all.
3. Go use another portal.

[astrait]

Roy, your "pretty picture" did not add any information to what is said in the reference manual and, more over, seems to have missed the point of this entire thread. If this is the kind of flippant response one can expect from someone with a jboss email address then maybe it is time to move on to another AS and portal.

-Alan

[roy.russo]

"astrait" wrote:
Roy, your "pretty picture" did not add any information to what is said in the reference manual and, more over, seems to have missed the point of this entire thread.

Which question in this thread was not answered by either the documentation OR the picture OR the download zip I posted OR the available source code?

"astrait" wrote:

If this is the kind of flippant response one can expect from someone with a jboss email address then maybe it is time to move on to another AS and portal.

Let me know how it works out for you. Actually, don't bother. I don't care.

[marec]

Hope that this image will help us all to get the correct view on what we need: [img]http://home.gamca.sk/~marec/portals.gif[/img]http://home.gamca.sk/~marec/portals.gif

On the left side there is portal-core.war from the jboss-portal.sar with it's definition of the portlets and also the portlet instances what is currently not important for us, because we want to have our own instance in our echo portal.

On the right side there is the echo.war with portlet instance and portal definition, probably with some more files which are not important at the moment. As you can see (in the portlet-instance.xml from the echo.war) we want to instantiate portlet defined in another portal (in this case defined in portal-core.war). Than we want to use this new instance in our portal (marked with red color in the picture). I believe that this instance reference (instance-ref tag) is correct. The problem is when I browse this page in my browser the "ContentPortletWindow1" is not displayed.
I debug the portal sources and I found that the STATE of the window is just "registered" and NOT "started", therefore it is not rendered.

Can you tell me why or how to get the window to state "started"?

[roy.russo]

ok, so the only way to get this scenario to work is as follows:

Your echo-portal should look like this:

 <window>
 <window-name>ContentPortletWindow</window-name>
 <instance-ref>portal.ContentPortlet.MyEchoContentPortletInstance</instance-ref>
 <region>left</region>
 <height>2</height>
 </window>

Use 'portal.' here, as the Portlet is deployed under the portal web-app name.

Now you have to go in to jboss-portal-exploded.sar\portal-core.war\WEB-INF\portlet-instances.xml and add your contentPortlet instance:

 <instance>
 <instance-name>MyEchoContentPortletInstance</instance-name>
 <component-ref>ContentPortlet</component-ref>
 <preferences>
 <preference>
 <name>uri</name>
 <value>/echo/page01.html</value>
 </preference>
 </preferences>
 </instance>

You cannot achieve this from outside of this war.

[astrait]

Marec, thank you for restating the question--your diagram worked well.

You cannot achieve this from outside of this war.

Roy, thank you for the answer.

-Alan