- This topic has 7 replies, 2 voices, and was last updated 15 years ago by
Michael Streubel.
-
AuthorPosts
-
Michael StreubelMemberMyEclipse Blue 8.5 M2.
Deploying a portlet project to the new Websphere Portal 6.1 connector doesn’t lead to a deployed portlet from the point of view of the portal server. It merely results in a web application having been deployed onto the underlying application server. However, you don’t see anything of the new portlet application within the portal server admin console and hence no portal page is created which could carry the portlet since the latter doesn’t exist at all.
Has anyone have any experiences with this already?
Michael
April 13, 2010 at 4:45 am #307601
Michael StreubelMemberUnfortunateley, the same is true for 8.5.0 final release.
Nobody who is suffering from the same defect?
No support people comments?
April 29, 2010 at 10:28 am #308060
Brian FernandesModeratorMichael,
Sorry for the delayed response, I’m surprised this got overlooked. Out of curiosity, have you used our previous 6.0 connector successfully? Or is this the first Portal connector you have tried?
Also, can you detail how you created the portal project and past the portal.xml file here please?
My team is looking at this issue right now at high priority.
May 3, 2010 at 3:57 pm #308118
Brian FernandesModeratorMichael,
I checked with our QA team and the developer team as well – the portlets that we created did show up in portal server 6.1 on the “Manage Portlets” page for instance.
If you try creating a web project, add portlet capabilities to it and deploy it to 6.1 does that show up? We have a “hello world” sort of portlet that we create with new projects.
Have you successfully deployed your portlet project through any other tool and know for a fact that it is working?
May 12, 2010 at 7:05 am #308337
Michael StreubelMemberSorry for the delay in my reply. I was attending a conference.
Yes, I’ve added portlet capabilities and it didn’t help. Yes, we’ve tried with several projects and they’ve been successfully deployed to WP 6.1 thorugh RAD. In fact, we’re investigating MB as a replacement candidate for RAD 7.5.
May 12, 2010 at 2:33 pm #308346
Brian FernandesModeratorMichael,
Yes, I’ve added portlet capabilities and it didn’t help.
Did you try creating a new webproject and adding portlet capabilities to this – and then tried to deploy this to Portal Server 6.1? Or did you try with an existing project?
May 13, 2010 at 3:58 pm #308372
Michael StreubelMemberBrian,
we tried with quite a lot of existing projects. Sometime we got new ones to show up in “Manage Portlets”.
Michael
May 31, 2010 at 4:56 am #308745
Michael StreubelMemberTo continue (hopefully) with our discusson, for some of our portlet enabled projects we can see this statement in the myEclipse console when trying to deploy the application:
com.ibm.wps.services.registry.ObjectModelRegistry registerPortletApplication EJPPG0024I: Web application with context root /.SWFCourse_Tomahawk12_Portlet286 is deployed in the application server but not registered with portal
As mentioned earlier, the very same application deploys flawlessly in WebSphere Portal together with RAD.
Michael
-
AuthorPosts