Apply JBESB-2481 to SOA CP branch
---------------------------------
Key: JBESB-2482
URL: https://jira.jboss.org/jira/browse/JBESB-2482
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.4 CP2
Reporter: Kevin Conner
Assignee: Kevin Conner
Fix For: 4.4 CP3
--
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
Merge fix for JBESB-2468 into SOA branch
----------------------------------------
Key: JBESB-2479
URL: https://jira.jboss.org/jira/browse/JBESB-2479
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Management
Affects Versions: 4.4 CP2
Reporter: Kevin Conner
Assignee: Kevin Conner
Fix For: 4.4 CP3
SOA team have asked for the JBESB-2468 fix to be included into their 4.3.0.CP1 release. As our CP branch has already moved forward we need to merge this directly into the SOA specific branch for this release.
--
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
Duplicate schema types in wsdl generated by EBWS
------------------------------------------------
Key: JBESB-2470
URL: https://jira.jboss.org/jira/browse/JBESB-2470
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Web Services
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.4 FP1, 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
http-listener: Add support for specifying a user configured jboss-web.xml
-------------------------------------------------------------------------
Key: JBESB-2472
URL: https://jira.jboss.org/jira/browse/JBESB-2472
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
Change JBoss4ESBDeployer.deployDeployableGateways to just use the DeploymentInfo.localCl classloader
----------------------------------------------------------------------------------------------------
Key: JBESB-2478
URL: https://jira.jboss.org/jira/browse/JBESB-2478
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.4 FP1
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Fix For: 4.4 FP1
--
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
Implement support for schema import in EBWS WSDL generation/action pipeline validation.
---------------------------------------------------------------------------------------
Key: JBESB-2217
URL: https://jira.jboss.org/jira/browse/JBESB-2217
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Rosetta, Web Services
Affects Versions: 4.4
Reporter: Kevin Conner
Fix For: 4.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
Implement support for schema import in EBWS WSDL generation/action pipeline validation.
---------------------------------------------------------------------------------------
Key: JBESB-2323
URL: https://jira.jboss.org/jira/browse/JBESB-2323
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Rosetta, Web Services
Affects Versions: 4.4, 4.4 CP1
Reporter: Kevin Conner
Fix For: 4.4 CP3
--
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
Cross-Site scripting issues in ESB management console
-----------------------------------------------------
Key: JBESB-2128
URL: https://jira.jboss.org/jira/browse/JBESB-2128
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Management
Affects Versions: 4.4
Reporter: Kevin Conner
Fix For: 4.4 CP1
Go through all jsp pages and make sure that all variable output is encoded for HTML display.
--
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
Evaluate, if a AS/400 Dataqueue Ressource Adapter is usable for Jboss and/or Jboss ESB
--------------------------------------------------------------------------------------
Key: JBESB-1996
URL: https://jira.jboss.org/jira/browse/JBESB-1996
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Adapters
Reporter: Heiko Wiesjbossner
A Dataqueue is like a jms queue on IBM's (AS/400 / Iseries / System i / and all the other names for the AS/400).
Whith the Ressource Adapter i wrote you can transform the Dataqueue Message into a jms Message
without any coding. Configuration is made with annotations. The rest is handled by the RA.
I think, this is the best way to connect from old school RPG or Cobol Applications to J2EE. It is a very performant and ressource saving way.
--
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