RE: Re[2]: [exoplatform] problem with portlet deployment

["Kito D. Mann" <kmann@xxxxxxxxxx>]

Roman,

I just ran into this restriction over the weekend (guess I didn't notice it
before, as the display-name happened to match the name of the WAR). This
looks like a bug to me -- I don't remember seeing this in the portlet spec. 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kito D. Mann - Author, JavaServer Faces in Action
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info

* Sign up for the JSF Central newsletter!
http://oi.vresp.com/?fid=ac048d0e17 *



 

> -----Original Message-----
> From: Roman Pedchenko [mailto:roman.pedchenko@xxxxxxxxxxxxxxxxxx] 
> Sent: Monday, February 26, 2007 7:25 AM
> To: jeremie.garcia
> Cc: exoplatform@xxxxxxxxxxxxx
> Subject: Re[2]: [exoplatform] problem with portlet deployment
> 
> Hello jeremie.garcia,
> 
> Monday, February 26, 2007, 1:24:41 PM, you wrote:
> 
> > yes, sorry , the war file I attached wasn't complete ( I 
> apology for 
> > my omission, this one contains web.xml and portlet.xml ) in fact I 
> > already did what you recomand and I obtain the error previously 
> > described
> 
> Ok. Note that web-app/display-name value in your 
> WEB-INF/web.xml must have the same name as war context name 
> (for tomcat -- war file name if you didn't write any 
> additional context configuration) for the PC to work 
> properly. So if you write
> 
> <web-app>
>   <display-name>SamplePortlet</display-name>
> 
> you have to rename your war to SamplePortlet.war or in the 
> opposite way you may modify your display-name to Sample-Portlet
> 
> 
> --
> Best regards,
>  Roman                 mailto:roman.pedchenko@xxxxxxxxxxxxxxxxxx
> 
> 
>