April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-407) Replace the MSC shutdown hook with an AS-specific variant

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-407?page=com.atlassian.jira.plugin.s... ] Thomas Diesler commented on WFLY-407: ------------------------------------- Brian says: The org.jboss.as.controller.ControlledProcessStateService service is meant to be used for this kind of thing. But, the case of stopping via a soft kill instead of a management op isn't properly handled. For that, someone would need to do https://issues.jboss.org/browse/AS7-4492 > Replace the MSC shutdown hook with an AS-specific variant > --------------------------------------------------------- > > Key: WFLY-407 > URL: https://issues.jboss.org/browse/WFLY-407 > Project: WildFly > Issue Type: Task > Components: Domain Management, Server > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > The AS should use its own shutdown hook instead of relying on MSC's, so it can take actions unrelated to MSC shutdown. > See linked forum thread. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1280) Allow OSGi services to be registered as JAX-WS endpoints

by Thomas Diesler (JIRA)

Thomas Diesler created WFLY-1280: ------------------------------------ Summary: Allow OSGi services to be registered as JAX-WS endpoints Key: WFLY-1280 URL: https://issues.jboss.org/browse/WFLY-1280 Project: WildFly Issue Type: Feature Request Components: OSGi, Web Services Reporter: Thomas Diesler Assignee: Thomas Diesler It should be possible to register a WS endpoint similar to this {code} public void start(BundleContext context) { HelloService helloService = new HelloServiceImpl(); Dictionary props = new Hashtable(); props.put("service.exported.interfaces", "*"); props.put("service.exported.configs", "org.apache.cxf.ws"); props.put("org.apache.cxf.ws.address", "http://localhost:8090/soap"); registration = context.registerService(HelloService.class.getName(), helloService, props); } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1280) Allow OSGi services to be registered as JAX-WS endpoints

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1280?page=com.atlassian.jira.plugin.... ] SBS JIRA Integration updated WFLY-1280: --------------------------------------- Forum Reference: https://community.jboss.org/message/805154#805154 > Allow OSGi services to be registered as JAX-WS endpoints > -------------------------------------------------------- > > Key: WFLY-1280 > URL: https://issues.jboss.org/browse/WFLY-1280 > Project: WildFly > Issue Type: Feature Request > Components: OSGi, Web Services > Reporter: Thomas Diesler > Assignee: Thomas Diesler > > It should be possible to register a WS endpoint similar to this > {code} > public void start(BundleContext context) { > HelloService helloService = new HelloServiceImpl(); > Dictionary props = new Hashtable(); > props.put("service.exported.interfaces", "*"); > props.put("service.exported.configs", "org.apache.cxf.ws"); > props.put("org.apache.cxf.ws.address", "http://localhost:8090/soap"); > registration = context.registerService(HelloService.class.getName(), helloService, props); > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1274) Camel integration with CDI

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1274?page=com.atlassian.jira.plugin.... ] Thomas Diesler commented on WFLY-1274: -------------------------------------- Ales says: try Weld 1.2.0.Beta1 (the only CDI+OSGi enabled version) > Camel integration with CDI > -------------------------- > > Key: WFLY-1274 > URL: https://issues.jboss.org/browse/WFLY-1274 > Project: WildFly > Issue Type: Sub-task > Components: OSGi > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Labels: camel > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBEE-125) Batch Applications for the Java Platform (JSR-352)

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-125?page=com.atlassian.jira.plugin.s... ] Shelly McGowan commented on JBEE-125: ------------------------------------- 1.0.0.Alpha1 of the Batch APIs have been released: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... > Batch Applications for the Java Platform (JSR-352) > --------------------------------------------------- > > Key: JBEE-125 > URL: https://issues.jboss.org/browse/JBEE-125 > Project: JBoss JavaEE Spec APIs > Issue Type: Sub-task > Components: jboss-batch-api > Reporter: Shelly McGowan > Assignee: Cheng Fang > Fix For: JavaEE 7 Spec APIs 1.0.0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1279) Logging MBeans have references to a changed when moving to JDK 7

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-1279?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-1279: -------------------------------- Description: See {{PlatformLoggingMXBeanAttributeHandler}} for an example. These should probably be reviewed for logging changes as well. The note: {code} Implementation note: This implementation uses indirect access to the mbean (i.e. via the {@code MBeanServerConnection} API) in order to avoid adding a compile time dependency on JDK 7. If the base JDK requirement for JBoss AS ever moves to JDK 7, this implementation can be updated to use the {@code java.lang.management.PlatformLoggingMXBean} interface. {code} was: See {{PlatformLoggingMXBeanAttributeHandler}} for an example. These should probably be reviewed for logging changes as well. The note: Implementation note: This implementation uses indirect access to the mbean (i.e. via the * {@code MBeanServerConnection} API) in order to avoid adding a compile time dependency on JDK 7. If the base * JDK requirement for JBoss AS ever moves to JDK 7, this implementation can be updated to use the * {@code java.lang.management.PlatformLoggingMXBean} interface. > Logging MBeans have references to a changed when moving to JDK 7 > ---------------------------------------------------------------- > > Key: WFLY-1279 > URL: https://issues.jboss.org/browse/WFLY-1279 > Project: WildFly > Issue Type: Task > Components: JMX > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > See {{PlatformLoggingMXBeanAttributeHandler}} for an example. These should probably be reviewed for logging changes as well. > The note: > {code} > Implementation note: This implementation uses indirect access to the mbean (i.e. via the > {@code MBeanServerConnection} API) in order to avoid adding a compile time dependency on JDK 7. If the base > JDK requirement for JBoss AS ever moves to JDK 7, this implementation can be updated to use the > {@code java.lang.management.PlatformLoggingMXBean} interface. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1279) Logging MBeans should use java.lang.management.PlatformLoggingMXBean

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-1279?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-1279: -------------------------------- Summary: Logging MBeans should use java.lang.management.PlatformLoggingMXBean (was: Logging MBeans have references to a changed when moving to JDK 7) > Logging MBeans should use java.lang.management.PlatformLoggingMXBean > -------------------------------------------------------------------- > > Key: WFLY-1279 > URL: https://issues.jboss.org/browse/WFLY-1279 > Project: WildFly > Issue Type: Task > Components: JMX > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > See {{PlatformLoggingMXBeanAttributeHandler}} for an example. These should probably be reviewed for logging changes as well. > The note: > {code} > Implementation note: This implementation uses indirect access to the mbean (i.e. via the > {@code MBeanServerConnection} API) in order to avoid adding a compile time dependency on JDK 7. If the base > JDK requirement for JBoss AS ever moves to JDK 7, this implementation can be updated to use the > {@code java.lang.management.PlatformLoggingMXBean} interface. > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1279) Logging MBeans have references to a changed when moving to JDK 7

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-1279?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-1279: -------------------------------- Description: See {{PlatformLoggingMXBeanAttributeHandler}} for an example. These should probably be reviewed for logging changes as well. The note: Implementation note: This implementation uses indirect access to the mbean (i.e. via the * {@code MBeanServerConnection} API) in order to avoid adding a compile time dependency on JDK 7. If the base * JDK requirement for JBoss AS ever moves to JDK 7, this implementation can be updated to use the * {@code java.lang.management.PlatformLoggingMXBean} interface. was:See {{PlatformLoggingMXBeanAttributeHandler}} for an example. These should probably be reviewed for logging changes as well. > Logging MBeans have references to a changed when moving to JDK 7 > ---------------------------------------------------------------- > > Key: WFLY-1279 > URL: https://issues.jboss.org/browse/WFLY-1279 > Project: WildFly > Issue Type: Task > Components: JMX > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > > See {{PlatformLoggingMXBeanAttributeHandler}} for an example. These should probably be reviewed for logging changes as well. > The note: > Implementation note: This implementation uses indirect access to the mbean (i.e. via the > * {@code MBeanServerConnection} API) in order to avoid adding a compile time dependency on JDK 7. If the base > * JDK requirement for JBoss AS ever moves to JDK 7, this implementation can be updated to use the > * {@code java.lang.management.PlatformLoggingMXBean} interface. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1279) Logging MBeans have references to a changed when moving to JDK 7

by James Perkins (JIRA)

James Perkins created WFLY-1279: ----------------------------------- Summary: Logging MBeans have references to a changed when moving to JDK 7 Key: WFLY-1279 URL: https://issues.jboss.org/browse/WFLY-1279 Project: WildFly Issue Type: Task Components: JMX Reporter: James Perkins Assignee: James Perkins Priority: Minor See {{PlatformLoggingMXBeanAttributeHandler}} for an example. These should probably be reviewed for logging changes as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-939) Class-Path manifest entries for WARs-in-EAR not handled properly

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-939?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved WFLY-939. --------------------------------- Fix Version/s: 8.0.0.Alpha1 Resolution: Done > Class-Path manifest entries for WARs-in-EAR not handled properly > ---------------------------------------------------------------- > > Key: WFLY-939 > URL: https://issues.jboss.org/browse/WFLY-939 > Project: WildFly > Issue Type: Bug > Components: Server > Reporter: James Livingston > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > ManifestClassPathProcessor handles the processing of Class-Path entries in deployments. The handling of those entries in sub-deployments is broken. > https://github.com/doctau/examples/tree/master/war-manifest-classpath builds an EAR containing a utility JAR and two WARs, where both WARs refer to the jar via Class-Path manifest headers. The jar is not in the EAR's library directory nor in application.xml > The resulting module setup will result in the jar being added to the first WAR's module, and the remaining WAR(s) depending on a separate "jar classloader". All WARs should depend on the single shared jar classloader. > When ManifestClassPathProcessor.handlingExistingClassPathEntry() runs for the first war, it will call createAdditionalModule(), which calls createResourceRoot(). The "deploymentUnit.addToAttachmentList(Attachments.RESOURCE_ROOTS, resourceRoot)" adds it to the resource roots for that WAR. > When handlingExistingClassPathEntry() runs for the second (and subsequent) WAR, it will already be in the additionalModules list, so "target.addToAttachmentList(Attachments.CLASS_PATH_ENTRIES, moduleSpecification.getModuleIdentifier())" gets run. > I believe the step of adding it to the CLASS_PATH_ENTRIES attachment needs to happen on the first WAR (so it is added as a module dependency), and it should not be added to the DU RESOURCE_ROOTS so it is not in the WAR's own classloader. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 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 April 2013