You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hivemind.apache.org by "Marcus Brito (JIRA)" <hi...@jakarta.apache.org> on 2005/03/30 00:37:16 UTC
[jira] Created: (HIVEMIND-105) ServiceImplementationFactoryParameters.getFirstParameter should cope better with zero parameters
ServiceImplementationFactoryParameters.getFirstParameter should cope better with zero parameters
------------------------------------------------------------------------------------------------
Key: HIVEMIND-105
URL: http://issues.apache.org/jira/browse/HIVEMIND-105
Project: HiveMind
Type: Improvement
Components: framework
Versions: 1.1
Reporter: Marcus Brito
Priority: Minor
Attachments: get-first-parameter.patch
ServiceImplementationFactoryParameters.getFirstParameter() bails with an IndexOutOfBoundsException if there aren't any paremeters to start with. I think it should:
1) Return null, or
2) Throw an ApplicationRuntimeException explaining the situation
Attached goes a patch that implements (1), since I find it to be easier to check for a null first parameter than catch an exception, and it's more streamlined that checking for an empty parameter list.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org
[jira] Updated: (HIVEMIND-105) ServiceImplementationFactoryParameters.getFirstParameter should cope better with zero parameters
Posted by "Marcus Brito (JIRA)" <hi...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/HIVEMIND-105?page=history ]
Marcus Brito updated HIVEMIND-105:
----------------------------------
Attachment: get-first-parameter.patch
> ServiceImplementationFactoryParameters.getFirstParameter should cope better with zero parameters
> ------------------------------------------------------------------------------------------------
>
> Key: HIVEMIND-105
> URL: http://issues.apache.org/jira/browse/HIVEMIND-105
> Project: HiveMind
> Type: Improvement
> Components: framework
> Versions: 1.1
> Reporter: Marcus Brito
> Priority: Minor
> Attachments: get-first-parameter.patch
>
> ServiceImplementationFactoryParameters.getFirstParameter() bails with an IndexOutOfBoundsException if there aren't any paremeters to start with. I think it should:
> 1) Return null, or
> 2) Throw an ApplicationRuntimeException explaining the situation
> Attached goes a patch that implements (1), since I find it to be easier to check for a null first parameter than catch an exception, and it's more streamlined that checking for an empty parameter list.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org
[jira] Resolved: (HIVEMIND-105) ServiceImplementationFactoryParameters.getFirstParameter should cope better with zero parameters
Posted by "James Carman (JIRA)" <hi...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/HIVEMIND-105?page=all ]
James Carman resolved HIVEMIND-105:
-----------------------------------
Assign To: James Carman
Resolution: Fixed
Fix Version: 1.1
> ServiceImplementationFactoryParameters.getFirstParameter should cope better with zero parameters
> ------------------------------------------------------------------------------------------------
>
> Key: HIVEMIND-105
> URL: http://issues.apache.org/jira/browse/HIVEMIND-105
> Project: HiveMind
> Type: Improvement
> Components: framework
> Versions: 1.1
> Reporter: Marcus Brito
> Assignee: James Carman
> Priority: Minor
> Fix For: 1.1
> Attachments: get-first-parameter.patch
>
> ServiceImplementationFactoryParameters.getFirstParameter() bails with an IndexOutOfBoundsException if there aren't any paremeters to start with. I think it should:
> 1) Return null, or
> 2) Throw an ApplicationRuntimeException explaining the situation
> Attached goes a patch that implements (1), since I find it to be easier to check for a null first parameter than catch an exception, and it's more streamlined that checking for an empty parameter list.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org
[jira] Closed: (HIVEMIND-105) ServiceImplementationFactoryParameters.getFirstParameter should cope better with zero parameters
Posted by "James Carman (JIRA)" <hi...@jakarta.apache.org>.
[ http://issues.apache.org/jira/browse/HIVEMIND-105?page=all ]
James Carman closed HIVEMIND-105:
---------------------------------
> ServiceImplementationFactoryParameters.getFirstParameter should cope better with zero parameters
> ------------------------------------------------------------------------------------------------
>
> Key: HIVEMIND-105
> URL: http://issues.apache.org/jira/browse/HIVEMIND-105
> Project: HiveMind
> Type: Improvement
> Components: framework
> Versions: 1.1
> Reporter: Marcus Brito
> Assignee: James Carman
> Priority: Minor
> Fix For: 1.1
> Attachments: get-first-parameter.patch
>
> ServiceImplementationFactoryParameters.getFirstParameter() bails with an IndexOutOfBoundsException if there aren't any paremeters to start with. I think it should:
> 1) Return null, or
> 2) Throw an ApplicationRuntimeException explaining the situation
> Attached goes a patch that implements (1), since I find it to be easier to check for a null first parameter than catch an exception, and it's more streamlined that checking for an empty parameter list.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-dev-help@jakarta.apache.org