This happens because you have two @portlet.portlet tags on your class.
The first one is:
@portlet.portlet name=amites_struts
description=Amites Portlet Test Struts
display-name=Amites Portlet Test Struts
The second one is several lines down and looks like:
Hmmm...I understand what it would take to fix this, but I would think
that your portlet container should be more forgiving of the whitespace
surrounding the FQCN. Which portlet container are you using?
Regardless...I just fixed the template and committed it to CVS.
AndreasWuest wrote:
Hi
Hi Craig,
i am using the Liferay portal, Version 3.2.0 on a tomcat.
thanks,
Andreas
Hmmm...I understand what it would take to fix this, but I would think
that your portlet container should be more forgiving of the whitespace
surrounding the FQCN. Which portlet container are you using?
Hi Craig,
thanks a lot for helping me solve this problem.
Andreas
This happens because you have two @portlet.portlet tags on your class.
The first one is:
@portlet.portlet name=amites_struts
description=Amites Portlet Test Struts
display-name=Amites Portlet Test
Hi, I have some question about the philosohy of using merge files for plain
old java code generation.
I started asking about this here in the Xdoclet In Action forum:
http://www.manning-sandbox.com/thread.jspa?threadID=11401tstart=0
Basically I sold the idea of xdoclet to management. I still
On Thu, 2005-02-17 at 18:31, Paul Lee wrote:
Hi, I have some question about the philosohy of using merge files for plain
old java code generation.
I started asking about this here in the Xdoclet In Action forum:
http://www.manning-sandbox.com/thread.jspa?threadID=11401tstart=0
Basically I
Hi,
I have been banging
my head against a wall trying to upgrade our XDoclet from 1.2.0 Beta 2 to
1.2.2.
I fear that this is
a trivial oversight, but I can't seem to figure it out.
All I did for the
upgrade is replace the XDoclet jars in our lib directory. I verified that
taskdefs
