9:26 p.m.
ProcessSessionBeanTest testProcessSessionBeanEvent count
--------------------------------------------------------
Key: CDITCK-215
URL: https://issues.jboss.org/browse/CDITCK-215
Project: CDI TCK
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.0.4.Final
Reporter: David Blevins
[Side note maybe there should be versions for 1.0.4.SP1 and 1.0.4.SP2]
Test:
org.jboss.jsr299.tck.tests.extensions.processBean.ProcessSessionBeanTest.testProcessSessionBeanEvent
Not sure if this is an issue or not, so filling this as a bug and not a challenge. The
test essentially has two observer methods and is asserting that only one of them are
called.
public void observeElephantSessionBean(@Observes ProcessSessionBean<Elephant>
event)
{
ProcessBeanObserver.elephantProcessSessionBean = event;
}
public void observeElephantBean(@Observes ProcessBean<Elephant> event)
{
ProcessBeanObserver.elephantProcessBeanCount++;
}
Specifically the test asserts that observeElephantSessionBean is called and that
observeElephantBean is not called.
Currently we call both because ProcessSessionBean is assignable to ProcessBean and the
generics are the same.
Is there a part of the spec that mandates only the most specific observer method is
called?
The only thing I can find is in 10.4 which says pretty clearly:
There may be arbitrarily many observer methods with the same event parameter type and
qualifiers.
A bean (or extension) may declare multiple observer methods.
Well I guess it's not that clear as it says essentially "this may happen"
rather than "this may happen...and when it does the behavior is...[all are invoked ||
only the most specific is invoked]"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:47 p.m.
New subject: [JBoss JIRA] Commented: (CDITCK-215) ProcessSessionBeanTest testProcessSessionBeanEvent count
[
https://issues.jboss.org/browse/CDITCK-215?page=com.atlassian.jira.plugin...
]
Pete Muir commented on CDITCK-215:
----------------------------------
The signature of ProcessSessionBean is
{code}
public interface ProcessSessionBean<X> extends ProcessManagedBean<Object> {
{code}
So I don't believe you would see a ProcessBean<Elephant> observer called, as
10.2.1 tells us:
{quote}
the observed event type parameter is an actual type with identical raw type to the event
type parameter, and, if the type is parameterized, the event type parameter is assignable
to the observed event type parameter according to these rules
{quote}
and Object is not assignable to Elephant.
ProcessSessionBeanTest testProcessSessionBeanEvent count
--------------------------------------------------------
Key: CDITCK-215
URL: https://issues.jboss.org/browse/CDITCK-215
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.4.Final
Reporter: David Blevins
[Side note maybe there should be versions for 1.0.4.SP1 and 1.0.4.SP2]
Test:
org.jboss.jsr299.tck.tests.extensions.processBean.ProcessSessionBeanTest.testProcessSessionBeanEvent
Not sure if this is an issue or not, so filling this as a bug and not a challenge. The
test essentially has two observer methods and is asserting that only one of them are
called.
public void observeElephantSessionBean(@Observes ProcessSessionBean<Elephant>
event)
{
ProcessBeanObserver.elephantProcessSessionBean = event;
}
public void observeElephantBean(@Observes ProcessBean<Elephant> event)
{
ProcessBeanObserver.elephantProcessBeanCount++;
}
Specifically the test asserts that observeElephantSessionBean is called and that
observeElephantBean is not called.
Currently we call both because ProcessSessionBean is assignable to ProcessBean and the
generics are the same.
Is there a part of the spec that mandates only the most specific observer method is
called?
The only thing I can find is in 10.4 which says pretty clearly:
There may be arbitrarily many observer methods with the same event parameter type and
qualifiers.
A bean (or extension) may declare multiple observer methods.
Well I guess it's not that clear as it says essentially "this may happen"
rather than "this may happen...and when it does the behavior is...[all are invoked ||
only the most specific is invoked]"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:19 a.m.
New subject: [JBoss JIRA] Commented: (CDITCK-215) ProcessSessionBeanTest testProcessSessionBeanEvent count
[
https://issues.jboss.org/browse/CDITCK-215?page=com.atlassian.jira.plugin...
]
Gurkan Erdogdu commented on CDITCK-215:
---------------------------------------
10.2
An event is delivered to an observer method if:
• The event object is assignable to the observed event type, taking type parameters into
consideration.
EvenType is ProcessSessionBean, Observed event type is ProcessBean.
ProcessSessionBean.isAssignableto(ProcessBean)
I think that for parameterized type, raw type must be identical contradicts the above
definition.
ProcessSessionBeanTest testProcessSessionBeanEvent count
--------------------------------------------------------
Key: CDITCK-215
URL: https://issues.jboss.org/browse/CDITCK-215
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.4.Final
Reporter: David Blevins
[Side note maybe there should be versions for 1.0.4.SP1 and 1.0.4.SP2]
Test:
org.jboss.jsr299.tck.tests.extensions.processBean.ProcessSessionBeanTest.testProcessSessionBeanEvent
Not sure if this is an issue or not, so filling this as a bug and not a challenge. The
test essentially has two observer methods and is asserting that only one of them are
called.
public void observeElephantSessionBean(@Observes ProcessSessionBean<Elephant>
event)
{
ProcessBeanObserver.elephantProcessSessionBean = event;
}
public void observeElephantBean(@Observes ProcessBean<Elephant> event)
{
ProcessBeanObserver.elephantProcessBeanCount++;
}
Specifically the test asserts that observeElephantSessionBean is called and that
observeElephantBean is not called.
Currently we call both because ProcessSessionBean is assignable to ProcessBean and the
generics are the same.
Is there a part of the spec that mandates only the most specific observer method is
called?
The only thing I can find is in 10.4 which says pretty clearly:
There may be arbitrarily many observer methods with the same event parameter type and
qualifiers.
A bean (or extension) may declare multiple observer methods.
Well I guess it's not that clear as it says essentially "this may happen"
rather than "this may happen...and when it does the behavior is...[all are invoked ||
only the most specific is invoked]"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1 p.m.
New subject: [JBoss JIRA] Commented: (CDITCK-215) ProcessSessionBeanTest testProcessSessionBeanEvent count
[
https://issues.jboss.org/browse/CDITCK-215?page=com.atlassian.jira.plugin...
]
Pete Muir commented on CDITCK-215:
----------------------------------
Gurkan, I don't quite understand your comment.
Regardless, an Event is fired that has the following types:
ProcessSessionBean<Elephant>, ProcessManagedBean<Object>,
ProcessBean<Object>, Object.
We have an observer, ProcessBean<Elephant>.
As the resolution rules tell us, first we look for identical raw types, which leaves with
ProcessBean<Elephant> as the observer, and ProcessBean<Object> as the event
type. Now we must apply the rule I pasted - that Object must be assignable to Elephant
(which it isn't). Therefore this observer does not match.
ProcessSessionBeanTest testProcessSessionBeanEvent count
--------------------------------------------------------
Key: CDITCK-215
URL: https://issues.jboss.org/browse/CDITCK-215
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.4.Final
Reporter: David Blevins
[Side note maybe there should be versions for 1.0.4.SP1 and 1.0.4.SP2]
Test:
org.jboss.jsr299.tck.tests.extensions.processBean.ProcessSessionBeanTest.testProcessSessionBeanEvent
Not sure if this is an issue or not, so filling this as a bug and not a challenge. The
test essentially has two observer methods and is asserting that only one of them are
called.
public void observeElephantSessionBean(@Observes ProcessSessionBean<Elephant>
event)
{
ProcessBeanObserver.elephantProcessSessionBean = event;
}
public void observeElephantBean(@Observes ProcessBean<Elephant> event)
{
ProcessBeanObserver.elephantProcessBeanCount++;
}
Specifically the test asserts that observeElephantSessionBean is called and that
observeElephantBean is not called.
Currently we call both because ProcessSessionBean is assignable to ProcessBean and the
generics are the same.
Is there a part of the spec that mandates only the most specific observer method is
called?
The only thing I can find is in 10.4 which says pretty clearly:
There may be arbitrarily many observer methods with the same event parameter type and
qualifiers.
A bean (or extension) may declare multiple observer methods.
Well I guess it's not that clear as it says essentially "this may happen"
rather than "this may happen...and when it does the behavior is...[all are invoked ||
only the most specific is invoked]"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:01 p.m.
New subject: [JBoss JIRA] Closed: (CDITCK-215) ProcessSessionBeanTest testProcessSessionBeanEvent count
[
https://issues.jboss.org/browse/CDITCK-215?page=com.atlassian.jira.plugin...
]
Pete Muir closed CDITCK-215.
----------------------------
Assignee: Pete Muir
Resolution: Rejected
Closing as rejected as the test is correct.
ProcessSessionBeanTest testProcessSessionBeanEvent count
--------------------------------------------------------
Key: CDITCK-215
URL: https://issues.jboss.org/browse/CDITCK-215
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.4.Final
Reporter: David Blevins
Assignee: Pete Muir
[Side note maybe there should be versions for 1.0.4.SP1 and 1.0.4.SP2]
Test:
org.jboss.jsr299.tck.tests.extensions.processBean.ProcessSessionBeanTest.testProcessSessionBeanEvent
Not sure if this is an issue or not, so filling this as a bug and not a challenge. The
test essentially has two observer methods and is asserting that only one of them are
called.
public void observeElephantSessionBean(@Observes ProcessSessionBean<Elephant>
event)
{
ProcessBeanObserver.elephantProcessSessionBean = event;
}
public void observeElephantBean(@Observes ProcessBean<Elephant> event)
{
ProcessBeanObserver.elephantProcessBeanCount++;
}
Specifically the test asserts that observeElephantSessionBean is called and that
observeElephantBean is not called.
Currently we call both because ProcessSessionBean is assignable to ProcessBean and the
generics are the same.
Is there a part of the spec that mandates only the most specific observer method is
called?
The only thing I can find is in 10.4 which says pretty clearly:
There may be arbitrarily many observer methods with the same event parameter type and
qualifiers.
A bean (or extension) may declare multiple observer methods.
Well I guess it's not that clear as it says essentially "this may happen"
rather than "this may happen...and when it does the behavior is...[all are invoked ||
only the most specific is invoked]"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:19 p.m.
New subject: [JBoss JIRA] Commented: (CDITCK-215) ProcessSessionBeanTest testProcessSessionBeanEvent count
[
https://issues.jboss.org/browse/CDITCK-215?page=com.atlassian.jira.plugin...
]
David Blevins commented on CDITCK-215:
--------------------------------------
Ok, I see what you're talking about. This is cool.
{code}
public class Example {
{
// will compile
Red<Foo> red = new Red<Foo>();
Color<Foo> color = red;
// will not compile
Circle<Foo> circle = new Circle<Foo>();
Shape<Foo> shape = circle;
}
public static class Foo {}
public static class Color<X> {}
public static class Red<X> extends Color<X> {}
public static class Shape<X> {}
public static class Circle<X> extends Shape<Object> {}
}
{code}
ProcessSessionBeanTest testProcessSessionBeanEvent count
--------------------------------------------------------
Key: CDITCK-215
URL: https://issues.jboss.org/browse/CDITCK-215
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.4.Final
Reporter: David Blevins
Assignee: Pete Muir
[Side note maybe there should be versions for 1.0.4.SP1 and 1.0.4.SP2]
Test:
org.jboss.jsr299.tck.tests.extensions.processBean.ProcessSessionBeanTest.testProcessSessionBeanEvent
Not sure if this is an issue or not, so filling this as a bug and not a challenge. The
test essentially has two observer methods and is asserting that only one of them are
called.
public void observeElephantSessionBean(@Observes ProcessSessionBean<Elephant>
event)
{
ProcessBeanObserver.elephantProcessSessionBean = event;
}
public void observeElephantBean(@Observes ProcessBean<Elephant> event)
{
ProcessBeanObserver.elephantProcessBeanCount++;
}
Specifically the test asserts that observeElephantSessionBean is called and that
observeElephantBean is not called.
Currently we call both because ProcessSessionBean is assignable to ProcessBean and the
generics are the same.
Is there a part of the spec that mandates only the most specific observer method is
called?
The only thing I can find is in 10.4 which says pretty clearly:
There may be arbitrarily many observer methods with the same event parameter type and
qualifiers.
A bean (or extension) may declare multiple observer methods.
Well I guess it's not that clear as it says essentially "this may happen"
rather than "this may happen...and when it does the behavior is...[all are invoked ||
only the most specific is invoked]"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:36 p.m.
New subject: [JBoss JIRA] Commented: (CDITCK-215) ProcessSessionBeanTest testProcessSessionBeanEvent count
[
https://issues.jboss.org/browse/CDITCK-215?page=com.atlassian.jira.plugin...
]
Gurkan Erdogdu commented on CDITCK-215:
---------------------------------------
Pete, What I was saying is that
- Event Type : ProcessSessionBean
- Observed Event Type : ProcessBean
- Event Type Argument : Elephant from ProcessSessionBean<Elephant>
- Observed Event Type Argument : Elephant from ProcessBean<Elephant>
Then ProcessBean.isAssignableFrom(ProcessSessionBean) and
Elephant.isAssignableFrom(Elephant).
Why are you getting <Object> as an observer type parameter? Observer is
ProcessBean<Elephant>, then observer' event type parameter is <Elephant>.
ProcessSessionBeanTest testProcessSessionBeanEvent count
--------------------------------------------------------
Key: CDITCK-215
URL: https://issues.jboss.org/browse/CDITCK-215
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.4.Final
Reporter: David Blevins
Assignee: Pete Muir
[Side note maybe there should be versions for 1.0.4.SP1 and 1.0.4.SP2]
Test:
org.jboss.jsr299.tck.tests.extensions.processBean.ProcessSessionBeanTest.testProcessSessionBeanEvent
Not sure if this is an issue or not, so filling this as a bug and not a challenge. The
test essentially has two observer methods and is asserting that only one of them are
called.
public void observeElephantSessionBean(@Observes ProcessSessionBean<Elephant>
event)
{
ProcessBeanObserver.elephantProcessSessionBean = event;
}
public void observeElephantBean(@Observes ProcessBean<Elephant> event)
{
ProcessBeanObserver.elephantProcessBeanCount++;
}
Specifically the test asserts that observeElephantSessionBean is called and that
observeElephantBean is not called.
Currently we call both because ProcessSessionBean is assignable to ProcessBean and the
generics are the same.
Is there a part of the spec that mandates only the most specific observer method is
called?
The only thing I can find is in 10.4 which says pretty clearly:
There may be arbitrarily many observer methods with the same event parameter type and
qualifiers.
A bean (or extension) may declare multiple observer methods.
Well I guess it's not that clear as it says essentially "this may happen"
rather than "this may happen...and when it does the behavior is...[all are invoked ||
only the most specific is invoked]"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:51 p.m.
New subject: [JBoss JIRA] Commented: (CDITCK-215) ProcessSessionBeanTest testProcessSessionBeanEvent count
[
https://issues.jboss.org/browse/CDITCK-215?page=com.atlassian.jira.plugin...
]
Pete Muir commented on CDITCK-215:
----------------------------------
Gurkan, this is not how observer resolution works, . See 10.2.1. Essentially, the issue is
that when the the event type is parameterized, you must consider only the observed type
where the raw type is identical, so we can only consider ProcessBean<Object> as the
event type to match the parameterized types for. David gives an abstract example above.
Regarding the parameterized type of ProcessBean in the ProcessSessionBean type hierarchy,
this is as described in 11.5.8.
ProcessSessionBeanTest testProcessSessionBeanEvent count
--------------------------------------------------------
Key: CDITCK-215
URL: https://issues.jboss.org/browse/CDITCK-215
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.4.Final
Reporter: David Blevins
Assignee: Pete Muir
[Side note maybe there should be versions for 1.0.4.SP1 and 1.0.4.SP2]
Test:
org.jboss.jsr299.tck.tests.extensions.processBean.ProcessSessionBeanTest.testProcessSessionBeanEvent
Not sure if this is an issue or not, so filling this as a bug and not a challenge. The
test essentially has two observer methods and is asserting that only one of them are
called.
public void observeElephantSessionBean(@Observes ProcessSessionBean<Elephant>
event)
{
ProcessBeanObserver.elephantProcessSessionBean = event;
}
public void observeElephantBean(@Observes ProcessBean<Elephant> event)
{
ProcessBeanObserver.elephantProcessBeanCount++;
}
Specifically the test asserts that observeElephantSessionBean is called and that
observeElephantBean is not called.
Currently we call both because ProcessSessionBean is assignable to ProcessBean and the
generics are the same.
Is there a part of the spec that mandates only the most specific observer method is
called?
The only thing I can find is in 10.4 which says pretty clearly:
There may be arbitrarily many observer methods with the same event parameter type and
qualifiers.
A bean (or extension) may declare multiple observer methods.
Well I guess it's not that clear as it says essentially "this may happen"
rather than "this may happen...and when it does the behavior is...[all are invoked ||
only the most specific is invoked]"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:05 a.m.
New subject: [JBoss JIRA] Commented: (CDITCK-215) ProcessSessionBeanTest testProcessSessionBeanEvent count
[
https://issues.jboss.org/browse/CDITCK-215?page=com.atlassian.jira.plugin...
]
Gurkan Erdogdu commented on CDITCK-215:
---------------------------------------
Pete, thanks for the answer.
Why public interface ProcessSessionBean<X> extends ProcessManagedBean<Object>
instead of public interface ProcessSessionBean<X> extends
ProcessManagedBean<X>
Thks.
ProcessSessionBeanTest testProcessSessionBeanEvent count
--------------------------------------------------------
Key: CDITCK-215
URL: https://issues.jboss.org/browse/CDITCK-215
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.4.Final
Reporter: David Blevins
Assignee: Pete Muir
[Side note maybe there should be versions for 1.0.4.SP1 and 1.0.4.SP2]
Test:
org.jboss.jsr299.tck.tests.extensions.processBean.ProcessSessionBeanTest.testProcessSessionBeanEvent
Not sure if this is an issue or not, so filling this as a bug and not a challenge. The
test essentially has two observer methods and is asserting that only one of them are
called.
public void observeElephantSessionBean(@Observes ProcessSessionBean<Elephant>
event)
{
ProcessBeanObserver.elephantProcessSessionBean = event;
}
public void observeElephantBean(@Observes ProcessBean<Elephant> event)
{
ProcessBeanObserver.elephantProcessBeanCount++;
}
Specifically the test asserts that observeElephantSessionBean is called and that
observeElephantBean is not called.
Currently we call both because ProcessSessionBean is assignable to ProcessBean and the
generics are the same.
Is there a part of the spec that mandates only the most specific observer method is
called?
The only thing I can find is in 10.4 which says pretty clearly:
There may be arbitrarily many observer methods with the same event parameter type and
qualifiers.
A bean (or extension) may declare multiple observer methods.
Well I guess it's not that clear as it says essentially "this may happen"
rather than "this may happen...and when it does the behavior is...[all are invoked ||
only the most specific is invoked]"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:24 p.m.
New subject: [JBoss JIRA] Commented: (CDITCK-215) ProcessSessionBeanTest testProcessSessionBeanEvent count
[
https://issues.jboss.org/browse/CDITCK-215?page=com.atlassian.jira.plugin...
]
Pete Muir commented on CDITCK-215:
----------------------------------
Gurkan, suggest you raise this on the cdi-dev list..
ProcessSessionBeanTest testProcessSessionBeanEvent count
--------------------------------------------------------
Key: CDITCK-215
URL: https://issues.jboss.org/browse/CDITCK-215
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.4.Final
Reporter: David Blevins
Assignee: Pete Muir
[Side note maybe there should be versions for 1.0.4.SP1 and 1.0.4.SP2]
Test:
org.jboss.jsr299.tck.tests.extensions.processBean.ProcessSessionBeanTest.testProcessSessionBeanEvent
Not sure if this is an issue or not, so filling this as a bug and not a challenge. The
test essentially has two observer methods and is asserting that only one of them are
called.
public void observeElephantSessionBean(@Observes ProcessSessionBean<Elephant>
event)
{
ProcessBeanObserver.elephantProcessSessionBean = event;
}
public void observeElephantBean(@Observes ProcessBean<Elephant> event)
{
ProcessBeanObserver.elephantProcessBeanCount++;
}
Specifically the test asserts that observeElephantSessionBean is called and that
observeElephantBean is not called.
Currently we call both because ProcessSessionBean is assignable to ProcessBean and the
generics are the same.
Is there a part of the spec that mandates only the most specific observer method is
called?
The only thing I can find is in 10.4 which says pretty clearly:
There may be arbitrarily many observer methods with the same event parameter type and
qualifiers.
A bean (or extension) may declare multiple observer methods.
Well I guess it's not that clear as it says essentially "this may happen"
rather than "this may happen...and when it does the behavior is...[all are invoked ||
only the most specific is invoked]"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:48 p.m.
New subject: [JBoss JIRA] Commented: (CDITCK-215) ProcessSessionBeanTest testProcessSessionBeanEvent count
[
https://issues.jboss.org/browse/CDITCK-215?page=com.atlassian.jira.plugin...
]
Gurkan Erdogdu commented on CDITCK-215:
---------------------------------------
Done. Thanks.
ProcessSessionBeanTest testProcessSessionBeanEvent count
--------------------------------------------------------
Key: CDITCK-215
URL: https://issues.jboss.org/browse/CDITCK-215
Project: CDI TCK
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.4.Final
Reporter: David Blevins
Assignee: Pete Muir
[Side note maybe there should be versions for 1.0.4.SP1 and 1.0.4.SP2]
Test:
org.jboss.jsr299.tck.tests.extensions.processBean.ProcessSessionBeanTest.testProcessSessionBeanEvent
Not sure if this is an issue or not, so filling this as a bug and not a challenge. The
test essentially has two observer methods and is asserting that only one of them are
called.
public void observeElephantSessionBean(@Observes ProcessSessionBean<Elephant>
event)
{
ProcessBeanObserver.elephantProcessSessionBean = event;
}
public void observeElephantBean(@Observes ProcessBean<Elephant> event)
{
ProcessBeanObserver.elephantProcessBeanCount++;
}
Specifically the test asserts that observeElephantSessionBean is called and that
observeElephantBean is not called.
Currently we call both because ProcessSessionBean is assignable to ProcessBean and the
generics are the same.
Is there a part of the spec that mandates only the most specific observer method is
called?
The only thing I can find is in 10.4 which says pretty clearly:
There may be arbitrarily many observer methods with the same event parameter type and
qualifiers.
A bean (or extension) may declare multiple observer methods.
Well I guess it's not that clear as it says essentially "this may happen"
rather than "this may happen...and when it does the behavior is...[all are invoked ||
only the most specific is invoked]"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4694
days inactive
4699
days old
10 comments
3 participants
participants (3)
-
David Blevins (JIRA) -
Gurkan Erdogdu (JIRA)
-
Pete Muir (JIRA)