[JBoss JIRA] (JBASMP-70) Hard deploy is not supported
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/JBASMP-70?page=com.atlassian.jira.plugin.... ]
James Perkins closed JBASMP-70.
-------------------------------
Resolution: Rejected
This isn't going to be done for the {{jboss-as-maven-plugin}}. New features will only go into the [{{wildfly-maven-plugin}}|https://issues.jboss.org/browse/WFMP/].
> Hard deploy is not supported
> ----------------------------
>
> Key: JBASMP-70
> URL: https://issues.jboss.org/browse/JBASMP-70
> Project: JBoss AS Maven Plugins
> Issue Type: Feature Request
> Reporter: Amal Jose
> Priority: Minor
>
> In Jboss 5 days we used to use a different plugin - which supports jboss hard -deploy i.e it copies the war to location where deployement scaner of jboss is searching a war...advantage of this particular implementation is that JBOSS need not be up for the plugin to run - once the jboss is up, it will take up the war..
> The current implementation does support soft deploy using JBOSS Management API..but there is no hard-deploy goal that used to be supported in JBOSS 5 plugins like http://mojo.codehaus.org/jboss-maven-plugin
> Reducing priority as this is possible using other plugins like antrun of maven...
> But can JBOSS AS MAVEN plugin support hard deploy (offline Deploy-where jboss instance is not running)
> Some online discussions regarding same : http://stackoverflow.com/questions/22936893/jboss-7-x-redeploy-option
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBASMP-41) Create goals to add modules do Jboss AS
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/JBASMP-41?page=com.atlassian.jira.plugin.... ]
James Perkins closed JBASMP-41.
-------------------------------
Resolution: Rejected
This isn't going to be done for the {{jboss-as-maven-plugin}}. New features will only go into the [{{wildfly-maven-plugin}}|https://issues.jboss.org/browse/WFMP/].
> Create goals to add modules do Jboss AS
> ---------------------------------------
>
> Key: JBASMP-41
> URL: https://issues.jboss.org/browse/JBASMP-41
> Project: JBoss AS Maven Plugins
> Issue Type: Feature Request
> Reporter: Gustavo Orair
>
> A command to create modules using Jboss CLI was created
> (refer to https://issues.jboss.org/browse/AS7-4265).
> It should be nice if one may create these modules on Jboss server referencing a maven dependency similarly to deploy-artifact configuration section.
> Maybe a possible workaround for now should be use execute-commands but it would need to locate where the maven depencies are located:
> <execution>
> <id>create-modules</id>
> <phase>install</phase>
> <goals>
> <goal>execute-commands</goal>
> </goals>
> <configuration>
> <execute-commands>
> <commands>
> <command>module add --name=oracle.jdbc --resources=ojdbc6.jar --dependencies=javax.api,javax.transaction.api</command>
> </commands>
> </execute-commands>
> </configuration>
> </execution>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JGRP-2070) Add flag back to disable individual thread pools
by Bela Ban (JIRA)
Bela Ban created JGRP-2070:
------------------------------
Summary: Add flag back to disable individual thread pools
Key: JGRP-2070
URL: https://issues.jboss.org/browse/JGRP-2070
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Minor
Fix For: 4.0
In 4.0, {{xxx_thread_pool.enbled}} was removed. The idea was that this could be done programmatically by using {{TP.setOOBThreadPool()}} using a {{DirectExecutor}}.
However, sometimes it is convenient to do this declaratively, in the XML config file, e.g. if the code cannot be changed or the channel cannot be retrieved.
Therefore add the attribute(s) to disable/enable thread pools back.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JGRP-2069) UNICAST3: bypass or remove when running over TCP
by Bela Ban (JIRA)
Bela Ban created JGRP-2069:
------------------------------
Summary: UNICAST3: bypass or remove when running over TCP
Key: JGRP-2069
URL: https://issues.jboss.org/browse/JGRP-2069
Project: JGroups
Issue Type: Enhancement
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Minor
Fix For: 3.6.10, 4.0
When running over TCP as transport, UNICAST3 is still required: while TCP/IP retransmits messages reliably and also provides sender-FIFO ordering, the receiver's thread pool might be exhausted and thus the message might get rejected.
However, *if* the regular and OOB thread pools are disabled, we could actually bypass (or completely remove) UNICAST3. If messages get dropped by a protocol further up the stack, however, there will be no retransmission in this case.
SOLUTION:
* Document this behavior
* Emit an INFO message (or automatically bypass UNICAST3) when run over a TCP transport and both OOB and regular pools are disabled
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFCORE-1568) AttributeDefinition should defer handling of undefined values to CapabilityReferenceRecorder
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1568?page=com.atlassian.jira.plugi... ]
Paul Ferraro updated WFCORE-1568:
---------------------------------
Description: This allows an attribute to potentially reference some other static named capability if its value is undefined, as determined by the CapabilityReferenceRecorder implementation. (was: This allows an attribute to potentially reference some other static named capability if its value is null, as determined by the CapabilityReferenceRecorder implementation.)
> AttributeDefinition should defer handling of undefined values to CapabilityReferenceRecorder
> --------------------------------------------------------------------------------------------
>
> Key: WFCORE-1568
> URL: https://issues.jboss.org/browse/WFCORE-1568
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Affects Versions: 2.2.0.CR2
> Reporter: Paul Ferraro
> Assignee: Brian Stansberry
>
> This allows an attribute to potentially reference some other static named capability if its value is undefined, as determined by the CapabilityReferenceRecorder implementation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (DROOLS-1190) Drool Modify operator causing ClassCastException
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-1190:
-----------------------------------
Summary: Drool Modify operator causing ClassCastException
Key: DROOLS-1190
URL: https://issues.jboss.org/browse/DROOLS-1190
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 6.4.0.Final
Environment: JBoss BRMS 6.3 on EAP 6.4.6
Reporter: gravity Blast!
Assignee: Mario Fusco
Priority: Blocker
When using the modify operator in Drools I am getting a java.lang.ClassCastException: org.adcb.finance.ResponseFact cannot be cast to org.drools.core.common.InternalFactHandle.
This seems to happen in rules that contain Arrays & using the in/not in operator on them. I have other rules using the matches regex expression and I dont get this issue.
This is a critical issue for us as we're using the RulesExecutionService in 6.4.0 to extend the KIE Execution service and are due to go live very soon so there is no chance of rolling back to 6.3.x without some heavy rework.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months