[jboss-jira] [JBoss JIRA] Resolved: (AS7-1576) Improve server port specification and configuration of port sets

[Jason Greene (JIRA)]

     [ https://issues.jboss.org/browse/AS7-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Greene resolved AS7-1576.
-------------------------------

    Resolution: Rejected


You appear to be talking about AS6 and earlier. AS7 has a completely different configuration, one that is completely user focused, has no internal wiring details like yu mention.

> Improve server port specification and configuration of port sets
> ----------------------------------------------------------------
>
>                 Key: AS7-1576
>                 URL: https://issues.jboss.org/browse/AS7-1576
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Server
>    Affects Versions: 7.0.1.Final
>            Reporter: Nick Bower
>            Assignee: Jason Greene
>            Priority: Minor
>
> Hi.  The way ports are selected in JBoss are very unconventional (from a traditional sysadmin pov).
> As there are so many, they are specified as sets either at runtime via -Djboss.service.binding.set=<portset>, at which point they are lost to remote controlling apps like JBDS, or you can over-ride the "ServiceBindingManagementObject" bean in
> ./jboss-as/server/default/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml
> However a *nix sysadmin would be looking for a conventional way to affect port setup, like a standard properties or text file in
> ./jboss-as/server/default/conf/
> not by configuring code-level service beans.  Consider how standard mail, DNS, web, database etc servers are easily deployable.  Why should   JBoss AS be so different?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira