AFAIK They don't claim Portlet support. So it is not surprising that it doesn't work.
Sure, but extremeComponents is working flowlessly with uPortal and Liferay, so I was wondering why not in JBoss. In fact I'm developping a portlet oriented framework and I want it to run on the largest number of portals.
Looks like some components will be available on restricted portals.
Thanks for answering me, Thomas.
If it is JSR 168 compliant it should work in JBoss Portal.
If you figure out what is wrong, please let me know.
If you have a very simple portlet that i can use to test, that could also help.
I think I found why it doesn't work out of the box.
Tomorrow I'll give you some more explanations, but if you could tell me what is this "action" parameter (/portal/auth/..../11?action=2&.... for example), it would be very helpfull.
...The tag produces a HTML form...
URL looks like:
The "action" param is added by the <portlet:renderURL> tag. So it's difficult to guess it.
I need to add it manually, there are 2 solutions:
- I guess how "action" is computed
Did you understand my explanations?