[JBoss JIRA] (ARTIF-641) Disable Auditing by default
by Brett Meyer (JIRA)
Brett Meyer created ARTIF-641:
---------------------------------
Summary: Disable Auditing by default
Key: ARTIF-641
URL: https://issues.jboss.org/browse/ARTIF-641
Project: Artificer
Issue Type: Sub-task
Reporter: Brett Meyer
Assignee: Brett Meyer
Profiling shows auditing to be somewhat of a CPU hotspot (in addition to creating artifact child nodes). Disable by default.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (ARTIF-640) Disable JMS support by default
by Brett Meyer (JIRA)
Brett Meyer created ARTIF-640:
---------------------------------
Summary: Disable JMS support by default
Key: ARTIF-640
URL: https://issues.jboss.org/browse/ARTIF-640
Project: Artificer
Issue Type: Sub-task
Reporter: Brett Meyer
Assignee: Brett Meyer
Make JMS support configurable, disabled by default. It's one of the worst hot spots in CPU profiling, mainly due to Jackson serialization.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (ARTIF-615) S-RAMP performance enhancements
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-615?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-615:
------------------------------
Description:
A parent task to track performance enhancements. These stem from JProfiler CPU and mem profiling on large amounts of:
- logical artifact uploads
- document artifact uploads (including derivation and extraction)
- artifact updates
- artifact content updates
- artifact deletes
- queries
Minor fixes will be committed under this ticket. More complex issues will be sub-tasks.
was:
A parent task to track performance enhancements.
Discussion: https://developer.jboss.org/message/910254
> S-RAMP performance enhancements
> -------------------------------
>
> Key: ARTIF-615
> URL: https://issues.jboss.org/browse/ARTIF-615
> Project: Artificer
> Issue Type: Enhancement
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 1.0.0.Alpha1
>
>
> A parent task to track performance enhancements. These stem from JProfiler CPU and mem profiling on large amounts of:
> - logical artifact uploads
> - document artifact uploads (including derivation and extraction)
> - artifact updates
> - artifact content updates
> - artifact deletes
> - queries
> Minor fixes will be committed under this ticket. More complex issues will be sub-tasks.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (ARTIF-639) Protect EJB with Keycloak
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-639?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-639:
------------------------------
Fix Version/s: 1.0.0.Alpha1
> Protect EJB with Keycloak
> -------------------------
>
> Key: ARTIF-639
> URL: https://issues.jboss.org/browse/ARTIF-639
> Project: Artificer
> Issue Type: Enhancement
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 1.0.0.Alpha1
>
>
> ARTIF-638 created EJBs, but each bean includes a #login(username, password) call. That call results in a SimpleCredentials provided to ModeShape. This works well enough, but requires a separate Wildfly/EAP user be created. It would be better to protect the EJBs with Keycloak and authenticate that way.
> Could something similar be accomplished for JMS, removing the need for a Wildfly/EAP user altogether?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (ARTIF-639) Protect EJB with Keycloak
by Brett Meyer (JIRA)
Brett Meyer created ARTIF-639:
---------------------------------
Summary: Protect EJB with Keycloak
Key: ARTIF-639
URL: https://issues.jboss.org/browse/ARTIF-639
Project: Artificer
Issue Type: Enhancement
Reporter: Brett Meyer
Assignee: Brett Meyer
ARTIF-638 created EJBs, but each bean includes a #login(username, password) call. That call results in a SimpleCredentials provided to ModeShape. This works well enough, but requires a separate Wildfly/EAP user be created. It would be better to protect the EJBs with Keycloak and authenticate that way.
Could something similar be accomplished for JMS, removing the need for a Wildfly/EAP user altogether?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months
[JBoss JIRA] (ARTIF-638) Support interacting with Artificer through EJB
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/ARTIF-638?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated ARTIF-638:
------------------------------
Description: For better integration with other apps (especially Hawkular), support interacting with Artificer through EJB, removing the need to hit its REST services. (was: For better integration with other apps (especially Hawkular), support embedding Artificer and removing the need to hit its REST services.)
> Support interacting with Artificer through EJB
> ----------------------------------------------
>
> Key: ARTIF-638
> URL: https://issues.jboss.org/browse/ARTIF-638
> Project: Artificer
> Issue Type: Feature Request
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
> For better integration with other apps (especially Hawkular), support interacting with Artificer through EJB, removing the need to hit its REST services.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 11 months