May 2015 - jboss-jira - Jboss List Archives

[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)

11 years, 2 months

1
0
0 / 0

[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)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-579) ProxyMetadataSource does not return JDK8 'default' methods from interfaces

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-579?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-579: ------------------------------------ Fix Version/s: 1.0.0.CR2 (was: 1.0.0.CR1) > ProxyMetadataSource does not return JDK8 'default' methods from interfaces > -------------------------------------------------------------------------- > > Key: WFCORE-579 > URL: https://issues.jboss.org/browse/WFCORE-579 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha19 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[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)

11 years, 2 months

1
0
0 / 0

[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)

11 years, 2 months

1
0
0 / 0

[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 updated WFCORE-129: ------------------------------------ Fix Version/s: 2.0.0.Alpha1 (was: 1.0.0.CR1) 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)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-109) Update syslog handler attributes

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-109?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-109: ------------------------------------ Fix Version/s: 2.0.0.Alpha1 (was: 1.0.0.CR1) > Update syslog handler attributes > -------------------------------- > > Key: WFCORE-109 > URL: https://issues.jboss.org/browse/WFCORE-109 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 2.0.0.Alpha1 > > > The syslog handler does not currently expose the formatter for formatting messages. There will also be changes in a future logmanager release for TCP support and various other properties based on the new TCP support. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-602) Ability to view an objects index of it's position in a list.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-602?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-602: ------------------------------------ Fix Version/s: (was: 1.0.0.CR1) > Ability to view an objects index of it's position in a list. > ------------------------------------------------------------ > > Key: WFCORE-602 > URL: https://issues.jboss.org/browse/WFCORE-602 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Tomaz Cerar > Labels: affects_elytron > > General improvements are being made to the management model for more fine grained manipulation of complex attributes, amongst these changes will be the ability to insert items at a specific position in a list. > This feature request is to ask for the ability to see an items index to identify it's position. > i.e. an end user can call :read-recource and see an items position without needing to count how many items there are in order to identify the position of the next insert. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-602) Ability to view an objects index of it's position in a list.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-602?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-602: ----------------------------------------- This sounds like a structural change to the output format. > Ability to view an objects index of it's position in a list. > ------------------------------------------------------------ > > Key: WFCORE-602 > URL: https://issues.jboss.org/browse/WFCORE-602 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Tomaz Cerar > Labels: affects_elytron > Fix For: 1.0.0.CR1 > > > General improvements are being made to the management model for more fine grained manipulation of complex attributes, amongst these changes will be the ability to insert items at a specific position in a list. > This feature request is to ask for the ability to see an items index to identify it's position. > i.e. an end user can call :read-recource and see an items position without needing to count how many items there are in order to identify the position of the next insert. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-651) Port jboss-as-remoting_1_2.xsd to WildFly Core

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-651?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-651: ------------------------------------ Fix Version/s: 1.0.0.CR2 (was: 1.0.0.CR1) Moving to 1.0.0.CR2, although it's possible we'll defer to 2.0. > Port jboss-as-remoting_1_2.xsd to WildFly Core > ---------------------------------------------- > > Key: WFCORE-651 > URL: https://issues.jboss.org/browse/WFCORE-651 > Project: WildFly Core > Issue Type: Sub-task > Components: Remoting > Reporter: Darran Lofthouse > Assignee: David Lloyd > Fix For: 1.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2015