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 "Lin Sun (JIRA)" <ji...@apache.org> on 2007/08/23 21:20:32 UTC
[jira] Closed: (AXIS2-3144) Check for serviceImplClass being null
in JavaBeanDispatcher.java
[ https://issues.apache.org/jira/browse/AXIS2-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lin Sun closed AXIS2-3144.
--------------------------
Resolution: Invalid
This issue can be cancelled as we made a fix in geronimo not passing serviceimplclass as null.
> Check for serviceImplClass being null in JavaBeanDispatcher.java
> ----------------------------------------------------------------
>
> Key: AXIS2-3144
> URL: https://issues.apache.org/jira/browse/AXIS2-3144
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Affects Versions: 1.4
> Environment: Win XP + Sun JDK 1.5
> Reporter: Lin Sun
> Priority: Minor
> Fix For: 1.4
>
> Attachments: axis2-3144.patch
>
>
> I am running some test that caused a NPE at serviceImplClass.getName()) in the invoke method of JavaBeanDispatcher.java. It turned out serviceImplClass is null which prevent the rest of code in the invoke method getting executed. If I disable the logging, my test would run fine. A simple fix is to do the logging when serviceImplClass is not null.
--
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