August 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2756) No quickstart for http-provider

by Aaron Pestel (JIRA)

No quickstart for http-provider ------------------------------- Key: JBESB-2756 URL: https://jira.jboss.org/jira/browse/JBESB-2756 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.6 Environment: JBoss ESB 4.6 Reporter: Aaron Pestel We need a quickstart for http-provider. I'm attaching one I got from Burr previously. It doesn't seem to work out of the box for me, but may be a good place to start. -- 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, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-2625) Add v1.2 XSD

by Tom Fennelly (JIRA)

Add v1.2 XSD ------------ Key: JBESB-2625 URL: https://jira.jboss.org/jira/browse/JBESB-2625 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.6 -- 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, 8 months

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-2473) http-listener: Add security related intergration code e.g. mapping auth info onto message etc

by Tom Fennelly (JIRA)

http-listener: Add security related intergration code e.g. mapping auth info onto message etc --------------------------------------------------------------------------------------------- Key: JBESB-2473 URL: https://jira.jboss.org/jira/browse/JBESB-2473 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta, Transports Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.4 FP1 At the moment, the new http-listener allows you to specify a user configured web.xml. Should also allow specification of a jboss-web.xml. -- 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, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-2618) Merge new http gateway across to trunk

by Kevin Conner (JIRA)

Merge new http gateway across to trunk -------------------------------------- Key: JBESB-2618 URL: https://jira.jboss.org/jira/browse/JBESB-2618 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Tom Fennelly Fix For: 4.6 Move the version in the FP release across. -- 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, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-2757) Implement a common codebase on which war based sub deployments (gateways etc) can be based

by Tom Fennelly (JIRA)

Implement a common codebase on which war based sub deployments (gateways etc) can be based ------------------------------------------------------------------------------------------ Key: JBESB-2757 URL: https://jira.jboss.org/jira/browse/JBESB-2757 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta, Transports Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.7 This is to accommodate merging of EBWS and HttpGateway war deployment requirements in a single "per .esb" war sub deployment. -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2769) Upgrade groovy to 1.5.4

by Kevin Conner (JIRA)

Upgrade groovy to 1.5.4 ----------------------- Key: JBESB-2769 URL: https://jira.jboss.org/jira/browse/JBESB-2769 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Scripting Affects Versions: 4.6 Reporter: Kevin Conner Fix For: 4.7 This brings it in line with seam/EAP 5. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2806) EBWS creates SOAP message factory with every request

by Martin Vecera (JIRA)

EBWS creates SOAP message factory with every request ---------------------------------------------------- Key: JBESB-2806 URL: https://jira.jboss.org/jira/browse/JBESB-2806 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.4 CP3 Environment: SOA-P 4.3.CP02 CR2 Reporter: Martin Vecera Priority: Blocker Every request to an ESB service published via EBWS requests can request several new SOAP message factories (at least one is created) - lookup javax.xml.soap.MessageFactory.newInstance() in org.jboss.internal.soa.esb.webservice.BaseWebService. With a scenario, which causes ESB to create only one new message factory for a request, a 13% overhead is introduced. -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2790) wsdl link broken in the jbossesb contract page.

by Jeff Yu (JIRA)

wsdl link broken in the jbossesb contract page. ----------------------------------------------- Key: JBESB-2790 URL: https://jira.jboss.org/jira/browse/JBESB-2790 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.6 Environment: Fedora Reporter: Jeff Yu Fix For: 4.7 Build a web service proxy for ESB service, like webservice_producer example, I can publish it successfully, however, if I log into the http://localhost:8080/contract, and found my web service wsd like, like as following: * Endpoint: http://localhost:8765 * Contract: http://localhost:8080/contract/contract.jsp?serviceCat=org.jboss.overlord... And click the Contract link, it would give me: Unavailable: Received status code '404' on WSDL HTTP (GET) request: 'http://127.0.0.1:8080/creditAgency-creditAgency/CreditAgencyService?wsdl'. While in the 4.5 release, it would point me to the wsdl file for this service. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2807) EBWS: Make the "DOM to String" and back conversion optional

by Martin Vecera (JIRA)

EBWS: Make the "DOM to String" and back conversion optional ----------------------------------------------------------- Key: JBESB-2807 URL: https://jira.jboss.org/jira/browse/JBESB-2807 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.4 CP3 Environment: SOA-P 4.3.CP02 CR2 Reporter: Martin Vecera Priority: Critical In org.jboss.internal.soa.esb.webservice.BaseWebService, there are two calls that cause significant performance overhead in request processing: org.jboss.soa.esb.dom.YADOMUtil.parseStream - 16% org.jboss.soa.esb.dom.YADOMUtil.serialize - 9.5% There are (3) reasons to make the conversion from DOM to String optional by a configuration parameter in jboss-esb.xml and possibly make it the default: 1) ESB Message is able to carry objects, 2) it is expected to have XML message content, 3) and that the user would like to work with the DOM in an ESB service (in a proxy alias WS Virtualization scenario) Thanks to Jirka Pechanec for help. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-2788) "Server started in..." message is not shown as the very last one after server start.

by Pavel Macik (JIRA)

"Server started in..." message is not shown as the very last one after server start. ------------------------------------------------------------------------------------ Key: JBESB-2788 URL: https://jira.jboss.org/jira/browse/JBESB-2788 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Affects Versions: 4.4 CP2, 4.4 CP1, 4.4, 4.4 CP3 Reporter: Pavel Macik Priority: Minor When server starting the "Server started in ..." message is not shown at the very end of server booting when it is supposed to be displayed. See the server log ... 15:54:05,192 INFO [NamingHelper] JNDI InitialContext properties:{} 15:54:05,297 INFO [JDBCDataStore] Generated token 'authToken:6D695240-8B35-11DE-A14E-A661D793521F' for user: 'jbossesb/JBoss ESB User' 15:54:05,440 INFO [TomcatDeployer] deploy, ctxPath=/jbossesb, warUrl=.../tmp/deploy/tmp4263966216198980073management.esb-contents/jbossesb-exp.war/ 15:54:05,527 INFO [ContextConfig] WARNING: Security role name user used in an <auth-constraint> without being defined in a <security-role> 15:54:05,703 INFO [JBoss4ESBDeployer] create esb service, slsb.esb 15:54:07,079 INFO [JBoss4ESBDeployer] create esb service, smooks.esb 15:54:07,089 INFO [TopicService] Topic[/topic/org.jboss.soa.esb.transformation.Update] started, fullSize=200000, pageSize=2000, downCacheSize=2000 15:54:07,153 INFO [SmooksService] Centralized Smooks Instance (Console Based) instance not started. See the 'console.url' property in '/smooks.esb.properties' 15:54:08,696 INFO [JBoss4ESBDeployer] create esb service, soap.esb 15:54:10,083 INFO [JBoss4ESBDeployer] create esb service, spring.esb 15:54:10,273 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080 15:54:10,296 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009 15:54:10,354 INFO [Server] JBoss (MX MicroKernel) [4.3.0.GA_CP02_SOA (build: SVNTag=4.3.0.GA_CP02_SOA date=200908121503)] Started in 1m:13s:356ms 15:54:15,010 INFO [Configuration] configuring from resource: monitoring.cfg.xml 15:54:15,012 INFO [Configuration] Configuration resource: monitoring.cfg.xml 15:54:15,019 INFO [Configuration] Reading mappings from resource : org/jboss/soa/esb/monitoring/monitoring-mappings.hbm.xml 15:54:15,027 INFO [HbmBinder] Mapping class: org.jboss.soa.esb.monitoring.pojo.JMXPattern -> JMXPATTERN 15:54:15,030 INFO [HbmBinder] Mapping class: org.jboss.soa.esb.monitoring.pojo.JMXData -> JMXDATA 15:54:15,034 INFO [HbmBinder] Mapping class: org.jboss.soa.esb.monitoring.pojo.JMXOperationResult -> JMXOPERATIONRESULT 15:54:15,037 INFO [HbmBinder] Mapping class: org.jboss.soa.esb.monitoring.pojo.JMXAttribute -> JMXATTRIBUTE 15:54:15,038 INFO [HbmBinder] Mapping class: org.jboss.soa.esb.monitoring.pojo.JMXOperation -> JMXOPERATION 15:54:15,039 INFO [Configuration] Configured SessionFactory: null 15:54:15,039 INFO [NamingHelper] JNDI InitialContext properties:{} 15:54:15,044 INFO [DatasourceConnectionProvider] Using datasource: java:/ManagementDS 15:54:15,063 INFO [SettingsFactory] RDBMS: HSQL Database Engine, version: 1.8.0 15:54:15,063 INFO [SettingsFactory] JDBC driver: HSQL Database Engine Driver, version: 1.8.0 15:54:15,070 INFO [Dialect] Using dialect: org.hibernate.dialect.HSQLDialect 15:54:15,071 INFO [TransactionFactoryFactory] Using default transaction strategy (direct JDBC transactions) 15:54:15,077 INFO [TransactionManagerLookupFactory] No TransactionManagerLookup configured (in JTA environment, use of read-write or transactional second-level cache is not recommended) 15:54:15,077 INFO [SettingsFactory] Automatic flush during beforeCompletion(): disabled 15:54:15,077 INFO [SettingsFactory] Automatic session close at end of transaction: disabled 15:54:15,077 INFO [SettingsFactory] JDBC batch size: 15 15:54:15,077 INFO [SettingsFactory] JDBC batch updates for versioned data: disabled 15:54:15,077 INFO [SettingsFactory] Scrollable result sets: enabled 15:54:15,077 INFO [SettingsFactory] JDBC3 getGeneratedKeys(): disabled 15:54:15,077 INFO [SettingsFactory] Connection release mode: auto 15:54:15,077 INFO [SettingsFactory] Default batch fetch size: 1 15:54:15,077 INFO [SettingsFactory] Generate SQL with comments: disabled 15:54:15,077 INFO [SettingsFactory] Order SQL updates by primary key: disabled 15:54:15,077 INFO [SettingsFactory] Order SQL inserts for batching: disabled 15:54:15,078 INFO [SettingsFactory] Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory 15:54:15,078 INFO [ASTQueryTranslatorFactory] Using ASTQueryTranslatorFactory 15:54:15,078 INFO [SettingsFactory] Query language substitutions: {} 15:54:15,078 INFO [SettingsFactory] JPA-QL strict compliance: disabled 15:54:15,078 INFO [SettingsFactory] Second-level cache: enabled 15:54:15,078 INFO [SettingsFactory] Query cache: disabled 15:54:15,078 INFO [SettingsFactory] Cache provider: org.hibernate.cache.NoCacheProvider 15:54:15,079 INFO [SettingsFactory] Optimize cache for minimal puts: disabled 15:54:15,080 INFO [SettingsFactory] Structured second-level cache entries: disabled 15:54:15,080 INFO [SettingsFactory] Statistics: disabled 15:54:15,080 INFO [SettingsFactory] Deleted entity synthetic identifier rollback: disabled 15:54:15,080 INFO [SettingsFactory] Default entity-mode: pojo 15:54:15,080 INFO [SettingsFactory] Named query checking : enabled 15:54:15,084 INFO [SessionFactoryImpl] building session factory 15:54:15,180 INFO [SessionFactoryObjectFactory] Factory name: java:/hibernate/MonitoringSessionFactory 15:54:15,180 INFO [NamingHelper] JNDI InitialContext properties:{} 15:54:15,181 INFO [NamingHelper] Creating subcontext: hibernate 15:54:15,181 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name: java:/hibernate/MonitoringSessionFactory 15:54:15,182 WARN [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, 8 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2009