Nicolas,
My goal is to change the favicon from /portal, without affecting custom
modifications that might have been done at /sample-portal. I think we
have already this behavior for templates via extensions, but it doesn't
seem to work for other resources (like .ico files).
The final solution could be anything (extensions, service, ...), hence
the request for suggestions :-)
- Juca.
On 11/28/2013 05:07 PM, Nicolas Filotto wrote:
I'm not sure I understand what you want to do, you want to be
able to
modify the favicon from an extension (like sample-extension) or from an
new portal (like sample-portal)?
On Thu, Nov 28, 2013 at 3:40 PM, Juraci Paixão Kröhling
<jpkroehling(a)redhat.com <mailto:jpkroehling@redhat.com>> wrote:
All,
We have a request to display a specific favicon for JBoss Portal, and it
seems there's no "easy" (or correct) solution in place for that
right now.
The first intuitive solution would be to override the templates, to make
them link to the desired favicon. This doesn't scales, as the whole
template is duplicated and it will only cause headaches in the future.
The second possible solution would be to incorporate the path to the
favicon into the properties file, but this means having a fixed path to
the favicon, which is a step backwards from what there is today: in one
of the templates for /portal, it gets the favicon for the context path,
so, if the current portal is /example-portal, it currently gets the
favicon at /example-portal/favicon . With the favicon coming from the
properties file, this would not be the case anymore, as all favicons
would be coming from a fixed path.
The third solution would be to build a FaviconService, that would take
care of determining the proper favicon path. It sounds to me that this
is a bit of overkill, but would be a clean solution.
Of course, the best option would be to be possible to override the
favicon from /portal, but this doesn't seems to be possible at the
moment. It seems that only templates are overriden.
Before proceeding with the third solution (which seems the most
desirable as of now), I would like to get your comments, opinions and
suggestions on how this could be better handled.
Best Regards,
Juca.
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org <mailto:gatein-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/gatein-dev
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev