April 2013 - jboss-jira - Jboss List Archives

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

by Keith Babo (JIRA)

[ https://issues.jboss.org/browse/WFLY-1274?page=com.atlassian.jira.plugin.... ] Keith Babo commented on WFLY-1274: ---------------------------------- Camel makes extensive use of beans for configuration of processors, endpoints, and as a container for user-provided logic. The bean registry is pluggable and compatible with CDI/DeltaSpike. In the SwitchYard project, we are able to use CDI in place of Spring as a bean registry provider which works quite nicely for us and in AS in general. In this sense, CDI integration is not required for Camel, it's just really nice to have. http://camel.apache.org/how-does-camel-look-up-beans-and-endpoints.html > 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

1
0
0 / 0

[JBoss JIRA] (WFLY-455) Add LDAP authorization for security realms.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-455?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated WFLY-455: ---------------------------------- Priority: Critical (was: Major) > Add LDAP authorization for security realms. > ------------------------------------------- > > Key: WFLY-455 > URL: https://issues.jboss.org/browse/WFLY-455 > Project: WildFly > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.0.Alpha1 > > > Add support for loading roles from LDAP in security realms. -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-886) JBAS014884: No operation named 'composite' exists at address

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-886?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar edited comment on WFLY-886 at 4/24/13 9:28 AM: ----------------------------------------------------------- I cannot reproduce this problem. Tested with latest WildFly master, EAP 6.1.0.Beta(ER4) and EAP6.1 ER5 was (Author: ctomc): I cannot reproduce this problem. Tested with latest WildFly master, EAP 6.1.0.Beta(ER5) and EAP6.1 ER5 > JBAS014884: No operation named 'composite' exists at address > ------------------------------------------------------------ > > Key: WFLY-886 > URL: https://issues.jboss.org/browse/WFLY-886 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Environment: RHEL 6, JDK 1.7 > Reporter: Van Halbert > Assignee: Tomaz Cerar > > I'm using EAP 6.1 ER5, and trying to execute the following using CLI: > > /profile=ha/subsystem=security/security-domain=teiid-security:add(cache-type=default) > /profile=ha/subsystem=security/security-domain=teiid-security/authentication=classic/:add(login-modules=[{"code"=>"org.jboss.security.auth.spi.UsersRolesLoginModule", "flag"=>"required", "module-options"=>[("usersProperties"=>"${jboss.domain.config.dir}/teiid-security-users.properties"), ("rolesProperties"=>"${jboss.domain.config.dir}/teiid-security-roles.properties")]}]) > but I get the message: > … > "failure-description" => "JBAS014884: No operation named 'composite' exists at address [ > … > (see forum for full discussion) -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-455) Add LDAP authorization for security realms.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-455?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned WFLY-455: ------------------------------------- Assignee: Darran Lofthouse (was: Remy Maucherat) > Add LDAP authorization for security realms. > ------------------------------------------- > > Key: WFLY-455 > URL: https://issues.jboss.org/browse/WFLY-455 > Project: WildFly > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > Add support for loading roles from LDAP in security realms. -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-886) JBAS014884: No operation named 'composite' exists at address

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-886?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar commented on WFLY-886: ---------------------------------- I cannot reproduce this problem. Tested with latest WildFly master, EAP 6.1.0.Beta(ER5) and EAP6.1 ER5 > JBAS014884: No operation named 'composite' exists at address > ------------------------------------------------------------ > > Key: WFLY-886 > URL: https://issues.jboss.org/browse/WFLY-886 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Environment: RHEL 6, JDK 1.7 > Reporter: Van Halbert > Assignee: Tomaz Cerar > > I'm using EAP 6.1 ER5, and trying to execute the following using CLI: > > /profile=ha/subsystem=security/security-domain=teiid-security:add(cache-type=default) > /profile=ha/subsystem=security/security-domain=teiid-security/authentication=classic/:add(login-modules=[{"code"=>"org.jboss.security.auth.spi.UsersRolesLoginModule", "flag"=>"required", "module-options"=>[("usersProperties"=>"${jboss.domain.config.dir}/teiid-security-users.properties"), ("rolesProperties"=>"${jboss.domain.config.dir}/teiid-security-roles.properties")]}]) > but I get the message: > … > "failure-description" => "JBAS014884: No operation named 'composite' exists at address [ > … > (see forum for full discussion) -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-1196) Provide Camel middleware integration

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1196?page=com.atlassian.jira.plugin.... ] Thomas Diesler commented on WFLY-1196: -------------------------------------- There is no dependency on OSGi, except that we register camel context as OSGi services during deployment. They are also registered as MSC services. The other dependency is that we register the Camel modules with the OSGi layer so that Bundle deployments can use the Camel APIs. > Provide Camel middleware integration > ------------------------------------ > > Key: WFLY-1196 > URL: https://issues.jboss.org/browse/WFLY-1196 > Project: WildFly > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Labels: camel > > Provide integration with key middleware services for 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

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: -------------------------------------- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-1196) Provide Camel middleware integration

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-1196?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-1196: ----------------------------------- How is this tied to OSGi? If Camel has a tight integration with OSGi then we have failed. Requirements doc! > Provide Camel middleware integration > ------------------------------------ > > Key: WFLY-1196 > URL: https://issues.jboss.org/browse/WFLY-1196 > Project: WildFly > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Labels: camel > > Provide integration with key middleware services for 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

1
0
0 / 0

[JBoss JIRA] (WFLY-1276) Allow Camel expressions in subsystem configuration

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-1276?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-1276: ----------------------------------- Defining routes in the domain config is specifically not what was agreed upon by the AS and Fuse teams. Is there a requirements doc that outlines the need for this? > Allow Camel expressions in subsystem configuration > -------------------------------------------------- > > Key: WFLY-1276 > URL: https://issues.jboss.org/browse/WFLY-1276 > Project: WildFly > Issue Type: Task > Components: OSGi > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Labels: camel > > We currently support camel system context definitions like this > {code} > <subsystem xmlns="urn:jboss:domain:camel:1.0"> > <camelContext id="system-context-1"> > <![CDATA[ > <route> > <from uri="direct:start"/> > <transform> > <simple>Hello #{body}</simple> > </transform> > </route> > ]]> > </camelContext> > </subsystem> > {code} > This uses a substitution hack for $ -- 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

1
0
0 / 0

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

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-1274?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-1274: ----------------------------------- Why does Camel need CDI integration? What is the nature of this integration? > 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

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