October 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3508) Update juddi to 3.0.4-SNAPSHOT

by Kevin Conner (JIRA)

Update juddi to 3.0.4-SNAPSHOT ------------------------------ Key: JBESB-3508 URL: https://jira.jboss.org/browse/JBESB-3508 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.9 CP1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-3471) CamelGateway does not support JNDI lookups

by David Ward (JIRA)

CamelGateway does not support JNDI lookups ------------------------------------------ Key: JBESB-3471 URL: https://jira.jboss.org/browse/JBESB-3471 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.9 Reporter: David Ward Assignee: David Ward One of the more common Camel components that a user might want to employ is the JMS Component: http://camel.apache.org/jms.html To use this component, one needs to specify the JMS ConnectionFactory. There is a parameter called "connectionFactory", but unfortunately, it does not take a String, but an actual javax.jms.ConnectionFactory. This would be fine if we depended on Spring to wire together the Camel components, but we don't want to enforce that dependency. In the absense of a parameter that simply takes the JNDI name of the ConnectionFactory and does the lookup for us, the CamelGateway should register a Camel TypeConverter that can convert from String (the JNDI name) to a ConnectionFactory (via JNDI lookup). Without this fix, users cannot use the JMS Component. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
18
0 / 0

[JBoss JIRA] Created: (JBESB-3511) JBESB camel integration issue with JPA URI

by Dushman Elvitigala (JIRA)

JBESB camel integration issue with JPA URI ------------------------------------------ Key: JBESB-3511 URL: https://jira.jboss.org/browse/JBESB-3511 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.9 Environment: Windows XP, Java(TM) SE Runtime Environment (build 1.6.0_14-b08) Reporter: Dushman Elvitigala Test was performed with the below configuration: <providers> <camel-provider name="camelProvider1"> <camel-bus busid="camelBus2"> <from uri="jpa://[classname]?persistenceUnit=cdrLoader&consumer.namedQuery=loadRecords" /> </camel-bus> </camel-provider> </providers> <services> <service category="camelDbServiceCategory" name="camelDbService" description="databse service" invmScope="GLOBAL"> <listeners> <camel-gateway name="camelGateway2" busidref="camelBus2" /> </listeners> <actions> <action name="action1" class="org.jboss.soa.esb.actions.SystemPrintln" /> </actions> </service> </services> ===================================================== <persistence-unit name="cdrLoader" transaction-type="RESOURCE_LOCAL"> <non-jta-data-source>java:/cepDS</non-jta-data-source> <class>xxxxxx</class> <properties> <property name="hibernate.archive.autodetection" value="class, hbm" /> <property name="hibernate.dialect" value="org.hibernate.dialect.Oracle10gDialect" /> <property name="hibernate.hbm2ddl.auto" value="update" /> <property name="hibernate.show_sql" value="true" /> <property name="hibernate.format_sql" value="true" /> </properties> </persistence-unit> ====================================================== Exception: ERROR [DefaultErrorHandler] Failed delivery for exchangeId: 3ed796b8-8e03-4538-91d4-e4fded1fdeac. Exhausted after delivery attempt: 1 caught: java.lang.IllegalArgumentException: Value of property 'CamelJpaTemplate' must implement java.io.Serializable. Value is of type org.springframework.orm.jpa.JpaTemplate java.lang.IllegalArgumentException: Value of property 'CamelJpaTemplate' must implement java.io.Serializable. Value is of type org.springframework.orm.jpa.JpaTemplate at org.jboss.internal.soa.esb.message.format.xml.PropertiesImpl.setProperty(PropertiesImpl.java:77) at org.jboss.soa.esb.listeners.gateway.camel.CamelMessageComposer.populateMessage(CamelMessageComposer.java:63) at org.jboss.soa.esb.listeners.gateway.camel.CamelMessageComposer.populateMessage(CamelMessageComposer.java:41) at org.jboss.soa.esb.listeners.message.AbstractMessageComposer.compose(AbstractMessageComposer.java:76) at org.jboss.soa.esb.listeners.gateway.camel.ServiceProcessor.process(ServiceProcessor.java:48) at org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:95) at org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:65) at org.apache.camel.impl.converter.AsyncProcessorTypeConverter$ProcessorToAsyncProcessorBridge.process(AsyncProcessorTypeConverter.java:50) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70) at org.apache.camel.processor.SendProcessor$2.doInAsyncProducer(SendProcessor.java:104) at org.apache.camel.impl.ProducerCache.doInAsyncProducer(ProducerCache.java:272) at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:98) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:98) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:89) at org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:99) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70) at org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:290) at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:202) at org.apache.camel.processor.DefaultChannel.process(DefaultChannel.java:256) at org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:99) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:98) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:89) at org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:91) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:85) at org.apache.camel.component.jpa.JpaConsumer.processBatch(JpaConsumer.java:145) at org.apache.camel.component.jpa.JpaConsumer$1.doInJpa(JpaConsumer.java:95) at org.apache.camel.component.jpa.JpaTemplateTransactionStrategy$1$1.doInJpa(JpaTemplateTransactionStrategy.java:82) at org.springframework.orm.jpa.JpaTemplate.execute(JpaTemplate.java:183) at org.springframework.orm.jpa.JpaTemplate.execute(JpaTemplate.java:146) at org.apache.camel.component.jpa.JpaTemplateTransactionStrategy$1.doInTransaction(JpaTemplateTransactionStrategy.java:80) at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:130) at org.apache.camel.component.jpa.JpaTemplateTransactionStrategy.execute(JpaTemplateTransactionStrategy.java:78) at org.apache.camel.component.jpa.JpaConsumer.poll(JpaConsumer.java:79) at org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:98) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
8
0 / 0

[JBoss JIRA] Created: (JBESB-3523) ESB message store does not contain Sybase SQL

by Julian Coleman (JIRA)

ESB message store does not contain Sybase SQL --------------------------------------------- Key: JBESB-3523 URL: https://jira.jboss.org/browse/JBESB-3523 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store Affects Versions: 4.9 Environment: SOA 5.1.0 ER3 Based on: http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_9_CP1_ER3 revision 35536 Reporter: Julian Coleman Fix For: 4.9 CP1 There is no Sybase SQL in the message store SQL directory: product/services/jbossesb/src/main/resources/message-store-sql Creating a directory "sybase" and copying the files ("create_database.sql" and "drop_database.sql") from the "mssql" directory is a workaround (tested against Sybase ASE 15). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3520) JON Plug-In: Wrong description used for ESB Service Entities

by Larry O'Leary (JIRA)

JON Plug-In: Wrong description used for ESB Service Entities ------------------------------------------------------------ Key: JBESB-3520 URL: https://jira.jboss.org/browse/JBESB-3520 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Environment: JON Plug-In deployed in JON 2.4 JON Plug-In deployed in SOA-P 5.0.0 (admin-console) JON Plug-In deployed in SOA-P 5.0.2 (admin-console) Reporter: Larry O'Leary Viewing an ESB service entity in admin-console shows the same description for all services within a service deployment. For example: <host> -> JBossAS Servers -> JBoss AS 5 (default) -> JBoss ESB -> Deployments -> jbossesb.esb -> Services -> DeadLetterService Service - and - <host> -> JBossAS Servers -> JBoss AS 5 (default) -> JBoss ESB -> Deployments -> jbossesb.esb -> Services -> RedeliverService Service Show the same description. In this case the description shown is for the RedeliverService Service. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-3522) Update jon plugin version

by Kevin Conner (JIRA)

Update jon plugin version ------------------------- Key: JBESB-3522 URL: https://jira.jboss.org/browse/JBESB-3522 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Kevin Conner Priority: Minor Fix For: 4.9 CP1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3521) JON Plug-In: Wrong description used for ESB Service Entities

by Larry O'Leary (JIRA)

JON Plug-In: Wrong description used for ESB Service Entities ------------------------------------------------------------ Key: JBESB-3521 URL: https://jira.jboss.org/browse/JBESB-3521 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Environment: JON Plug-In deployed in JON 2.4 JON Plug-In deployed in SOA-P 5.0.0 (admin-console) JON Plug-In deployed in SOA-P 5.0.2 (admin-console) Reporter: Larry O'Leary Viewing an ESB service entity in admin-console shows the same description for all services within a service deployment. For example: <host> -> JBossAS Servers -> JBoss AS 5 (default) -> JBoss ESB -> Deployments -> jbossesb.esb -> Services -> DeadLetterService Service - and - <host> -> JBossAS Servers -> JBoss AS 5 (default) -> JBoss ESB -> Deployments -> jbossesb.esb -> Services -> RedeliverService Service Show the same description. In this case the description shown is for the RedeliverService Service. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3519) ESB war file generation can create authentication configuration which prevents access

by Kevin Conner (JIRA)

ESB war file generation can create authentication configuration which prevents access ------------------------------------------------------------------------------------- Key: JBESB-3519 URL: https://jira.jboss.org/browse/JBESB-3519 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.9 CP1 The issue is that the generated war file contains an empty auth-constraint tag, which denies all access to the servlet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3518) Add a JAX WS catalog for the juddi webservices

by Kevin Conner (JIRA)

Add a JAX WS catalog for the juddi webservices ---------------------------------------------- Key: JBESB-3518 URL: https://jira.jboss.org/browse/JBESB-3518 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.9 CP1 The CXF integration requires an XML catalog to be specified otherwise it will resolve the schemas/dtds remotely. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2450) Integrate quickstarts into the CI system (again)

by Kevin Conner (JIRA)

Integrate quickstarts into the CI system (again) ------------------------------------------------ Key: JBESB-2450 URL: https://jira.jboss.org/jira/browse/JBESB-2450 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 A lot of quickstarts have been added to the codebase without being integrated into the CI system. We need to identify those which are not integrated and look at adding tests for them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
17
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2010