[JBoss JIRA] (SRAMP-502) Upgrade arquillian-tomcat-managed-7 to 1.0.0.Final
by Brett Meyer (JIRA)
Brett Meyer created SRAMP-502:
---------------------------------
Summary: Upgrade arquillian-tomcat-managed-7 to 1.0.0.Final
Key: SRAMP-502
URL: https://issues.jboss.org/browse/SRAMP-502
Project: S-RAMP
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Brett Meyer
Assignee: Brett Meyer
Once arquillian-tomcat-managed-7 1.0.0.Final is out, upgrade it in s-ramp-test. (If SRAMP-431 is not yet merged, update brmeyer's integration-test branch.)
Note that the following line can then be removed in arquillian.xml:
<property name="catalinaBase">target/apache-tomcat-7.0.54</property>
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (SRAMP-168) Create a TCK test suite
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-168?page=com.atlassian.jira.plugin.... ]
Brett Meyer edited comment on SRAMP-168 at 7/7/14 4:22 PM:
-----------------------------------------------------------
Remove the current tck from s-ramp. Create a new tck repo in Overlord (Governance/s-ramp-tck). The tck should have no dependencies on overlord whatsoever. Keep it limited to simple REST, xmlunit, xpath, etc.
was (Author: brmeyer):
Remove the current tck from s-ramp. Create a new tck repo in Overlord. The tck should have no dependencies on overlord whatsoever. Keep it limited to simple REST, xmlunit, xpath, etc.
> Create a TCK test suite
> -----------------------
>
> Key: SRAMP-168
> URL: https://issues.jboss.org/browse/SRAMP-168
> Project: S-RAMP
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Distro
> Reporter: Kurt Stam
> Assignee: Brett Meyer
> Fix For: 0.6.0
>
>
> Adding a Technical Compatibility Kit.
> - add examples from spec docs
> - add tests to validate the implementation adheres to the spec
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (SRAMP-168) Create a TCK test suite
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-168?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-168:
-----------------------------------
Remove the current tck from s-ramp. Create a new tck repo in Overlord. The tck should have no dependencies on overlord whatsoever. Keep it limited to simple REST, xmlunit, xpath, etc.
> Create a TCK test suite
> -----------------------
>
> Key: SRAMP-168
> URL: https://issues.jboss.org/browse/SRAMP-168
> Project: S-RAMP
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Distro
> Reporter: Kurt Stam
> Assignee: Brett Meyer
> Fix For: 0.6.0
>
>
> Adding a Technical Compatibility Kit.
> - add examples from spec docs
> - add tests to validate the implementation adheres to the spec
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[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}
Logically I would expect S-RAMP to be configured with a default notification topic and a simple way to support multiple named queues (for each of the consumers, of which dtgov is one). A named queue should be relatively easy to create, such that the DTGov installer would add it to the S-RAMP config during DTGov install time.
{quote}
+1, that was my original intention. All topics would be predefined. Queues would be a simple list of names in the S-RAMP properties file. DTGov queue support would be "out of the box" in that the DTGov installer would automatically add a queue name to the list.
> 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
[JBoss JIRA] (SRAMP-497) Exclude s-ramp-demos-assembly from all distro zips
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-497?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-497:
-----------------------------------
[~virchete], what ZIP did you see s-ramp-demos-assembly in? I just ran a build and don't see it in s-ramp-distro/assembly's s-ramp-[VERSION].zip
> Exclude s-ramp-demos-assembly from all distro zips
> --------------------------------------------------
>
> Key: SRAMP-497
> URL: https://issues.jboss.org/browse/SRAMP-497
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Distro
> Reporter: Eric Wittmann
> Assignee: Brett Meyer
> Fix For: 0.5.0
>
>
> Reported by David (0.5.0.Beta1 Testing):
> This is not a demo, but rather a packaging of the other demos. It should be excluded from all zips. Ensure that it is.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 6 months
[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on SRAMP-433:
-------------------------------------
What are we trying to avoid by installing S-RAMP with a default "dtgov" queue? Is it hard to configure queues? Will the DTGov installer not be able to set up its own queue in S-RAMP? Just trying to understand. Logically I would expect S-RAMP to be configured with a default notification topic and a simple way to support multiple named queues (for each of the consumers, of which dtgov is one). A named queue should be relatively easy to create, such that the DTGov installer would add it to the S-RAMP config during DTGov install time.
> 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
[JBoss JIRA] (SRAMP-433) Create a proper Event producer for s-ramp
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on SRAMP-433:
-------------------------------------
One thing I would add is that I don't think queue or topic configuration should be done by storing that information in s-ramp itself. While it's true that we are moving some of the DTGov config information from dtgov.properties into S-RAMP artifacts, I don't necessarily think this config is applicable. On the S-RAMP (producer) side, there is no precedent for storing config in the repo. On the DTGov (consumer) side, it might make more sense but thus far we have only moved configuration into the S-RAMP repo for stuff that users are likely to "frequently" change (ie more than just initial app config time).
> 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