February 2015 - overlord-issues - Jboss List Archives

[JBoss JIRA] (ARTIF-202) The not() function doesn't quite work with relationships

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-202?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-202: ----------------------------------- Eric's example currently does: {code} SELECT artifact1.* FROM [sramp:baseArtifactType] AS artifact1 INNER JOIN [sramp:relationship] AS relationship2 ON ISCHILDNODE(relationship2,artifact1) WHERE (artifact1.[sramp:artifactType] = 'Part' AND (NOT (relationship2.[sramp:relationshipType] = 'element') AND ISDESCENDANTNODE([sramp:baseArtifactType],'/s-ramp'))) {code} > The not() function doesn't quite work with relationships > -------------------------------------------------------- > > Key: ARTIF-202 > URL: https://issues.jboss.org/browse/ARTIF-202 > Project: Artificer > Issue Type: Bug > Reporter: Eric Wittmann > Assignee: Brett Meyer > Priority: Minor > Fix For: 1.0.0.Alpha1 > > > The not() function works well with properties, but not quite with relationships. An example of what doesn't work: > /s-ramp/wsdl/Part[not(element)] > That should return all Parts that do *not* have an element relationship. Since relationships are found by doing a JOIN, it's actually tricky to invert. Right now I think the query engine will produce something that would return all Parts that have some *other* relationship - but it won't return Parts without any relationships at all. I'm not sure how to do the latter other than by using an IN with a subquery (which is supported by ModeShape but is non-standard). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-203) Ensure the not() function works with classifiers

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-203?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-203: ----------------------------------- Appears to be working after the query parser was re-worked. However, committing some beefed-up tests. > Ensure the not() function works with classifiers > ------------------------------------------------ > > Key: ARTIF-203 > URL: https://issues.jboss.org/browse/ARTIF-203 > Project: Artificer > Issue Type: Bug > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 1.0.0.Alpha1 > > > Not sure if this is working or not (I expect not): > /s-ramp/core/Document\[xp2:not(classifiedByAnyOf(., '#blue', '#red'))\] > It shouldn't be too hard to support - but not sure if it's working ATM. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-203) Ensure the not() function works with classifiers

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-203?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-203: ------------------------------ Description: Not sure if this is working or not (I expect not): /s-ramp/core/Document\[xp2:not(classifiedByAnyOf(., '#blue', '#red'))\] It shouldn't be too hard to support - but not sure if it's working ATM. was: Not sure if this is working or not (I expect not): /s-ramp/core/Document[xp2:not(classifiedByAnyOf(., '#blue', '#red'))] It shouldn't be too hard to support - but not sure if it's working ATM. > Ensure the not() function works with classifiers > ------------------------------------------------ > > Key: ARTIF-203 > URL: https://issues.jboss.org/browse/ARTIF-203 > Project: Artificer > Issue Type: Bug > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 1.0.0.Alpha1 > > > Not sure if this is working or not (I expect not): > /s-ramp/core/Document\[xp2:not(classifiedByAnyOf(., '#blue', '#red'))\] > It shouldn't be too hard to support - but not sure if it's working ATM. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-642) Create a json-schemas for the json files used in RTGov (EPN, IP, AV, ACS)

by Jorge Morales (JIRA)

Jorge Morales created RTGOV-642: ----------------------------------- Summary: Create a json-schemas for the json files used in RTGov (EPN, IP, AV, ACS) Key: RTGOV-642 URL: https://issues.jboss.org/browse/RTGOV-642 Project: RTGov (Run Time Governance) Issue Type: Feature Request Reporter: Jorge Morales Assignee: Gary Brown If there are json-schemas for the json files used in RTGov (AV, EPN, ACS, and IP) it should be easier to use them. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-584) Test and document Nexus Proxy support

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-584?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-584: ----------------------------------- https://developer.jboss.org/message/917685 > Test and document Nexus Proxy support > ------------------------------------- > > Key: ARTIF-584 > URL: https://issues.jboss.org/browse/ARTIF-584 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Once the Facade is "finished", verify that it can be used as a Nexus Proxy. Then, document this use case: "gain S-RAMP without losing your existing enterprise repo!" -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-584) Test and document Nexus Proxy support

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-584?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on ARTIF-584: ----------------------------------- https://github.com/brmeyer/s-ramp/tree/nexus > Test and document Nexus Proxy support > ------------------------------------- > > Key: ARTIF-584 > URL: https://issues.jboss.org/browse/ARTIF-584 > Project: Artificer > Issue Type: Sub-task > Reporter: Brett Meyer > Fix For: 1.0.0.Alpha1 > > > Once the Facade is "finished", verify that it can be used as a Nexus Proxy. Then, document this use case: "gain S-RAMP without losing your existing enterprise repo!" -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[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 closed ARTIF-639. ----------------------------- Resolution: Won't Fix Not supported by Keycloak > 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, 10 months

1
0
0 / 0

[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: (was: 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 > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-506) Maven repository facade. Add extended type

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-506?page=com.atlassian.jira.plugin.... ] Brett Meyer closed ARTIF-506. ----------------------------- Resolution: Won't Fix For now, rejecting this. However, note that some semblance of this is now available in the Maven facade. When you configure Artificer as a repo in your pom, you can add "?artifactType=FooType" to the URL. This sets the type for the *primary* artifact only. Since this entire discussion revolves around primary types, I'm calling that "good enough" for now. I'd rather keep it to something simple, rather than require users to add custom metadata (and have Artificer parse it). > Maven repository facade. Add extended type > ------------------------------------------ > > Key: ARTIF-506 > URL: https://issues.jboss.org/browse/ARTIF-506 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: Brett Meyer > > It is necessary to add the possibility of setting a different s-ramp type. > By default right now the s-ramp type is Java Archive. For uploading switchyard applications it is necessary to add a mechanism to set the extended type. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARTIF-506) Maven repository facade. Add extended type

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/ARTIF-506?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-506: ------------------------------ Fix Version/s: (was: 1.0.0.Alpha1) > Maven repository facade. Add extended type > ------------------------------------------ > > Key: ARTIF-506 > URL: https://issues.jboss.org/browse/ARTIF-506 > Project: Artificer > Issue Type: Sub-task > Reporter: David virgil naranjo > Assignee: Brett Meyer > > It is necessary to add the possibility of setting a different s-ramp type. > By default right now the s-ramp type is Java Archive. For uploading switchyard applications it is necessary to add a mechanism to set the extended type. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues February 2015