留言板

Reject serveResource for ABC after I added $processor.processPortlet() ...

Patrick Warnecke,修改在11 年前。

Reject serveResource for ABC after I added $processor.processPortlet() ...

New Member 帖子: 13 加入日期: 12-9-18 最近的帖子
Hi,

I want to include a static Portlet on all my Pages, thus I added $processor.processPortlet("PORTLETID") in a custom layout. This works fine after I fixed the Bug mentioned here: https://www.liferay.com/de/community/forums/-/message_boards/message/15753181#_19_message_15753056
But now I get the errors (couple more, all the same except other threads):
06:58:11,161 ERROR [http-bio-8080-exec-7][LayoutAction:1019] Reject serveResource for http://localhost:8080/web/guest/welcome on SeparateClassificationTree_WAR_SeparateClassificationTreeportlet
06:58:11,161 ERROR [http-bio-8080-exec-5][LayoutAction:1019] Reject serveResource for http://localhost:8080/web/guest/welcome on SeparateClassificationTree_WAR_SeparateClassificationTreeportlet
06:58:11,161 ERROR [http-bio-8080-exec-9][LayoutAction:1019] Reject serveResource for http://localhost:8080/web/guest/welcome on SeparateClassificationTree_WAR_SeparateClassificationTreeportlet


And the following:
23.10.2012 06:58:09 org.icefaces.impl.event.BridgeSetup addMandatoryResources
WARNUNG: When processing mandatory resource components, could not create instance of 'com.icesoft.faces.component.gmap.GMap'
23.10.2012 06:58:09 org.icefaces.impl.event.BridgeSetup addMandatoryResources
WARNUNG: When processing mandatory resource components, could not create instance of 'com.icesoft.faces.component.inputrichtext.InputRichText'


Somewhere (can't find the source at the moment) I found the suggestion to edit "portla-service/src/com/liferay/portal/util/PortalUtil.java" line ~1367. I edited it so if the method "isAllowAddPortletDefaultResource" for my specific portlet ID would always return true. That got rid of the first error itself, but the Portlet still isn't working.
I still get the second error and now I'm not sure wheter it is purely an ICEFaces thing or if it has something to do with liferay.
Plus I'm not sure if my "bug fixes" are appropriate or something of the portlet configuration is wrong.

Any help appreciated!
Patrick Warnecke,修改在11 年前。

RE: Reject serveResource for ABC after I added $processor.processPortlet()

New Member 帖子: 13 加入日期: 12-9-18 最近的帖子
Has noone any idea what might cause this problem?
thumbnail
Jitendra Rajput,修改在11 年前。

RE: Reject serveResource for ABC after I added $processor.processPortlet()

Liferay Master 帖子: 875 加入日期: 11-1-7 最近的帖子
Did you set <add-default-resource>true</add-default-resource> in your liferay-portlet.xml ?
Srikanth Konjarla,修改在11 年前。

RE: Reject serveResource for ABC after I added $processor.processPortlet()

Junior Member 帖子: 51 加入日期: 08-10-25 最近的帖子
Check this out. http://www.liferay.com/community/forums/-/message_boards/message/17083203

Essentially, review the parameter "portlet.add.default.resource.check.enabled=true"
Patrick Warnecke,修改在11 年前。

RE: Reject serveResource for ABC after I added $processor.processPortlet()

New Member 帖子: 13 加入日期: 12-9-18 最近的帖子
None of that helped.
But my mainproblem isn't really the "reject serveResource". The "hack" I applied to portal-service.jar would be fine to me, that is no problem. But this error "When processing mandatory resource components [...]" really annoys me and blocks any further development emoticon
thumbnail
Neil Griffin,修改在11 年前。

RE: Reject serveResource for ABC after I added $processor.processPortlet()

Liferay Legend 帖子: 2655 加入日期: 05-7-27 最近的帖子
I would recommend that you download the source code for ICEfaces and set a breakpoint in MandatoryResourcesSetup.addMandatoryResources(FacesContext,Map,String) in this block of code:

                } catch (Exception e) {
                    if (log.isLoggable(Level.WARNING)) {
                        log.log(Level.WARNING, "When processing mandatory " +
                                "resource components, could not create instance " +
                                "of '" + compClassName + "'");
                    }
                }


Then report the stacktrace/cause of the error here.