[
https://issues.apache.org/jira/browse/PIVOT-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906340#action_12906340
]
Greg Brown commented on PIVOT-629:
----------------------------------
I can definitely see the value in this suggestion. Historically, I have handled
this by creating application-specific properties for the hostname, port, etc.
of the web service host. However, it would be much easier to simply rely on the
origin property.
Since "origin" has a very specific definition, particularly in an applet
context, I'm reluctant to allow a caller to directly override it. However,
allowing someone to specify an alternate origin to a DesktopApplicationContext
makes a lot of sense.
I suggest adding a new "origin" command-line argument to
DesktopApplicationContext. That will facilitate testing by allowing a caller to
easily specify an alternate origin during debugging, but won't compromise the
definition of "origin" in an applet context. Would that be sufficient for your
needs?
> Set ApplicationContext origin property in desktop application
> --------------------------------------------------------------
>
> Key: PIVOT-629
> URL: https://issues.apache.org/jira/browse/PIVOT-629
> Project: Pivot
> Issue Type: New Feature
> Reporter: Oleg Orlov
>
> As a developer of RIA application i'd like to have possibility to set origin
> property of the application context of desktop application. It will help to
> keep one codebase for applet, web start and desktop applications (for debug
> purpose in my case). It will be very usefull to have a possibility to set the
> origin as an argument of "main" function.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
