[JBoss JIRA] (ARQ-1747) Move InjectionPoint one level up in DroneContext
by Tadeas Kriz (JIRA)
[ https://issues.jboss.org/browse/ARQ-1747?page=com.atlassian.jira.plugin.s... ]
Tadeas Kriz reassigned ARQ-1747:
--------------------------------
Assignee: Tadeas Kriz
> Move InjectionPoint one level up in DroneContext
> ------------------------------------------------
>
> Key: ARQ-1747
> URL: https://issues.jboss.org/browse/ARQ-1747
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Affects Versions: drone_2.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Tadeas Kriz
> Fix For: drone_2.0.0.Alpha2
>
>
> Instead of having
> {code}
> context.getDrone(InjectionPoint<?>)
> context.getDroneConfiguration(InjectionPoint<?>)
> {code}
> provide rather
> {code}
> context.get(InjectionPoint<?>).getInstance() // type defined by IP
> context.get(InjectionPoint<?>).getInstanceAs(Class<?>)
> context.get(InjectionPoint<?>).getConfigurationAs(Class<?>)
> context.get(InjectionPoint<?>).getMetadataAs(String, Class<?>)
> {code}
> Implementation note: We might provide NullInjectionPoint to avoid people doing null checks. Or, we can throw exception instead.
--
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
10 years, 9 months
[JBoss JIRA] (ARQ-1745) Rename InjectionPoint
by Tadeas Kriz (JIRA)
[ https://issues.jboss.org/browse/ARQ-1745?page=com.atlassian.jira.plugin.s... ]
Tadeas Kriz reassigned ARQ-1745:
--------------------------------
Assignee: Tadeas Kriz
> Rename InjectionPoint
> ---------------------
>
> Key: ARQ-1745
> URL: https://issues.jboss.org/browse/ARQ-1745
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Affects Versions: drone_2.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Tadeas Kriz
> Fix For: drone_2.0.0.Alpha2
>
>
> InjectionPoint is already in Arquillian SPI. Rather, follow the conventions and rename it to DronePoint.
> There is already InjectionPoint and EventPoint in Drone. Having a DronePoint makes perfect sense using this optics.
--
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
10 years, 9 months
[JBoss JIRA] (ARQ-1744) Provide metadata storage in DroneContext
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1744?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic commented on ARQ-1744:
----------------------------------------
[~kpiwko] [~tkriz]
Is it possible to have this in 2.0.0.Alpha1? Having this particular JIRA done, it would simplify Droidium code tremendously and I would move with other things as well for which this one being resolved is very needed prerequisity. Waiting for Alpha2 is just time blocker for me.
> Provide metadata storage in DroneContext
> ----------------------------------------
>
> Key: ARQ-1744
> URL: https://issues.jboss.org/browse/ARQ-1744
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Affects Versions: drone_2.0.0.Alpha1
> Reporter: Karel Piwko
> Fix For: drone_2.0.0.Alpha2
>
>
> Other extensions might want to store additional data next to Drone callable/instance and its configuration.
> It would be convenient to expose key:String and value:Object storage for storing metadata directly in DroneContext.
> It is not needed to solve conflict anyhow.
--
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
10 years, 9 months
[JBoss JIRA] (ARQ-1747) Move InjectionPoint one level up in DroneContext
by Karel Piwko (JIRA)
Karel Piwko created ARQ-1747:
--------------------------------
Summary: Move InjectionPoint one level up in DroneContext
Key: ARQ-1747
URL: https://issues.jboss.org/browse/ARQ-1747
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Drone
Affects Versions: drone_2.0.0.Alpha1
Reporter: Karel Piwko
Fix For: drone_2.0.0.Alpha2
Instead of having
{code}
context.getDrone(InjectionPoint<?>)
context.getDroneConfiguration(InjectionPoint<?>)
{code}
provide rather
{code}
context.get(InjectionPoint<?>).getInstance() // type defined by IP
context.get(InjectionPoint<?>).getInstanceAs(Class<?>)
context.get(InjectionPoint<?>).getConfigurationAs(Class<?>)
context.get(InjectionPoint<?>).getMetadataAs(String, Class<?>)
{code}
Implementation note: We might provide NullInjectionPoint to avoid people doing null checks. Or, we can throw exception instead.
--
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
10 years, 9 months
[JBoss JIRA] (ARQ-1746) Remove objects (instance, configuration) from Drone events
by Karel Piwko (JIRA)
Karel Piwko created ARQ-1746:
--------------------------------
Summary: Remove objects (instance, configuration) from Drone events
Key: ARQ-1746
URL: https://issues.jboss.org/browse/ARQ-1746
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Drone
Affects Versions: drone_2.0.0.Alpha1
Reporter: Karel Piwko
Fix For: drone_2.0.0.Alpha2
Remove all objects from Drone Events as they might be already old and the time events are processed.
Always use DroneContext to get their actual value. Event model must enforce that.
--
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
10 years, 9 months
[JBoss JIRA] (ARQ-1745) Rename InjectionPoint
by Karel Piwko (JIRA)
Karel Piwko created ARQ-1745:
--------------------------------
Summary: Rename InjectionPoint
Key: ARQ-1745
URL: https://issues.jboss.org/browse/ARQ-1745
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Drone
Affects Versions: drone_2.0.0.Alpha1
Reporter: Karel Piwko
Fix For: drone_2.0.0.Alpha2
InjectionPoint is already in Arquillian SPI. Rather, follow the conventions and rename it to DronePoint.
There is already InjectionPoint and EventPoint in Drone. Having a DronePoint makes perfect sense using this optics.
--
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
10 years, 9 months
[JBoss JIRA] (ARQ-1744) Provide metadata storage in DroneContext
by Karel Piwko (JIRA)
Karel Piwko created ARQ-1744:
--------------------------------
Summary: Provide metadata storage in DroneContext
Key: ARQ-1744
URL: https://issues.jboss.org/browse/ARQ-1744
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Drone
Affects Versions: drone_2.0.0.Alpha1
Reporter: Karel Piwko
Fix For: drone_2.0.0.Alpha2
Other extensions might want to store additional data next to Drone callable/instance and its configuration.
It would be convenient to expose key:String and value:Object storage for storing metadata directly in DroneContext.
It is not needed to solve conflict anyhow.
--
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
10 years, 9 months
[JBoss JIRA] (ARQ-1743) Merge configuration and callable creation together
by Karel Piwko (JIRA)
Karel Piwko created ARQ-1743:
--------------------------------
Summary: Merge configuration and callable creation together
Key: ARQ-1743
URL: https://issues.jboss.org/browse/ARQ-1743
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Extension - Drone
Affects Versions: drone_2.0.0.Alpha1
Reporter: Karel Piwko
Fix For: drone_2.0.0.Alpha2
There should be just one event and either both or none of the object should be present.
This mean that callable and configuration should be created at the same time. This would make usage of Drone much easier.
--
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
10 years, 9 months