You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by loseyourself <hj...@hotmail.com> on 2007/05/21 07:02:31 UTC
Portlet and MyFaces integration:
java.lang.IllegalArgumentException: only absolute URLs or full path URIs
are allowed
Hi,
Currently I am using RSA 7.0 and Websphere Portal Server 6.0 to do the
portlet development with myfaces. While I am running the portlet, I always
get the following exception:
java.lang.IllegalArgumentException: only absolute URLs or full path URIs are
allowed
… more details are in the attachment.
I uploaded all the configuration files and the exception stack, could
anybody to help me have a look? I do appreciate for any help.
Cheers,
hj
http://www.nabble.com/file/p10713214/configfiles.rar configfiles.rar
--
View this message in context: http://www.nabble.com/Portlet-and-MyFaces-integration%3A-java.lang.IllegalArgumentException%3A-only-absolute-URLs-or-full-path-URIs-are-allowed-tf3788305.html#a10713214
Sent from the MyFaces - Users mailing list archive at Nabble.com.
RE: Portlet and MyFaces integration:
java.lang.IllegalArgumentException: only absolute URLs or full path URIs
are allowed
Posted by loseyourself <hj...@hotmail.com>.
Hi Nebinger,
I do appreciate your help. Currently the portlet can work properly.
Cheers,
hj
--
View this message in context: http://www.nabble.com/Portlet-and-MyFaces-integration%3A-java.lang.IllegalArgumentException%3A-only-absolute-URLs-or-full-path-URIs-are-allowed-tf3788305.html#a10729479
Sent from the MyFaces - Users mailing list archive at Nabble.com.
RE: Portlet and MyFaces integration: java.lang.IllegalArgumentException: only absolute URLs or full path URIs are allowed
Posted by "Nebinger, David" <dn...@tbbgl.com>.
> java.lang.IllegalArgumentException: only absolute URLs or
> full path URIs are allowed
I usually get this if a partial URI is used, i.e. some sort of <img
src="images/filename" /> kind of thing. Using an absolute URI, i.e.
<img src="/images/filename" /> should resolve it.
The issue is that typically even though you're deploying a separate web
app, the portal is actually rewriting urls so that it remains the focal
point on the generated portal page; without fully qualifying your URIs
the portal doesn't know if a resource is relative to the portal root or
the portlet root...