[ https://issues.jboss.org/browse/AS7-3363?page=com.atlassian.jira.plugin.s... ] Pavel Slegr reassigned AS7-3363: -------------------------------- Assignee: Pavel Slegr (was: Heiko Braun) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3363?page=com.atlassian.jira.plugin.s... ] Jan Martiska commented on AS7-3363: ----------------------------------- @Pavel: STANDALONE MODE Socket bindings for the socket-binding-group 'standard-sockets', which is the default and only group in standalone mode, can be created using console in the tab General Configuration/Socket Binding Groups. a list of currently available socket bindings is at DMR address /socket-binding-group=standard-sockets/socket-binding= .. DOMAIN MODE This gets much trickier. First of all, defined CONNECTORs should be bound to a SERVER GROUP, not a PROFILE, that is an inconsistency in AS7's domain model. Having a fixed PROFILE doesn't define a fixed SOCKET BINDING GROUP, therefore having a fixed PROFILE doesn't provide you a set of allowed SOCKET BINDINGs. Therefore it is possible for a PROFILE to define a CONNECTOR bound to a SOCKET BINDING which doesn't exist in the SOCKET BINDING GROUP that is used by one or more of the SERVER GROUPS which use this profile, therefore it is possible that SERVERs in one of these SERVER GROUPS will be forced to use a SOCKET BINDING that doesn't exist in their own SOCKET BINDING GROUP. Because of this inconsistency, it is not possible to provide a consistent set of possible SOCKET BINDINGs to be chosen from while creating a CONNECTOR bound to a PROFILE. Simple isn't it? :)) Ok, let's get down to business: In my opinion, the best solution (quite simple, yet not THAT inconsistent) is to create a union set of all unique existing socket binding names from all socket binding groups in the domain. That means, when the user is creating a connector, the choices provided should include all socket bindings in standard-sockets, ha-sockets and all other socket binding groups. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-3363?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated AS7-3363: ----------------------------- Summary: Admin console: Creating a web connector should show a list of available socket bindings (was: Admin console: Creating a connector should show a list of available socket bindings) Git Pull Request: https://github.com/heiko-braun/as7-console/pulls (was: https://github.com/heiko-braun/as7-console/pulls) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira