You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org> on 2009/02/03 18:36:00 UTC
[jira] Created: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
---------------------------------------------------------------------------------
Key: UIMA-1288
URL: https://issues.apache.org/jira/browse/UIMA-1288
Project: UIMA
Issue Type: Improvement
Components: Async Scaleout
Reporter: Jerry Cwiklik
Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
A placeholder syntax could be inherited from Spring, where it looks like {$placeholder-name}. We can agree on special syntax for specifying broker placeholders. Perhaps something like:
{$uima.as.broker1}
{$uima.as.broker2}
....
dd2spring would need to change to accept a placeholder and *not* interpret it. I believe that dd2spring currently makes decisions based on what protocol is specified in the Broker URL ( tcp vs vm). There are other protocols that we may need to support other than tcp and vm. Most notably, the failover protocol that allows for specifying a redundant broker. We cant currently use this protocol for deploying UIMA AS services. An example of this protocol for activeMQ:
failover:(tcp://primary:61616,tcp://secondary:61616)?randomize=false
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Tong Fin (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tong Fin closed UIMA-1288.
--------------------------
Resolution: Fixed
Fix Version/s: 2.3AS
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Tong Fin
> Fix For: 2.3AS
>
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor reassigned UIMA-1288:
------------------------------------
Assignee: Marshall Schor
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Marshall Schor
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Closed: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by Tong Fin <to...@gmail.com>.
I think I have to open a different JIRA for DDE to allow an "empty" value
for the "Broker URL for input queue" field in Overview page of DDE GUI.
Right now, the value of this field is "required".
-- Tong
On Tue, Apr 21, 2009 at 12:04 AM, Marshall Schor <ms...@schor.com> wrote:
> Hi Jerry -
>
> I don't think this change is documented in our official documentation.
> Could you either re-open this issue or do a new issue so we don't forget
> to do that? I'm happy to "edit" someone else's first draft of updates,
> or, if I get a chance I might try to update this myself (but I'm kind of
> swamped with other work these days).
>
> Thanks. -Marshall
>
> Jerry Cwiklik (JIRA) wrote:
> > [
> https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
> >
> > Jerry Cwiklik closed UIMA-1288.
> > -------------------------------
> >
> > Resolution: Fixed
> >
> >
> >> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment
> Descriptor
> >>
> ---------------------------------------------------------------------------------
> >>
> >> Key: UIMA-1288
> >> URL: https://issues.apache.org/jira/browse/UIMA-1288
> >> Project: UIMA
> >> Issue Type: Improvement
> >> Components: Async Scaleout
> >> Reporter: Jerry Cwiklik
> >> Assignee: Marshall Schor
> >>
> >> Each UIMA AS deployment descriptor requires at least one Broker URL for
> the connection factory. Instead of hard coding the URL, perhaps a
> placeholder for it should be used. At runtime, the placeholder could be
> resolved to the actual URL by Spring resolver component. The value could
> come from either an external file or from an environment. The new approach
> should accommodate specifying more than one placeholder, since an aggregate
> may have delegates whose queues are managed by a different broker. The new
> approach would simplify deployment of UIMA AS services, especially during
> testing.
> >> A placeholder syntax could be inherited from Spring, where it looks like
> ${placeholder-name}.
> >> dd2spring would need to change to handle a placeholder notation in
> addition to supporting hard coded broker URL that we use now. A new bean
> must be added to the generated xml. It will be :
> >> <bean
> class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> >> <property name="systemPropertiesModeName"
> value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> >> </bean>
> >>
> >> This bean is setup to resolve placeholders using system variables, like
> -Dplaceholder-name=placeholder-value
> >>
> >
> >
>
--
Tong
Re: [jira] Closed: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by Marshall Schor <ms...@schor.com>.
Hi Jerry -
I don't think this change is documented in our official documentation.
Could you either re-open this issue or do a new issue so we don't forget
to do that? I'm happy to "edit" someone else's first draft of updates,
or, if I get a chance I might try to update this myself (but I'm kind of
swamped with other work these days).
Thanks. -Marshall
Jerry Cwiklik (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Jerry Cwiklik closed UIMA-1288.
> -------------------------------
>
> Resolution: Fixed
>
>
>> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
>> ---------------------------------------------------------------------------------
>>
>> Key: UIMA-1288
>> URL: https://issues.apache.org/jira/browse/UIMA-1288
>> Project: UIMA
>> Issue Type: Improvement
>> Components: Async Scaleout
>> Reporter: Jerry Cwiklik
>> Assignee: Marshall Schor
>>
>> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
>> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
>> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
>> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
>> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
>> </bean>
>>
>> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
>>
>
>
[jira] Closed: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-1288.
-------------------------------
Resolution: Fixed
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Marshall Schor
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Tong Fin (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748857#action_12748857 ]
Tong Fin commented on UIMA-1288:
--------------------------------
When a new deployment descriptor for UIMA-AS is created, the current behavior of the Deployment Descriptor Editor (DDE) GUI is to initialized the field of the brokerURL with the "tcp://localhost:61616" string.
With this JIRA, the initialized string of the brokerURL field will be "${defaultBrokerURL}". This string can be changed by a user to any string as necessary.
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Tong Fin
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-1288.
-------------------------------
Resolution: Fixed
Updated UIMA AS deployment descriptors in examples/deploy/dir to use placeholder for brokerURL
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.3AS
>
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik reopened UIMA-1288:
---------------------------------
Modify UIMA-AS client code to accept broker placeholder ${placeholdername} and resolve it using System property with the name 'placeholdername'
This enables support for placeholders in the jms client descriptor
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.3AS
>
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1288:
--------------------------------
Description:
Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
<bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
</bean>
This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
was:
Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
A placeholder syntax could be inherited from Spring, where it looks like {$placeholder-name}. We can agree on special syntax for specifying broker placeholders. Perhaps something like:
{$uima.as.broker1}
{$uima.as.broker2}
....
dd2spring would need to change to accept a placeholder and *not* interpret it. I believe that dd2spring currently makes decisions based on what protocol is specified in the Broker URL ( tcp vs vm). There are other protocols that we may need to support other than tcp and vm. Most notably, the failover protocol that allows for specifying a redundant broker. We cant currently use this protocol for deploying UIMA AS services. An example of this protocol for activeMQ:
failover:(tcp://primary:61616,tcp://secondary:61616)?randomize=false
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik reopened UIMA-1288:
---------------------------------
Change UIMA AS example deployment descriptors to use broker placeholder: ${defaultBrokerURL}
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.3AS
>
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689687#action_12689687 ]
Marshall Schor commented on UIMA-1288:
--------------------------------------
dd2spring looks at all the brokers, and for those brokers other than "vm://localBroker...." it generates a factory for a specific external queue broker looking something like
{noformat}
<bean id="an id generated from the broker name"
class="org.apache.activemq.ActiveMQConnectionFactory">
<property name="brokerURL" value="{@brokerURL}"/>
<property name="prefetchPolicy" ref="prefetchPolicy"/>
</bean>
and a similar bean for the reply queue...
{noformat}
WIth this proposal, I could always generate this, even for brokers that later turn out to be "vm://localBroker... " kinds. Is this OK?
Dd2spring only generates beans for the localhost connection factory, and the broker deployer service if vm://localhost is specified as the top-level broker. If this was substituted, the logic would fail to generate those beans. Should those beans always be generated just in case, if the ${...} syntax is used?
The following error checks, now done by dd2spring, would not work (please confirm this is OK)
* vm: protocol was not being specified for a remote delegate
* top level input Queue broker must be a tcp:// style for C++ component
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698398#action_12698398 ]
Jerry Cwiklik commented on UIMA-1288:
-------------------------------------
As part of this, modify dd2spring and Uima AS java code to support default broker URLs. A user may omit specifying a brokerURLs in the Deployment Descriptor. In such case, dd2spring will add a brokerURL property with a value of "${defaultBrokerURL}" to the top level service as well as all remote delegates of this service for which a user did not provide specify brokerURL property. The value for defaultBrokerURL will be taken from the system property and it will be set by both UIMA_Service and RunRemoteAsyncAE. A user may specify the value for defaultBrokerURL by adding a new command line argument for UIMA_Service and RunRemoteAsyncAE. This would be an optional argument. If the argument is not provided, the code will set defaultBrokerURL to "tcp://localhost:61616".
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Marshall Schor
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-1288.
-------------------------------
Resolution: Fixed
Modified UIMA AS client code to detect placeholder in a brokerURL and resolve it using System properties
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.3AS
>
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698432#action_12698432 ]
Jerry Cwiklik commented on UIMA-1288:
-------------------------------------
Modified UIMA_Service to accept new (optional) command line argument -brokerURL. The code sets a system property defaultBrokerURL to a value bound to the new argument if the argument is provided. If the argument is not provided, the defaultBrokerURL system property will be set to tcp://localhost:61616. RunRemoteAsyncAE was also changed to support setting of the defaultBrokerURL property to the value provided by a user in brokerURL command line argument.
dd2spring needs to change to handle missing brokerURL property on the inputQueue element in a deployment descriptor. If missing, dd2spring will add brokerURL property and set its value to a placeholder ${defaultBrokerURL} as in the following example:
<inputQueue endpoint="RoomNumberAnnotatorQueue" brokerURL="${defaultBrokerURL}"/>
The placeholder value will be taken from a system property set by UIMA_Service and RunRemoteAsyncAE.
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Marshall Schor
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694208#action_12694208 ]
Marshall Schor commented on UIMA-1288:
--------------------------------------
Jerry tells me that the specifying vm://localhost was not working - so no one could be using it - so it's OK to remove it without concern for breaking backwards compatibility.
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eddie Epstein reopened UIMA-1288:
---------------------------------
Assignee: Tong Fin (was: Marshall Schor)
Seems better to use this issue to fix the DDE too. When you are done, please assign it to me to finish the documentation. Thanks, Eddie
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Tong Fin
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik reopened UIMA-1288:
---------------------------------
Assignee: Jerry Cwiklik (was: Tong Fin)
When Uima AS starts up it prints:
>>> Setting defaultBrokerURL to:tcp://localhost:61616
even though the brokerURL attribute references a different broker.
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.3AS
>
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689992#action_12689992 ]
Jerry Cwiklik commented on UIMA-1288:
-------------------------------------
Vm protocol is no longer used. It was used for messaging between colocated
services. Since we use java queues for internal messaging, vm is obsolete. We do need to support
http in addition to tcp protocol however. In a near future we need to support lists of URLs to support
broker failover in deployments that use Network of Brokers.
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (UIMA-1288) Need a Better Approach For
Specifying UIMA AS Broker URL in Deployment Descriptor
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698432#action_12698432 ]
Jerry Cwiklik edited comment on UIMA-1288 at 4/14/09 7:40 AM:
--------------------------------------------------------------
Modified UIMA_Service to accept new (optional) command line argument -brokerURL. The code sets a system property defaultBrokerURL to a value bound to the new argument if the argument is provided. If the argument is not provided, the defaultBrokerURL system property will be set to tcp://localhost:61616. RunRemoteAsyncAE was also changed to support setting of the defaultBrokerURL property to the value provided by a user in brokerURL command line argument.
dd2spring needs to change to handle missing brokerURL property on the inputQueue element in a deployment descriptor. If missing, dd2spring will add brokerURL property and set its value to a placeholder ${defaultBrokerURL} as in the following example:
<inputQueue endpoint="RoomNumberAnnotatorQueue" brokerURL="${defaultBrokerURL}"/>
The placeholder value will be taken from a system property set by UIMA_Service and RunRemoteAsyncAE.
The brokerURL property may be omitted from the top level input queue as well as input queue of any of the delegates. dd2spring will only add the brokerURL property if it is missing. If it is specified, dd2spring will not attempt to override existing value.
was (Author: cwiklik):
Modified UIMA_Service to accept new (optional) command line argument -brokerURL. The code sets a system property defaultBrokerURL to a value bound to the new argument if the argument is provided. If the argument is not provided, the defaultBrokerURL system property will be set to tcp://localhost:61616. RunRemoteAsyncAE was also changed to support setting of the defaultBrokerURL property to the value provided by a user in brokerURL command line argument.
dd2spring needs to change to handle missing brokerURL property on the inputQueue element in a deployment descriptor. If missing, dd2spring will add brokerURL property and set its value to a placeholder ${defaultBrokerURL} as in the following example:
<inputQueue endpoint="RoomNumberAnnotatorQueue" brokerURL="${defaultBrokerURL}"/>
The placeholder value will be taken from a system property set by UIMA_Service and RunRemoteAsyncAE.
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Marshall Schor
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eddie Epstein reassigned UIMA-1288:
-----------------------------------
Assignee: Eddie Epstein (was: Tong Fin)
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Eddie Epstein
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor reassigned UIMA-1288:
------------------------------------
Assignee: Tong Fin (was: Eddie Epstein)
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Tong Fin
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1288) Need a Better Approach For Specifying
UIMA AS Broker URL in Deployment Descriptor
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-1288.
-------------------------------
Resolution: Fixed
Modified to show brokerURL only in the case when it is explicitly set via -brokerURL command line parameter
> Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1288
> URL: https://issues.apache.org/jira/browse/UIMA-1288
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.3AS
>
>
> Each UIMA AS deployment descriptor requires at least one Broker URL for the connection factory. Instead of hard coding the URL, perhaps a placeholder for it should be used. At runtime, the placeholder could be resolved to the actual URL by Spring resolver component. The value could come from either an external file or from an environment. The new approach should accommodate specifying more than one placeholder, since an aggregate may have delegates whose queues are managed by a different broker. The new approach would simplify deployment of UIMA AS services, especially during testing.
> A placeholder syntax could be inherited from Spring, where it looks like ${placeholder-name}.
> dd2spring would need to change to handle a placeholder notation in addition to supporting hard coded broker URL that we use now. A new bean must be added to the generated xml. It will be :
> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
> <property name="systemPropertiesModeName" value="SYSTEM_PROPERTIES_MODE_OVERRIDE"/>
> </bean>
>
> This bean is setup to resolve placeholders using system variables, like -Dplaceholder-name=placeholder-value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.