December 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JASSIST-256) Javassist - add annotation to class doesn't work on reflections

by Rui C. (JIRA)

Rui C. created JASSIST-256: ------------------------------ Summary: Javassist - add annotation to class doesn't work on reflections Key: JASSIST-256 URL: https://issues.jboss.org/browse/JASSIST-256 Project: Javassist Issue Type: Bug Affects Versions: 3.20.0-GA Environment: JDK1.7, IDEA Reporter: Rui C. Assignee: Shigeru Chiba Priority: Minor {code:java} ClassPool pool = ClassPool.getDefault(); CtClass superclass = pool.getCtClass(AbstractEntity.class.getName()); CtClass cc = pool.makeClass("com.rapid.develop.entity.Ponit", superclass); ClassFile ccFile = cc.getClassFile(); ConstPool constpool = ccFile.getConstPool(); AnnotationsAttribute attr = new AnnotationsAttribute(constpool, AnnotationsAttribute.visibleTag); Annotation entityAnno = new Annotation("Entity", constpool); Annotation tableAnno = new Annotation("Table", constpool); tableAnno.addMemberValue("name", new StringMemberValue("test", ccFile.getConstPool())); attr.addAnnotation(entityAnno); attr.addAnnotation(tableAnno); ccFile.addAttribute(attr); Class clazz = cc.toClass(); Object o = clazz.newInstance(); assertTrue(o.getClass().getName().equals("com.rapid.develop.entity.Ponit")); // annotations length = zero java.lang.annotation.Annotation[] annotations = clazz.getDeclaredAnnotations(); assertEquals(2, annotations.length); {code} I used javassist to add annotation for class， I saw these annotations were added to class file. But I can't get them using java API clazz.getDeclaredAnnotations() and clazz.getAnnotations() -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5822) Clustering performance regression in ejbremote-dist-sync scenario

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-5822?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz edited comment on WFLY-5822 at 12/17/15 5:53 PM: --------------------------------------------------------------------- Michal, two points: - can you run an EAP 6.4 stress test with the same debug parameters as specified above and give me a link to the job; I need to compare remote calls for both jobs - what are the steps for adding a Byteman script to the job? I may have to look at writing one. was (Author: rachmato): Michal, what are the steps for adding a Byteman script to the job? I may have to look at writing one. > Clustering performance regression in ejbremote-dist-sync scenario > ------------------------------------------------------------------ > > Key: WFLY-5822 > URL: https://issues.jboss.org/browse/WFLY-5822 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 10.0.0.CR5 > Reporter: Michal Vinkler > Assignee: Richard Achmatowicz > Priority: Critical > > Compared to EAP 6, all SYNC scenarios have the same/better performance except of this one, wonder why? > Compare these results: > stress-ejbremote-dist-sync > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] > --------------------------------------- > Just for comparison: ejbremote REPL_SYNC scenario *performs well* on the other hand: > stress-ejbremote-repl-sync > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5822) Clustering performance regression in ejbremote-dist-sync scenario

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-5822?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on WFLY-5822: ------------------------------------------- Michal, what are the steps for adding a Byteman script to the job? I may have to look at writing one. > Clustering performance regression in ejbremote-dist-sync scenario > ------------------------------------------------------------------ > > Key: WFLY-5822 > URL: https://issues.jboss.org/browse/WFLY-5822 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 10.0.0.CR5 > Reporter: Michal Vinkler > Assignee: Richard Achmatowicz > Priority: Critical > > Compared to EAP 6, all SYNC scenarios have the same/better performance except of this one, wonder why? > Compare these results: > stress-ejbremote-dist-sync > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] > --------------------------------------- > Just for comparison: ejbremote REPL_SYNC scenario *performs well* on the other hand: > stress-ejbremote-repl-sync > 7.0.0.ER2: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...] > 6.4.0.GA: [throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-12) mvn test fails with 'Failed to process feature pack'

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFBUILD-12?page=com.atlassian.jira.plugin... ] Ken Wills commented on WFBUILD-12: ---------------------------------- FWIW, this does occur with maven-3.3 and above, but works fine with maven-3.2.3. With 3.3+, changing the feature pack package type to JAR allows builld & test to run, but obviously doesn't include the plugin.xml. So it looks to me like an issue with the maven plugin builder. > mvn test fails with 'Failed to process feature pack' > ---------------------------------------------------- > > Key: WFBUILD-12 > URL: https://issues.jboss.org/browse/WFBUILD-12 > Project: WildFly Build Tools > Issue Type: Bug > Reporter: Stian Thorgersen > Assignee: Stuart Douglas > > Running 'mvn test' on [wildfly|https://github.com/wildfly/wildfly] fails with: > {code} > [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.Beta1:build (server-provisioning) on project wildfly-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.Beta1:build failed: java.lang.RuntimeException: java.lang.RuntimeException: Failed to process feature pack /home/st/.m2/repository/org/wildfly/wildfly-feature-pack/10.0.0.Alpha6-SNAPSHOT/wildfly-feature-pack-10.0.0.Alpha6-SNAPSHOT.zip modules: Could not extract resources from org.wildfly:wildfly-embedded: /home/st/tmp/wildfly/embedded/target/classes (Is a directory) -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-12) mvn test fails with 'Failed to process feature pack'

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFBUILD-12?page=com.atlassian.jira.plugin... ] Ken Wills edited comment on WFBUILD-12 at 12/17/15 5:33 PM: ------------------------------------------------------------ FWIW, this does occur with maven-3.3 and above, but works fine with maven-3.2.3. With 3.3+, changing the feature pack package type to jar allows builld & test to run, but obviously doesn't include the plugin.xml. So it looks to me like an issue with the maven plugin builder. was (Author: luck3y): FWIW, this does occur with maven-3.3 and above, but works fine with maven-3.2.3. With 3.3+, changing the feature pack package type to JAR allows builld & test to run, but obviously doesn't include the plugin.xml. So it looks to me like an issue with the maven plugin builder. > mvn test fails with 'Failed to process feature pack' > ---------------------------------------------------- > > Key: WFBUILD-12 > URL: https://issues.jboss.org/browse/WFBUILD-12 > Project: WildFly Build Tools > Issue Type: Bug > Reporter: Stian Thorgersen > Assignee: Stuart Douglas > > Running 'mvn test' on [wildfly|https://github.com/wildfly/wildfly] fails with: > {code} > [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.Beta1:build (server-provisioning) on project wildfly-build: Execution server-provisioning of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.0.Beta1:build failed: java.lang.RuntimeException: java.lang.RuntimeException: Failed to process feature pack /home/st/.m2/repository/org/wildfly/wildfly-feature-pack/10.0.0.Alpha6-SNAPSHOT/wildfly-feature-pack-10.0.0.Alpha6-SNAPSHOT.zip modules: Could not extract resources from org.wildfly:wildfly-embedded: /home/st/tmp/wildfly/embedded/target/classes (Is a directory) -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5871) post-binding attribute of PicketLink Federation service provider should be of type Boolean not String

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/WFLY-5871?page=com.atlassian.jira.plugin.... ] Pedro Igor moved JBEAP-2462 to WFLY-5871: ----------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-5871 (was: JBEAP-2462) Workflow: GIT Pull Request workflow (was: CDW v1) Component/s: Security (was: Security) Target Release: (was: 7.0.0.GA) Affects Version/s: 10.0.0.CR4 (was: 7.0.0.ER2 (Beta)) > post-binding attribute of PicketLink Federation service provider should be of type Boolean not String > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-5871 > URL: https://issues.jboss.org/browse/WFLY-5871 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 10.0.0.CR4 > Reporter: Pedro Igor > Assignee: Pedro Igor > Priority: Minor > > Currently type of this attribute is String despite it's description "Indicate if this service provider uses a HTTP POST(true) or REDIRECT(false) binding." > If user tries to write other value than "true" or "false" to this attribute IllegalArgumentException is thrown. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5870) post-binding attribute of PicketLink Federation service provider should be of type Boolean not String

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/WFLY-5870?page=com.atlassian.jira.plugin.... ] Pedro Igor deleted WFLY-5870: ----------------------------- > post-binding attribute of PicketLink Federation service provider should be of type Boolean not String > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-5870 > URL: https://issues.jboss.org/browse/WFLY-5870 > Project: WildFly > Issue Type: Bug > Reporter: Pedro Igor > Assignee: Pedro Igor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5870) post-binding attribute of PicketLink Federation service provider should be of type Boolean not String

by Pedro Igor (JIRA)

Pedro Igor created WFLY-5870: -------------------------------- Summary: post-binding attribute of PicketLink Federation service provider should be of type Boolean not String Key: WFLY-5870 URL: https://issues.jboss.org/browse/WFLY-5870 Project: WildFly Issue Type: Bug Components: Security Affects Versions: 10.0.0.CR4 Reporter: Pedro Igor Assignee: Pedro Igor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-399) More flexible PeerIdentity concept

by David Lloyd (JIRA)

David Lloyd created ELY-399: ------------------------------- Summary: More flexible PeerIdentity concept Key: ELY-399 URL: https://issues.jboss.org/browse/ELY-399 Project: WildFly Elytron Issue Type: Enhancement Components: API / SPI Reporter: David Lloyd Assignee: David Lloyd The existing PeerIdentity APIs aren't working out, because the separation of the PeerIdentity and its backing implementation introduces too much complexity while making it too difficult for service providers to do anything with them. Simplify the API so that PeerIdentity and PeerIdentityContext are (secure) abstract classes which can be extended by providers, which can then use the API directly in a more useful manner. Move responsibility for managing anonymous identities on to the subclass, with the new default being "no identity in particular", which allows e.g. the Remoting provider to default to the connection identity, while other providers can default to the anonymous identity (if there is one). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1237) Remove @Deprecated from ExtensionContext.isRegisterTransformers()

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1237: ---------------------------------------- Summary: Remove @Deprecated from ExtensionContext.isRegisterTransformers() Key: WFCORE-1237 URL: https://issues.jboss.org/browse/WFCORE-1237 Project: WildFly Core Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: 3.0.0.Alpha1 Even if we change how transformers are done, this method could probably be retained for a bit. It's annoying to have a method every extension must invoke giving a deprecation warning for years for something maybe we'll change. And SubsystemRegistration.registerModelTransformers isn't deprecated and its the method far more likely to be broken by any change. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2015