[JBoss JIRA] (WFLY-84) Jasper using wrong ProtectionDomain for compiled JSP
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-84?page=com.atlassian.jira.plugin.sy... ]
Tomaz Cerar reassigned WFLY-84:
-------------------------------
Assignee: Remy Maucherat (was: Heiko Braun)
> Jasper using wrong ProtectionDomain for compiled JSP
> ----------------------------------------------------
>
> Key: WFLY-84
> URL: https://issues.jboss.org/browse/WFLY-84
> Project: WildFly
> Issue Type: Bug
> Components: Web (JBoss Web)
> Reporter: David Lloyd
> Assignee: Remy Maucherat
> Fix For: 8.0.0.Alpha1
>
>
> Compiled JSPs loaded via JasperLoader appear to be using a different ProtectionDomain than the rest of the WAR deployment. I think it should probably be using a PD which contains the permissions from the deployment's ClassLoader, and probably the CodeSource from the deployment unit from which the JSP file originated. This will ensure that permissions set via deployment descriptor and/or the management model will take proper effect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (WFLY-377) Provide "destroy-queue" and "destroy-topic" operations to CLI
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-377?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated WFLY-377:
----------------------------------
Assignee: Alexey Loubyansky (was: Brian Stansberry)
> Provide "destroy-queue" and "destroy-topic" operations to CLI
> -------------------------------------------------------------
>
> Key: WFLY-377
> URL: https://issues.jboss.org/browse/WFLY-377
> Project: WildFly
> Issue Type: Feature Request
> Components: CLI, JMS
> Reporter: Miroslav Novak
> Assignee: Alexey Loubyansky
> Fix For: 8.0.0.Alpha1
>
>
> Operations "destroy-queue" and "destroy-topic" would destroy queue/topic with all its messages and subscriptions.
> They would be used under for example /subsystem=messaging/hornetq-server=default/jms-queue=testQueue or /subsystem=messaging/hornetq-server=default/jms-topic=testTopic.
> The goal is to provide a simple way how to get rid of those objects to administrators.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months
[JBoss JIRA] (WFLY-1048) Allow hooking into logging subsystem through Management API
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-1048?page=com.atlassian.jira.plugin.... ]
James Perkins updated WFLY-1048:
--------------------------------
Assignee: James Perkins (was: Brian Stansberry)
> Allow hooking into logging subsystem through Management API
> -----------------------------------------------------------
>
> Key: WFLY-1048
> URL: https://issues.jboss.org/browse/WFLY-1048
> Project: WildFly
> Issue Type: Feature Request
> Components: Logging
> Reporter: Ondrej Zizka
> Assignee: James Perkins
> Labels: logging
>
> Provide a way to poll log messages through the management API.
> Could be then used in the AS console. Some kind of detached window, or perhaps tab, with log, perhaps pushed through Servlet 3.2's onDataAvailable() ...
> Note that this is different from AS7-2213, which needs AS to keep some history. This doesn't.
> BTW, JBDS gets the logs through SSH, because the AS may fail booting before anything is able to hook in like this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 8 months