November 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3354) samples/quickstarts/http_gateway/readme.txt - refers to "http-listener" - should refer to http-gateway

by Len DiMaggio (JIRA)

samples/quickstarts/http_gateway/readme.txt - refers to "http-listener" - should refer to http-gateway ------------------------------------------------------------------------------------------------------ Key: JBESB-3354 URL: https://jira.jboss.org/browse/JBESB-3354 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, Examples Affects Versions: 4.8 Reporter: Len DiMaggio Priority: Minor samples/quickstarts/http_gateway/readme.txt - refers to "http-listener" - should refer to http-gateway samples/quickstarts/http_gateway/readme.txt: service. Will return some details about the request. This Service's <http-listener> does not refer -- 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

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3528) Replace references to jboss.esb.bind.address within esb.juddi.client.xml

by Kevin Conner (JIRA)

Replace references to jboss.esb.bind.address within esb.juddi.client.xml ------------------------------------------------------------------------ Key: JBESB-3528 URL: https://jira.jboss.org/browse/JBESB-3528 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kevin Conner This configuration is intended for access to remote juddi endpoints however the use of this property suggests it can be used locally. -- 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

15 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3525) Add support for scheduled connectors in camel gateway

by Kevin Conner (JIRA)

Add support for scheduled connectors in camel gateway ----------------------------------------------------- Key: JBESB-3525 URL: https://jira.jboss.org/browse/JBESB-3525 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.9 Reporter: Kevin Conner Fix For: 4.9 CP1 The CamelGateway provides a mechanism via which we can integrate the connectors provided within camel however, as it currently stands, we have no mechanism for supporting scheduled behaviour. -- 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

15 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-3516) generatePackageFile in business_ruleservice_ruleAgent QS fails

by Kevin Conner (JIRA)

generatePackageFile in business_ruleservice_ruleAgent QS fails -------------------------------------------------------------- Key: JBESB-3516 URL: https://jira.jboss.org/browse/JBESB-3516 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.9 Reporter: 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

15 years, 2 months

2
2
0 / 0

[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

15 years, 2 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

15 years, 2 months

3
18
0 / 0

[JBoss JIRA] Created: (JBESB-3526) CamelGatewayMapper failing to parse endpoint URIs containing invalid URI characters

by Tom Fennelly (JIRA)

CamelGatewayMapper failing to parse endpoint URIs containing invalid URI characters ----------------------------------------------------------------------------------- Key: JBESB-3526 URL: https://jira.jboss.org/browse/JBESB-3526 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.9 Reporter: Tom Fennelly Assignee: Tom Fennelly Some of the Camel components support query params that can contain invalid URI chars (e.g. spaces). Camel handles this by encoding the URI using org.apache.camel.util.UnsafeUriCharactersEncoder.endoce(String) before it tries to parse it as a URI. Our CamelGatewayMapper (createURI method) barfs on such URIs because it doesn't perform such an encoding first. -- 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

15 years, 2 months

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

15 years, 2 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

15 years, 2 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues November 2010