What you are saying is correct and that is indeed the case (dynamic configuration) I am not focusing on my use case alone, but my use case does expose this bug.
The way the code is right now is incorrect. This is not just reported by me but by at least Alejandro as well. There is a test as well in the comments. On Sep 3, 2013, at 1:42 PM, Kalle Korhonen wrote: > On Tue, Sep 3, 2013 at 10:33 AM, Lenny Primak <[email protected]>wrote: > >> In any case, this is clearly a bug and should be fixed without requiring >> developers >> to specify ports to Tapestry that are already known by the system. >> > > Don't focus on your use case alone. There are too many ways to set up the > routing, which is why it's best to explicitly set the hostname and ports > yourself. If your app lives in multiple environment, don't try to make the > app contain these settings but set them in an external configuration. > > Kalle > > > >> >> On Sep 3, 2013, at 1:26 PM, Dmitry Gusev wrote: >> >>> Lenny, what cloud / cluster environments are you talking about? Do you >> have >>> any concrete examples? >>> I'm using this feature with OpenShift and Jelastic and it works fine, >>> there's no any dynamically assigned ports. >>> Is this even can be possible? >>> Because as far as I know application servers require so their binding >> ports >>> have to be set implicitly in configs. >>> Or these ports can be set using app-server specific system variables, >> which >>> you may read in provideApplicationDefaults and set those as value for the >>> tapestry symbols. >>> >>> >>> On Tue, Sep 3, 2013 at 8:53 PM, Lenny Primak <[email protected]> >> wrote: >>> >>>> Indeed it does (as stated in the comments of the issue also) >>>> Setting them is not a good option, as the installation is in the cloud / >>>> clusters >>>> with multiple ports, dynamically assigned ports, etc. >>>> Setting these would be a maintenance nightmare (if even possible) >>>> >>>> On Sep 3, 2013, at 9:20 AM, Massimo Lusetti wrote: >>>> >>>>> On Tue, Sep 3, 2013 at 10:22 AM, Lenny Primak <[email protected] >>>>> wrote: >>>>> >>>>>> In this issue: https://issues.apache.org/jira/browse/TAP5-1973 >>>>>> >>>>>> If you take a look at the last comment from Alejandro Scandroli, >>>>>> it looks like the side effect is still not fixed in 5.4. >>>>>> Right now, this is being worked around in FlowLogix, but I would like >> to >>>>>> remove >>>>>> this code (i.e. asking for this bug to get fixed) in 5.4 >>>>>> >>>>>> Thank you >>>>>> >>>>>> >>>>> Does the "issue" pops out only if you don't set HOSTPORT and >>>>> HOSTPORT_SECURE ? >>>>> >>>>> -- >>>>> Massimo Lusetti >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >>> >>> -- >>> Dmitry Gusev >>> >>> AnjLab Team >>> http://anjlab.com >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
