September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11029) Undelivered messages in remote jca topology after restart

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-11029?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-11029: ------------------------------------- [~mnovak] Are you sure those are the correct logs? I see nothing in the logs that indicates a cluster formation issue on node-3. > Undelivered messages in remote jca topology after restart > --------------------------------------------------------- > > Key: WFLY-11029 > URL: https://issues.jboss.org/browse/WFLY-11029 > Project: WildFly > Issue Type: Bug > Components: Clustering, JMS > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > > There are undelivered messages in scenario with where servers in remote JCA topology are restarted. There are undelivered message after test. > Test scenario: > * Start 2 server in Artemis cluster > * Start 2 servers with MDB connected to Artemis cluster > ** MDB resends messages from InQueue to OutQueue from/to remote cluster > * Send messages to InQueue > * Restart all server (one by one) > * Consumes messages from OutQueue > Results: > After the test there are missing messages in OutQueue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2499) ClassCastException in method mergeNodes in org.drools.core.reteoo.builder.BuildUtils class

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2499?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-2499: ------------------------------------- Can you please provide a reproducer for that CCE? > ClassCastException in method mergeNodes in org.drools.core.reteoo.builder.BuildUtils class > ------------------------------------------------------------------------------------------ > > Key: DROOLS-2499 > URL: https://issues.jboss.org/browse/DROOLS-2499 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.4.1.Final, 7.5.0.Final, 7.6.0.Final, 7.7.0.Final > Reporter: Antonio Morales Nicolás > Assignee: Mario Fusco > Priority: Critical > > java.lang.ClassCastException: org.drools.core.rule.constraint.EvaluatorConstraint cannot be cast to org.drools.core.rule.constraint.MvelConstraint > at org.drools.core.reteoo.builder.BuildUtils.mergeNodes(BuildUtils.java:176) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-395) jboss-app:moduleType should use jee:moduleType as a base

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/JBMETA-395?page=com.atlassian.jira.plugin... ] Richard Opalka updated JBMETA-395: ---------------------------------- Fix Version/s: 12.0.0.Beta1 > jboss-app:moduleType should use jee:moduleType as a base > -------------------------------------------------------- > > Key: JBMETA-395 > URL: https://issues.jboss.org/browse/JBMETA-395 > Project: JBoss Metadata > Issue Type: Bug > Components: ear > Reporter: Rob Stryker > Fix For: 12.0.0.Beta1 > > > While attempting to make a simple ear with a war and a service inside, we run into several validation errors continuously. The following xml, for example, fails to validate: > {code} > <?xml version="1.1" encoding="UTF-8"?> > <jboss-app version="6" xmlns="http://www.jboss.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:jbee="http://www.jboss.com/xml/ns/javaee" > xmlns:jee="http://java.sun.com/xml/ns/javaee" > xsi:schemaLocation=" > http://www.jboss.com/xml/ns/javaee > http://www.jboss.org/schema/jbossas/jboss-app_7_0.xsd"> > <jee:display-name>Test</jee:display-name> > <jee:module> > <jee:web> > <jee:web-uri>myweb.war</jee:web-uri> > <jee:context-root>SomeRoot</jee:context-root> > </jee:web> > <jbee:service>bundled.sar</jbee:service> > </jee:module> > <jbee:distinct-name>MyDistinct</jbee:distinct-name> > </jboss-app> > {code} > The error is: cvc-complex-type.2.4.a: Invalid content was found starting with element 'jbee:service'. One of '{"http:// java.sun.com/xml/ns/javaee":alt-dd}' is expected. > Basically, a jbee:service does not belong inside a jee:module. However, trying to declare jbee:module rather than jee:module fails because: cvc-complex-type.2.4.a: Invalid content was found starting with element 'jbee:module'. One of '{"http:// > java.sun.com/xml/ns/javaee":display-name, "http://java.sun.com/xml/ns/javaee":icon, "http://java.sun.com/ > xml/ns/javaee":initialize-in-order, "http://java.sun.com/xml/ns/javaee":module}' is expected. > In short, jbee:moduleType should probably be using jee:moduleType as a base. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-406) Deprecate ReplicationConfig and remove from next schema version

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/JBMETA-406?page=com.atlassian.jira.plugin... ] Richard Opalka updated JBMETA-406: ---------------------------------- Fix Version/s: 12.0.0.Beta1 > Deprecate ReplicationConfig and remove from next schema version > --------------------------------------------------------------- > > Key: JBMETA-406 > URL: https://issues.jboss.org/browse/JBMETA-406 > Project: JBoss Metadata > Issue Type: Task > Components: web > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 12.0.0.Beta1 > > > This configuration is planning to grow in complexity and is moving into a WildFly subsystem. > See: https://issues.jboss.org/browse/WFLY-5550 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-404) Validation errors with "jboss-web_11_0.xsd

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/JBMETA-404?page=com.atlassian.jira.plugin... ] Richard Opalka updated JBMETA-404: ---------------------------------- Fix Version/s: 12.0.0.Beta1 > Validation errors with "jboss-web_11_0.xsd > ------------------------------------------ > > Key: JBMETA-404 > URL: https://issues.jboss.org/browse/JBMETA-404 > Project: JBoss Metadata > Issue Type: Bug > Affects Versions: 10.0.2.Final > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Fix For: 12.0.0.Beta1 > > > Eclipse reports some errors when validating a "jboss-web.xml" file which defines the 11.0 xsd. > First problem: "web-app_3_1.xsd" is imported. The target namespace seems to be invalid, it should be "http://xmlns.jcp.org/xml/ns/javaee" instead of "http://java.sun.com/xml/ns/javaee" > <xsd:import namespace="http://xmlns.jcp.org/xml/ns/javaee" schemaLocation="http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"/> > The validation error: *"The namespace attribute 'http://java.sun.com/xml/ns/javaee' of an import element information must be identical to the targetNamespace attribute 'http://xmlns.jcp.org/xml/ns/javaee' of the imported document".* > It would probably also make sense to include the full schemaLocation URL ;-). > After fixing the namespace, there are four more errors left: > *src-resolve: Cannot resolve the name 'jboss:jndiEnvironmentRefsGroup' to a( n ) group component > src-resolve: Cannot resolve the name 'javaee:generic-booleanType' to a( n ) 'simpleType definition' component > src-ct.2.1: Complex type definition Representation Error for type 'symbolic-link-allowedType' ... > src-resolve: Cannot resolve the name 'jboss:security-roleType' to a( n ) 'type definition' component* > The first two errors: previous versions of jboss-web.xsd imported "jboss-common_6_0.xsd" which defined a "jndiEnvironmentRefsGroup". This file also imported "javaee_6.xsd", which defines the "generic-booleanType". -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2587) Java 8 and Drools 7.5.0

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2587?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-2587: ------------------------------------- Please provide a reproducer for this issue. > Java 8 and Drools 7.5.0 > ----------------------- > > Key: DROOLS-2587 > URL: https://issues.jboss.org/browse/DROOLS-2587 > Project: Drools > Issue Type: Bug > Components: decision tables > Affects Versions: 7.5.0.Final > Environment: Development > Reporter: Gibran Castillo > Assignee: Mario Fusco > Labels: support > Original Estimate: 1 day > Remaining Estimate: 1 day > > I upgraded my Drools 5.x (drools-compiler 5.2.1.Final, drools-decisiontables 5.4.0.Final, and drools-templates 5.4.0.Final; jbpm-flow 5.1.1.Final, jbpm-bmpn2 5.1.1.Final and with their respective dependencies) Java 1.7.0_21 job to drools 7.5.0 and use kie-api/kie-ci and Java 1.8.0_162; I had to do some refactoring because now drools is part of the KIE (Knowledge Is Everything) umbrella, specifically the code below: > KieServices ks = KieServices.Factory.get(); > KieContainer kc = ks.getKieClasspathContainer(); > KieSession ks = kc.newKieSession("ksession-dtables"); //stateful session > FactHandle fh = ks.insert(fact); > ks.fireAllRules(); > .... > I added the pom.properties file and kmodule.xml file. The java job builds successfully. When I run the java job the packages and rules are loaded into the Knowledge Base but only the first rules fire up and then it stops or ends. > This seems to be a bug in the decision table (spreadsheet), it works with Java 7/Drools 5 but not with Java 8/Drools 7 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-410) IIOPMetaDataParser must support both legacy and new parsing routines

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/JBMETA-410?page=com.atlassian.jira.plugin... ] Richard Opalka updated JBMETA-410: ---------------------------------- Fix Version/s: 12.0.0.Beta1 (was: 11.0.1.Final) > IIOPMetaDataParser must support both legacy and new parsing routines > -------------------------------------------------------------------- > > Key: JBMETA-410 > URL: https://issues.jboss.org/browse/JBMETA-410 > Project: JBoss Metadata > Issue Type: Bug > Components: ejb > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 12.0.0.Beta1 > > > With fix of [BZ-1192591] legacy iiop config parsing routine was discontinued. > Due to backward compatibility issues we need to support both legacy and > new parsing routines. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-410) IIOPMetaDataParser must support both legacy and new parsing routines

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/JBMETA-410?page=com.atlassian.jira.plugin... ] Richard Opalka closed JBMETA-410. --------------------------------- Resolution: Done > IIOPMetaDataParser must support both legacy and new parsing routines > -------------------------------------------------------------------- > > Key: JBMETA-410 > URL: https://issues.jboss.org/browse/JBMETA-410 > Project: JBoss Metadata > Issue Type: Bug > Components: ejb > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 12.0.0.Beta1 > > > With fix of [BZ-1192591] legacy iiop config parsing routine was discontinued. > Due to backward compatibility issues we need to support both legacy and > new parsing routines. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2731) ArrayIndexOutOfBoundsException when updating the rules at the runtime

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2731?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2731. --------------------------------- Resolution: Cannot Reproduce > ArrayIndexOutOfBoundsException when updating the rules at the runtime > --------------------------------------------------------------------- > > Key: DROOLS-2731 > URL: https://issues.jboss.org/browse/DROOLS-2731 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.6.0.Final > Reporter: Bhavneet Singh > Assignee: Mario Fusco > Priority: Blocker > > We update rules at runtime. Sometimes the system reaches a state when it starts throwing error - > java.lang.ArrayIndexOutOfBoundsException: 1 > at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:349) ~[drools-core-7.6.0.Final.jar:7.6.0.Final] > at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:169) ~[drools-core-7.6.0.Final.jar:7.6.0.Final] > at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:127) ~[drools-core-7.6.0.Final.jar:7.6.0.Final] > at org.drools.core.phreak.RuleExecutor.evaluateNetwork(RuleExecutor.java:71) ~[drools-core-7.6.0.Final.jar:7.6.0.Final] > at org.drools.core.common.DefaultAgenda.evaluateEagerList(DefaultAgenda.java:887) ~[drools-core-7.6.0.Final.jar:7.6.0.Final] > at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1061) ~[drools-core-7.6.0.Final.jar:7.6.0.Final] > at org.drools.core.common.DefaultAgenda.internalFireAllRules(DefaultAgenda.java:1014) ~[drools-core-7.6.0.Final.jar:7.6.0.Final] > at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1006) ~[drools-core-7.6.0.Final.jar:7.6.0.Final] > at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1318) ~[drools-core-7.6.0.Final.jar:7.6.0.Final] > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1309) ~[drools-core-7.6.0.Final.jar:7.6.0.Final] > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1293) ~[drools-core-7.6.0.Final.jar:7.6.0.Final] > at com.adobe.sophia.executionlayer.RuleEngine.client.RuleEngineSession.fireAllRules(RuleEngineSession.java:111) ~[Rule-Engine-0.5.4.jar:?] > at com.adobe.sophia.executionlayer.RuleEngine.client.Evaluator.evaluate(Evaluator.java:416) ~[Rule-Engine-0.5.4.jar:?] > at com.adobe.sophia.executionlayer.RuleEngine.client.Evaluator$$FastClassBySpringCGLIB$$cfed13fd.invoke(<generated>) ~[Rule-Engine-0.5.4.jar:?] > at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) ~[spring-core-4.3.4.RELEASE.jar:4.3.4.RELEASE] > at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720) ~[spring-aop-4.3.4.RELEASE.jar:4.3.4.RELEASE] > at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.3.4.RELEASE.jar:4.3.4.RELEASE] > at org.springframework.retry.annotation.AnnotationAwareRetryOperationsInterceptor.invoke(AnnotationAwareRetryOperationsInterceptor.java:156) ~[spring-retry-1.2.2.RELEASE.jar:?] > at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.4.RELEASE.jar:4.3.4.RELEASE] > at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655) ~[spring-aop-4.3.4.RELEASE.jar:4.3.4.RELEASE] > at com.adobe.sophia.executionlayer.RuleEngine.client.Evaluator$$EnhancerBySpringCGLIB$$fb776e74.evaluate(<generated>) ~[Rule-Engine-0.5.4.jar:?] > at com.adobe.sophia.executionlayer.psdk.RuleEngineEvaluator.RuleEvaluator.evaluate(RuleEvaluator.java:393) ~[RuleEvaluator.class:?] > at com.adobe.sophia.executionlayer.psdk.RuleEngineEvaluator.CardRuleEvaluator.evaluate(CardRuleEvaluator.java:117) ~[CardRuleEvaluator.class:?] > at com.adobe.sophia.executionlayer.psdk.content.service.ContentServiceImpl.fetchAllCardsUtilSophia(ContentServiceImpl.java:460) [ContentServiceImpl.class:?] > at com.adobe.sophia.executionlayer.psdk.content.service.ContentServiceImpl.fetchContentGeneric(ContentServiceImpl.java:268) [ContentServiceImpl.class:?] > at com.adobe.sophia.executionlayer.psdk.content.service.ContentServiceImpl.fetchContent(ContentServiceImpl.java:219) [ContentServiceImpl.class:?] > at sun.reflect.GeneratedMethodAccessor269.invoke(Unknown Source) ~[?:?] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_51] > at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_51] > at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180) [cxf-core-3.1.3.jar:3.1.3] > at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) [cxf-core-3.1.3.jar:3.1.3] > at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:200) [cxf-rt-frontend-jaxrs-3.1.3.jar:3.1.3] > at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:99) [cxf-rt-frontend-jaxrs-3.1.3.jar:3.1.3] > at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59) [cxf-core-3.1.3.jar:3.1.3] > at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96) [cxf-core-3.1.3.jar:3.1.3] > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) [cxf-core-3.1.3.jar:3.1.3] > at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-core-3.1.3.jar:3.1.3] > at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:251) [cxf-rt-transports-http-3.1.3.jar:3.1.3] > at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234) [cxf-rt-transports-http-3.1.3.jar:3.1.3] > at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208) [cxf-rt-transports-http-3.1.3.jar:3.1.3] > at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160) [cxf-rt-transports-http-3.1.3.jar:3.1.3] > at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171) [cxf-rt-transports-http-3.1.3.jar:3.1.3] > at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:293) [cxf-rt-transports-http-3.1.3.jar:3.1.3] > at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:212) [cxf-rt-transports-http-3.1.3.jar:3.1.3] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:650) [tomcat7-servlet-3.0-api.jar:?] > at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:268) [cxf-rt-transports-http-3.1.3.jar:3.1.3] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) [catalina.jar:7.0.85] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) [catalina.jar:7.0.85] > at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) [tomcat7-websocket.jar:7.0.85] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) [catalina.jar:7.0.85] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) [catalina.jar:7.0.85] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219) [catalina.jar:7.0.85] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110) [catalina.jar:7.0.85] > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:498) [catalina.jar:7.0.85] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169) [catalina.jar:7.0.85] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) [catalina.jar:7.0.85] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) [catalina.jar:7.0.85] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:445) [catalina.jar:7.0.85] > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1115) [tomcat-coyote.jar:7.0.85] > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637) [tomcat-coyote.jar:7.0.85] > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318) [tomcat-coyote.jar:7.0.85] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_51] > at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-coyote.jar:7.0.85] > at java.lang.Thread.run(Thread.java:745) [?:1.8.0_51] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11055) Port Infinispan subsystem to use generic parser/writer from wildfly-core

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-11055: ----------------------------------- Summary: Port Infinispan subsystem to use generic parser/writer from wildfly-core Key: WFLY-11055 URL: https://issues.jboss.org/browse/WFLY-11055 Project: WildFly Issue Type: Task Components: Clustering Affects Versions: 14.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Port Infinispan subsystem to use generic parser/writer from wildfly-core. Without WFCORE-3939, a new schema will need to be created that conforms to the limitations of PersistentResourceXMLParser. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 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 September 2018