[JBoss AS 7 Development] - Unable to compile class for JSP
by Balaji Rathinavel
Balaji Rathinavel [http://community.jboss.org/people/gcebala] created the discussion
"Unable to compile class for JSP"
To view the discussion, visit: http://community.jboss.org/message/640061#640061
--------------------------------------------------------------
Hi,
I got the following error at run time when i use include jsp option. Any suggestion please..
19:46:05,274 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/IPTS].[jsp]] (http--127.0.0.1-8080-5) Servlet.service() for servlet jsp threw exception: org.apache.jasper.JasperException: Unable to compile class for JSP:
An error occurred at line: 4,552 in the generated java file
Syntax error, insert "}" to complete Block
An error occurred at line: 4,552 in the generated java file
Syntax error, insert "else Statement" to complete IfStatement
An error occurred at line: 4,552 in the generated java file
Syntax error, insert "}" to complete Block
An error occurred at line: 4,552 in the generated java file
Syntax error, insert "while ( Expression ) ;" to complete DoStatement
Stacktrace:
at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:92) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:446) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:340) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:607) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:312) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:734) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:639) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:576) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.jsp.jsp.projectManagement.IPTS_005fTeamManagement_jsp._jspService(IPTS_005fTeamManagement_jsp.java:693)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:734) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:541) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:479) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:407) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069) [struts.jar:]
at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:274) [struts.jar:]
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455) [struts.jar:]
at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.java:320) [struts.jar:]
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279) [struts.jar:]
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482) [struts.jar:]
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507) [struts.jar:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:734) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:541) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:479) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:407) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069) [struts.jar:]
at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:274) [struts.jar:]
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455) [struts.jar:]
at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.java:320) [struts.jar:]
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279) [struts.jar:]
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482) [struts.jar:]
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507) [struts.jar:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at com.caritor.ipts.utility.generic.IPTSFilter.doFilter(IPTSFilter.java:144) [classes:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final]
at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.2.Final.jar:7.0.2.Final]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.2.Final]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_14]
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/640061#640061]
Start a new discussion in JBoss AS 7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 5 months
[JBoss AS7 Development] - Spring-WS 1.5.9 on JBoss AS 7
by Andrei Biketov
Andrei Biketov [http://community.jboss.org/people/kmv2000] created the discussion
"Spring-WS 1.5.9 on JBoss AS 7"
To view the discussion, visit: http://community.jboss.org/message/633180#633180
--------------------------------------------------------------
Hi,
I'm getting the following exception trying to deploy web application that uses spring-ws 1.5.9. This application works without any problem on tomcat and other web app. servers. I suspect that there is a conflict between jdk1.6 soap implementation and jboss 7 implementatin in JAR
*jboss-saaj-api_1.3_spec-1.0.1.Final.jar*. I tried to exclude jboss module *javax.xml.soap.api* using jboss-deployment-structure.xml file
<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.0">
<deployment>
<exclusions>
<module name="javax.xml.soap.api"/>
</exclusions>
</deployment>
</jboss-deployment-structure>
but it didn't help.
Anyone had a similar problem or knows work around?
Thnaks,
Caused by: org.springframework.beans.factory.BeanCreationException: Invocation of init method failed; nested exception is org.springframework.ws.soap.SoapMessageCreationException: Could not create SAAJ MessageFactory: Unable to create message factory for SOAP: java.lang.reflect.InvocationTargetException; nested exception is javax.xml.soap.SOAPException: Unable to create message factory for SOAP: java.lang.reflect.InvocationTargetException
at org.springframework.ws.support.DefaultStrategiesHelper.instantiateBean(DefaultStrategiesHelper.java:169) [spring-ws-core-1.5.9.jar:]
at org.springframework.ws.support.DefaultStrategiesHelper.getDefaultStrategies(DefaultStrategiesHelper.java:115) [spring-ws-core-1.5.9.jar:]
at org.springframework.ws.support.DefaultStrategiesHelper.getDefaultStrategy(DefaultStrategiesHelper.java:200) [spring-ws-core-1.5.9.jar:]
at org.springframework.ws.support.DefaultStrategiesHelper.getDefaultStrategy(DefaultStrategiesHelper.java:184) [spring-ws-core-1.5.9.jar:]
at org.springframework.ws.client.core.WebServiceTemplate.initMessageFactory(WebServiceTemplate.java:315) [spring-ws-core-1.5.9.jar:]
at org.springframework.ws.client.core.WebServiceTemplate.initDefaultStrategies(WebServiceTemplate.java:304) [spring-ws-core-1.5.9.jar:]
at org.springframework.ws.client.core.WebServiceTemplate.<init>(WebServiceTemplate.java:133) [spring-ws-core-1.5.9.jar:]
at org.springframework.ws.client.core.support.WebServiceGatewaySupport.<init>(WebServiceGatewaySupport.java:65) [spring-ws-core-1.5.9.jar:]
at com.nrx.adg.messaging.gateway.xforms.SisXFromsClientGateway.<init>(SisXFromsClientGateway.java:8) [messaging-6.1_SP3-SNAPSHOT.jar:]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [:1.6.0_25]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [:1.6.0_25]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [:1.6.0_25]
at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [:1.6.0_25]
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:126) [spring-beans-3.0.6.RELEASE.jar:]
... 49 more
Caused by: org.springframework.ws.soap.SoapMessageCreationException: Could not create SAAJ MessageFactory: Unable to create message factory for SOAP: java.lang.reflect.InvocationTargetException; nested exception is javax.xml.soap.SOAPException: Unable to create message factory for SOAP: java.lang.reflect.InvocationTargetException
at org.springframework.ws.soap.saaj.SaajSoapMessageFactory.afterPropertiesSet(SaajSoapMessageFactory.java:147) [spring-ws-core-1.5.9.jar:]
at org.springframework.ws.support.DefaultStrategiesHelper.instantiateBean(DefaultStrategiesHelper.java:166) [spring-ws-core-1.5.9.jar:]
... 62 more
*Caused by: javax.xml.soap.SOAPException: Unable to create message factory for SOAP: java.lang.reflect.InvocationTargetException*
* at javax.xml.soap.MessageFactory.newInstance(MessageFactory.java:112) [jboss-saaj-api_1.3_spec-1.0.1.Final.jar:1.0.1.Final]*
* at org.springframework.ws.soap.saaj.SaajSoapMessageFactory.afterPropertiesSet(SaajSoapMessageFactory.java:133) [spring-ws-core-1.5.9.jar:]*
... 63 more
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/633180#633180]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 5 months
[JBoss AS 7 Development] - Cannot obain servlet version
by Amos Feng
Amos Feng [http://community.jboss.org/people/zhfeng] created the discussion
"Cannot obain servlet version"
To view the discussion, visit: http://community.jboss.org/message/639967#639967
--------------------------------------------------------------
Hi all,
I use arquillian to run tests of web app. They work fine before, but I get the following exception when I updated to the newest jboss-as from git.
> Caused by: java.lang.IllegalStateException: Cannot obtain servlet version
> at org.jboss.metadata.parser.servlet.WebMetaDataParser.parse(WebMetaDataParser.java:103)
> at org.jboss.metadata.parser.servlet.WebMetaDataParser.parse(WebMetaDataParser.java:54)
> at org.jboss.as.web.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:87)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:]
>
our web.xml looks like:
<!DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN http://java.sun.com/dtd/web-app_2_3.dtd>
<web-app>
<display-name>XTS Service Tests Service</display-name>
<description>XTS Service Tests Service</description>
...
</web-app>
any idea about this issue ?
Thanks,
Amos
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/639967#639967]
Start a new discussion in JBoss AS 7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 5 months
[PicketBox Development] - XACML Resource Management
by Dan Gradl
Dan Gradl [http://community.jboss.org/people/dgradl] created the discussion
"XACML Resource Management"
To view the discussion, visit: http://community.jboss.org/message/639710#639710
--------------------------------------------------------------
This is a post in a serious of discussions I am starting to get some discussion going on XACML. I led the implementation of XACML on a large scale using the original SunXACML libraries as the PDP and I am sharing some of my insights as a way to elicit some requirements on the further development of XACML. The original post and index to these discussions is http://community.jboss.org/thread/175091?tstart=0 http://community.jboss.org/thread/175091?tstart=0.
This discussion thread is to discuss managing resources as it relates to XACML. I think this is actually just a part of the policy administration point where you will be authoring the policies about who has access to what. However, there is just a few details of resource management that I would like to bring up here.
The first thing to discuss is that resources can often be organized into a hierarchy, in which you may want to grant access at the parent level in some cases or at finer grain level than others. If your resources are pages in a web application, perhaps you want to grant access to an entire section of a site, or maybe another user just has access to one page. So the resource management capability needs to be able to organize them into a hierarchy. The JBoss PDP is capable of decisioning based on hierarchy, but a way to manage it is necessary.
The other item is that many of the resources you need to protect are already defined in some other way and just need to be imported or synchronized to the central resource directory. When the application server starts up it is able identify all of the available servlets, ejbs, and other resources from deployment descriptors, rather than requiring a XACML administrator go into the PAP and create all these resources, and maintain them as they are added/removed within an application... there should be a way for the application server to communicate with the PAP to keep the resource directory synchronized. Its also possible that the resource being protected is not an application resource, but a data resource (access to an account), and this too may need synchronization (between an operational database and the resource directory).
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/639710#639710]
Start a new discussion in PicketBox Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 5 months
[PicketBox Development] - XACML Deployment
by Dan Gradl
Dan Gradl [http://community.jboss.org/people/dgradl] created the discussion
"XACML Deployment"
To view the discussion, visit: http://community.jboss.org/message/639689#639689
--------------------------------------------------------------
This is a post in a serious of discussions I am starting to get some discussion going on XACML. I led the implementation of XACML on a large scale using the original SunXACML libraries as the PDP and I am sharing some of my insights as a way to elicit some requirements on the further development of XACML. The original post and index to these discussions is http://community.jboss.org/thread/175091?tstart=0 http://community.jboss.org/thread/175091?tstart=0.
This is a thread to talk about deployment. In a simple XACML implementation you may be able to have everything (PAP, PDP, PEP) co-located in a single JVM, but as you protect more resources in a distributed system or across multiple sytems you may need a more distributed approach. You may want the capability to administer centrally, but spread the work across multiple PDPs to put them closer to their PEPs or to enable them to index/process against smaller sets of policies. You may want to separate the PDP concern from the application (and the PEP) for maintainability, or perhaps you have a non-java system that needs to execute policies using PDP as a service.
There needs to be protocols to support a variety of deployment models. Ways to distribute policies from PAP to 1 or more PDPs, ways to communicate to PDPs remotely from PEPs, etc. There is an article already about using a PDP remotely, so there may already be ways to handle some of this distributed capability.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/639689#639689]
Start a new discussion in PicketBox Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 5 months
[PicketBox Development] - XACML Administration
by Dan Gradl
Dan Gradl [http://community.jboss.org/people/dgradl] created the discussion
"XACML Administration"
To view the discussion, visit: http://community.jboss.org/message/639670#639670
--------------------------------------------------------------
This is a post in a serious of discussions I am starting to get some discussion going on XACML. I led the implementation of XACML on a large scale using the original SunXACML libraries as the PDP and I am sharing some of my insights as a way to elicit some requirements on the further development of XACML. The original post and index to these discussions is http://community.jboss.org/thread/175091?tstart=0 http://community.jboss.org/thread/175091?tstart=0.
This post is to discuss the Policy Administration Point (PAP) portion of the XACML model.
In terms of what a PAP should do it's fairly straightforward, its a tool that helps you to author and manage your policies, rules, and policy sets. If you are going to use RBAC, it probably also provides the mechanism to define the permissions associated to a role. It may possibly deal with user to role assignment or user to permission assignment, but these may also be handled by other tools.
There are several reasons why a PAP is important (and lacking in picketbox):
1. The XACML policy format provides a powerful tool to define complex policies and rules in the security space, but they can also be difficult to right. First and foremost a PAP helps to author these policies without specialized skills.
2. The same flexibility of XACML means that you can achieve the same effect several different ways. For example, you can grant access to action=execute, resource=myService, by creating a policy that target's this action/resource with an empty rule=permit; you could also have an empty target (would match everything), and a rule that looks for these values. There are advantages to doing things a certain way (targets should allow indexing and locating policies more quickly). So a PAP enables policies to come out in a predicable way that then the decision point can take advantage of in optimized performance.
3. As you scale up the number of things you protect with XACML policies... you will wind up with many many policies and just managing the sheer volume (organizing, finding them, etc.) can become unwieldy.
4. It helps with auditing/reporting
5. If your architecture calls for distributed PDPs it can aide in deplolyment
I have also observed a secondary piece of administration that is less obvious. In some of the more complex rule situations, you may have a policy and then you may have a piece of related external data that may need to be managed. For example the policy may be that a user can only access the system from their assigned terminal, the mapping of user to terminal (e.g. IP address), may be an external lookup, rather than authoring unique policies for each user. So you may need a mechanism to manage the policy rule and also a way to adminster other related data.
You may also need to consider the usability of the tool for different types of people. You may have dedicated adminstrators that author policies and manage more complex aspects, and you may have delegated adminstrators who need a simpler interface and manage a smaller subset of things.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/639670#639670]
Start a new discussion in PicketBox Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
12 years, 5 months
