[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 11:38 AM:
----------------------------------------------------------------
We need to at least verify that the camel-cdi component integrates with our cdi subsystem and that it actually works when a cdi/camel deployment gets processed by our DUPs. When such a thing gets deployed, the camel context and its associated routes must work with the components all wired together. I suspect there is work to be done at the DUP level.
was (Author: thomas.diesler):
We need to at least verify that the camel-cdi component integrates with our cdi subsystem and that it actually works when a cdi/camel deployment gets processed by our DUPs. When such a thing gets deployed, the camel context and its associated routes must work with the beans with the components all wired together . I suspect there is work to be done at the DUP level.
> 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
[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:
--------------------------------------
We need to at least verify that the camel-cdi component integrates with our cdi subsystem and that it actually works when a cdi/camel deployment gets processed by our DUPs. When such a thing gets deployed, the camel context and its associated routes must work with the beans with the components all wired together . I suspect there is work to be done at the DUP level.
> 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
[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
13 years
[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
13 years