June 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts to be created with invalid characters in the Artifact Type

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-395: ----------------------------------------------- Rick Wagner <rwagner(a)redhat.com> changed the Status of [bug 1114732|https://bugzilla.redhat.com/show_bug.cgi?id=1114732] from NEW to MODIFIED > S-RAMP allows artifacts to be created with invalid characters in the Artifact Type > ---------------------------------------------------------------------------------- > > Key: SRAMP-395 > URL: https://issues.jboss.org/browse/SRAMP-395 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Alpha1, 0.5.0 > > > There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type. The first is via the CLI: > {code} > s-ramp:upload /path/to/file.ext "Invalid Type" > s-ramp:create "Invalid Type" "Valid Artifact Name" "Description goes here." > {code} > The other is via the s-ramp UI's Import Artifact dialog. This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up. > We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer). > For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-395) S-RAMP allows artifacts to be created with invalid characters in the Artifact Type

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-395?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated SRAMP-395: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1085429, https://bugzilla.redhat.com/show_bug.cgi?id=1114732 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1085429) > S-RAMP allows artifacts to be created with invalid characters in the Artifact Type > ---------------------------------------------------------------------------------- > > Key: SRAMP-395 > URL: https://issues.jboss.org/browse/SRAMP-395 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0.Alpha1, 0.5.0 > > > There are two ways (I believe) that users can mistakenly create artifacts with an invalid artifact type. The first is via the CLI: > {code} > s-ramp:upload /path/to/file.ext "Invalid Type" > s-ramp:create "Invalid Type" "Valid Artifact Name" "Description goes here." > {code} > The other is via the s-ramp UI's Import Artifact dialog. This dialog allows the user to type in any Artifact Type they want, which is an opportunity to mess it up. > We need to make sure we have appropriate validation of any custom Artifact Type provided by the user on the server (probably in the REST layer). > For bonus points we can add validation to the UI and CLI to prevent the request from even being made to the server unless it's valid. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ] Gary Brown commented on SRAMP-433: ---------------------------------- In general I think if a queue has been configured, then they don't want messages lost - even if DTGov was down for some time. However, as you say, the expiration time could be used to ensure the queue does not grow indefinitely. > Create a proper Event producer for s-ramp > ----------------------------------------- > > Key: SRAMP-433 > URL: https://issues.jboss.org/browse/SRAMP-433 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. > Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-433: ----------------------------------- {quote} I don't think the client should have any control - it should just be a recipient of events. SRAMP should just be configured with the relevant destinations without caring if there is a recipient - so truly decoupled. {quote} For pub/sub, of course. But for the queue(s), should S-RAMP be filling it if no client is popping off the messages? That was my thought process behind the client-driven portion. Of course, JMS message expiration times would take care of that... > Create a proper Event producer for s-ramp > ----------------------------------------- > > Key: SRAMP-433 > URL: https://issues.jboss.org/browse/SRAMP-433 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. > Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ] Gary Brown commented on SRAMP-433: ---------------------------------- I don't think the client should have any control - it should just be a recipient of events. SRAMP should just be configured with the relevant destinations without caring if there is a recipient - so truly decoupled. So its the choice of the event producer (i.e. jms queue or durable topic) that dictates the quality of service (i.e. guaranteed delivery or fire and forget). I think the format of events may not always be in our control, so we probably shouldn't fix the format - however we would hope that generally it will be xml or json. Would prefer not to deal with serialized java objects, although it would not necessarily be a show stopper. Perhaps for sramp we should just use something simple - e.g. json, and define our own format for use in cases where we do control the publisher. > Create a proper Event producer for s-ramp > ----------------------------------------- > > Key: SRAMP-433 > URL: https://issues.jboss.org/browse/SRAMP-433 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. > Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-433: ----------------------------------- Really rough design ideas and an initial JMS impl: https://github.com/brmeyer/s-ramp/commit/258b3f2bfda5799b39fd642c9b700ef6... EventProducer provides an extendable internal/external API for managing pub/sub and queues. JMSEventProducer is the first impl and demonstrates the concept. Presumably the repository will push the events and the client will be responsible for telling the module when to start and stop the individual queues. Topics and queues will need to be predefined on the platform and discovered through JNDI. I definitely need feedback on the types of events and the format (text, JSON, Serializable, etc.). > Create a proper Event producer for s-ramp > ----------------------------------------- > > Key: SRAMP-433 > URL: https://issues.jboss.org/browse/SRAMP-433 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. > Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ] Work on SRAMP-433 started by Brett Meyer. > Create a proper Event producer for s-ramp > ----------------------------------------- > > Key: SRAMP-433 > URL: https://issues.jboss.org/browse/SRAMP-433 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. > Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-413) Audit uses of BND in POMs

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-413?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-413: ----------------------------------- Hold off until 0.6. Things are finally "stable" for 0.5 and this would need tested thoroughly. > Audit uses of BND in POMs > ------------------------- > > Key: SRAMP-413 > URL: https://issues.jboss.org/browse/SRAMP-413 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.6.0 > > > In most POMs, the Felix/BND plugin usage is really explicit. See if it can be cleaned up. For the most part, BND should be able to automatically generate what's needed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-413) Audit uses of BND in POMs

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-413?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-413: ------------------------------ Fix Version/s: 0.6.0 > Audit uses of BND in POMs > ------------------------- > > Key: SRAMP-413 > URL: https://issues.jboss.org/browse/SRAMP-413 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.6.0 > > > In most POMs, the Felix/BND plugin usage is really explicit. See if it can be cleaned up. For the most part, BND should be able to automatically generate what's needed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-433: ----------------------------------- We should simultaneously support creating point-to-point queues and pub/sub. I'll still try to do it as an abstract API w/ a JMS impl. > Create a proper Event producer for s-ramp > ----------------------------------------- > > Key: SRAMP-433 > URL: https://issues.jboss.org/browse/SRAMP-433 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Currently dtgov monitors s-ramp for changes by polling. It would be more efficient if dtgov could listen for events it cared about. > Ideally we could add a listener to the s-ramp repository either at the global level or by including a filter of some kind, so we can make sure to get only a subset of the total events coming from the server. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues June 2014