April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1282) rewrite doesn't support conditions

by Jean-Frederic Clere (JIRA)

Jean-Frederic Clere created WFLY-1282: ----------------------------------------- Summary: rewrite doesn't support conditions Key: WFLY-1282 URL: https://issues.jboss.org/browse/WFLY-1282 Project: WildFly Issue Type: Bug Components: Web (JBoss Web) Reporter: Jean-Frederic Clere Assignee: Jean-Frederic Clere -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1281) Camel integration with JMX

by Thomas Diesler (JIRA)

Thomas Diesler created WFLY-1281: ------------------------------------ Summary: Camel integration with JMX Key: WFLY-1281 URL: https://issues.jboss.org/browse/WFLY-1281 Project: WildFly Issue Type: Sub-task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler -- 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

11 years, 8 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 edited comment on WFLY-1274 at 4/25/13 6:25 AM: --------------------------------------------------------------- A camel context definition may reference beans. There are various ways of wiring these beans and camel provided entities (e.g. the CamelContext) together. We currently support routes defined by Camel API and Spring camel context definitions. There is however a general move toward Blueprint and CDI (i.e. not use Spring) Keith was telling me that [switchyard|http://www.jboss.org/switchyard] also uses CDI as their preferred way of DI. was (Author: thomas.diesler): A camel context definition may reference beans. There are various ways of wiring these beans and camel provided entities (e.g. the CamelContext) together. We currently support routs defined by Camel API and Spring camel context definitions. There is however a general move toward Blueprint and CDI (i.e. not use Spring) Keith was telling me that [switchyard|http://www.jboss.org/switchyard] also uses CDI as their preferred way of DI. > 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-6079) EJB 2.1 CMP configuration options missing (sync-on-commit-only, insert-after-ejb-post-create, call-ejb-store-on-clean)

by Abhi Datt (JIRA)

[ https://issues.jboss.org/browse/AS7-6079?page=com.atlassian.jira.plugin.s... ] Abhi Datt commented on AS7-6079: -------------------------------- Hi, Can you please verify that whether this patch allows "only" these three options: sync-on-commit-only, insert-after-ejb-post-create, call-ejb-store-on-clean OR it also allows the important options like <commit-option>B</commit-option> along with other cache options Thanks > EJB 2.1 CMP configuration options missing (sync-on-commit-only, insert-after-ejb-post-create, call-ejb-store-on-clean) > ---------------------------------------------------------------------------------------------------------------------- > > Key: AS7-6079 > URL: https://issues.jboss.org/browse/AS7-6079 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.0.Alpha1, 7.1.3.Final (EAP) > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.4.Final (EAP) > > > In JBoss AS 7, EJB 2.1 CMP beans cannot configure some options such as sync-on-commit-only and insert-after-ejb-post which were configurable in previous versions of JBoss. > Should also confirm how to configure the rest of the options that were available previously. > <container-configuration> > <container-name>Clustered CMP 2.x EntityBean</container-name> > <call-logging>false</call-logging> > <invoker-proxy-binding-name>clustered-entity-rmi-invoker</invoker-proxy-binding-name> > <sync-on-commit-only>false</sync-on-commit-only> > <insert-after-ejb-post-create>false</insert-after-ejb-post-create> > <container-interceptors> > ... > </container-interceptors> > <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool> > <instance-cache>org.jboss.ejb.plugins.EntityInstanceCache</instance-cache> > <persistence-manager>org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager</persistence-manager> > <locking-policy>org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock</locking-policy> > <container-cache-conf> > <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy> > <cache-policy-conf> > <min-capacity>50</min-capacity> > <max-capacity>1000000</max-capacity> > <overager-period>300</overager-period> > <max-bean-age>600</max-bean-age> > <resizer-period>400</resizer-period> > <max-cache-miss-period>60</max-cache-miss-period> > <min-cache-miss-period>1</min-cache-miss-period> > <cache-load-factor>0.75</cache-load-factor> > </cache-policy-conf> > </container-cache-conf> > <container-pool-conf> > <MaximumSize>100</MaximumSize> > </container-pool-conf> > <commit-option>B</commit-option> > </container-configuration> -- 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

11 years, 8 months

1
0
0 / 0

[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

11 years, 8 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

11 years, 8 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

11 years, 8 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

11 years, 8 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

11 years, 8 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

11 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013