May 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-177) Enable authentication for HEAD requests in s-ramp-server

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-177?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-177: -------------------------------- Fix Version/s: 0.3.0 JBPM6 Integration (was: 0.5.0 - Future) > Enable authentication for HEAD requests in s-ramp-server > -------------------------------------------------------- > > Key: SRAMP-177 > URL: https://issues.jboss.org/browse/SRAMP-177 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.0 JBPM6 Integration > > > Currently HEAD requests are allowed even without authentication information (basic auth). This was done because jBPM requires it. I have added the following issue: > https://issues.jboss.org/browse/JBPM-3967 > Once it is fixed, we can fix this issue by updating the s-ramp-server web.xml. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-176) Test ModeShape CND upgrade

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-176?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-176: -------------------------------- Fix Version/s: 0.3.0 JBPM6 Integration (was: 0.5.0 - Future) > Test ModeShape CND upgrade > -------------------------- > > Key: SRAMP-176 > URL: https://issues.jboss.org/browse/SRAMP-176 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.0 JBPM6 Integration > > > Since we're using ModeShape, we should test upgrading the CND (like a DDL upgrade in a DB). Want to make sure it works as advertised (I'm certain it will!). -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-170) Atom feeds do not work very well in exisiting clients

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-170?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-170: -------------------------------- Priority: Minor (was: Major) > Atom feeds do not work very well in exisiting clients > ----------------------------------------------------- > > Key: SRAMP-170 > URL: https://issues.jboss.org/browse/SRAMP-170 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Atom Binding > Affects Versions: 0.1.1 > Reporter: Kurt Stam > Assignee: Kurt Stam > Priority: Minor > Fix For: 0.3.0 JBPM6 Integration > > Attachments: Screen Shot 2013-03-10 at 12.08.22 PM.png > > > When using exiting atom clients our feed don't work very well. I think one should be able to follow links down into an entry for example, but the link is not populated. We should investigate why this is. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-171) Enable WSLA artifacts to be associated with a service

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-171?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-171: -------------------------------- Fix Version/s: 0.3.0 JBPM6 Integration (was: 0.2.0 Security) > Enable WSLA artifacts to be associated with a service > ----------------------------------------------------- > > Key: SRAMP-171 > URL: https://issues.jboss.org/browse/SRAMP-171 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Kurt Stam > Fix For: 0.3.0 JBPM6 Integration > > > WSLA will be used to represent the service level agreement properties related to response time and availability for a service. Therefore it should be possible to represent these documents in the repository and establish a relationship between them and the service contracts. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-170) Atom feeds do not work very well in exisiting clients

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-170?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-170: -------------------------------- Fix Version/s: 0.3.0 JBPM6 Integration (was: 0.2.0 Security) > Atom feeds do not work very well in exisiting clients > ----------------------------------------------------- > > Key: SRAMP-170 > URL: https://issues.jboss.org/browse/SRAMP-170 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Atom Binding > Affects Versions: 0.1.1 > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.3.0 JBPM6 Integration > > Attachments: Screen Shot 2013-03-10 at 12.08.22 PM.png > > > When using exiting atom clients our feed don't work very well. I think one should be able to follow links down into an entry for example, but the link is not populated. We should investigate why this is. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-167) Add support for the logical models defined in the S-RAMP spec (SOA, ServiceImpl, etc)

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-167?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-167: -------------------------------- Fix Version/s: 0.4.0 API Management (was: 0.3.0 JBPM6 Integration) > Add support for the logical models defined in the S-RAMP spec (SOA, ServiceImpl, etc) > ------------------------------------------------------------------------------------- > > Key: SRAMP-167 > URL: https://issues.jboss.org/browse/SRAMP-167 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.4.0 API Management > > > We need to make sure that we can support the logical (non-document) artifact types. The mechanism for creating them is different (there's no POST of a document). -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-163) Authorization: Role based access to S-RAMP data

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-163?page=com.atlassian.jira.plugin.... ] Kurt Stam commented on SRAMP-163: --------------------------------- http://www.day.com/specs/jcr/2.0/16_Access_Control_Management.html > Authorization: Role based access to S-RAMP data > ----------------------------------------------- > > Key: SRAMP-163 > URL: https://issues.jboss.org/browse/SRAMP-163 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0 - Future > > > Support role-based (fine-grained) access to s-ramp artifact data. The authenticated user should only see artifacts she has access to. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-163) Authorization: Role based access to S-RAMP data

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-163?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-163: -------------------------------- Fix Version/s: 0.4.0 API Management (was: 0.5.0 - Future) > Authorization: Role based access to S-RAMP data > ----------------------------------------------- > > Key: SRAMP-163 > URL: https://issues.jboss.org/browse/SRAMP-163 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.4.0 API Management > > > Support role-based (fine-grained) access to s-ramp artifact data. The authenticated user should only see artifacts she has access to. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-161) S-RAMP Client: obey endpoints found in /servicedocument

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-161?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-161: -------------------------------- Priority: Minor (was: Major) > S-RAMP Client: obey endpoints found in /servicedocument > ------------------------------------------------------- > > Key: SRAMP-161 > URL: https://issues.jboss.org/browse/SRAMP-161 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: S-RAMP API > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Priority: Minor > Fix For: 0.3.0 JBPM6 Integration > > > Currently we use the non-normative URL formats suggested in the S-RAMP Atom Binding document as presumptive endpoints for the various artifact types. Instead, the Atom API Java client should obey the endpoints it finds in the /servicedocument. This means it will *always* query that service document. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-162) Spec: allow properties to be defined on a relationship

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-162?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-162: -------------------------------- Fix Version/s: 0.5.0 - Future > Spec: allow properties to be defined on a relationship > ------------------------------------------------------ > > Key: SRAMP-162 > URL: https://issues.jboss.org/browse/SRAMP-162 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Kurt Stam > Fix For: 0.5.0 - Future > > > Not necessarily for version 1.0 of the spec, but wanted to record this as a placeholder for the requirement. > Specific use-case in mind is where a relationship between a BPMN2 choreography and a BPMN2 process model needs to describe which participant the process model represents in the choreography. > Although this particular case could be addressed simply by having the same name, there may be other artifact types (i.e. not BPMN2 process models) that represent endpoint behaviour, and need to be related to the choreography with additional context (i.e. the participant name). -- 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, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues May 2013