[ http://jira.jboss.com/jira/browse/JBESB-38?page=comments#action_12339760 ]
Mark Little commented on JBESB-38:
----------------------------------
Yes, assuming you think the existing tests fall into QA. If they don't, then make sure they are consistent with the unit test approach.
> Migrate existing tests to QA
> ----------------------------
>
> Key: JBESB-38
> URL: http://jira.jboss.com/jira/browse/JBESB-38
> Project: JBoss ESB
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: ESB Core, Testing
> Reporter: Mark Little
> Assigned To: Arvinder Singh
> Fix For: 4.0 Beta 1
>
>
> Take the existing Rosetta tests and make sure they are added to the QA system for JBossESB. We need to be running this nightly too.
--
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
[ http://jira.jboss.com/jira/browse/JBESB-38?page=comments#action_12339759 ]
Arvinder Singh commented on JBESB-38:
-------------------------------------
Can I just check what this task involves:
1) Create top level QA directory, so the structure is
<trunk>/QA
build.xml
src
2) Migrate the ESBCore/Tests code to the folder above minus the 1 test that were converted to 2 separate unit tests, see http://jira.jboss.com/jira/browse/JBESB-71
> Migrate existing tests to QA
> ----------------------------
>
> Key: JBESB-38
> URL: http://jira.jboss.com/jira/browse/JBESB-38
> Project: JBoss ESB
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: ESB Core, Testing
> Reporter: Mark Little
> Assigned To: Arvinder Singh
> Fix For: 4.0 Beta 1
>
>
> Take the existing Rosetta tests and make sure they are added to the QA system for JBossESB. We need to be running this nightly too.
--
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
[ http://jira.jboss.com/jira/browse/EJBTHREE-436?page=all ]
Bill Burke closed EJBTHREE-436.
-------------------------------
Resolution: Rejected
just use XML instead of @Clustered.
> partition name should not be part of the @clustered annotation
> --------------------------------------------------------------
>
> Key: EJBTHREE-436
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-436
> Project: EJB 3.0
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: EJB 3.0 RC4 - PFD
> Reporter: Martin Welss
> Assigned To: Bill Burke
> Priority: Critical
> Fix For: EJB 3.0 RC9 - FD
>
>
> Why is the partition name part of the ejb-clustering annotation?
> Suppose there are three clusters: one for integration, one for test, one for production and each has a distinct partition name. It would not be possible to 'move' an application from integration to test without changing the code!
> And because of the attributes default value, there is no way to say to the bean 'never mind the partition name, just run everywhere'
--
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
[ http://jira.jboss.com/jira/browse/EJBTHREE-594?page=comments#action_12339756 ]
Jan Normann Nielsen commented on EJBTHREE-594:
----------------------------------------------
This is obviously still an issue in RC8, just watch the RC8 announcement thread.
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956392
It should also be noted that there's an lib/hibernate3.jar file in the EJB3 RC8 distribution that no one says what to do with.
Please fix in RC9. Otherwise, the EJB3 package is unusable because the installation instructions are erroneous.
> Copy jboss-ejb3-client.jar from the lib/ directory of the distribution to jboss-4.0.x/client in INSTALL.html
> ------------------------------------------------------------------------------------------------------------
>
> Key: EJBTHREE-594
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-594
> Project: EJB 3.0
> Issue Type: Bug
> Affects Versions: EJB 3.0 RC7 - FD
> Reporter: Stefan Lindner
>
> The file jboss-ejb3-client.jar is missing. The INSTALL.html file says "15. Copy jboss-ejb3-client.jar from the lib/ directory of the distribution to jboss-4.0.x/client". But no such file is in the RC7 distribution.
--
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
Need binary distribution package
--------------------------------
Key: JBADMCON-147
URL: http://jira.jboss.com/jira/browse/JBADMCON-147
Project: JBoss Admin Console
Issue Type: Feature Request
Components: General Console
Affects Versions: 1.1 alpha
Reporter: Peter Johnson
Assigned To: Peter Johnson
Fix For: 1.1 alpha
Need to provide a binary package with a simple script (ant based with bat and sh invokers) to install the admin console.
--
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