uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Cwiklik (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Commented: (UIMA-1288) Need a Better Approach For Specifying UIMA AS Broker URL in Deployment Descriptor
Date Mon, 13 Apr 2009 16:42:15 GMT

    [ 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.


Mime
View raw message