You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Glen Daniels (JIRA)" <ji...@apache.org> on 2007/05/30 16:03:16 UTC
[jira] Created: (AXIS2-2732) Too much introspection in
MessageReceivers
Too much introspection in MessageReceivers
------------------------------------------
Key: AXIS2-2732
URL: https://issues.apache.org/jira/browse/AXIS2-2732
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Reporter: Glen Daniels
Assignee: Glen Daniels
If you take a look at any of the Java-class-backed MessageReceivers we currently have (RawXML... or RPC... for instance), you'll notice that we search for the appropriate java.lang.Method on each request - see, for instance, RawXMLInOutMessageReceiver.findOperation(). This a potentially serious performance issue, as introspection is expensive, and it's also just not very clean design.
We should instead be caching the java.lang.Method in the AxisOperation. This has come up before but I didn't find a JIRA about it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2732) Too much introspection in
MessageReceivers
Posted by "Glen Daniels (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Glen Daniels resolved AXIS2-2732.
---------------------------------
Resolution: Fixed
Fix Version/s: nightly
Fixed.
> Too much introspection in MessageReceivers
> ------------------------------------------
>
> Key: AXIS2-2732
> URL: https://issues.apache.org/jira/browse/AXIS2-2732
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Reporter: Glen Daniels
> Assignee: Glen Daniels
> Priority: Blocker
> Fix For: nightly
>
>
> If you take a look at any of the Java-class-backed MessageReceivers we currently have (RawXML... or RPC... for instance), you'll notice that we search for the appropriate java.lang.Method on each request - see, for instance, RawXMLInOutMessageReceiver.findOperation(). This a potentially serious performance issue, as introspection is expensive, and it's also just not very clean design.
> We should instead be caching the java.lang.Method in the AxisOperation. This has come up before but I didn't find a JIRA about it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2732) Too much introspection in
MessageReceivers
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-2732:
------------------------------------
Priority: Blocker (was: Major)
> Too much introspection in MessageReceivers
> ------------------------------------------
>
> Key: AXIS2-2732
> URL: https://issues.apache.org/jira/browse/AXIS2-2732
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Reporter: Glen Daniels
> Assignee: Glen Daniels
> Priority: Blocker
>
> If you take a look at any of the Java-class-backed MessageReceivers we currently have (RawXML... or RPC... for instance), you'll notice that we search for the appropriate java.lang.Method on each request - see, for instance, RawXMLInOutMessageReceiver.findOperation(). This a potentially serious performance issue, as introspection is expensive, and it's also just not very clean design.
> We should instead be caching the java.lang.Method in the AxisOperation. This has come up before but I didn't find a JIRA about it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2732) Too much introspection in
MessageReceivers
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500643 ]
Deepal Jayasinghe commented on AXIS2-2732:
------------------------------------------
+1
> Too much introspection in MessageReceivers
> ------------------------------------------
>
> Key: AXIS2-2732
> URL: https://issues.apache.org/jira/browse/AXIS2-2732
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Reporter: Glen Daniels
> Assignee: Glen Daniels
>
> If you take a look at any of the Java-class-backed MessageReceivers we currently have (RawXML... or RPC... for instance), you'll notice that we search for the appropriate java.lang.Method on each request - see, for instance, RawXMLInOutMessageReceiver.findOperation(). This a potentially serious performance issue, as introspection is expensive, and it's also just not very clean design.
> We should instead be caching the java.lang.Method in the AxisOperation. This has come up before but I didn't find a JIRA about it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2732) Too much introspection in
MessageReceivers
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502809 ]
Davanum Srinivas commented on AXIS2-2732:
-----------------------------------------
Let's please fix this for 1.3
> Too much introspection in MessageReceivers
> ------------------------------------------
>
> Key: AXIS2-2732
> URL: https://issues.apache.org/jira/browse/AXIS2-2732
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Reporter: Glen Daniels
> Assignee: Glen Daniels
> Priority: Blocker
>
> If you take a look at any of the Java-class-backed MessageReceivers we currently have (RawXML... or RPC... for instance), you'll notice that we search for the appropriate java.lang.Method on each request - see, for instance, RawXMLInOutMessageReceiver.findOperation(). This a potentially serious performance issue, as introspection is expensive, and it's also just not very clean design.
> We should instead be caching the java.lang.Method in the AxisOperation. This has come up before but I didn't find a JIRA about it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org