Jeanfrancois,
As this is a publicly available feature, the current use of the
property must be maintained in a compatible way in 9.2!
If Port Unification is the right name, why is it also not the right
name now?
In other words, if this is for customer use, you MAY NOT break
compatibility in Appserver 9.2, at least not without doing a WSARC
case, and having such a change approved.
Lloyd
On Nov 10, 2006, at 10:07 AM, Jeanfrancois Arcand wrote:
> Hi,
>
> Lloyd L Chambers wrote:
>> Jeanfrancois,
>> If this is "TCP Port Unification", then why is the property named
>> "proxied_protocols"? Perhaps the name should reflect the goal,
>> not the implmentation.
>
> For now since the mechanism is enabled via an http-listener (for
> 9.1), the proxied_protocols is really what it means. For 9.2, a new
> element will be added to domain.dtd and at that time Port
> Unification will be the right name.
>
>> Also, could we please not invent a new naming convention? Nothing
>> else in domain.xml uses an underscore. Most things use camel
>> case, and one uses a dash "-" character. Others use a "." when
>> there are multiple properties.
>
> Agreed.
>
> --Jeanfrancois
>
>> Examples:
>> <property name="PortNumber" value="1527"/>
>> <property name="Password" value="APP"/>
>> <property name="User" value="APP"/>
>> <property name="serverName" value="localhost"/>
>> <property name="DatabaseName" value="sun-appserv-samples"/>
>> <property name="connectionAttributes" value=";create=true"/>
>> <property name="docroot" value="${com.sun.aas.instanceRoot}/
>> docroot"/>
>> <property name="accesslog" value="${com.sun.aas.instanceRoot}/logs/
>> access"/>enabled="true"/>
>> <property name="client-hostname" value="MB.local"/></jmx-connector>
>> <property name="file" value="${com.sun.aas.instanceRoot}/config/
>> admin-keyfile"/>
>> <property name="jaas-context" value="fileRealm"/>
>> <property name="repository" value="${com.sun.aas.instanceRoot}/
>> generated/policy"/>
>> <property name="auditOn" value="false"/>
>> <property name="encryption.key.alias" value="s1as"/>
>> <property name="signature.key.alias" value="s1as"/>
>> <property name="dynamic.username.password" value="false"/>
>> <property name="debug" value="false"/>
>> On Nov 9, 2006, at 12:42 PM, Jeanfrancois Arcand wrote:
>>> Hi,
>>>
>>> just an update about the TCP port unification that will soon be
>>> enabled. The feature will be enabled via domain.xml the following
>>> way:
>>>
>>> <http-listener ... port="4848" ... security-enabled="false">
>>> <property name="proxied_protocols" value="https"/>
>>> </http-listener>
>>>
>>> <http-listener ... port="4848" ... security-enabled="true">
>>> <property name="proxied_protocols" value="http"/>
>>> </http-listener>
>>>
>>> <http-listener ... port="8080" ... security-enabled="false">
>>> <property name="proxied_protocols" value="wsit"/>
>>> </http-listener>
>>>
>>> For 9.1, only port 8080 and 4848 will use the feature. People
>>> that are interested to extends the current protocols list will
>>> have to follow what I've described in [1].
>>>
>>> Comments?
>>>
>>> -- Jeanfrancois
>>>
>>> [1] http://weblogs.java.net/blog/jfarcand/archive/2006/11/
>>> one_port_to_rul.html
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>