May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2562) [DMN Editor] Graph View - Add support for using User defined data-types

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2562?page=com.atlassian.jira.plugi... ] Jozef Marko edited comment on DROOLS-2562 at 5/21/18 6:11 AM: -------------------------------------------------------------- [~manstis] Thanks, I filed DROOLS-2572 was (Author: jomarko): [~manstis] Thanks filed DROOLS-2572 > [DMN Editor] Graph View - Add support for using User defined data-types > ----------------------------------------------------------------------- > > Key: DROOLS-2562 > URL: https://issues.jboss.org/browse/DROOLS-2562 > Project: Drools > Issue Type: Sub-task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > Decision, BKM and InputData can have an "output data-type" selected. > Add support for selecting User defined types. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2572) [DMN Editor] Graph View - Add support for using Java data-types

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2572?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2572: -------------------------------- Description: Decision, BKM and InputData can have an "output data-type" selected. Add support for selecting Java data types. was: Decision, BKM and InputData can have an "output data-type" selected. Add support for selecting User defined types. > [DMN Editor] Graph View - Add support for using Java data-types > --------------------------------------------------------------- > > Key: DROOLS-2572 > URL: https://issues.jboss.org/browse/DROOLS-2572 > Project: Drools > Issue Type: Sub-task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > > Decision, BKM and InputData can have an "output data-type" selected. > Add support for selecting Java data types. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2571) DRL function import doesn't work using static inner class

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-2571: ------------------------------------- Summary: DRL function import doesn't work using static inner class Key: DROOLS-2571 URL: https://issues.jboss.org/browse/DROOLS-2571 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.7.0.Final Reporter: Tibor Zimányi Assignee: Mario Fusco Priority: Minor When having a test case like this [1], the build ends with errors. See the build output here [2]. To reproduce the issue, just paste the test to ImportsTest test class. [1] https://gist.github.com/baldimir/6d27b37d157abd87b846e0947b1011cb [2] https://gist.github.com/baldimir/71809d454cce4e26ad7080b1fa5655a8 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2268) Disable reliable transmission of SEQUENCER on coordinator change

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2268?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2268: --------------------------- Fix Version/s: 4.0.12 > Disable reliable transmission of SEQUENCER on coordinator change > ---------------------------------------------------------------- > > Key: JGRP-2268 > URL: https://issues.jboss.org/browse/JGRP-2268 > Project: JGroups > Issue Type: Feature Request > Reporter: Kishore Kumar > Assignee: Bela Ban > Priority: Optional > Fix For: 4.0.12 > > > The SEQUENCER protocol ensures that the messages that are not acked by the previous coordinator are forwarded to the new coordinator. This ensures reliable transmission of data. It will be better to have a way to turn off this behavior. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2572) [DMN Editor] Graph View - Add support for using Java data-types

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2572: ----------------------------------- Summary: [DMN Editor] Graph View - Add support for using Java data-types Key: DROOLS-2572 URL: https://issues.jboss.org/browse/DROOLS-2572 Project: Drools Issue Type: Sub-task Components: DMN Editor Reporter: Jozef Marko Assignee: Michael Anstis Decision, BKM and InputData can have an "output data-type" selected. Add support for selecting User defined types. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2570) DRL function import doesn't work using static inner class

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-2570: ------------------------------------- Summary: DRL function import doesn't work using static inner class Key: DROOLS-2570 URL: https://issues.jboss.org/browse/DROOLS-2570 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.7.0.Final Reporter: Tibor Zimányi Assignee: Mario Fusco Priority: Minor When having a test case like this [1], the build ends with errors. See the build output here [2]. To reproduce the issue, just paste the test to ImportsTest test class. [1] https://gist.github.com/baldimir/6d27b37d157abd87b846e0947b1011cb [2] https://gist.github.com/baldimir/71809d454cce4e26ad7080b1fa5655a8 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10394) Lookup using remote-naming context does not work in WildFly 13

by Martin Styk (JIRA)

[ https://issues.jboss.org/browse/WFLY-10394?page=com.atlassian.jira.plugin... ] Martin Styk commented on WFLY-10394: ------------------------------------ Hi, I see the same issues with jboss-client for EAP 7.0.x connecting to EAP CD13. > Lookup using remote-naming context does not work in WildFly 13 > -------------------------------------------------------------- > > Key: WFLY-10394 > URL: https://issues.jboss.org/browse/WFLY-10394 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming > Affects Versions: 13.0.0.Beta1 > Reporter: Michal Jurc > Assignee: David Lloyd > Priority: Blocker > > Upon attempting to lookup a remote EJB using {{jboss-ejb-client}} 2 with {{remote-naming}} context, the following exception is produced clientside: > {code} > Exception in thread "main" org.jboss.naming.remote.protocol.NamingIOException: Failed to lookup [Root exception is java.io.IOException: java.lang.ClassNotFoundException: javax.naming.CompositeName from [Module "org.wildfly.extension.io" version 5.0.0.Beta3 from local module loader @490caf5f (finder: local module finder @6337c201 (roots: /home/mjurc/testing/wildfly/build/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules,/home/mjurc/testing/wildfly/build/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))]] > at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:49) > at org.jboss.naming.remote.protocol.v1.Protocol$1.execute(Protocol.java:104) > at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1.lookup(RemoteNamingStoreV1.java:95) > at org.jboss.naming.remote.client.HaRemoteNamingStore$1.operation(HaRemoteNamingStore.java:276) > at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:137) > at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272) > at org.jboss.naming.remote.client.RemoteContext.lookupInternal(RemoteContext.java:104) > at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:93) > at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:146) > at javax.naming.InitialContext.lookup(InitialContext.java:417) > at client.Client.main(Client.java:22) > Caused by: java.io.IOException: java.lang.ClassNotFoundException: javax.naming.CompositeName from [Module "org.wildfly.extension.io" version 5.0.0.Beta3 from local module loader @490caf5f (finder: local module finder @6337c201 (roots: /home/mjurc/testing/wildfly/build/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules,/home/mjurc/testing/wildfly/build/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] > at org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:177) > at org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:106) > at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:844) > Caused by: java.lang.ClassNotFoundException: javax.naming.CompositeName from [Module "org.wildfly.extension.io" version 5.0.0.Beta3 from local module loader @490caf5f (finder: local module finder @6337c201 (roots: /home/mjurc/testing/wildfly/build/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules,/home/mjurc/testing/wildfly/build/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:374) > at org.jboss.marshalling.AbstractClassResolver.loadClass(AbstractClassResolver.java:123) > at org.jboss.marshalling.AbstractClassResolver.resolveClass(AbstractClassResolver.java:104) > at org.jboss.marshalling.river.RiverUnmarshaller.doReadClassDescriptor(RiverUnmarshaller.java:1022) > at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1351) > at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272) > at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:205) > at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:76) > at org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:170) > ... 8 more > {code} > This is a regression compared to WildFly 12, therefore I am marking this issue as a blocker. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-244) curl -LOk https://dl.google.com/go/go1.10.linux-amd64.tar.gz fails with SSL received a record with an incorrect Message Authentication Code.

by Filip Brychta (JIRA)

Filip Brychta created SWSQE-244: ----------------------------------- Summary: curl -LOk https://dl.google.com/go/go1.10.linux-amd64.tar.gz fails with SSL received a record with an incorrect Message Authentication Code. Key: SWSQE-244 URL: https://issues.jboss.org/browse/SWSQE-244 Project: Kiali QE Issue Type: Bug Reporter: Filip Brychta Assignee: Filip Brychta For some not yet known reason following command: curl -LOk https://dl.google.com/go/go1.10.linux-amd64.tar.gz fails when running from our BOS lab with: curl: (56) SSL received a record with an incorrect Message Authentication Code. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10230) Premature end of file if PathParam and PUT/POST are used together

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-10230?page=com.atlassian.jira.plugin... ] Alessio Soldano reassigned WFLY-10230: -------------------------------------- Assignee: Marek Marusic (was: Alessio Soldano) > Premature end of file if PathParam and PUT/POST are used together > ----------------------------------------------------------------- > > Key: WFLY-10230 > URL: https://issues.jboss.org/browse/WFLY-10230 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 11.0.0.Final > Reporter: Ray Ramos > Assignee: Marek Marusic > > The below fails with "Premature End of File". It is a PUT with a PathParam and a JAXB serializeable entity. > @PUT > @Path("{tenant}") > @Consumes(MediaType.APPLICATION_XML) > public void upsert(@PathParam("tenant") String tenant, DataTransferModel model) > 2:58:03,715 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-2) RESTEASY002005: Failed executing PUT /gateway/tenant: org.jboss.resteasy.plugins.providers.jaxb.JAXBUnmarshalException: javax.xml.bind.UnmarshalException > - with linked exception: > [org.xml.sax.SAXParseException; Premature end of file.] > at org.jboss.resteasy.plugins.providers.jaxb.AbstractJAXBProvider.readFrom(AbstractJAXBProvider.java:136) > at org.jboss.resteasy.core.interception.AbstractReaderInterceptorContext.readFrom(AbstractReaderInterceptorContext.java:66) > at org.jboss.resteasy.core.interception.ServerReaderInterceptorContext.readFrom(ServerReaderInterceptorContext.java:61) > at org.jboss.resteasy.core.interception.AbstractReaderInterceptorContext.proceed(AbstractReaderInterceptorContext.java:56) > at org.jboss.resteasy.security.doseta.DigitalVerificationInterceptor.aroundReadFrom(DigitalVerificationInterceptor.java:36) > at org.jboss.resteasy.core.interception.AbstractReaderInterceptorContext.proceed(AbstractReaderInterceptorContext.java:59) > at org.jboss.resteasy.core.MessageBodyParameterInjector.inject(MessageBodyParameterInjector.java:151) > at org.jboss.resteasy.core.MethodInjectorImpl.injectArguments(MethodInjectorImpl.java:92) > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:115) > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:406) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:213) > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:228) > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) > However, if you remove the PathParam, it works. > @PUT > @Path("tenant") > @Consumes(MediaType.APPLICATION_XML) > public void upsert(DataTransferModel model) > I tried swapping the order of the parameters and I get a "Stream Closed" exception instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10412) [GSS](7.1.z) TLDs under META-INF/resources inside the web-fragment jar is not loaded

by Masafumi Miura (JIRA)

Masafumi Miura created WFLY-10412: ------------------------------------- Summary: [GSS](7.1.z) TLDs under META-INF/resources inside the web-fragment jar is not loaded Key: WFLY-10412 URL: https://issues.jboss.org/browse/WFLY-10412 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 13.0.0.Beta1 Reporter: Masafumi Miura Assignee: Stuart Douglas Attachments: jsp-taglib-jar-in-war.zip TLDs under META-INF/resources inside the web-fragment jar is not loaded. {code:title=directory structure of the web-fragment jar} taglib-jar |-- META-INF | |-- resources | | `-- WEB-INF | | `-- tlds | | `-- hi.tld | `-- web-fragment.xml `-- simple `-- HiTag.class {code} {code:title=web-fragment.xml} <?xml version="1.0" encoding="UTF-8"?> <web-fragment id="WebFragment_ID" version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-fragment_3_0.xsd"> ...(snip)... <jsp-config> <taglib> <taglib-uri>/HiTag</taglib-uri> <taglib-location>/WEB-INF/tlds/hi.tld</taglib-location> </taglib> </jsp-config> </web-fragment> {code} The following ERROR is thrown at the deployment: {code} ERROR [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0074: Could not find TLD /WEB-INF/tlds/hi.tld {code} JSP returns "500 Internal Server Error" and Jastow throws the following ERROR when accessing the JSP which has {{<%@ taglib uri="/HiTag" prefix="say"%>}} or {{<%@ taglib uri="/WEB-INF/tlds/hi.tld" prefix="say"%>}}: {code} ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /taglib-jar-in-war/hi.jsp: org.apache.jasper.JasperException: JBWEB004036: File "/HiTag" not found at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:57) at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:278) at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:75) at org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:171) at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:412) at org.apache.jasper.compiler.Parser.parseDirective(Parser.java:475) at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1459) at org.apache.jasper.compiler.Parser.parse(Parser.java:143) at org.apache.jasper.compiler.ParserController.doParse(ParserController.java:223) at org.apache.jasper.compiler.ParserController.parse(ParserController.java:102) at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:200) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:354) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:334) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:321) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:652) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:358) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:403) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:347) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) ...(snip)... {code} {code} ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /taglib-jar-in-war/index.jsp: org.apache.jasper.JasperException: JBWEB004036: File "/WEB-INF/tlds/hi.tld" not found at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:57) at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:278) at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:75) at org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:171) at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:412) at org.apache.jasper.compiler.Parser.parseDirective(Parser.java:475) at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1459) at org.apache.jasper.compiler.Parser.parse(Parser.java:143) at org.apache.jasper.compiler.ParserController.doParse(ParserController.java:223) at org.apache.jasper.compiler.ParserController.parse(ParserController.java:102) at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:200) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:354) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:334) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:321) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:652) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:358) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:403) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:347) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) ...(snip)... {code} Note that the same war file can be deployed and the JSPs works on Tomcat 8. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2018