[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-699) Allow packages to define their own default interceptors
7:44 p.m.
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: http://jira.jboss.com/jira/browse/JBSEAM-699
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Priority: Critical
Fix For: 1.2.0.BETA1
Currently, all default interceptors get listed out in an ugly method on Component. This is
extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:25 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-699) Allow packages to define their own default interceptors
[ http://jira.jboss.com/jira/browse/JBSEAM-699?page=comments#action_12362184 ]
Chris Rudd commented on JBSEAM-699:
-----------------------------------
The current initDefaultInterceptors attempts to do some "smart" processing only
adding interceptors that are needed (based on the classes layout / metadata).
What if the @Interceptor that can be applied to class level annotations was also appied to
method and field level annotations.
I.e. Currently ant class level annotation that itself is annotated with @Interceptor (
<interceptor> ) will instruct the component to install the interceptor
<interceptor>.
If the same is applied to fields/methods than the @Restirct could be modified to be :
@Target({TYPE,METHOD})
@Documented
@Retention(RUNTIME)
@Inherited
@Interceptor(SecurityInterceptor.class)
public @interface Restrict
{
/**
* Restrictions may be expressed using any EL expression, and usually
* include the use of s:hasRole(...) or s:hasPermission(..., /..).
*
* @return An EL expression that defines the restriction to be checked
*/
String value() default "";
}
Then applied like so :
@Name("foo")
public class Foo
{
@Restrict
public void doIt() { }
}
@Name("bar")
public class Bar
{
public void doIt() { }
}
Under this new scenario the component infrastructure would isntall the SecurityInterceptor
for component foo but not for bar.
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: http://jira.jboss.com/jira/browse/JBSEAM-699
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Priority: Critical
Fix For: 1.3.0.BETA1
Currently, all default interceptors get listed out in an ugly method on Component. This
is extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:19 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-699) Allow packages to define their own default interceptors
[ http://jira.jboss.com/jira/browse/JBSEAM-699?page=all ]
Gavin King updated JBSEAM-699:
------------------------------
Fix Version/s: 1.3.1.BETA1
(was: 1.3.0.ALPHA)
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: http://jira.jboss.com/jira/browse/JBSEAM-699
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Priority: Critical
Fix For: 1.3.1.BETA1
Currently, all default interceptors get listed out in an ugly method on Component. This
is extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:55 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-699) Allow packages to define their own default interceptors
[ http://jira.jboss.com/jira/browse/JBSEAM-699?page=all ]
Gavin King updated JBSEAM-699:
------------------------------
Fix Version/s: 1.3.0.GA
(was: 1.3.0.BETA1)
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: http://jira.jboss.com/jira/browse/JBSEAM-699
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Priority: Critical
Fix For: 1.3.0.GA
Currently, all default interceptors get listed out in an ugly method on Component. This
is extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:59 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-699) Allow packages to define their own default interceptors
[ http://jira.jboss.com/jira/browse/JBSEAM-699?page=all ]
Gavin King updated JBSEAM-699:
------------------------------
Fix Version/s: 1.3.1.GA
(was: 1.3.0.GA)
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: http://jira.jboss.com/jira/browse/JBSEAM-699
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Priority: Critical
Fix For: 1.3.1.GA
Currently, all default interceptors get listed out in an ugly method on Component. This
is extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:03 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-699) Allow packages to define their own default interceptors
[ http://jira.jboss.com/jira/browse/JBSEAM-699?page=all ]
Gavin King updated JBSEAM-699:
------------------------------
Fix Version/s: 1.3.0.BETA2
(was: 1.3.1.GA)
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: http://jira.jboss.com/jira/browse/JBSEAM-699
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Priority: Critical
Fix For: 1.3.0.BETA2
Currently, all default interceptors get listed out in an ugly method on Component. This
is extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:37 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-699) Allow packages to define their own default interceptors
[ http://jira.jboss.com/jira/browse/JBSEAM-699?page=comments#action_12366913 ]
Luke Maurer commented on JBSEAM-699:
------------------------------------
I'd appreciate this, too - I've got a @Trace annotation that installs an
interceptor to spit out log messages on method entry and exit. It's awkward to use if
you only want to trace one method, because the annotation has to appear on the class.
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: http://jira.jboss.com/jira/browse/JBSEAM-699
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Priority: Critical
Fix For: 1.3.0.BETA2
Currently, all default interceptors get listed out in an ugly method on Component. This
is extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:03 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-699) Allow packages to define their own default interceptors
[ http://jira.jboss.com/jira/browse/JBSEAM-699?page=all ]
Gavin King updated JBSEAM-699:
------------------------------
Fix Version/s: 2.0.0.GA
(was: 2.0.0.CR1)
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: http://jira.jboss.com/jira/browse/JBSEAM-699
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Priority: Critical
Fix For: 2.0.0.GA
Currently, all default interceptors get listed out in an ugly method on Component. This
is extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:27 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-699) Allow packages to define their own default interceptors
[ http://jira.jboss.com/jira/browse/JBSEAM-699?page=all ]
Norman Richards updated JBSEAM-699:
-----------------------------------
Fix Version/s: 2.0.1.GA
(was: 2.0.0.GA)
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: http://jira.jboss.com/jira/browse/JBSEAM-699
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Priority: Critical
Fix For: 2.0.1.GA
Currently, all default interceptors get listed out in an ugly method on Component. This
is extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:41 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-699) Allow packages to define their own default interceptors
[ http://jira.jboss.com/jira/browse/JBSEAM-699?page=all ]
Pete Muir updated JBSEAM-699:
-----------------------------
Fix Version/s: 2.0.x
(was: 2.0.1.GA)
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: http://jira.jboss.com/jira/browse/JBSEAM-699
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Priority: Critical
Fix For: 2.0.x
Currently, all default interceptors get listed out in an ugly method on Component. This
is extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:10 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-699) Allow packages to define their own default interceptors
[ http://jira.jboss.com/jira/browse/JBSEAM-699?page=all ]
Pete Muir updated JBSEAM-699:
-----------------------------
Fix Version/s: 2.1.0.GA
(was: 2.0.x)
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: http://jira.jboss.com/jira/browse/JBSEAM-699
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Gavin King
Priority: Critical
Fix For: 2.1.0.GA
Currently, all default interceptors get listed out in an ugly method on Component. This
is extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:55 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Assigned: (JBSEAM-699) Allow packages to define their own default interceptors
[ http://jira.jboss.com/jira/browse/JBSEAM-699?page=all ]
Pete Muir reassigned JBSEAM-699:
--------------------------------
Assignee: Pete Muir (was: Gavin King)
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: http://jira.jboss.com/jira/browse/JBSEAM-699
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Pete Muir
Priority: Critical
Fix For: 2.1.0.GA
Currently, all default interceptors get listed out in an ugly method on Component. This
is extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:59 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-699) Allow packages to define their own default interceptors
[ http://jira.jboss.com/jira/browse/JBSEAM-699?page=all ]
Norman Richards updated JBSEAM-699:
-----------------------------------
Fix Version/s: 2.1.0.GA
(was: 2.1.0.A1)
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: http://jira.jboss.com/jira/browse/JBSEAM-699
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Pete Muir
Priority: Critical
Fix For: 2.1.0.GA
Currently, all default interceptors get listed out in an ugly method on Component. This
is extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:28 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-699) Allow packages to define their own default interceptors
[ http://jira.jboss.com/jira/browse/JBSEAM-699?page=all ]
Pete Muir updated JBSEAM-699:
-----------------------------
Fix Version/s: 2.1.0.GA
(was: 2.1.0.BETA1)
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: http://jira.jboss.com/jira/browse/JBSEAM-699
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Pete Muir
Priority: Critical
Fix For: 2.1.0.GA
Currently, all default interceptors get listed out in an ugly method on Component. This
is extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:31 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-699) Allow packages to define their own default interceptors
[ http://jira.jboss.com/jira/browse/JBSEAM-699?page=all ]
Pete Muir updated JBSEAM-699:
-----------------------------
Fix Version/s: 2.1.0.BETA2
(was: 2.1.0.GA)
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: http://jira.jboss.com/jira/browse/JBSEAM-699
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assigned To: Pete Muir
Priority: Critical
Fix For: 2.1.0.BETA2
Currently, all default interceptors get listed out in an ugly method on Component. This
is extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:12 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-699) Allow packages to define their own default interceptors
[ http://jira.jboss.com/jira/browse/JBSEAM-699?page=all ]
Pete Muir updated JBSEAM-699:
-----------------------------
Assignee: (was: Pete Muir)
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: http://jira.jboss.com/jira/browse/JBSEAM-699
Project: Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Priority: Critical
Fix For: 2.1.0.BETA2
Currently, all default interceptors get listed out in an ugly method on Component. This
is extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:52 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-699) Allow packages to define their own default interceptors
[
https://jira.jboss.org/jira/browse/JBSEAM-699?page=com.atlassian.jira.plu...
]
Pete Muir commented on JBSEAM-699:
----------------------------------
This should be fairly easy now, just need a way of configuring it.
To actually add an interceptor
Init.instance().getInterceptors().add(interceptorClassName);
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: https://jira.jboss.org/jira/browse/JBSEAM-699
Project: Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Priority: Critical
Fix For: The future
Currently, all default interceptors get listed out in an ugly method on Component. This
is extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:49 a.m.
New subject: [JBoss JIRA] Closed: (JBSEAM-699) Allow packages to define their own default interceptors
[
https://jira.jboss.org/jira/browse/JBSEAM-699?page=com.atlassian.jira.plu...
]
Pete Muir closed JBSEAM-699.
----------------------------
Fix Version/s: (was: The future)
Resolution: Out of Date
Assignee: Pete Muir
Not relevant to CDI interceptors
Allow packages to define their own default interceptors
-------------------------------------------------------
Key: JBSEAM-699
URL: https://jira.jboss.org/jira/browse/JBSEAM-699
Project: Seam
Issue Type: Feature Request
Components: Core
Reporter: Gavin King
Assignee: Pete Muir
Priority: Critical
Currently, all default interceptors get listed out in an ugly method on Component. This
is extremely non-extensible. We need some way to externalize that code to the package that
needs the interceptor. This would let us split out security to its own jar, for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5232
days inactive
6325
days old
17 comments
6 participants
participants (6)
-
Chris Rudd (JIRA) -
Gavin King (JIRA) -
Gavin King (JIRA)
-
Luke Maurer (JIRA)
-
Norman Richards (JIRA)
-
Pete Muir (JIRA)