[JBoss JIRA] Created: (JBAS-8795) Allow the plan for executing an operation to specify a list of required hosts / servers
by Brian Stansberry (JIRA)
Allow the plan for executing an operation to specify a list of required hosts / servers
---------------------------------------------------------------------------------------
Key: JBAS-8795
URL: https://issues.jboss.org/browse/JBAS-8795
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Fix For: 7.0.0.Beta1
This is to record an idea for future consideration.
When a client submits an operation to the domain or host controller, it can include rules for how many servers the operation can fail on within a server group before the operation is reverted across the server group.
Add the ability to specify a list of servers and or hosts where the operation must succeed.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Created: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
by Savas Ali Tokmen (JIRA)
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: VFS
Affects Versions: 6.0.0.M3, JBossAS-5.1.0.GA, JBossAS-5.0.1.GA, JBossAS-5.0.0.GA
Environment: JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
JBoss 6.0.0 M3 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x, and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.), we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5 and JBoss 6; in JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws: java.io.IOException: No context factory for http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
--
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
13 years, 3 months
[JBoss JIRA] Created: (JBRULES-2858) misc. decision table bugs and improvements
by Wolfgang Laun (JIRA)
misc. decision table bugs and improvements
------------------------------------------
Key: JBRULES-2858
URL: https://issues.jboss.org/browse/JBRULES-2858
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-decisiontables
Affects Versions: 5.1.1.FINAL
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Fix For: 5.2.0.M2
RuleTable and column headers (CONDITION, ACTION,...) are ignored when written with a leading space.
Errors are reported in row & column numbers; this should be done using cell names.
Duplicate columns for rule attributes are silently ignored; there should be a diagnostic.
NumberFormatException thrown on bad integer must be caught and result in a proper diagnostic.
Description entry is notwritten into the generated DRL.
Some attributes cannot be produced: lock-on-active, etc.
NPE thrown for certain entries
Documentation is rather "off" in several places.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Created: (JBAS-8204) Deployment via a deployment plan
by Brian Stansberry (JIRA)
Deployment via a deployment plan
--------------------------------
Key: JBAS-8204
URL: https://jira.jboss.org/browse/JBAS-8204
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Fix For: 7.0.0.M2
I want us to have some sort of deployment plan notion in our deployment API so users can specify in a document how a rolling upgrade should occur, e.g. here's the new deployment(s), first quiesce this set of servers, then upgrade, roll on to this set of servers, etc.
Basically describe in a document the set of operations that are meant to be atomic.
--
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
13 years, 3 months
[JBoss JIRA] Created: (SECURITY-561) JBossResponseContext getResult strips multiple obligations from the evaluation response.
by Brian Krisler (JIRA)
JBossResponseContext getResult strips multiple obligations from the evaluation response.
----------------------------------------------------------------------------------------
Key: SECURITY-561
URL: https://issues.jboss.org/browse/SECURITY-561
Project: PicketBox (JBoss Security and Identity Management)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: PicketBox
Affects Versions: 2.0.2.CR12
Environment: N/A
Reporter: Brian Krisler
Assignee: Anil Saldhana
The getResult() method in JBossResponseContext prevents multiple Obligations from getting returned to the PEP. The code block:
//Obligations
Set<Obligation> obligationsSet = result.getObligations();
if(obligationsSet != null)
{
for(Obligation obl:obligationsSet)
{
ObligationType obType = new ObligationType();
obType.setObligationId(obl.getId().toASCIIString());
obType.setFulfillOn(EffectType.fromValue(Result.DECISIONS[obl.getFulfillOn()]));
ObligationsType obligationsType = new ObligationsType();
obligationsType.getObligation().add(obType);
resultType.setObligations(obligationsType);
}
}
Causes the obligations to constantly get overwritten with the last one read in.
--> resultType.setObligations(obligationsType)
To fix, do something more like:
// Obligations
Set<Obligation> obligationsSet = result.getObligations();
if (obligationsSet != null && obligationsSet.size() > 0) {
ObligationsType obligationsType = new ObligationsType();
for (Obligation obl : obligationsSet) {
ObligationType obType = new ObligationType();
obType.setObligationId(obl.getId().toASCIIString());
obType.setFulfillOn(EffectType.fromValue(Result.DECISIONS[obl.getFulfillOn()]));
obligationsType.getObligation().add(obType);
}
resultType.setObligations(obligationsType);
}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months