[JBoss JIRA] (WFLY-4577) Missing dependency "ibm.jdk" in module org.jboss.security.negotiation
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/WFLY-4577?page=com.atlassian.jira.plugin.... ]
Ramesh Reddy moved TEIID-3416 to WFLY-4577:
-------------------------------------------
Project: WildFly (was: Teiid)
Key: WFLY-4577 (was: TEIID-3416)
Issue Type: Enhancement (was: Feature Request)
Workflow: GIT Pull Request workflow (was: classic default workflow)
Affects Version/s: JBoss AS7 7.2.0.Final
(was: 8.7.1)
> Missing dependency "ibm.jdk" in module org.jboss.security.negotiation
> ---------------------------------------------------------------------
>
> Key: WFLY-4577
> URL: https://issues.jboss.org/browse/WFLY-4577
> Project: WildFly
> Issue Type: Enhancement
> Affects Versions: JBoss AS7 7.2.0.Final
> Reporter: Juraj Duráni
> Assignee: Ramesh Reddy
>
> The module org.jboss.security.negotiation is missing "ibm.jdk" dependency. This module is needed if the JDV is running on IBM jdk - contains com.ibm.security.auth.module.Krb5LoginModule class.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (WFCORE-114) Get RuntimeVaultReader into WildFly Core
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-114?page=com.atlassian.jira.plugin... ]
Tomaz Cerar commented on WFCORE-114:
------------------------------------
This change doesn't really require us to bundle picketbox into distro. It is just compile dependency. which is fine.
> Get RuntimeVaultReader into WildFly Core
> ----------------------------------------
>
> Key: WFCORE-114
> URL: https://issues.jboss.org/browse/WFCORE-114
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha8
> Reporter: Brian Stansberry
> Assignee: ehsavoie Hugonnet
> Priority: Blocker
> Fix For: 1.0.0.CR2
>
>
> The only real implementation of AbstractVaultReader isn't in wildfly-core; it's in the wildfly-full security subsystem module.
> This means WildFly Core currently doesn't really support vault expressions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (WFBUILD-11) Add support for assembling the host.xml configuration files.
by Darran Lofthouse (JIRA)
Darran Lofthouse created WFBUILD-11:
---------------------------------------
Summary: Add support for assembling the host.xml configuration files.
Key: WFBUILD-11
URL: https://issues.jboss.org/browse/WFBUILD-11
Project: WildFly Build Tools
Issue Type: Feature Request
Reporter: Darran Lofthouse
Assignee: Stuart Douglas
Fix For: 1.0.0.Alpha7
Now that a host.xml can contain subsystems the same assembly requirements as already apply to standalone.xml and domain.xml are going to be required.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (DROOLS-778) Deserialization error: java.io.InvalidClassException: org.drools.base.evaluators.StrEvaluatorDefinition$StrEvaluator; no valid constructor
by Philip McWilliams (JIRA)
Philip McWilliams created DROOLS-778:
----------------------------------------
Summary: Deserialization error: java.io.InvalidClassException: org.drools.base.evaluators.StrEvaluatorDefinition$StrEvaluator; no valid constructor
Key: DROOLS-778
URL: https://issues.jboss.org/browse/DROOLS-778
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 5.5.0.Final
Environment: Windows 7; Java 6; Drools 5.5.0.Final (incl. drools-core, drools-compiler, drools-spring and drools-camel)
Reporter: Philip McWilliams
Assignee: Mario Fusco
I am seeking to compile rules at build-time and then save (serialize) the output to disk. At deployment, I then wish to build a knowledge base from the deserialized knowledge packages (rather than by re-compiling the source rules files).
In general this works ... unless I use the "str" operator in an LHS. This operator is implemented by the *org.drools.base.evaluators.StrEvaluatorDefinition$StrEvaluator* class and this class does not appear to deserialize properly.
A round trip exercise on my local machine always fails with this error:
{code}
java.io.InvalidClassException: org.drools.base.evaluators.StrEvaluatorDefinition$StrEvaluator; org.drools.base.evaluators.StrEvaluatorDefinition$StrEvaluator; no valid constructor
{code}
My serialization/deserialization code is standard ... to serialize:
{code}
private void saveOutput(KnowledgeBuilder kbuilder) throws IOException {
Collection<KnowledgePackage> kpkgs = kbuilder.getKnowledgePackages();
String outputFilename = outputFile == null ? "" : outputFile.trim();
if (outputFilename.isEmpty()) {
outputFilename = project.getBasedir() + "target/classes/drools.drlx";
}
ObjectOutputStream out = null;
try {
getLog().info("Saving compiled Drools output to " + outputFilename);
out = new ObjectOutputStream(new FileOutputStream(outputFilename));
out.writeObject(kpkgs);
} finally {
if (out != null) {
out.close();
}
}
}
{code}
... to deserialize:
{code}
private Collection<KnowledgePackage> deserializeKnowledgePackages(Resource[] knowledgePackageObjects) throws IOException, ClassNotFoundException {
Collection<KnowledgePackage> knowledgePackages = new ArrayList<KnowledgePackage>();
for (Resource knowledgePackageObject : knowledgePackageObjects) {
LOG.info("Deserializing pre-compiled package " + knowledgePackageObject.getFilename());
ObjectInputStream in = null;
try {
in = new ObjectInputStream(knowledgePackageObject.getInputStream());
// The input stream might contain an individual package or a collection.
knowledgePackages.addAll((Collection<KnowledgePackage>) in.readObject());
} finally {
if (in != null) {
in.close();
}
}
}
return knowledgePackages;
}
{code}
My workaround is to avoid using the "str" operator.
*Apologies*: I have *not* checked version 6.2.0.Final because I have not yet worked out what versions of the Drools Spring and Camel modules to use (for 5.5.0.Final they were all versioned identically).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (WFCORE-129) Overlay does not work for subunits in exploded deployments.
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-129?page=com.atlassian.jira.plugin... ]
Brian Stansberry edited comment on WFCORE-129 at 5/1/15 11:48 AM:
------------------------------------------------------------------
I'm rescheduling items not completed out of 1.0.0 and into 2.0. It sounds like this might be already done though as part of WFCORE-547. If so, please resolve.
was (Author: brian.stansberry):
I'm rescheduling items not completed out of 1.0.0 and into 2.0. It sounds like this might be already done though as part of WFCORE-579. If so, please resolve.
> Overlay does not work for subunits in exploded deployments.
> -----------------------------------------------------------
>
> Key: WFCORE-129
> URL: https://issues.jboss.org/browse/WFCORE-129
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Affects Versions: 1.0.0.Alpha8
> Reporter: Bartosz Baranowski
> Assignee: Bartosz Baranowski
> Fix For: 2.0.0.Alpha1
>
>
> If deployment is exploded and has subdeployments overlay wont work on files contained in said subdeployments.
> Reproducers: https://github.com/baranowb/wildfly/tree/WFCORE-83-TESTS
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (WFCORE-278) Revisit error message for an authentication failure.
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-278?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-278:
------------------------------------
Fix Version/s: 2.0.0.Alpha1
(was: 1.0.0.CR1)
> Revisit error message for an authentication failure.
> ----------------------------------------------------
>
> Key: WFCORE-278
> URL: https://issues.jboss.org/browse/WFCORE-278
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management, Remoting, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 2.0.0.Alpha1
>
>
> After authentication fails in the CLI the following error message is output: -
> {code}
> Unable to authenticate against controller at localhost:9990: Authentication failed: the server presented no authentication mechanisms
> {code}
> This text is a bit misleading, what it actually means is all mechanisms presented have either been excluded or attempted and now no further mechanisms are available to try.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months