[JBoss JIRA] Created: (JBRULES-2707) Split up drools-guvnor into drools-guvnor-gwtclient and drools-guvnor(-server)
by Geoffrey De Smet (JIRA)
Split up drools-guvnor into drools-guvnor-gwtclient and drools-guvnor(-server)
------------------------------------------------------------------------------
Key: JBRULES-2707
URL: https://jira.jboss.org/browse/JBRULES-2707
Project: Drools
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Fix For: 5.2.0.M1
All classes/resources under the client/public package go to drools-guvnor-gwtclient.
The drools-guvnor-gwtclient pom.xml
- is of type war
- has only the gwt dependencies
All classes under the server package go to drools-guvnor(-server)
The drools-guvnor(-server) pom.xml
- is of type war
- has a dependency on drools-guvnor-gwtclient (= war overlay!)
- has dependencies on drools-core, drools-compiler (so on jdt too), ...
What do we do with drools-ide-common and drools-factconstraints? Split them up to, or simply move the client package code into drools-guvnor?
Where will the drools-ide-common and drools-factconstraints GWT modules be reused, besides in Guvnor?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JGRP-1268) Allow 0.0.0.0 as bind address
by Bela Ban (JIRA)
Allow 0.0.0.0 as bind address
-----------------------------
Key: JGRP-1268
URL: https://issues.jboss.org/browse/JGRP-1268
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.12
Currently, bind_addr has to be a valid interface and the wildcard (0.0.0.0) address is not permitted. The reason is that bind_addr determines the physical address of a node, e.g. 192.168.1.5:46537, and using 0.0.0.0:46537 wouldn't allow us to identify the node in order to send it a message.
To allow for TCP and UDP sockets to bind to the wildcard address, we could either use a bind_addr of 0.0.0.0 and introduce an additional property to pick the physical address (e.g. physical_addr="192.168.1.5" / physical_addr="GLOBAL"), or continue using bind_addr to determine the physical address and add a property (bind_to_wild_card_addr="true") to make the UDP and TCP sockets bind to the wildcard address (if true).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months