September 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1238) Decrease code duplication in the Quickstarts.

by Kurt Stam (JIRA)

Decrease code duplication in the Quickstarts. ---------------------------------------------- Key: JBESB-1238 URL: http://jira.jboss.com/jira/browse/JBESB-1238 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 IR1 Reporter: Kurt Stam Assigned To: Mark Little Fix For: 4.2.1 The quickstarts use classes like Send- and ReceiveJMSMessage. These classes are copied across many QSs, and are starting to lead their own life, which makes it hard to maintain them. We should extract these common classes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

5
12
0 / 0

[JBoss JIRA] Created: (JBESB-807) JBossRemotingGateway doesn't support Http BASIC Auth (and probably more)

by Tom Fennelly (JIRA)

JBossRemotingGateway doesn't support Http BASIC Auth (and probably more) ------------------------------------------------------------------------ Key: JBESB-807 URL: http://jira.jboss.com/jira/browse/JBESB-807 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 Talked with Ron Sigal and he thinks we might have to explicitly use the Servlet transport (i.e. the CoyoteInvoker might not be configurable for BASIC auth). Here's what Ron said exactly..... "1. HTTPServerInvoker is obsolete. It's been replaced by CoyoteInvoker. 2. According to my O'Reilly Tomcat book, BASIC authorization is configured in the web.xml file by the <login-config> element. But CoyoteInvoker doesn't use the full Tomcat implementation, just the Coyote adapter. I'm really not sure if the Coyote adapter has anything to do with the web.xml file. 3. There is another Remoting transport, the servlet transport, which really does use Tomcat. It uses a servlet as a front end to the server invoker. There's even a web.xml file: src\etc\web\web.xml in the Remoting project directory." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
11
0 / 0

[JBoss JIRA] Created: (JBESB-476) Make action, listener etc configuration setting by setter method the default

by Tom Fennelly (JIRA)

Make action, listener etc configuration setting by setter method the default ---------------------------------------------------------------------------- Key: JBESB-476 URL: http://jira.jboss.com/jira/browse/JBESB-476 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.2 We currently configure everything by constructor. This is not great for a number of reasons: 1. It can't be compile time validated. 2. Not as "obvious" to someone developing against the API. If in an interface, their IDE (or at least compiler - if using a stone ax) will complain immediately that they're not implementing the interface correctly. 3. Makes our code a little bit more complicated re the reflection code that needs to be implemented. So I suggest making the interface (that all these things implement) contain a setter method that takes the config. The mandate on the implementation is that they contain a public default constructor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
12
0 / 0

[JBoss JIRA] Created: (JBESB-2077) Missing/broken dependency for Management

by Jiri Pechanec (JIRA)

Missing/broken dependency for Management ---------------------------------------- Key: JBESB-2077 URL: https://jira.jboss.org/jira/browse/JBESB-2077 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.4 Reporter: Jiri Pechanec Priority: Critical In version IR4 and previous the log during startup conatined this messages - Note that the message about startup is the last one 2008-09-29 09:20:01,553 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, management.esb 2008-09-29 09:20:01,564 INFO [org.jboss.jms.server.destination.QueueService] Queue[/queue/DataFilerQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000 2008-09-29 09:20:01,571 INFO [org.jboss.jms.server.destination.QueueService] Queue[/queue/OperationsFilerQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000 2008-09-29 09:20:01,582 INFO [org.jboss.jms.server.destination.QueueService] Queue[/queue/InvokerFilerQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000 2008-09-29 09:20:01,934 INFO [org.quartz.core.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. 2008-09-29 09:20:01,943 INFO [org.jboss.internal.soa.esb.dependencies.DatabaseInitializer] Initializing java:/ManagementDS from listed sql files 2008-09-29 09:20:01,949 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/jbossesb, warUrl=.../tmp/deploy/tmp3371management.esb-contents/jbossesb-exp.war/ 2008-09-29 09:20:02,099 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, slsb.esb 2008-09-29 09:20:02,143 INFO [org.quartz.core.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. 2008-09-29 09:20:05,033 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, smooks.esb 2008-09-29 09:20:05,048 INFO [org.jboss.jms.server.destination.TopicService] Topic[/topic/org.jboss.soa.esb.transformation.Update] started, fullSize=200000, pageSize=2000, downCacheSize=2000 2008-09-29 09:20:05,086 INFO [org.jboss.soa.esb.actions.converters.SmooksService] Centralized Smooks Instance (Console Based) instance not started. See the 'console.url' property in '/smooks.esb.properties' 2008-09-29 09:20:05,161 INFO [org.quartz.core.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. 2008-09-29 09:20:08,209 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, soap.esb 2008-09-29 09:20:08,272 INFO [org.quartz.core.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. 2008-09-29 09:20:09,492 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, spring.esb 2008-09-29 09:20:09,523 INFO [org.quartz.core.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. 2008-09-29 09:20:09,610 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [SOA_4.3.0.GA_IR4 (build: SVNTag=SOA_4.3.0.GA_IR4 date=200809041212)] Started in 1m:9s:902ms In version IR5 there is a message 2008-09-29 09:23:25,425 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [SOA_4.3.0.IR5 (build: SVNTag=SOA_4.3.0.IR5 date=200809251150)] Started in 59s:126ms but the initalization still continues 2008-09-29 09:23:22,307 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, management.esb 2008-09-29 09:23:22,321 INFO [org.jboss.jms.server.destination.QueueService] Queue[/queue/DataFilerQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000 2008-09-29 09:23:22,328 INFO [org.jboss.jms.server.destination.QueueService] Queue[/queue/OperationsFilerQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000 2008-09-29 09:23:22,330 INFO [org.jboss.jms.server.destination.QueueService] Queue[/queue/InvokerFilerQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000 2008-09-29 09:23:22,415 INFO [org.quartz.core.QuartzScheduler] Scheduler ScheduleProviderScheduler_$_NON_CLUSTERED started. 2008-09-29 09:23:23,272 INFO [org.jboss.internal.soa.esb.dependencies.DatabaseInitializer] java:/ManagementDS datasource is already initialized 2008-09-29 09:23:23,274 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/jbossesb, warUrl=.../tmp/deploy/tmp64795management.esb-contents/jbossesb-exp.war/ 2008-09-29 09:23:23,333 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, slsb.esb 2008-09-29 09:23:23,375 INFO [org.quartz.core.QuartzScheduler] Scheduler ScheduleProviderScheduler_$_NON_CLUSTERED started. 2008-09-29 09:23:23,845 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, smooks.esb 2008-09-29 09:23:23,849 INFO [org.jboss.jms.server.destination.TopicService] Topic[/topic/org.jboss.soa.esb.transformation.Update] started, fullSize=200000, pageSize=2000, downCacheSize=2000 2008-09-29 09:23:23,861 INFO [org.jboss.soa.esb.actions.converters.SmooksService] Centralized Smooks Instance (Console Based) instance not started. See the 'console.url' property in '/smooks.esb.properties' 2008-09-29 09:23:23,938 INFO [org.quartz.core.QuartzScheduler] Scheduler ScheduleProviderScheduler_$_NON_CLUSTERED started. 2008-09-29 09:23:24,046 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, soap.esb 2008-09-29 09:23:24,127 INFO [org.quartz.core.QuartzScheduler] Scheduler ScheduleProviderScheduler_$_NON_CLUSTERED started. 2008-09-29 09:23:25,274 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, spring.esb 2008-09-29 09:23:25,330 INFO [org.quartz.core.QuartzScheduler] Scheduler ScheduleProviderScheduler_$_NON_CLUSTERED started. 2008-09-29 09:23:25,425 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [SOA_4.3.0.IR5 (build: SVNTag=SOA_4.3.0.IR5 date=200809251150)] Started in 59s:126ms 2008-09-29 09:23:34,092 INFO [org.hibernate.cfg.Configuration] configuring from resource: monitoring.cfg.xml 2008-09-29 09:23:34,092 INFO [org.hibernate.cfg.Configuration] Configuration resource: monitoring.cfg.xml 2008-09-29 09:23:34,097 INFO [org.hibernate.cfg.Configuration] Reading mappings from resource : org/jboss/soa/esb/monitoring/monitoring-mappings.hbm.xml 2008-09-29 09:23:34,104 INFO [org.hibernate.cfg.HbmBinder] Mapping class: org.jboss.soa.esb.monitoring.pojo.JMXPattern -> JMXPATTERN 2008-09-29 09:23:34,105 INFO [org.hibernate.cfg.HbmBinder] Mapping class: org.jboss.soa.esb.monitoring.pojo.JMXData -> JMXDATA 2008-09-29 09:23:34,108 INFO [org.hibernate.cfg.HbmBinder] Mapping class: org.jboss.soa.esb.monitoring.pojo.JMXOperationResult -> JMXOPERATIONRESULT 2008-09-29 09:23:34,119 INFO [org.hibernate.cfg.HbmBinder] Mapping class: org.jboss.soa.esb.monitoring.pojo.JMXAttribute -> JMXATTRIBUTE 2008-09-29 09:23:34,119 INFO [org.hibernate.cfg.HbmBinder] Mapping class: org.jboss.soa.esb.monitoring.pojo.JMXOperation -> JMXOPERATION 2008-09-29 09:23:34,120 INFO [org.hibernate.cfg.Configuration] Configured SessionFactory: null 2008-09-29 09:23:34,121 INFO [org.hibernate.util.NamingHelper] JNDI InitialContext properties:{} 2008-09-29 09:23:34,121 INFO [org.hibernate.connection.DatasourceConnectionProvider] Using datasource: java:/ManagementDS 2008-09-29 09:23:34,129 INFO [org.hibernate.cfg.SettingsFactory] RDBMS: HSQL Database Engine, version: 1.8.0 2008-09-29 09:23:34,129 INFO [org.hibernate.cfg.SettingsFactory] JDBC driver: HSQL Database Engine Driver, version: 1.8.0 2008-09-29 09:23:34,207 INFO [org.hibernate.dialect.Dialect] Using dialect: org.hibernate.dialect.HSQLDialect 2008-09-29 09:23:34,212 INFO [org.hibernate.transaction.TransactionFactoryFactory] Using default transaction strategy (direct JDBC transactions) 2008-09-29 09:23:34,214 INFO [org.hibernate.transaction.TransactionManagerLookupFactory] No TransactionManagerLookup configured (in JTA environment, use of read-write or transactional second-level cache is not recommended) 2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Automatic flush during beforeCompletion(): disabled 2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Automatic session close at end of transaction: disabled 2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] JDBC batch size: 15 2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] JDBC batch updates for versioned data: disabled 2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Scrollable result sets: enabled 2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] JDBC3 getGeneratedKeys(): disabled 2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Connection release mode: auto 2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Default batch fetch size: 1 2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Generate SQL with comments: disabled 2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Order SQL updates by primary key: disabled 2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Order SQL inserts for batching: disabled 2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory 2008-09-29 09:23:34,215 INFO [org.hibernate.hql.ast.ASTQueryTranslatorFactory] Using ASTQueryTranslatorFactory 2008-09-29 09:23:34,215 INFO [org.hibernate.cfg.SettingsFactory] Query language substitutions: {} 2008-09-29 09:23:34,215 INFO [org.hibernate.cfg.SettingsFactory] JPA-QL strict compliance: disabled 2008-09-29 09:23:34,215 INFO [org.hibernate.cfg.SettingsFactory] Second-level cache: enabled 2008-09-29 09:23:34,215 INFO [org.hibernate.cfg.SettingsFactory] Query cache: disabled 2008-09-29 09:23:34,215 INFO [org.hibernate.cfg.SettingsFactory] Cache provider: org.hibernate.cache.NoCacheProvider 2008-09-29 09:23:34,216 INFO [org.hibernate.cfg.SettingsFactory] Optimize cache for minimal puts: disabled 2008-09-29 09:23:34,216 INFO [org.hibernate.cfg.SettingsFactory] Structured second-level cache entries: disabled 2008-09-29 09:23:34,216 INFO [org.hibernate.cfg.SettingsFactory] Statistics: disabled 2008-09-29 09:23:34,216 INFO [org.hibernate.cfg.SettingsFactory] Deleted entity synthetic identifier rollback: disabled 2008-09-29 09:23:34,216 INFO [org.hibernate.cfg.SettingsFactory] Default entity-mode: pojo 2008-09-29 09:23:34,217 INFO [org.hibernate.cfg.SettingsFactory] Named query checking : enabled 2008-09-29 09:23:34,225 INFO [org.hibernate.impl.SessionFactoryImpl] building session factory 2008-09-29 09:23:34,351 INFO [org.hibernate.impl.SessionFactoryObjectFactory] Factory name: java:/hibernate/MonitoringSessionFactory 2008-09-29 09:23:34,351 INFO [org.hibernate.util.NamingHelper] JNDI InitialContext properties:{} 2008-09-29 09:23:34,352 INFO [org.hibernate.util.NamingHelper] Creating subcontext: hibernate 2008-09-29 09:23:34,352 INFO [org.hibernate.impl.SessionFactoryObjectFactory] Bound factory to JNDI name: java:/hibernate/MonitoringSessionFactory 2008-09-29 09:23:34,352 WARN [org.hibernate.impl.SessionFactoryObjectFactory] InitialContext did not implement EventContext -- 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, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-785) specify a (non-default) jboss profile when running the HelloWorld esb wizard

by Johnathon Lee (JIRA)

specify a (non-default) jboss profile when running the HelloWorld esb wizard ---------------------------------------------------------------------------- Key: JBESB-785 URL: http://jira.jboss.com/jira/browse/JBESB-785 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: Johnathon Lee Assigned To: Mark Little Attachments: profileSelection.txt When running the esb HelloWorld wizard the "default" profile is assumed. Enable selection of a different profile and storing of the profile selection via preferences -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
9
0 / 0

[JBoss JIRA] Created: (JBESB-1485) Project bug for SOA-P JIRA SOA-311

by Len DiMaggio (JIRA)

Project bug for SOA-P JIRA SOA-311 ---------------------------------- Key: JBESB-1485 URL: http://jira.jboss.com/jira/browse/JBESB-1485 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Len DiMaggio Assigned To: Mark Little ESB project bug for SOA-P JIRA: http://jira.jboss.com/jira/browse/SOA-311 OutOfMemory Errors on webservice_bpel quickstart -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
12
0 / 0

[JBoss JIRA] Created: (JBESB-834) Include Smooks documentation in release

by Mark Little (JIRA)

Include Smooks documentation in release --------------------------------------- Key: JBESB-834 URL: http://jira.jboss.com/jira/browse/JBESB-834 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Tom Fennelly On behalf of intern: "It would be nice if the Smooks docs were included in the distribution. In general, it would be nice if all 3rd party libs that the user may need to play with have some form of self-contained docs." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-556) Make the webservice_bpel quickstart into a Trailblazer

by Tom Fennelly (JIRA)

Make the webservice_bpel quickstart into a Trailblazer ------------------------------------------------------ Key: JBESB-556 URL: http://jira.jboss.com/jira/browse/JBESB-556 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 This is really a Trailblazer - too much in it to be a QS -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-1691) MRG/RHM support

by Mark Little (JIRA)

MRG/RHM support --------------- Key: JBESB-1691 URL: http://jira.jboss.com/jira/browse/JBESB-1691 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 CP2 Reporter: Mark Little -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1429) Need an MBean for CronExpressions

by Tom Cunningham (JIRA)

Need an MBean for CronExpressions --------------------------------- Key: JBESB-1429 URL: http://jira.jboss.com/jira/browse/JBESB-1429 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.2.1 Reporter: Tom Cunningham Assigned To: Tom Cunningham Need a way of dynamically updating a cron expression at runtime. MBean probably would be the preferable method for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2008