December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBVFS-199) RealFileSystem:exists is not case sensitive in windows leading to a compilation failure with undertow and jbossweb

by Enrique González Martínez (JIRA)

[ https://issues.jboss.org/browse/JBVFS-199?page=com.atlassian.jira.plugin.... ] Enrique González Martínez edited comment on JBVFS-199 at 12/18/14 10:29 AM: ---------------------------------------------------------------------------- Problems during VirtualFile::exists If the real root mount point provided to the RealFileSystem is not an exact match (canonical form) if the flag jboss.vfs.forceCaseSensitive is set was (Author: elguardian): Problems during VirtualFile::exists If the real root mount point provided to the RealFileSystem is not an exact match (canonical form). > RealFileSystem:exists is not case sensitive in windows leading to a compilation failure with undertow and jbossweb > ------------------------------------------------------------------------------------------------------------------ > > Key: JBVFS-199 > URL: https://issues.jboss.org/browse/JBVFS-199 > Project: JBoss VFS > Issue Type: Bug > Affects Versions: 3.2.5.Final, 3.5.0.Alpha1 > Environment: Windows 64 bits > JDK 1.7.0_71 > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > Fix For: 3.2.8.Final, 3.5.0.Alpha1 > > > In Wildfly, during jsp compilation the lookup function uses the Classloader::getResourceAsStream that relies on VFSResourceLoader for opening an InputStream. This function is working different due to windows file system (not case sensitive). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-486) cli echo command should not output the result in columns

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-486?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-486: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1173615 > cli echo command should not output the result in columns > -------------------------------------------------------- > > Key: WFCORE-486 > URL: https://issues.jboss.org/browse/WFCORE-486 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > Current implementation of echo command displays the results in columns. Originally its arguments where limited to variables only. Now it also accepts arbitrary text mixed with expressions. So, the logical and expected output would be now the string with the expressions resolved. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBVFS-199) RealFileSystem:exists is not case sensitive in windows leading to a compilation failure with undertow and jbossweb

by Enrique González Martínez (JIRA)

[ https://issues.jboss.org/browse/JBVFS-199?page=com.atlassian.jira.plugin.... ] Enrique González Martínez reopened JBVFS-199: --------------------------------------------- Problems during VirtualFile::exists If the real root mount point provided to the RealFileSystem is not an exact match (canonical form). > RealFileSystem:exists is not case sensitive in windows leading to a compilation failure with undertow and jbossweb > ------------------------------------------------------------------------------------------------------------------ > > Key: JBVFS-199 > URL: https://issues.jboss.org/browse/JBVFS-199 > Project: JBoss VFS > Issue Type: Bug > Affects Versions: 3.2.5.Final, 3.5.0.Alpha1 > Environment: Windows 64 bits > JDK 1.7.0_71 > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > Fix For: 3.2.8.Final, 3.5.0.Alpha1 > > > In Wildfly, during jsp compilation the lookup function uses the Classloader::getResourceAsStream that relies on VFSResourceLoader for opening an InputStream. This function is working different due to windows file system (not case sensitive). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-486) cli echo command should not output the result in columns

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFCORE-486: ---------------------------------------- Summary: cli echo command should not output the result in columns Key: WFCORE-486 URL: https://issues.jboss.org/browse/WFCORE-486 Project: WildFly Core Issue Type: Enhancement Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Current implementation of echo command displays the results in columns. Originally its arguments where limited to variables only. Now it also accepts arbitrary text mixed with expressions. So, the logical and expected output would be now the string with the expressions resolved. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4100) Intermittent failure in org.jboss.as.test.integration.ejb.stateful.passivation.PassivationTestCase

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4100?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-4100: -------------------------------------- Another PassivationTestCase.testPassivationMaxSize failure seen here http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=31906&buildTyp... > Intermittent failure in org.jboss.as.test.integration.ejb.stateful.passivation.PassivationTestCase > -------------------------------------------------------------------------------------------------- > > Key: WFLY-4100 > URL: https://issues.jboss.org/browse/WFLY-4100 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Seems to be a transactional issue with Infinispan eviction. > {noformat} > javax.ejb.EJBException: java.lang.IllegalStateException: WFLYCLEJBINF0008: Stateful session bean {[-89, -53, -3, -58, 52, -115, 78, 79, -106, -9, -119, 3, 0, 35, -10, -106]} refers to an invalid bean group 6c5836ab-086a-464c-8ae9-29e1a79a8254 > at org.wildfly.clustering.ejb.infinispan.bean.InfinispanBeanFactory.createBean(InfinispanBeanFactory.java:75) > at org.wildfly.clustering.ejb.infinispan.InfinispanBeanManager.findBean(InfinispanBeanManager.java:266) > at org.jboss.as.ejb3.cache.distributable.DistributableCache.get(DistributableCache.java:115) > at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:58) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:280) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:345) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:243) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:79) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:44) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:622) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) > at org.jboss.as.ejb3.remote.LocalEjbReceiver.processInvocation(LocalEjbReceiver.java:243) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:184) > at org.jboss.ejb.client.EJBObjectInterceptor.handleInvocation(EJBObjectInterceptor.java:58) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.EJBHomeInterceptor.handleInvocation(EJBHomeInterceptor.java:83) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.as.test.integration.ejb.remote.client.api.interceptor.SimpleEJBClientInterceptor.handleInvocation(SimpleEJBClientInterceptor.java:48) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:125) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:253) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:198) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144) > at com.sun.proxy.$Proxy328.getManagedBeanMessage(Unknown Source) > at org.jboss.as.test.integration.ejb.stateful.passivation.PassivationTestCase.testPassivationMaxSize(PassivationTestCase.java:103) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-670) Using "attribute" tag causes injection of null values

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-670?page=com.atlassian.jira.plugin.s... ] Kabir Khan resolved WFLY-670. ----------------------------- Resolution: Rejected > Using "attribute" tag causes injection of null values > ----------------------------------------------------- > > Key: WFLY-670 > URL: https://issues.jboss.org/browse/WFLY-670 > Project: WildFly > Issue Type: Bug > Components: JMX > Reporter: Anders Welen > Assignee: Tomasz Adamski > Priority: Minor > Fix For: Awaiting Volunteers > > > Using "attribute" tag in "jboss-service.xml" in a SAR archive causes injection of null values. Even if your code can handle this it makes it impossible to use primitive datatypes. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-670) Using "attribute" tag causes injection of null values

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-670?page=com.atlassian.jira.plugin.s... ] Kabir Khan commented on WFLY-670: --------------------------------- It is correct that the JMX spec allows you to put in checks. However, the jboss-service.xml configuration from our SAR format is an extension to the JMX spec. My memory is rusty, but I am 99% sure that the JMX spec itself does not contain any configuration, injection and dependency mechanisms, which is why SAR was invented at JBoss to get around this. This was important since we used the JMX microcontroller based on the SAR format as our mechanism to wire services together since at least JBoss 4 (and pretty sure 3, and perhaps even earlier). So this null on stop/uninjection has always happened using our mechanism for attributes that were set via a jboss-service.xml. So I would say that although this example does not violate the spec, it is a user error not following the rules for something configured via jboss-service.xml. A few suggestions to get around this: * Remove the null check * Provide an alternative setter which does not check for null * Probably the best: Extend ServiceMBeanSupport, then change the setter to only perform this check if in STARTED state, e.g. {code} public class Test extends ServiceMBeanSupport implements TestMBean { private String text; public String getText() { return text; } public void setText(String text) { if (getState() == STARTED && text == null) { throw new NullPointerException("Parameter can not be null"); } this.text = text; } } {code} I don’t remember if ServiceMBeanSupport implementing ServiceMBean is enough, or if you also need to make your TestMBean interface extend ServiceMBean. > Using "attribute" tag causes injection of null values > ----------------------------------------------------- > > Key: WFLY-670 > URL: https://issues.jboss.org/browse/WFLY-670 > Project: WildFly > Issue Type: Bug > Components: JMX > Reporter: Anders Welen > Assignee: Tomasz Adamski > Priority: Minor > Fix For: Awaiting Volunteers > > > Using "attribute" tag in "jboss-service.xml" in a SAR archive causes injection of null values. Even if your code can handle this it makes it impossible to use primitive datatypes. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4171) Provide an html5 archetype for wildfly

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/WFLY-4171?page=com.atlassian.jira.plugin.... ] Rafael Benevides edited comment on WFLY-4171 at 12/18/14 6:48 AM: ------------------------------------------------------------------ I'll start this Jira Tomorrow (Friday) or Monday - I have another issue on DS to finish today before its release on weekend - and I believe that it will take one or two days to conclude it. So until the end of 23th I can have this done. Does that date satisfies the schedule ? Otherwise I can do that at the weekend. was (Author: rafabene): I'll start this Jira Tomorrow (Friday) or Monday - I have another issue on DS to finish today before its release on weekend - and I believe that it will take one or two days to conclude it. So until the end of 23th I can have this done. > Provide an html5 archetype for wildfly > -------------------------------------- > > Key: WFLY-4171 > URL: https://issues.jboss.org/browse/WFLY-4171 > Project: WildFly > Issue Type: Feature Request > Reporter: Fred Bricon > Assignee: Rafael Benevides > > We'd like to provide a Wildfly-ified version of the html5 archetype in JBoss Central, for JBoss Tools and Developer Studio, The current versions we serve right now are : > * org.jboss.aerogear.archetypes:jboss-html5-mobile-archetype:7.1.3.Final > * org.jboss.archetype.wfk:jboss-html5-mobile-archetype:2.6.0.Final -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-112) Move HexConverter main method functions to Main

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-112?page=com.atlassian.jira.plugin.sy... ] Jan Kalina reassigned ELY-112: ------------------------------ Assignee: Jan Kalina > Move HexConverter main method functions to Main > ----------------------------------------------- > > Key: ELY-112 > URL: https://issues.jboss.org/browse/ELY-112 > Project: WildFly Elytron > Issue Type: Task > Components: Utils > Reporter: David Lloyd > Assignee: Jan Kalina > Priority: Minor > Fix For: 1.0.0.Beta1 > > > The HexConverter main routine should be part of the single command-line entry point class, Main. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-112) Move HexConverter main method functions to Main

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-112?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-112: -------------------------------- Main routine is currently also in UsernamePasswordHashUtil - should be also merged into Main class? > Move HexConverter main method functions to Main > ----------------------------------------------- > > Key: ELY-112 > URL: https://issues.jboss.org/browse/ELY-112 > Project: WildFly Elytron > Issue Type: Task > Components: Utils > Reporter: David Lloyd > Priority: Minor > Fix For: 1.0.0.Beta1 > > > The HexConverter main routine should be part of the single command-line entry point class, Main. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 7 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 December 2014