[JBoss JIRA] (JGRP-1680) RDMA based transport
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-1680?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1680:
--------------------------------
Aso interesting: project Panama: http://openjdk.java.net/projects/panama/
> RDMA based transport
> --------------------
>
> Key: JGRP-1680
> URL: https://issues.jboss.org/browse/JGRP-1680
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 5.0
>
>
> Investigate whether an RDMA based transport makes sense.
> Advantages:
> * Speed, low latency (TCP/IP is bypassed entirely)
> * Low CPU usage
> Disadvantages:
> * JNI/C code
> ** Such a transport implementation would have to live outside of the JGroups repo
> ** Maintainability nightmare: the C code would also have to be ported to various OSes
> *** Investigate Java based libs (IBM's jVerbs) and C based libs (Apache Portable Runtime?)
> * High memory use, growing with cluster size: similarly to TCP, a 'group multicast' would involve N-1 sends. RDMA requires a Queue Pair (QP) for each destination. Each QP requires pinned memory (receive and send buffer), so each node would have to reserve (pin) N-1 memory buffers [1]
> ** OTOH, we may not use many group multicasts, e.g. with Infinispan's partial replication (DIST mode)
> * High cost of RDMA adapters, NICs and wiring: only a very small fraction of users would run such a transport.
> [1] http://www.hpcwire.com/hpcwire/2006-08-18/a_critique_of_rdma-1.html
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11302) Update root README with getting started instructions for CD releases
by Eduardo Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-11302?page=com.atlassian.jira.plugin... ]
Eduardo Martins moved JBEAP-15794 to WFLY-11302:
------------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-11302 (was: JBEAP-15794)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Quickstarts
(was: Quickstarts)
> Update root README with getting started instructions for CD releases
> --------------------------------------------------------------------
>
> Key: WFLY-11302
> URL: https://issues.jboss.org/browse/WFLY-11302
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Reporter: Eduardo Martins
> Assignee: Sande Gilda
> Priority: Major
>
> The root README file only contains instructions only for regular project and product releases. It was not updated to include the correct instructions for the CD releases.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11301) Banned dependencies not excluded
by Eduardo Martins (Jira)
Eduardo Martins created WFLY-11301:
--------------------------------------
Summary: Banned dependencies not excluded
Key: WFLY-11301
URL: https://issues.jboss.org/browse/WFLY-11301
Project: WildFly
Issue Type: Bug
Components: Build System
Reporter: Eduardo Martins
Assignee: Eduardo Martins
The following exclusions of banned dependencies should be added:
{code}
<dependency>
<groupId>org.jboss.ws.cxf</groupId>
<artifactId>jbossws-cxf-client</artifactId>
<exclusions>
<exclusion>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-tools-java2ws</artifactId>
<exclusions>
<exclusion>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-xjc</artifactId>
</exclusion>
<exclusion>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-core</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-tools-wsdlto-core</artifactId>
<exclusions>
<exclusion>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-core</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-tools-wsdlto-databinding-jaxb</artifactId>
<exclusions>
<exclusion>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-core</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-tools-validator</artifactId>
<exclusions>
<exclusion>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-core</artifactId>
</exclusion>
</exclusions>
</dependency>
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11300) Client BOMs Builder Maven Plugin
by Eduardo Martins (Jira)
Eduardo Martins created WFLY-11300:
--------------------------------------
Summary: Client BOMs Builder Maven Plugin
Key: WFLY-11300
URL: https://issues.jboss.org/browse/WFLY-11300
Project: WildFly
Issue Type: Enhancement
Components: Quickstarts
Reporter: Eduardo Martins
Assignee: Eduardo Martins
Client BOMs are painful to maintain manually, and should be replaced by poms creating the BOMs (and installing to maven repo) through a maven plugin, with many similarities with the plugin that builds wildfly's component matrix.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11125) Make org.jboss.as.security module an optional dependency of org.jboss.as.weld
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11125?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-11125:
------------------------------------
Priority: Minor (was: Major)
> Make org.jboss.as.security module an optional dependency of org.jboss.as.weld
> -----------------------------------------------------------------------------
>
> Key: WFLY-11125
> URL: https://issues.jboss.org/browse/WFLY-11125
> Project: WildFly
> Issue Type: Enhancement
> Components: CDI / Weld, Security
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
>
> The more optional deps the Weld subsystem module has, the better as it helps allow slimmer runtimes.
> 1) org.jboss.as.security -- classes from this module (SimpleSecurityManager[Service] should only be loaded if the org.wildfly.legacy-security capability is present, so this dep can be optional.
> -2) org.picketbox -- AFAICT these are only used via org.jboss.weld.security.spi.SecurityServices impl methods that are never called. And it seems like they wouldn't be expected to work without the org.wildfly.legacy-security capability being present anyway. So I believe this dep can be optional.-
> (Edited to comment out the second point since a) the SecurityServices methods are indeed called and b) it's not obvious they'd never be expected to be called without the security subsystem. Probably wouldn't work right but it's too complex a task to validate that.)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11125) Make org.jboss.as.security module an optional dependency of org.jboss.as.weld
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11125?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-11125:
------------------------------------
Description:
The more optional deps the Weld subsystem module has, the better as it helps allow slimmer runtimes.
1) org.jboss.as.security -- classes from this module (SimpleSecurityManager[Service] should only be loaded if the org.wildfly.legacy-security capability is present, so this dep can be optional.
-2) org.picketbox -- AFAICT these are only used via org.jboss.weld.security.spi.SecurityServices impl methods that are never called. And it seems like they wouldn't be expected to work without the org.wildfly.legacy-security capability being present anyway. So I believe this dep can be optional.-
(Edited to comment out the second point since a) the SecurityServices methods are indeed called and b) it's not obvious they'd never be expected to be called without the security subsystem. Probably wouldn't work right but it's too complex a task to validate that.)
was:
The more optional deps the Weld subsystem module has, the better as it helps allow slimmer runtimes.
1) org.jboss.as.security -- classes from this module (SimpleSecurityManager[Service] should only be loaded if the org.wildfly.legacy-security capability is present, so this dep can be optional.
2) org.picketbox -- AFAICT these are only used via org.jboss.weld.security.spi.SecurityServices impl methods that are never called. And it seems like they wouldn't be expected to work without the org.wildfly.legacy-security capability being present anyway. So I believe this dep can be optional.
> Make org.jboss.as.security module an optional dependency of org.jboss.as.weld
> -----------------------------------------------------------------------------
>
> Key: WFLY-11125
> URL: https://issues.jboss.org/browse/WFLY-11125
> Project: WildFly
> Issue Type: Enhancement
> Components: CDI / Weld, Security
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
>
> The more optional deps the Weld subsystem module has, the better as it helps allow slimmer runtimes.
> 1) org.jboss.as.security -- classes from this module (SimpleSecurityManager[Service] should only be loaded if the org.wildfly.legacy-security capability is present, so this dep can be optional.
> -2) org.picketbox -- AFAICT these are only used via org.jboss.weld.security.spi.SecurityServices impl methods that are never called. And it seems like they wouldn't be expected to work without the org.wildfly.legacy-security capability being present anyway. So I believe this dep can be optional.-
> (Edited to comment out the second point since a) the SecurityServices methods are indeed called and b) it's not obvious they'd never be expected to be called without the security subsystem. Probably wouldn't work right but it's too complex a task to validate that.)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (WFLY-11125) Make org.jboss.as.security module an optional dependency of org.jboss.as.weld
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11125?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-11125:
------------------------------------
Summary: Make org.jboss.as.security module an optional dependency of org.jboss.as.weld (was: Make org.jboss.as.security and org.picketbox modules optional dependencies of org.jboss.as.weld)
> Make org.jboss.as.security module an optional dependency of org.jboss.as.weld
> -----------------------------------------------------------------------------
>
> Key: WFLY-11125
> URL: https://issues.jboss.org/browse/WFLY-11125
> Project: WildFly
> Issue Type: Enhancement
> Components: CDI / Weld, Security
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
>
> The more optional deps the Weld subsystem module has, the better as it helps allow slimmer runtimes.
> 1) org.jboss.as.security -- classes from this module (SimpleSecurityManager[Service] should only be loaded if the org.wildfly.legacy-security capability is present, so this dep can be optional.
> 2) org.picketbox -- AFAICT these are only used via org.jboss.weld.security.spi.SecurityServices impl methods that are never called. And it seems like they wouldn't be expected to work without the org.wildfly.legacy-security capability being present anyway. So I believe this dep can be optional.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3266) [DMN Designer] Remove some properties from the Properties Panel
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-3266?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-3266:
---------------------------------------
{quote}
Edson Tirelli If file containing values for hidden fields is imported, should be those still be hidden? Just asking.
{quote}
[~jomarko] the values should be preserved internally for round tripping, but should not be presented in the UI, except for the "name" itself that is only presented once in the UI but should be identical in the information item and the container node on the XML.
> [DMN Designer] Remove some properties from the Properties Panel
> ---------------------------------------------------------------
>
> Key: DROOLS-3266
> URL: https://issues.jboss.org/browse/DROOLS-3266
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Priority: Blocker
> Labels: drools-tools
> Attachments: decision-table-output-header-selected.png, input-selected.png, input.png
>
>
> Remove the properties highlighted in red from the Properties Panel:
> I) When an input node is selected
> !input-selected.png|thumbnail!
> II) When a decision table header output is selected
> !decision-table-output-header-selected.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (DROOLS-3261) [DMN Designer] The `defaultOutputValue` is being persisted as an `outputValue`
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-3261?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-3261:
---------------------------------------
Michael, just to double check, when the "outputValues" is empty, it should not show up at all in the XML. So the XML you showed:
{code:xml}
<dmn:output id="_AF6071D7-C010-4B8B-9A06-F8B2AE0BE8BB" name="output-1" typeRef="string">
<dmn:outputValues id="_6FF95B64-CCF5-4349-BCE7-30A0015B0291">
<dmn:text></dmn:text>
</dmn:outputValues>
<dmn:defaultOutputEntry id="_24A04D8F-CAAC-4144-A011-06F086D53088" typeRef="string">
<dmn:text>cheese</dmn:text>
</dmn:defaultOutputEntry>
</dmn:output>
{code}
Should actually be:
{code:xml}
<dmn:output id="_AF6071D7-C010-4B8B-9A06-F8B2AE0BE8BB" name="output-1" typeRef="string">
<dmn:defaultOutputEntry id="_24A04D8F-CAAC-4144-A011-06F086D53088" typeRef="string">
<dmn:text>cheese</dmn:text>
</dmn:defaultOutputEntry>
</dmn:output>
{code}
> [DMN Designer] The `defaultOutputValue` is being persisted as an `outputValue`
> ------------------------------------------------------------------------------
>
> Key: DROOLS-3261
> URL: https://issues.jboss.org/browse/DROOLS-3261
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Michael Anstis
> Priority: Blocker
> Labels: drools-tools
> Fix For: 7.14.0.Final
>
> Attachments: diagram.png, dtable.png
>
>
> When the user persists the following diagram:
> !diagram.png|thumbnail!
> ..with the following Decision Table:
> !dtable.png|thumbnail!
> .. select the "Can drink beer?" header, set the default value as {{false}} and the file:
> {quote}
> <dmn:outputValues id="_A117F7DC-508C-4132-8F5F-8F8F2B0B489F">
> <dmn:text>false</dmn:text>
> </dmn:outputValues>
> <dmn:defaultOutputEntry id="_A4881AD1-7EDC-4B4D-AC00-078626795BA7" typeRef="string">
> <dmn:text></dmn:text>
> </dmn:defaultOutputEntry>
> {quote}
> ..and the expected behaviour is to persist the value {{false}} in the {{defaultOutputEntry}}.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months