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 Andrew,
That is strange. What do the Ant script and directory structure look
like now? All I can think of is that it must be picking up a second
copy of the class somewhere (possibly the compiled version, which
wouldn't contain any javadoc tags?)
Deleting the classes directory before
Hi Andrew,
just encountered another problem, which may be a bug. Running the
portlet doclet it generate
the following code if you have a preferences validator defined
(in this case de.amites.web.CustomPreferencesValidator) :
preferences-validator
On Thu, 2005-02-10 at 08:26, AndreasWuest wrote:
Hi Andrew,
thanks a lot for that tip. After changing the fileset the task finally
created the portlet definitions in the portlet.xml.
Unfortunately, now i have two other problems :
1. For some reason the task creates two portlet
Hi Andrew,
thanks a lot for that tip. After changing the fileset the task finally
created the portlet definitions in the portlet.xml.
Unfortunately, now i have two other problems :
1. For some reason the task creates two portlet definitions in the
portlet.xml for the one portlet i have.
The
Hi,
i have some major problems getting the portletdoclet to work. Seems like
i am the first one using that feature. Searching the net did not return
many results :(
My problem is that the portletdoclet task does not generate a portlet.xml
with my portlet definition. THe portlet.xml file is
Andreas,
Being the one who wrote the portlet module, I'm quite interested in
helping you figure out why portletdoclet isn't working. Unfortunately, I
am stuck in an all-day off-site meeting (sigh) and won't be able to look
at this until later today.
I can say with quite a bit of certainty that
Hello Craig,
if you need more information just tell me. I already had a look at the
source of the portletdoclet and the portletxml task, but could not
find anything, since all the functionality seems to be somewhere in the
xdoclet core, (populating the portlet tags with the given parameters).
On Wed, 2005-02-09 at 10:15, AndreasWuest wrote:
i have some major problems getting the portletdoclet to work. Seems like
i am the first one using that feature. Searching the net did not return
many results :(
My problem is that the portletdoclet task does not generate a portlet.xml
with my
12 matches
Mail list logo
