|
From: Geoffrey (JIRA) <no...@at...> - 2005-09-23 10:08:42
|
Determine webAppContextUrl through JNLP instead of hard coding it with patch: JnlpPropertyPlaceholderConfigurer
---------------------------------------------------------------------------------------------------------------
Key: RCP-198
URL: http://opensource.atlassian.com/projects/spring/browse/RCP-198
Project: Spring Framework Rich Client Project
Type: New Feature
Components: Helper Classes
Reporter: Geoffrey
Assigned to: Oliver Hutchison
In the petclinic example I saw the localhost:8080 hardcoded, which means this would have to be adjusted in the properties file in the jar (which is in in the war) for deployment on any domain.
With JnlpPropertyPlaceholderConfigurer (attached) there is not need to do this:
For example:
<bean id="jnlpPropertyPlaceholderConfigurer"
class="be.kahosl.mammoet.swingclient.util.JnlpPropertyPlaceholderConfigurer">
<property name="fallBackWebAppContextUrl" value="http://localhost:8080/mammoet-webclient/"/>
<property name="jnlpRelativeDirectoryPathFromWebAppContext" value="/jnlp/"/>
</bean>
<bean name="orderService"
class="org.springframework.remoting.caucho.BurlapProxyFactoryBean">
<property name="serviceUrl">
<value>${jnlp.webAppContextUrl}orderService.service</value> <!-- NO HARD CODING, not even in a properties file-->
</property>
<property name="serviceInterface">
<value>be.kahosl.mammoet.serviceapi.order.OrderService</value>
</property>
</bean>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/spring/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|