July 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-655) Add CORBA support

by Mark Little (JIRA)

Add CORBA support ----------------- Key: JBESB-655 URL: http://jira.jboss.com/jira/browse/JBESB-655 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 -- 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

17 years, 4 months

3
3
0 / 0

[JBoss JIRA] Commented: (JBESB-400) Trailblazer - add ANT task for generating client-side ws classes for the jsr-181 ws

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-400?page=comments#action_12369589 ] Mark Little commented on JBESB-400: ----------------------------------- Is this still relevant? > Trailblazer - add ANT task for generating client-side ws classes for the jsr-181 ws > ----------------------------------------------------------------------------------- > > Key: JBESB-400 > URL: http://jira.jboss.com/jira/browse/JBESB-400 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Examples > Affects Versions: 4.0 > Reporter: Daniel Brum > Assigned To: Tom Cunningham > Fix For: 4.2 > > > Add an ANT task to generate the client side ws classes for the JSR-181 pojo used in the trailblazer. -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-702) MR3 Issues with Getting Started Guide

by Tom Cunningham (JIRA)

MR3 Issues with Getting Started Guide -------------------------------------- Key: JBESB-702 URL: http://jira.jboss.com/jira/browse/JBESB-702 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Cunningham Assigned To: Tom Cunningham Priority: Critical Fix For: 4.2 Milestone Release 3 There's a lot of issues with the "Getting Started" guide - Burr came up with a list that he saw (see below). A lot of these are pretty heinous (telling users to use the wrong version of the appserver, incorrect steps with deployment.properties, etc) because it hasn't been updated since MR2. I'd really like to get this in to MR3 because this is the first thing that a new user looks at. * Page 9 has "After downloading and expanding the JBoss ESB 4.0 GA distribution" and the directory structure is now different based on the new samples that have been added or renamed. * Page 10 has "JBoss Application Server v4.0.5GA [with ejb3]" I believe we are now focused on AS 4.2 + Messaging 1.3.0 * Page 10: "You can deploy it to JBossAS, to Tomcat, or run it in standalone mode. " is not accurate. We have standalone bootstrapper & we have the standalone ESB Server. Page 12 walks the user through using the bootstrapper as the very first test so it is important that we clearly articulate what that animal is OR we change the nature of the test. Since this is the "Getting Started" guide we should really push the user into the use of the AS, not bootstrapper, not ESB Server, not Tomcat. The AS model is the only one that supports all features (e.g. WS hosting only works with AS). Plus that is the only deployment option that is well tested. * Page 10: "download the JBossESB 4.0.5GA" should refer to the proper version of AS that we want. * Page 10: "Run 'ant'. This will deploy the esb to your JBossAS instance. It copies the jbossesb.sar into your deploy directory." is no longer accurate, we deploy a couple of SARs and a several .esbs. We should list the files that are in fact deployed/tweaked on an existing AS instance. We should insert a screenshot of what the deploy directory now looks like. This section is confusing because it refers to "Standalone" and "Deploy to JBossAS" and it is unclear if I have to do both or that I can just pick one of these options. The example of the deployment.properties needs to be updated to reflect the correct version of AS and the "messaging" profile instead of "default". Note: I've not tested any of the quickstarts against the Tomcat deployment model so it is not clear to me if this even works. * Page 12: There a spurious "JBossESB" directly after "Content-Based Router," in the line that describes jbrules.esb * Page 12/13: should also demonstrate the .esb archive deployment model. Plus it should include screen shots of the various command windows so that it is even easier to visually "see" a valid test. * Page 14: The diagram is no longer accurate. It refers to 2 queues and those names are no longer used by the helloworld quickstart. Plus the Service Name has changed. * Page 14: Step 1 Service Registry is not accurate. It tries to describe the service registry capability as if it is "db" based, when in this particular quickstart (and virtually all of them) we are using the RMI-based trick to work with the UDDI registry living inside of the ESB Server or AS. Step 3 refers to the wrong service name and wrong queue name. We are trying to eliminate all references to "queue/B", "A,C &D" in the quickstarts so there are no overlapping service names or queue names as that causes havoc when you deploy more than one at a time. * Page 16: It seems the diagram is repeated (with the same errors as before) for some reason that is not clear to me. This document should also be published on the wiki/website for users who wish to review but not yet download. Plus, I intend to built "videos" of various demos that are hung off our blogs/wiki for those people who don't wish to ready & try first but just sit back and get a series of demos to determine if this is the right technology for them. Finally, we need a quickstarts "trailmap": 1. helloworld 2. helloworld_action 3. more_action 4. helloworld_file_action 5. helloworld_ftp_action 6. simple_cbr 7. fun_cbr 8. business_service 9. business_rules_service 10. scripting_groovy 11. transform_CSV2XML 12. transform_XML2POJO 13. transform_XML2XML_simple 14. transform_XML2XML_date_manipulation 15. aggregator 16. bpm_orchestration1 17. bpm_orchestration2 18. webservice_consumer1 19. webservice_producer The rest based upon what feature you need to understand next. aggregator & the bpm examples are fairly advanced so they build on the previous ones. the webservice ones are somewhat hard to grok so you need to feel really good about jboss-esb.xml and actions classes long before you get to this example. -- 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

17 years, 4 months

2
5
0 / 0

[JBoss JIRA] Work stopped: (JBESB-440) Remote management of services

by Tom Cunningham (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-440?page=all ] Work on JBESB-440 stopped by Tom Cunningham. > Remote management of services > ----------------------------- > > Key: JBESB-440 > URL: http://jira.jboss.com/jira/browse/JBESB-440 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Management > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Tom Cunningham > Fix For: 5.0 > > > Remotely start/stop/suspend/resume services. Via JMX and via lifecycle messages (as per original architecture). -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Work stopped: (JBESB-400) Trailblazer - add ANT task for generating client-side ws classes for the jsr-181 ws

by Tom Cunningham (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-400?page=all ] Work on JBESB-400 stopped by Tom Cunningham. > Trailblazer - add ANT task for generating client-side ws classes for the jsr-181 ws > ----------------------------------------------------------------------------------- > > Key: JBESB-400 > URL: http://jira.jboss.com/jira/browse/JBESB-400 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Examples > Affects Versions: 4.0 > Reporter: Daniel Brum > Assigned To: Tom Cunningham > Fix For: 4.2 > > > Add an ANT task to generate the client side ws classes for the JSR-181 pojo used in the trailblazer. -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-398) The use of java.net.URL doesnt allow support for protcols such as ftps, sftp. Refactor to use URI instead.

by Bruno Georges (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-398?page=comments#action_12369547 ] Bruno Georges commented on JBESB-398: ------------------------------------- SFTP support code has been added to the URI changes you made and checked in your workspace. > The use of java.net.URL doesnt allow support for protcols such as ftps, sftp. Refactor to use URI instead. > ----------------------------------------------------------------------------------------------------------- > > Key: JBESB-398 > URL: http://jira.jboss.com/jira/browse/JBESB-398 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta, Transports > Affects Versions: 4.0 CR1 > Reporter: Bruno Georges > Assigned To: Bruno Georges > Fix For: 5.0 Milestone Release 1 > > Original Estimate: 2 days > Time Spent: 40 minutes > Remaining Estimate: 1 day, 7 hours, 20 minutes > > Exception is thrown when using sftp/ftps protocols. > java.net.MalformedURLException: unknown protocol: sftp > Mark: We should really be using URIs everywhere since EPRs are based on WS-A, which is URI/IRI based. -- 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

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-681) Post JIRA to JBossWS re NPE issue with org.jboss.wsf.container.jboss42.WebMetaDataAdapter

by Tom Fennelly (JIRA)

Post JIRA to JBossWS re NPE issue with org.jboss.wsf.container.jboss42.WebMetaDataAdapter ----------------------------------------------------------------------------------------- Key: JBESB-681 URL: http://jira.jboss.com/jira/browse/JBESB-681 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 No point in doing this now because they'll be looking for unit tests to reproduce the issue. I'll come back to is after the MR3 release. -- 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

17 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-698) Check necessary classes/interfaces are in internal

by Mark Little (JIRA)

Check necessary classes/interfaces are in internal -------------------------------------------------- Key: JBESB-698 URL: http://jira.jboss.com/jira/browse/JBESB-698 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Mark Little Priority: Blocker Fix For: 4.2 This will make our versioning life easier. -- 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

17 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-683) ListenerUtil.obtainAtt has different interpretation of default value for null

by Mark Little (JIRA)

ListenerUtil.obtainAtt has different interpretation of default value for null ----------------------------------------------------------------------------- Key: JBESB-683 URL: http://jira.jboss.com/jira/browse/JBESB-683 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2 The normal assumption of null for a default value (e.g., in System.getProperty) is that you return null if there is nothing set. However, in ListenerUtil, if you pass null as a default value this means throw a ConfigurationException on finding null for the value. This is not intuitive and goes against all other similar mechanisms. If we need this capability, then let's add an explicit method for throwing an exception, or another parameter. -- 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

17 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-699) ConnectionManager interface should not be in internal package

by Mark Little (JIRA)

ConnectionManager interface should not be in internal package ------------------------------------------------------------- Key: JBESB-699 URL: http://jira.jboss.com/jira/browse/JBESB-699 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2 But the implementations of it should. -- 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

17 years, 4 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2007