Portal Administration ..Request Property Set Bug ??
In weblogic Administration Console, I have created a new role called 'r1'.
This role has a expression associated with it.
I want to have a role expression as mentioned below :
* The Visitor's Http request has some specific properties:
Propertyset: DefaultRequestPropertySet
Property: Query String
Values : Any
Contains: xyz
If I try to save the above then I get a exception as below:
Is this a WL bug or Do I need to do anything more?
Note: If I select 'equals' instead of 'contains' then I dont get any
exceptions and it works fine..
com.bea.jsptools.interaction.exceptions.MissingPropertyException
at
com.bea.jsptools.interaction.InteractionAdminManager.getPropertyDef(Interact
ionAdminManager.java:557)
at
com.bea.jsptools.interaction.InteractionAdminManager.isPropertyMultiValued(I
nteractionAdminManager.java:515)
at
com.bea.jsptools.common.ExpressionEditorHelper.addClause(ExpressionEditorHel
per.java:509)
at
jsp_servlet._entrolestools.__editexpression._jspService(__editexpression.jav
a:2456)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:387)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at
com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:
313)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:597)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:409)
at
com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.j
ava:460)
at
com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:424)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:427)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:172)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:95)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:380)
at com.bea.netuix.nf.UIControl.render(UIControl.java:580)
at
com.bea.netuix.servlets.controls.PresentationContext.render(PresentationCont
ext.java:341)
at
com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:12
3)
at
com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:5
8)
at
jsp_servlet._framework._skeletons._beatools.__gridlayout._jspService(__gridl
ayout.java:337)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:387)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at
com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:
313)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:597)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:409)
at
com.bea.netuix.servlets.controls.JspRenderer.renderAlt(JspRenderer.java:187)
at
com.bea.netuix.servlets.controls.JspRenderer.beginRender(JspRenderer.java:90
at
com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:420)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:427)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:172)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:95)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:380)
at com.bea.netuix.nf.UIControl.render(UIControl.java:580)
at
com.bea.netuix.servlets.controls.PresentationContext.render(PresentationCont
ext.java:341)
at
com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:12
3)
at
com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:5
8)
at
jsp_servlet._framework._skeletons._beatools.__gridlayout._jspService(__gridl
ayout.java:337)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:387)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at
com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:
313)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:597)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:409)
at
com.bea.netuix.servlets.controls.JspRenderer.renderAlt(JspRenderer.java:187)
at
com.bea.netuix.servlets.controls.JspRenderer.beginRender(JspRenderer.java:90
at
com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:420)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:427)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:172)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:95)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:380)
at com.bea.netuix.nf.UIControl.render(UIControl.java:580)
at
com.bea.netuix.servlets.controls.PresentationContext.render(PresentationCont
ext.java:341)
at
com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:12
3)
at
com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:5
8)
at
jsp_servlet._framework._skeletons._beatools.__gridlayout_outermost._jspServi
ce(__gridlayout_outermost.java:351)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:387)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at
com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:
313)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:597)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:409)
at
com.bea.netuix.servlets.controls.JspRenderer.renderAlt(JspRenderer.java:187)
at
com.bea.netuix.servlets.controls.JspRenderer.beginRender(JspRenderer.java:90
at
com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:420)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:427)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:172)
at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:220)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:158)
at
com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:363)
at
com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:207)
at
com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:583
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:387)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at
com.bea.servlet.PortalSystemAdministratorFilter.doFilter(PortalSystemAdminis
tratorFilter.java:78)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at
com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:
313)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(W
ebAppServletContext.java:6316)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubjec
t.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:3622)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Pramod,
That is a bug and will be fixed in Service Pack 2 (a couple of months).
Sorry for any inconvenience.
-Phil
"Pramod" <[email protected]> wrote in message
news:[email protected]...
We are using Weblogic 8.1 ....
In weblogic Administration Console, I have created a new role called
'r1'.
>>
This role has a expression associated with it.
I want to have a role expression as mentioned below :
* The Visitor's Http request has some specific properties:
Propertyset: DefaultRequestPropertySet
Property: Query String
Values : Any
Contains: xyz
If I try to save the above then I get a exception as below:
Is this a WL bug or Do I need to do anything more?
Note: If I select 'equals' instead of 'contains' then I dont get any
exceptions and it works fine..
com.bea.jsptools.interaction.exceptions.MissingPropertyException
at
com.bea.jsptools.interaction.InteractionAdminManager.getPropertyDef(Interact
ionAdminManager.java:557)
at
com.bea.jsptools.interaction.InteractionAdminManager.isPropertyMultiValued(I
nteractionAdminManager.java:515)
at
com.bea.jsptools.common.ExpressionEditorHelper.addClause(ExpressionEditorHel
per.java:509)
at
jsp_servlet._entrolestools.__editexpression._jspService(__editexpression.jav
a:2456)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:387)
atweblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
>>
at
com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:
313)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
>>
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:597)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:409)
at
com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.j
ava:460)
at
com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:424)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:427)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:172)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:95)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:380)
at com.bea.netuix.nf.UIControl.render(UIControl.java:580)
at
com.bea.netuix.servlets.controls.PresentationContext.render(PresentationCont
ext.java:341)
at
com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:12
3)
at
com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:5
8)
at
jsp_servlet._framework._skeletons._beatools.__gridlayout._jspService(__gridl
ayout.java:337)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:387)
atweblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
>>
at
com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:
313)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
>>
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:597)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:409)
at
com.bea.netuix.servlets.controls.JspRenderer.renderAlt(JspRenderer.java:187)
>>
at
com.bea.netuix.servlets.controls.JspRenderer.beginRender(JspRenderer.java:90
at
com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:420)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:427)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:172)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:95)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:380)
at com.bea.netuix.nf.UIControl.render(UIControl.java:580)
at
com.bea.netuix.servlets.controls.PresentationContext.render(PresentationCont
ext.java:341)
at
com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:12
3)
at
com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:5
8)
at
jsp_servlet._framework._skeletons._beatools.__gridlayout._jspService(__gridl
ayout.java:337)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:387)
atweblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
>>
at
com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:
313)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
>>
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:597)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:409)
at
com.bea.netuix.servlets.controls.JspRenderer.renderAlt(JspRenderer.java:187)
>>
at
com.bea.netuix.servlets.controls.JspRenderer.beginRender(JspRenderer.java:90
at
com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:420)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:427)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:172)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:95)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:380)
at com.bea.netuix.nf.UIControl.render(UIControl.java:580)
at
com.bea.netuix.servlets.controls.PresentationContext.render(PresentationCont
ext.java:341)
at
com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:12
3)
at
com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:5
8)
at
jsp_servlet._framework._skeletons._beatools.__gridlayout_outermost._jspServi
ce(__gridlayout_outermost.java:351)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:387)
atweblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
>>
at
com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:
313)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
>>
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:597)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
l.java:409)
at
com.bea.netuix.servlets.controls.JspRenderer.renderAlt(JspRenderer.java:187)
>>
at
com.bea.netuix.servlets.controls.JspRenderer.beginRender(JspRenderer.java:90
at
com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:420)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:427)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.ja
va:436)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:172)
at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:220)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:158)
at
com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:363)
>>
at
com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:207)
at
com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:583
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:387)
atweblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
>>
at
com.bea.servlet.PortalSystemAdministratorFilter.doFilter(PortalSystemAdminis
tratorFilter.java:78)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
>>
at
com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:
313)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
>>
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(W
ebAppServletContext.java:6316)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubjec
t.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
>>
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:3622)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Similar Messages
-
Session/Request Property Sets.
What are the Session and Request property sets used for? And how do I
get at them? The documentation states I can access these via the
Personalization Advisor. There doesn't appear to be a tag nor a method
to access these. Also if I create a Session Property it does not show up
in the HttpSession object.
[chris.jolley.vcf]Hi,
Thanks for your answer.
We are using Portal 4.0 and the com.beasys.commerce.axiom.p13n.jsp.P13NJspBase has
been
deprecated.
I found one solution "hidden" in the p13n examples.
It was in sample.jsp under p13nApp\p13n in the examples directory.
It would be nice if something was mentioned in the documentation
about how to get Session property sets to work.
br,
Chris
Ture Hoefner <[email protected]> wrote:
>
>
Hello Chris,
Do not set and get request and session properties with the
<um:setproperty> and <um:getproperty> tags. Use the methods
JspBase.setSessionValue() and JspBase.getSessionValue() for session values
and HttpRequest.setAttribute() and HttpRequest.getAttribute() for request
properties.
You have to use the JspBase methods for the session values because the
key
is "fixed up" by prepending the name that is registered to the
JspServiceManager or PortalServiceManager servlet for your application.
This allows multiple portals to be served to a client from a single server.
This also means that you cannot use session properties in an application
that does not use the JspServiceManager or PortalServiceManager.
Here is a test JSP that may be registered as a portlet and added to an
example portal. To use it, you must create your session and request
rulesheets (or use existing ones) with the admin tool. You can
create/register the "age" property in the DefaultRequestPropertySet and
in
the DefaultSessionPropertySet using the admin tool. The sample code works
for rulesheets named "request" and "session". Then create a classifier
in
each rulesheet called "middleage" that says something like this:
REQUEST.DefaultRequestPropertySet.age >= 40
and
REQUEST.DefaultRequestPropertySet.age < 65
SESSION.DefaultSessionPropertySet.age >= 40
and
SESSION.DefaultSessionPorpertySet.age < 65
<%@ taglib uri="lib/um_tags.jar" prefix="um" %>
<%@ taglib uri="pz.tld" prefix="pz" %>
<%-- A JSP page that uses the Personalization Advisor (typically
through the pz tags) must extend P13NJspBase --%>
<%@ page extends="com.beasys.commerce.axiom.p13n.jsp.P13NJspBase" %>
<%
/* Put an age in the session. Use the JspBase.setSessionValue() method
so
that the key is "fixed up" by prepending the name registered with
the JspServiceManager
or PortalServiceManager for this application.
This is to allow a single server to service multiple portals. */
Long ageLong = new Long(52);
setSessionValue("age", ageLong, request);
request.setAttribute("age", ageLong);
%>
<%-- Do not use <um:getproperty> and <um:setproperty> tags to get and set
session
properties. Session properties should be set/get with JspBase.setSessionValue()
and
JspBase.getSessionValue(). Request properties should be set/get with
HttpRequest.setAttribute()
and HttpRequest.getAttribute() --%>
<br>
The middleage classifier will run for the session property:
<br>
<pz:div
ruleset="jdbc://com.beasys.commerce.axiom.reasoning.rules.RuleSheetDefinitionHome/session"
rule="middleage" >
<br>
The middle age classifier evaluated to TRUE
<br>
</pz:div>
<br>
The middleage classifier will run for the request property:
<br>
<pz:div
ruleset="jdbc://com.beasys.commerce.axiom.reasoning.rules.RuleSheetDefinitionHome/request"
rule="middleage" >
<br>
The middle age classifier evaluated to TRUE
<br>
</pz:div>
<%
// Clean up the session in case you are testing this over and over
removeSessionValue("age", request);
request.removeAttribute("age");
%>
Ture Hoefner
BEA Systems, Inc.
2590 Pearl St.
Suite 110
Boulder, CO 80302
www.bea.com
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hello Chris,
<br> Do not set and get request and session properties with the <um:setproperty>
and <um:getproperty> tags. Use the methods JspBase.setSessionValue()
and JspBase.getSessionValue() for session values and HttpRequest.setAttribute()
and HttpRequest.getAttribute() for request properties.
<br> You have to use the JspBase methods for the session values because
the key is "fixed up" by prepending the name that is registered to the
JspServiceManager or PortalServiceManager servlet for your application.
This allows multiple portals to be served to a client from a single server.
This also means that you cannot use session properties in an application
that does not use the JspServiceManager or PortalServiceManager.
<br> Here is a test JSP that may be registered as a portlet and added
to an example portal. To use it, you must create your session and
request rulesheets (or use existing ones) with the admin tool. You
can create/register the "age" property in the DefaultRequestPropertySet
and in the DefaultSessionPropertySet using the admin tool. The sample
code works for rulesheets named "request" and "session". Then create
a classifier in each rulesheet called "middleage" that says something like
this:
<br>
<p> REQUEST.DefaultRequestPropertySet.age >= 40
<br> and
<br> REQUEST.DefaultRequestPropertySet.age < 65
<p> SESSION.DefaultSessionPropertySet.age >= 40
<br> and
<br> SESSION.DefaultSessionPorpertySet.age < 65
<br>--------------------------------------------------------------------------------------------
<pre><%@ taglib uri="lib/um_tags.jar" prefix="um" %></pre>
<pre><%@ taglib uri="pz.tld" prefix="pz" %></pre>
<pre></pre>
<pre><%-- A JSP page that uses the Personalization Advisor (typically</pre>
<pre> through the pz tags) must extend P13NJspBase
--%></pre>
<pre><%@ page extends="com.beasys.commerce.axiom.p13n.jsp.P13NJspBase"
%></pre>
<pre></pre>
<pre><%</pre>
<pre> /* Put an age in the session. Use the JspBase.setSessionValue()
method so</pre>
<pre> that the key is "fixed up" by
prepending the name registered with the JspServiceManager</pre>
<pre> or PortalServiceManager for this
application.</pre>
<pre> This is to allow a single
server to service multiple portals. */</pre>
<pre> Long ageLong = new Long(52);</pre>
<pre> setSessionValue("age", ageLong, request);</pre>
<pre></pre>
<pre> request.setAttribute("age", ageLong);</pre>
<pre>%></pre>
<pre> </pre>
<pre><%-- Do not use <um:getproperty> and <um:setproperty> tags
to get and set session</pre>
<pre> properties. Session properties should
be set/get with JspBase.setSessionValue() and</pre>
<pre> JspBase.getSessionValue(). Request properties
should be set/get with HttpRequest.setAttribute()</pre>
<pre> and HttpRequest.getAttribute() --%></pre>
<pre> </pre>
<pre><br></pre>
<pre>The middleage classifier will run for the session property:</pre>
<pre><br></pre>
<pre><pz:div</pre>
<pre> ruleset="jdbc://com.beasys.commerce.axiom.reasoning.rules.RuleSheetDefinitionHome/session"</pre>
<pre> rule="middleage" ></pre>
<pre> <br></pre>
<pre> The middle age classifier
evaluated to TRUE</pre>
<pre> <br></pre>
<pre></pz:div></pre>
<pre></pre>
<pre><br></pre>
<pre>The middleage classifier will run for the request property:</pre>
<pre><br></pre>
<pre><pz:div</pre>
<pre> ruleset="jdbc://com.beasys.commerce.axiom.reasoning.rules.RuleSheetDefinitionHome/request"</pre>
<pre> rule="middleage" ></pre>
<pre> <br></pre>
<pre> The middle age classifier
evaluated to TRUE</pre>
<pre> <br></pre>
<pre></pz:div></pre>
<pre> </pre>
<pre></pre>
<pre><%</pre>
<pre> // Clean up the session in case you are testing
this over and over</pre>
<pre> removeSessionValue("age", request);</pre>
<pre> request.removeAttribute("age");</pre>
<pre>%></pre>
<p>
<p>--
<br>Ture Hoefner
<br>BEA Systems, Inc.
<br>2590 Pearl St.
<br>Suite 110
<br>Boulder, CO 80302
<br>www.bea.com
<br> </html> -
Request property set proper usage
How to use request property set from datasync project properly ?
Should I just set a property and then dynamically do get and set header with
the property.
Any suggestion will be quite helpful
Thanks,
SubhabrataSubhabrata,
There is quite a bit of docs to look at. Take a look at the tags:
http://e-docs.bea.com/workshop/docs81/doc/en/core/index.html
-Phil
"Subhabrata Sarkar" <[email protected]> wrote in message
news:3fc52b1a$[email protected]..
>
>
How to use request property set from datasync project properly ?
Should I just set a property and then dynamically do get and set headerwith
>
the property.
Any suggestion will be quite helpful
Thanks,
Subhabrata -
Session Property Set not available in Portal Administration Console
We have a Portal Application (WLP 10.0 MP1) that needs to have visitor entitlements applied to allow some customization based upon a Session Property Set. The property set has been defined in Workshop and the .ses file is now included in our Portal EAR file in the /META-INF/data directory. When the EAR is deployed on a local (winXP) domain the property set is then available in the portal admin console and can be used to build entitlements. When the EAR is deployed to our test server (Solaris 10) the property set does not become available in the portal admin console. Both servers are in development mode and already have a previous version of the EAR deployed in streaming mode.
Is there anything obvious that needs to be done to ensure that a property set is enabled when deploying a new EAR?We are actually performing the portal EAR build using maven but are creating the same directory layout as is created by Workshop when a data sync project is used and an EAR exported, i.e. the contents of the data sync project ends up in the EAR /META-INF/data directory.
The mystery here is that the property set correctly deploys in one environment but not in another. I'd really like to know whether there are any particular tricks to the property set deployment and what the deployent process actually does. Could issues with the target environment prevent correct deployment of the property set? -
Setting up LDAP for authentication to portal:default property set named "ldap
Hi
I am trying to implement the LDAP authentication to WebLogic Portal .Iam went
thru the docmentation ( http://edocs.bea.com/wlp/docs40/p13ndev/users.htm#1131824).It
mentions using the default property set named "ldap" and deploying ldapprofile.jar.My
quenstion is:
-Is there a way to look into the property using EBCC
- Apart from deploying,configuring the ldapprofile.jar,do I have to do any additional
steps in order to make my portal(say,stockportal) authenticate users from LDAP?
-If a create my own portal,should I create a similar "ldap" property set?If so,how.
Any suggestions/help is appreciated.Thanks
- MikeThanks Dave.
"David Anderson" <[email protected]> wrote:
You should be able to view the property set for LDAP through the EBCC
if you
have the propertysetws.jar installed in your Portal domain. This provides
the ability for the EBCC to retrieve property set information from your
server.
Dave
"mike" <[email protected]> wrote in message
news:[email protected]...
Hi Adrian
Thank you for the pointers.Much appreciate it.However,one questionstill
persists.
What is the significance of the property set "ldap" mentioned in the
document(http://edocs.bea.com/wlp/docs40/p13ndev/users.htm#1131824).Where
does this property set feature vis-a-vis setting up LDAP securityrealm;does it
mater prior to/after the setting up as mentioned in the document pointeryou just
gave .
Is it sufficinet that i follow the procedure to set up the LDAP oris
there more
to post setting,like creating a property set (similar to "ldap" orcloning
it)
apaprt frpom deploying ldapprofile.jar.
Thanks.
- Mike
"Adrian Fletcher" <[email protected]> wrote:
Mike,
The documentation that covers LDAP authentication is listed under
Weblogic
Server rather than Weblogic Portal.
See Configuring the LDAP Security Realm in Managing Security
(http://e-docs.bea.com/wls/docs61////adminguide/cnfgsec.html#1071872)
Also take a look at the FAQ - Why can't I boot WebLogic Server whenusing
the LDAP Security Realm?
(http://e-docs.bea.com/wls/docs61//faq/security.html#25833)
Hope this helps,
Sincerely,
Adrian.
Adrian Fletcher.
Senior Software Engineer,
BEA Systems, Inc.
Boulder, CO.
email: [email protected]
"mike" <[email protected]> wrote in message
news:[email protected]...
Hi
I am trying to implement the LDAP authentication to WebLogic Portal.Iam
went
thru the docmentation
http://edocs.bea.com/wlp/docs40/p13ndev/users.htm#1131824).It
mentions using the default property set named "ldap" and deployingldapprofile.jar.My
quenstion is:
-Is there a way to look into the property using EBCC
- Apart from deploying,configuring the ldapprofile.jar,do I have
to
do any
additional
steps in order to make my portal(say,stockportal) authenticate usersfrom
LDAP?
-If a create my own portal,should I create a similar "ldap" propertyset?If so,how.
Any suggestions/help is appreciated.Thanks
- Mike -
Session property set not updating in Portal Admin console
Hello,
We have a Portal application running on 10 MP1. Included in the EAR file is a session property set and is correctly stored in the right directory (META-INF/data).
When deployed, I can view our session properties when I try to create some entitlements and expressions. However, we need to update the name of one property and when we redeployed the EAR with an updated session property file, in the Portal Admin console, the session property still has the old name.
This happens on one of our environments, but does not happen on my local machine. On my local machine, when I look at the database, the DATA_SYNC_ITEM table is empty. But on our other environment (where the problem exists), in the database I can see relevant entries for my app and property file in the DATA_SYNC_ITEM table.
Does anyone have any ideas why this table is not populated on my local machine and why I can't seem to update the session property file on my other environment where the table is populated?
Any help would be much appreciated.
Thanks,
JonathanProbably either development mode /prodiction mode differences or differences between deploying as an exploded ear (local) and a compressed ear (in your environment that doesnt work). The easiest way is to propagate the changes from your local to the other environment (you can scope it to just session properties)
http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/prodOps/propToolAdvanced.html -
Enhancement request: ADF BC property sets
Hi JDev team
"Yeehaw" on the property sets feature. Very Oracle Designer like.
To make them even more powerful can you:
1) In the App Navigator provide "analyze dependencies" option on the right mouse sub-menu.
2) In the ADF BC EO/VO attr document view, and attribute editor, can you show any values derived from the property set, and show them in a different colour.
3) If a custom value is given for an ADF BC EO/VO attr property, over-writing derived property set value, facility to change back to property set value, and/or set null.
4) The ability to create a new property set from an existing ADF BC EO/VO attribute
5) Ability to set property sets against ADF BC VO bind variables
Thanks,
CM.1) We plan a "Find Usages..." option on ADFBC components, including Property Sets
2) Filed ER# 6053438
3) Filed ER# 6053447
4) Filed ER# 6053454
5) Filed ER# 6053457
Thanks. -
Hello All:
I am looking for a way to deploy a property set file; joedoe.usr to Weblogic Portal 8.1. Has anyone successfully deployed a property set file (including the UUP ejb that uses it) to WebLogic outside of Workshop? If so, can you provide steps to do so?
FYI, I created a property set file and added to my ear in the META-INF directory. When I deploy my ear to Weblogic, I can see my portal application and all the portal resources in the Portal Admin. However, I do not see my "custom" property set when editing a user. My constraint is that my application must not use Workshop to create and deploy.
Thank you,
SouthinHi Deepak:
Thank you for replying to my message. Unfortunately, the example the BEA does not work for me. Yes my corporateProfile.usr is in the data/userprofiles folder where the CustomerProperties.usr resides. My custom ejb that extends extends com.bea.p13n.property.EntityPropertyManager is successfully deployed, however I cannot see the property set that I created in the Portal Admin console.
Attached are my weblogic-ejb-jar.xm and ejb-jar.xml files that I edit after following the instructions for "Deploy a ProfileManager That Can Use the New EntityPropertyManager." Does anyone see something wrong?
------------------------ ejb-jar.xml -------------
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC
'-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN'
'http://java.sun.com/dtd/ejb-jar_2_0.dtd' >
<ejb-jar>
<enterprise-beans>
<!-- TrackedAnonymous EJB -->
<entity>
<ejb-name>TrackedAnonymous</ejb-name>
<home>com.bea.p13n.usermgmt.profile.TrackedAnonymousHome</home>
<remote>com.bea.p13n.usermgmt.profile.TrackedAnonymous</remote>
<ejb-class>com.bea.p13n.usermgmt.profile.internal.TrackedAnonymousBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>TrackedAnonymousBean</abstract-schema-name>
<cmp-field>
<field-name>anonymousUserId</field-name>
</cmp-field>
<cmp-field>
<field-name>lastVisited</field-name>
</cmp-field>
<primkey-field>anonymousUserId</primkey-field>
<ejb-local-ref>
<description>Reference to TrackedPropertySet EJB</description>
<ejb-ref-name>ejb/TrackedPropertySet</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>com.bea.p13n.property.TrackedPropertySetHome</local-home>
<local>com.bea.p13n.property.TrackedPropertySet</local>
<ejb-link>TrackedPropertySet</ejb-link>
</ejb-local-ref>
</entity>
<!-- Tracked Property Set EJB -->
<!-- Local interfaces for this one only, because it's referred to only by TrackedAnonymous.
The relationships bewteen these two EJBs are defined in the 'relationships' attribute at
the end of this file. -->
<entity>
<ejb-name>TrackedPropertySet</ejb-name>
<local-home>com.bea.p13n.property.TrackedPropertySetHome</local-home>
<local>com.bea.p13n.property.TrackedPropertySet</local>
<ejb-class>com.bea.p13n.property.internal.TrackedPropertySetBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>TrackedPropertySetBean</abstract-schema-name>
<cmp-field>
<field-name>anonymousPropertyId</field-name>
</cmp-field>
<cmp-field>
<field-name>anonymousUserId</field-name>
</cmp-field>
<cmp-field>
<field-name>propertySetName</field-name>
</cmp-field>
<cmp-field>
<field-name>propertyName</field-name>
</cmp-field>
<cmp-field>
<field-name>propertyValue</field-name>
</cmp-field>
<primkey-field>anonymousPropertyId</primkey-field>
<!-- Find all property sets with the same anonymous user id. This gives us all property sets associated with a single
TrackedAnonymous EJB -->
<query>
<query-method>
<method-name>findByAnonymousUserId</method-name>
<method-params>
<method-param>java.lang.String</method-param>
</method-params>
</query-method>
<ejb-ql>SELECT OBJECT (a) FROM TrackedPropertySetBean a WHERE a.anonymousUserId = ?1 </ejb-ql>
</query>
</entity>
<!-- PropertySetManager EJB -->
<session>
<ejb-name>PropertySetManager</ejb-name>
<home>com.bea.p13n.property.PropertySetManagerHome</home>
<remote>com.bea.p13n.property.PropertySetManager</remote>
<ejb-class>com.bea.p13n.property.internal.PropertySetManagerImpl</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<env-entry>
<env-entry-name>repository/CONTENT</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>com.bea.content.manager.propertysets.PropertySetRepositoryImpl</env-entry-value>
</env-entry>
<!-- following are mappings from file extension to property set type -->
<env-entry>
<env-entry-name>extension/clg</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>CATALOG</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>extension/evt</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>EVENT</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>extension/req</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>REQUEST</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>extension/ses</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>SESSION</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>extension/usr</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>USER</env-entry-value>
</env-entry>
<!-- the ejb/ContentManagers branch is for the
com.bea.p13n.content.PropertyRepositoryImpl
-->
<ejb-ref>
<ejb-ref-name>ejb/ContentManagers/Document</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.bea.p13n.content.document.DocumentManagerHome</home>
<remote>com.bea.p13n.content.document.DocumentManager</remote>
<!-- FIXME. Eventually need to rework user manager stuff so we can do this. For now, the DocumentManager
is in weblogic-ejb-jar.xml, where it is deployed only if it is referenced.
<ejb-link>wps.jar#DocumentManager</ejb-link> -->
</ejb-ref>
</session>
<!-- EntityPropertyManager EJB -->
<session>
<ejb-name>EntityPropertyManager</ejb-name>
<home>com.bea.p13n.property.EntityPropertyManagerHome</home>
<remote>com.bea.p13n.property.EntityPropertyManager</remote>
<ejb-class>com.bea.p13n.property.internal.EntityPropertyManagerImpl</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<ejb-ref>
<ejb-ref-name>ejb/PropertySetManager</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.bea.p13n.property.PropertySetManagerHome</home>
<remote>com.bea.p13n.property.PropertySetManager</remote>
<ejb-link>PropertySetManager</ejb-link>
</ejb-ref>
<resource-ref>
<res-ref-name>jdbc/commercePool</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</session>
<!-- Ldap Property Manager
To use this, uncomment it here as well as in weblogic-ejb-jar.xml.
Configure the LDAP connection and settings using the env-entry values (see descriptions below).
Do not forget to uncomment the ejb-link and method-permission tags for the LdapPropertyManager.
An easy way to ensure you don't miss anything is to search for "ldap" (case-insensitive) here AND in
weblogic-ejb-jar.xml. Search from the beginning to the end of the file.
<session>
<ejb-name>LdapPropertyManager</ejb-name>
<home>com.bea.p13n.usermgmt.profile.ldap.LdapPropertyManagerHome</home>
<remote>com.bea.p13n.usermgmt.profile.ldap.LdapPropertyManager</remote>
<ejb-class>com.bea.p13n.usermgmt.profile.ldap.internal.LdapPropertyManagerImpl</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<env-entry>
<description>Use SSL to connect to ldap server</description>
<env-entry-name>config/useSSL</env-entry-name>
<env-entry-type>java.lang.Boolean</env-entry-type>
<env-entry-value>false</env-entry-value>
</env-entry>
<env-entry>
<description>LDAP Server URL</description>
<env-entry-name>config/serverURL</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>ldap://server.company.com:389</env-entry-value>
</env-entry>
<env-entry>
<description>Principal name to use when connecting to the ldap server (optional).
Anonymous bind will be used if not specified. This entry will be
ignored if config/credentialMBeanName is set below. </description>
<env-entry-name>config/principal</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>uid=admin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot</env-entry-value>
</env-entry>
<env-entry>
<description>The password of the principal specified above (required if principal set). This
entry is ignored if config/credentialMBeanName is set below.</description>
<env-entry-name>config/principalCredential</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>weblogic</env-entry-value>
</env-entry>
<env-entry>
<description>The name of the Credential MBean in application-config.xml that will
be used to store the principal's username and principal's password. The password
will be stored in an encrypted form. This is the principal/credential used to bind to
the LDAP server. The password will be decrypted before it is used to bind to the
LDAP server.
Using this entry will override anything set for the config/principal and
config/principalCredential. If this entry and config/principal and
config/principalCredential are not specified then anonymous bind will be used.
(this entry is optional)</description>
<env-entry-name>config/credentialMBeanName</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>LdapPropertyManager</env-entry-value>
</env-entry>
<env-entry>
<description> The location(s) of users in the ldap directory.
There can be one or more user DNs. The entries are named like this:
config/userDN
config/userDN-1
config/userDN-2
and they are searched in that order.
If there is only one, then it must be config/userDN
Typical values:
ou=People,o=company.com
ou=People,dc=mycompany,dc=com
</description>
<env-entry-name>config/userDN</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>ou=People,o=company.com</env-entry-value>
</env-entry>
<env-entry>
<description> The location(s) of groups in the ldap directory
There can be one or more group DNs. The entries are named like this:
config/groupDN
config/groupDN-1
config/groupDN-2
and they are searched in that order.
If there is only one, then it must be config/groupDN
Typical values:
ou=Groups,o=company.com
ou=Groups,dc=mycompany,dc=com
</description>
<env-entry-name>config/groupDN</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>ou=Groups,o=company.com</env-entry-value>
</env-entry>
<env-entry>
<description>A boolean to enbable/disable SUBTREE_SCOPE searches for user/group properties
below the userDN(s) and groupDN(s). For example, if this property is true, then you could specify
the "config/userDN" env-entry as ou=People,dc=mycompany,dc=com and users that are in both
ou=PeopleA,ou=People,dc=mycompany,dc=com and in ou=PeopleB,ou=People,dc=mycompany,dc=com
could be used. A getProperty() call would return a value for the first user found in
the specified "config/userDN" or in any branch below it. This boolean also affects
searches for group properties. If multiple userDNs (or groupDNs) are specified then
this SUBTREE_SCOPE will apply to searches starting in all of those specified DNs.
</description>
<env-entry-name>config/objectPropertySubtreeScope</env-entry-name>
<env-entry-type>java.lang.Boolean</env-entry-type>
<env-entry-value>false</env-entry-value>
</env-entry>
<env-entry>
<description>The user attribute to map to a username
If there is only one, then it is applied to all userDNs.
If there is more than one, then they are applied, in order,
to the userDNs. If there is more than one, then the number must
match the number of userDNs.
The entries are named like this:
config/usernameAttribute
config/usernameAttribute-1
config/usernameAttribute-2
and they are used in that order.
If there is only one, then it must be config/usernameAttribute
</description>
<env-entry-name>config/usernameAttribute</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>uid</env-entry-value>
</env-entry>
<env-entry>
<description> The group attribute to map to a group name
If there is only one, then it is applied to all groupDNs.
If there is more than one, then they are applied, in order,
to the groupDNs. If there is more than one, then the number must
match the number of groupDNs.
The entries are named like this:
config/groupnameAttribute
config/groupnameAttribute-1
config/groupnameAttribute-2
and they are used in that order.
If there is only one, then it must be config/groupnameAttribute
</description>
<env-entry-name>config/groupnameAttribute</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>cn</env-entry-value>
</env-entry>
<env-entry>
<description>Flag to specify if LDAP attributes will be determined to be
single value or multi-value via the schema obtained from
the attribute. If false, then the attribute is stored as
multi-valued (a Collection) only if it has more than one value.
Leave false unless you intend to use multi-valued LDAP attributes
that may have only one value. Using true adds overhead to check the
LDAP schema. Also, if you use true beware that most LDAP attributes
are multi-value. For example, iPlanet Directory Server 5.x uses multi-value
for givenName, which you may not expect unless you are familiar with LDAP
schemas.
This flag will apply to property searches for all userDNs and all groupDNs.
</description>
<env-entry-name>config/detectSingleValueFromSchema</env-entry-name>
<env-entry-type>java.lang.Boolean</env-entry-type>
<env-entry-value>false</env-entry-value>
</env-entry>
<env-entry>
<description>Value of the name of the attribute in the LDAP schema that is used to
determine single value or multi-value (RFC2252 uses SINGLE-VALUE)
This attribute in the schema should be true for single value and false or
absent from the schema otherwise.
The value only matters if config/detectSingleValueFromSchema is true.
</description>
<env-entry-name>config/singleValueSchemaAttribute</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>SINGLE-VALUE</env-entry-value>
</env-entry>
<env-entry>
<description> Name for the cache used by the ldap property manager
If you deploy multiple LdapPropertyManager beans, you must set
the caches to different names to avoid collisions.
Defaults to "ldapPropertyCache" if unset.
</description>
<env-entry-name>config/ldapPropertyCacheName</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>ldapPropertyCache</env-entry-value>
</env-entry>
</session>
-->
<!-- Property Set Web Service EJB -->
<session>
<ejb-name>PropertySetWebService</ejb-name>
<home>com.bea.p13n.property.webservice.PropertySetWebServiceHome</home>
<remote>com.bea.p13n.property.webservice.PropertySetWebService</remote>
<ejb-class>com.bea.p13n.property.webservice.internal.PropertySetWebServiceImpl</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<ejb-ref>
<ejb-ref-name>ejb/PropertySetManager</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.bea.p13n.property.PropertySetManagerHome</home>
<remote>com.bea.p13n.property.PropertySetManager</remote>
<ejb-link>PropertySetManager</ejb-link>
</ejb-ref>
</session>
<!-- RulesManager EJB -->
<session>
<ejb-name>RulesManager</ejb-name>
<home>com.bea.p13n.rules.manager.RulesManagerHome</home>
<remote>com.bea.p13n.rules.manager.RulesManager</remote>
<ejb-class>com.bea.p13n.rules.manager.internal.RulesManagerImpl</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<env-entry>
<description>
This property will be used by RulesManagerImpl to create an instance of
the RuleSetRepository.
</description>
<env-entry-name>RuleSetRepositoryClassName</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager</env-entry-value>
</env-entry>
</session>
<!-- User Manager EJB -->
<session>
<ejb-name>UserManager</ejb-name>
<home>com.bea.p13n.usermgmt.UserManagerHome</home>
<remote>com.bea.p13n.usermgmt.UserManager</remote>
<ejb-class>com.bea.p13n.usermgmt.internal.UserManagerImpl</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<!-- ReservedUserNames is used to list all names (case insensitive)
that are restricted: the UserManager will not create users
with these names. The list is comma-delimited.
-->
<!--
<env-entry>
<env-entry-name>ReservedUserNames</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>foo,foo2</env-entry-value>
</env-entry>
-->
<!-- ProtectedUserNames is used to list all names (case insensitive)
that cannot be deleted through the UserManager (or portal tools).
The list is comma-delimited.
-->
<!--
<env-entry>
<env-entry-name>ProtectedUserNames</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>foo,foo2</env-entry-value>
</env-entry>
-->
<!-- The UserManager used programatic security to allow
users to modify their own data (where username == profileName)
or anyone in one of these (administrative) roles.
Used in the methods: setPassword and removeUser.
Other methods can be protected using declarative security.
Should at least include the WebLogic Admin role, if left empty
or mapped to "empty" roles, then no one will be able to admin
user profiles.
Each role listed here should also have a security-role-ref entry below -->
<env-entry>
<env-entry-name>AuthorizedRoles</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>Admin,PortalSystemAdministrator</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>disallowedUserCharacters</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>*,%</env-entry-value>
</env-entry>
<ejb-ref>
<ejb-ref-name>ejb/UserProfileManager</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.bea.p13n.usermgmt.profile.ProfileManagerHome</home>
<remote>com.bea.p13n.usermgmt.profile.ProfileManager</remote>
<ejb-link>UserProfileManager</ejb-link>
</ejb-ref>
<ejb-ref>
<ejb-ref-name>ejb/ProfileType/WLCS_Customer</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.bea.commerce.ebusiness.customer.CustomerProfileManagerHome</home>
<remote>com.bea.commerce.ebusiness.customer.CustomerProfileManager</remote>
<!-- FIXME. Can't do this without always deploying Customer. Eventually need
to rework user manager stuff so we can do this. For now, the CustomerProfileManager
is in weblogic-ejb-jar.xml, where it is deployed only if it is referenced.
<ejb-link>commerce.jar#CustomerProfileManager</ejb-link> -->
</ejb-ref>
<!-- Security role refs for roles listed in AuthorizedRoles -->
<security-role-ref>
<description>Portal system administrators</description>
<role-name>PortalSystemAdministrator</role-name>
<role-link>PortalSystemAdministrator</role-link>
</security-role-ref>
<security-role-ref>
<description>WLS System administrators</description>
<role-name>Admin</role-name>
<role-link>Admin</role-link>
</security-role-ref>
<resource-ref>
<res-ref-name>jdbc/commercePool</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</session>
<!-- Group Manager EJB -->
<session>
<ejb-name>GroupManager</ejb-name>
<home>com.bea.p13n.usermgmt.GroupManagerHome</home>
<remote>com.bea.p13n.usermgmt.GroupManager</remote>
<ejb-class>com.bea.p13n.usermgmt.internal.GroupManagerImpl</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<!-- ProtectedGroupNames is used to list all names (case insensitive)
that cannot be deleted through the GroupManager (or portal tools).
The list is comma-delimited.
-->
<env-entry>
<env-entry-name>ProtectedGroupNames</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>Operators,Monitors,Deployers</env-entry-value>
</env-entry>
<ejb-ref>
<ejb-ref-name>ejb/GroupProfileManager</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.bea.p13n.usermgmt.profile.ProfileManagerHome</home>
<remote>com.bea.p13n.usermgmt.profile.ProfileManager</remote>
<ejb-link>GroupProfileManager</ejb-link>
</ejb-ref>
</session>
<!-- Realm Configuration EJB -->
<session>
<ejb-name>RealmConfiguration</ejb-name>
<home>com.bea.p13n.usermgmt.config.RealmConfigurationHome</home>
<remote>com.bea.p13n.usermgmt.config.RealmConfiguration</remote>
<ejb-class>com.bea.p13n.usermgmt.config.internal.RealmConfigurationImpl</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<ejb-ref>
<ejb-ref-name>ejb/GroupProfileManager</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.bea.p13n.usermgmt.profile.ProfileManagerHome</home>
<remote>com.bea.p13n.usermgmt.profile.ProfileManager</remote>
<ejb-link>GroupProfileManager</ejb-link>
</ejb-ref>
<ejb-ref>
<ejb-ref-name>ejb/UserProfileManager</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.bea.p13n.usermgmt.profile.ProfileManagerHome</home>
<remote>com.bea.p13n.usermgmt.profile.ProfileManager</remote>
<ejb-link>UserProfileManager</ejb-link>
</ejb-ref>
</session>
<!-- User Profile Manager-->
<session>
<ejb-name>UserProfileManager</ejb-name>
<home>com.bea.p13n.usermgmt.profile.ProfileManagerHome</home>
<remote>com.bea.p13n.usermgmt.profile.ProfileManager</remote>
<ejb-class>com.bea.p13n.usermgmt.profile.internal.UserProfileManagerImpl</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<!-- map all properties in property set ldap to ldap server -->
<env-entry>
<env-entry-name>PropertyMapping/ldap</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>LdapPropertyManager</env-entry-value>
</env-entry>
<!-- map all properties in corporateProfile property set to CorporateProfileManager -->
<env-entry>
<env-entry-name>PropertyMapping/corporateProfile</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>CorporateProfileManager</env-entry-value>
</env-entry>
<!-- The UserProfileManager used programatic security to allow
users to modify their own data (where username == profileName)
or anyone in one of these (administrative) roles.
Used in the methods: deleteProfile, removeProperty,
removeSuccessor, setProperty, and setSuccessor.
Other methods can be protected using declarative security.
Should at least include the WebLogic Admin role, if left empty
or mapped to "empty" roles, then noone will be able to admin
user profiles.
Each role listed here should also have a security-role-ref entry below --> -
Error while trying to edit in Bea Portal Administration Content Management
Hi,
we are exploring the weblogic portal administration 9.2 and we encounter an exception when editing a content in the Content Management feature. We use the weblogic default workflow, we create a user attached to a group, add that group to a role, then delegate the edit and view capability of a content node in the Content Management to that role, we login using the respective user, check out the content, try to edit the property but then the exception occurs.
It says "A Repository Exception was thrown: User does not have view privileges on the node"
the detail exceptio on the property page was:
"javax.servlet.jsp.JspException: Could not find a node at the key: nodeReqAttr
at com.bea.jsptools.content.node.ViewPropertyTag.doStartTag(ViewPropertiesTag.java374)
at jsp_servlet._contenet._node._nodeselected._properties._listpropertiescheckout._jsp_tag46 ...."
Could u help us what step we went wrong, because we previously try this in the WLP 8.1.4 portal administration the exact same step but never encounter this error before.
And is there anyway I can atteched screenshots to help better explain this problem?
Thank you for your help.Hi,
You have to set your activex control properly. then only edit locally in KM will work.
Also check the below wiki
https://www.sdn.sap.com/irj/scn/wiki?path=/display/KMC/HowtotroubleshootproblemswithLocalEditing
Hope that helps
Raghu -
User Property Sets / UUP -- not showing up
Hi. We are having problems getting any portal user property sets to show up in any environment other than our dev boxes. We are running 10.2. Our environment consists of our dev workstations, a dev server in 'development' mode, a stage server in 'production' mode, and a production server in 'production' mode.
On our development boxes, we see the following property sets from the portal admin:
Groupspace
CustomerProperties
BusinessUserProperties
BusinessEmployeeProperties
The latter 2 are our UUP property sets. As I said, these sets appear on our dev boxes, but from what I understand, that is expected because the EAR is exploded when published on a dev box.
Consultants developed much of this portal application for us, including the uup property sets, and they are backing away and not offering any help in this matter. They simply said to use the propegation tools. I used the propegation tool to merge my dev box inventory and our development server inventory, and the differences did indicate the 4 property sets listed above. I selected to add only those 4 property sets to the dev server, exported the merged inventory, and exported it to our dev server with no errors. However, still no property sets showed up. I then pulled down another inventory from our dev server, and it indicated that it still did not have the property sets. I repeated this cycle once more to no avail.
Things that are confusing to me are:
1) The 'Groupspace' and 'CustomerProperties' sets appear to be portal default property sets. Wouldn't they be expected to exist in all environments?
2) I thought that I read if the server you are deploying the EAR to is in 'development' mode, then the property sets should be moved over when deploying the EAR normally. I may be wrong about this as I am on information overload trying to learn these portal aspects under a time crunch.
3) Where in the portal database are the propertysets themselved defined? I can see the 'PROPERTY_KEY' and 'PROPERTY_VALUE' tables which handle storing the user properties themselves, but I don't see any tables which would define a property set.
Thanks in advance for any insights to this issue. It is making my week really tough.1st, I recommend posting in the WebLogic Portal forum:
WebLogic Portal
2ndly, I recommend opening a support case to get assistance if you are under a time crunch. -
AD security group as FIM Portal administrator
Hi Gurus
i have a question. I want to add an AD Security group in FIM for the users of the group to be the FIM portal administrator. I believe to do that I need to sync the group using a management agent, and then add that group to the Sharepoint administrator group.
Is this correct? If it's not then where can I find a procedure to make the members of the security group which is in an OU to be the administrators of the FIM portal? I don't want to sync the whole OU but only one group within the OU as there are other groups
within the OU which I do not want to have admin rights to the portal.
Is there a way I can achieve what I am trying to do? I haven't found any documentation to do it. As I am very new to this I apologize if the question sounds silly.
Any help will be greatly appreciated. Thanks in advance.
Regards,Hi Paul, Dave and Steve
Thank you all for all your valuable inputs. I have successfully resolved the issue. This is what I did.
I observed from the metaverse search in the Synchronization tool that after running the full synchronization on the ADMA following the synchronization order specified by Microsoft, the amount of objects was doubling. There were about 180 objects to begin
with and it doubled. I checked a number of solutions online which asked me to delete the object from the connector. However considering the number of objects that would have been a lot of work. So I decided to delete the users from the FIM portal and manually
run the sync again. I got this script from Carol Wapshere:
http://social.technet.microsoft.com/Forums/en-US/58796732-a605-4f22-8c27-17ea4f0968fe/using-powershell-to-delete-all-users-from-the-portal?forum=ilm2
The good thing about the script is that a few users can be added to the Administrator set in the portal and the script will not delete it. That way selective objects can be protected and not all access to the portal is lost. After that I ran the syncs in
order, added the users to the Admin set and it all worked fine. I know it is a bit of a sledgehammer approach but I believed that might be the best under current circumstances.
Thank you all again for taking your time out and answering my question. You have been great help!!
Regards, -
Error while trying to get Property Set Management in 3.2
Hi,
Using WLS 5.1 with sp6 and using WLCS 3.2. When I go into the
Administration Tools Home Page and click on the Property Set Management
I get the following errors. I just installed WLCS 3.2 and I'm trying
to run the Tour by "adding properties within a property set".
Wed Mar 14 09:35:26 MST 2001:<E> <WebAppServletContext-tools> Servlet
failed with Exception
weblogic.servlet.jsp.JspException: (line -1): Error in tag library at:
'wl': For tag 'repeat', cannot load extra info class
'weblogicx.jsp.tags.RepeatTagInfo'
at
weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
at
weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:201)
at
weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:146)
at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
at
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3739)
at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3495)
at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3356)
at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1694)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1535)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1425)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:825)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
at
weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:265)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:180)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:181)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:118)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:154)
at
com.beasys.commerce.foundation.flow.ServletDestinationHandler.handleDestination(ServletDestinationHandler.java:51)
at
com.beasys.commerce.foundation.flow.FlowManager.service(FlowManager.java:448)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:123)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:761)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:708)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)Fixed the problem I didn't have the weblogic-tags-510.jar from WLS 5.1 service pack 6.
Letty Campbell wrote:
Hi,
Using WLS 5.1 with sp6 and using WLCS 3.2. When I go into the
Administration Tools Home Page and click on the Property Set Management
I get the following errors. I just installed WLCS 3.2 and I'm trying
to run the Tour by "adding properties within a property set".
Wed Mar 14 09:35:26 MST 2001:<E> <WebAppServletContext-tools> Servlet
failed with Exception
weblogic.servlet.jsp.JspException: (line -1): Error in tag library at:
'wl': For tag 'repeat', cannot load extra info class
'weblogicx.jsp.tags.RepeatTagInfo'
at
weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
at
weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:201)
at
weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:146)
at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:87)
at
weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3739)
at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3495)
at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3356)
at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1694)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1535)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1425)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:825)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:116)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:97)
at
weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:265)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:180)
at
weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:181)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:118)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:154)
at
com.beasys.commerce.foundation.flow.ServletDestinationHandler.handleDestination(ServletDestinationHandler.java:51)
at
com.beasys.commerce.foundation.flow.FlowManager.service(FlowManager.java:448)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:123)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:761)
at
weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:708)
at
weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
at
weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
at
weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135) -
Cannot attach User property set within a Rule set
Hi,
I cannot attach a user property set within a rule set. When i create a new
rule set in the tools it doesnt give me a field to attach a User property
set to a rule set. I dont get this.
I am using WLCS 3.2, cloudscape, WL 5.1 SP 6, Win2000.
Any help wud be greatly appreciated.Hello Kapil,
This is a good thing. Allow me to convince you. Prior to WLCS 2.0.1 sp1,
each rule set required that a property set be associated with it. Rules in
that rule set could only use properties from that property set. You could not
write a rule that used properties from multiple property sets. Therefore, it
was impossible to combine user/group, session, and request properties in
rules. It is a good thing that you don't have to associate a property set
with the rule set anymore.
kapil wrote:
Hi,
I cannot attach a user property set within a rule set. When i create a new
rule set in the tools it doesnt give me a field to attach a User property
set to a rule set. I dont get this.
I am using WLCS 3.2, cloudscape, WL 5.1 SP 6, Win2000.
Any help wud be greatly appreciated.--
Ture Hoefner
BEA Systems, Inc.
2590 Pearl St.
Suite 110
Boulder, CO 80302
www.bea.com -
How do I make a new property that I added to a property set show up in the portal
admin tool when I am editing a user?
I was able to do this in my dev environment. After that worked, I updated my EAR
file with the modified property set file (the .usr file) and redeployed the app
in my QA environment. When I go into the admin tool and try to edit the property
set for a user (in QA), I still don't see the new property. Is there anything
else I need to do? Any help would be appreciated. Thanks
Also, is there a way to add new properties to a property set thru the portal admin
tool? Or is editing the file thru workshop the only way? Thankshttp://e-docs.bea.com/wlp/docs81/deploy/deploy.html#1003633 for the
first problem. Since you have a compressed EAR, you'll need to flush the
JDBC repository to have it pick up the files from the EAR.
You can only change possible and default values through the admin portal.
Greg
Ramesh wrote:
How do I make a new property that I added to a property set show up in the portal
admin tool when I am editing a user?
I was able to do this in my dev environment. After that worked, I updated my EAR
file with the modified property set file (the .usr file) and redeployed the app
in my QA environment. When I go into the admin tool and try to edit the property
set for a user (in QA), I still don't see the new property. Is there anything
else I need to do? Any help would be appreciated. Thanks
Also, is there a way to add new properties to a property set thru the portal admin
tool? Or is editing the file thru workshop the only way? Thanks -
How to Disable Library Services on Portal Administration Console?
How do we set the Library Services Enabled to false on Portal Administration Console?
ThanksThanks for the response.
Is it not possible to disable it in the config file (content-config.xml)?
not sure if this is related to that: [ http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/cm/deploydescriptorCM.html#wp1074440|http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/cm/deploydescriptorCM.html#wp1074440]
Maybe you are looking for
-
How do I sync mail accounts if I didn't choose that option during setup?
Is there some way to retroactively choose to sync mail accounts with iTunes after the phone has already been setup (and I chose not to do it at setup)? I looked around in iTunes and couldn't find a setting. I'm having problems setting up one of my IM
-
From XML to insert records in a database
I want to ask anyone out there for advice about parsing an XML document preparing its records for insertion into a database table. Below is not a very practical example but gives the gist of what I want to do. <?xml version="1.0"?> <MESSAGE> <CONTACT
-
SAP GRC 5.3 CUP: Approver Determinator "Super Access Owner"
Hi, when configuring a stage, a standard approver determinator called "Super Access Owner" could be selected.My question is where to specify the Super Access Owner in SAP GRC CUP? In the Config Guide of SAP GRC AC 5.3 a hint explains on page 145 "If
-
I have successfully installed ROracle.1.1-4 under R 2.15.0, Windows 32bit, my configuration is detailed here: Re: ROracle 1.1-4 install failure for R 64 only: R version 2.15.0, Rtools215 I am able to connect to my Oracle database from within R and t
-
How to use Mapquest GPS on iPhone?
I know this is is not an Apple App, but I am truing to figure out how do I save MapQuest routes on iPhone 4? After looking for over a month how to make it work, I gave up and came to this place hoping to get an answer. I found that only way to do it