[JBoss JIRA] (DROOLS-3689) Duplilcate column structure
by Anna Baker (Jira)
Anna Baker created DROOLS-3689:
----------------------------------
Summary: Duplilcate column structure
Key: DROOLS-3689
URL: https://issues.jboss.org/browse/DROOLS-3689
Project: Drools
Issue Type: Sub-task
Reporter: Anna Baker
Assignee: Mario Fusco
In current implementation of InsertColumn, instance header is duplicated but not property headers. Modify internalExecute of DuplicateColumnCommand to duplicate property headers across an instance column.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3357) Implement filter in the right panel to avoid double mapping of the same property
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3357?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-3357:
-------------------------------------
Description:
Implement a filter in the right panel to avoid double mapping of the same properties. Max one mapping per property per -section (GIVEN/EXPECT)- _instance_.
Make sure the filtering works for both rule-based and DMN-based test scenarios.
was:
Implement a filter in the right panel to avoid double mapping of the same properties. Max one mapping per property per section (GIVEN/EXPECT).
Make sure the filtering works for both rule-based and DMN-based test scenarios.
> Implement filter in the right panel to avoid double mapping of the same property
> --------------------------------------------------------------------------------
>
> Key: DROOLS-3357
> URL: https://issues.jboss.org/browse/DROOLS-3357
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: ScenarioSimulation
>
> Implement a filter in the right panel to avoid double mapping of the same properties. Max one mapping per property per -section (GIVEN/EXPECT)- _instance_.
> Make sure the filtering works for both rule-based and DMN-based test scenarios.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-3678) MVELConcequenceBuilder treats '#' within String incorrectly as a comment at 2nd appearance
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-3678?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-3678:
--------------------------------
Sprint: 2019 Week 08-10
> MVELConcequenceBuilder treats '#' within String incorrectly as a comment at 2nd appearance
> -------------------------------------------------------------------------------------------
>
> Key: DROOLS-3678
> URL: https://issues.jboss.org/browse/DROOLS-3678
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.14.0.Final
> Environment: RHDM 7.2.0
> dialect mvel
> Reporter: Hiroko Miura
> Assignee: Mario Fusco
> Priority: Major
>
> The rule below expects that "B#" is set to value of the fact. However, "B;#"(i.e. ';' added before '#") is set incorrectly
> {noformat}
> dialect "mvel"
>
> rule "testRule"
> when
> $fact : Fact();
> then
> $fact.name = "A#";
> $fact.value = "B#";
> System.out.println( $fact );
> end
> {noformat}
> Here is output.
> {noformat}
> Fact [name=A#, value=B;#]
> {noformat}
> '#' within the value at 2nd appearance is treated as a start of comment.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (JBJCA-1386) TCCL is not set to datasource module
by Stefano Maestri (Jira)
[ https://issues.jboss.org/browse/JBJCA-1386?page=com.atlassian.jira.plugin... ]
Stefano Maestri resolved JBJCA-1386.
------------------------------------
Resolution: Done
> TCCL is not set to datasource module
> ------------------------------------
>
> Key: JBJCA-1386
> URL: https://issues.jboss.org/browse/JBJCA-1386
> Project: IronJacamar
> Issue Type: Bug
> Affects Versions: WildFly/IronJacamar 1.4.2.Final
> Reporter: Bartosz Spyrko-Śmietanko
> Assignee: Bartosz Spyrko-Śmietanko
> Priority: Major
>
> TCCL is not set to datasource module
> User has a datasource that uses ORB classes and is getting a ClassNotFound.
> If a 3rd party JDBC driver implementation is using e. g. CORBA, the class loader is not set and thus the CORBA classes got loaded from the 'org.jboss.as.connector' modules class loader.
> So the root cause is the Thread Context ClassLoader (TCCL) is not set to the classloader/module of the datasource driver module. The particular datasource driver is making using of ORB.init which is a JDK class that looks on the TCCL and other places to load the class specified in ORB.init, but JCA when running has not set the TCCL thus the classes cannot be found.
> Having the TCCL set to the application is how JEE handles related situations to load application classes, so it would make sense that when JCA is running the datasource that it would have the TCCL set to the module of the datasource or a delegate class loader that sees both the datasource module and any other class loader that JCA might need, JBossWS does something similar.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-8136) allow JAX-RS @Produces in CDI @Stereotype
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFLY-8136?page=com.atlassian.jira.plugin.... ]
Marek Kopecký updated WFLY-8136:
--------------------------------
Affects Version/s: 15.0.0.Final
> allow JAX-RS @Produces in CDI @Stereotype
> -----------------------------------------
>
> Key: WFLY-8136
> URL: https://issues.jboss.org/browse/WFLY-8136
> Project: WildFly
> Issue Type: Feature Request
> Components: CDI / Weld, REST
> Affects Versions: 9.0.1.Final, 15.0.0.Final
> Environment: Windows 7, JDK 1.8.0_60
> Reporter: Andreas Klemp
> Assignee: Martin Stefanko
> Priority: Major
>
> A simple JAX-RS REST service can be annotated with @Produces to define the resulting mime-type. However, it is not working anymore, when the annotation is moved to a stereotype. The default application/octet-stream is used.
> {code}
> @Stereotype
> @Produces(MediaType.APPLICATION_JSON)
> @Target(ElementType.TYPE)
> @Retention(RetentionPolicy.RUNTIME)
> public @interface RestService {
> }
> @Path("/some")
> @RestService
> public class SomeRestService {
> @GET
> @Path("/")
> public Response getSome() {
> return Response.ok().entity("{\"x\" : 42, \"y\" : \"foo\"}").build();
> }
> }
> {code}
> Using the following dependencies in Gradle project.
> {noformat}
> providedCompile(
> [group: 'javax.enterprise', name: 'cdi-api', version: '1.2'],
> [group: 'org.jboss.spec.javax.ws.rs', name: 'jboss-jaxrs-api_2.0_spec', version: '1.0.0.Final'],
> [group: 'com.fasterxml.jackson.core', name: 'jackson-databind', version: '2.7.4']
> )
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFCORE-3090) Make script messages around process restarts consistent
by Marek Kopecký (Jira)
[ https://issues.jboss.org/browse/WFCORE-3090?page=com.atlassian.jira.plugi... ]
Marek Kopecký reassigned WFCORE-3090:
-------------------------------------
Assignee: James Perkins
> Make script messages around process restarts consistent
> -------------------------------------------------------
>
> Key: WFCORE-3090
> URL: https://issues.jboss.org/browse/WFCORE-3090
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 8.0.0.Beta5
> Reporter: Brian Stansberry
> Assignee: James Perkins
> Priority: Minor
>
> The message we output when a process is restarted is inconsistent:
> standalone.sh "Restarting application server..."
> domain.sh "Restarting JBoss..."
> standalone.ps1 "Restarting application server..." (from common.ps1)
> domain.ps1 "Restarting application server..." (from common.ps1)
> standalone.bat nothing
> domain.bat nothing
> Problems:
> 1) domain.ps1 is inaccurate as it's not just an application server being restarted
> 2) The bat files are inconsistent with the others
> 3) domain.sh's "Restarting JBoss..." is a bit vague and is odd theoretically given that WildFly Core is meant to be usable for all sorts of things that may not be regarded as "JBoss".
> Perhaps just KISS "Restarting..." in all cases? If we want to keep "application server" for the standalone.xxx cases then common.ps1's function will need to have a param added, and then we need to decide a meaningful value for that param (empty text being a valid choice.)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months