[esb-java-dev] [jira] Resolved: (ESBJAVA-87) Allows the endpoint name to be saved as " ", but gives and exception when trying to edit it.

Ruwan Linton (JIRA) jira at wso2.org
Sun May 20 23:07:02 PDT 2007


     [ http://www.wso2.org/jira/browse/ESBJAVA-87?page=all ]

Ruwan Linton resolved ESBJAVA-87.
---------------------------------

    Fix Version/s: 1.0-RC-1-b2
       Resolution: Fixed
         Assignee: Ruwan Linton  (was: indika kumara)

Fixed in the next build, check for the verification

> Allows the endpoint name to be saved as " ", but gives and exception when trying to edit it.
> --------------------------------------------------------------------------------------------
>
>                 Key: ESBJAVA-87
>                 URL: http://www.wso2.org/jira/browse/ESBJAVA-87
>             Project: WSO2 ESB-Java
>          Issue Type: Bug
>          Components: Administration Console
>    Affects Versions: 1.0-beta-2-b1
>         Environment: Windows XP \ IE 6.0.2 \ JDK1.5
>            Reporter: Yumani Ranaweera
>         Assigned To: Ruwan Linton
>             Fix For: 1.0-RC-1-b2
>
>         Attachments: endpoint exceptions.txt, name.txt, name_endpoint.JPG, name_sequence.JPG, sequence exception.txt
>
>
> Saves endpoints when a " " is given as the name, but gives and exception when trying to edit it. The exception is given below.
> ERROR [10 May 14:27:41]  RPCMessageReceiver - Exception occurred while trying to invoke service method getEndpoint
> java.lang.reflect.InvocationTargetException
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:116)
>         at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39)
>         at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:144)
>         at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:279)
>         at org.apache.axis2.transport.http.util.SOAPUtil.processPostRequest(SOAPUtil.java:63)
>         at org.wso2.esb.transport.jetty.Axis2SOAPHandler.processPostRequest(Axis2SOAPHandler.java:40)
>         at org.wso2.esb.transport.jetty.Axis2Handler.handle(Axis2Handler.java:144)
>         at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
>         at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
>         at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
>         at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
>         at org.mortbay.jetty.Server.handle(Server.java:285)
>         at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:502)
>         at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:835)
>         at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:638)
>         at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:202)
>         at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378)
>         at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:226)
>         at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
> Caused by: java.lang.NullPointerException
>         at org.wso2.esb.services.EndpointAdmin.getEndpoint(EndpointAdmin.java:355)
>         ... 23 more
> Steps to reproduce
> ------------------------
> 1. Invoke ESB admin console
> 2. Go to 'Endpoints' and press 'Add' button, select 'address endpoint'
> 3. In the 'Address Endpoint' page enter " " at the name.
> 4. Enter valid data to other fields and save.
> 5. From the 'Manage Endpoints' page, select to edit the above end point --->An exception appears (refer screen print "name_endpoint.jpg")
> NOTE: Simalarly a sequence with " " as the name also was allowed to save. When trying to edit this a message which says "Sequence with the name null does not exist in the synapse configuration". (refer screen print "name_sequence.jpg")
> ******Stack traces of both above instances are also attached (refer name.txt).
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> Update from Yumani 11/05/07
> 1. Throws exceptions when trying to 'edit\delete\enable statistics' of the endpoints created in the above manner. (refer endpoint exceptions.txt)
> 2. Throws exceptions when trying to 'enable statistics\enable tracing' of the endpoint created in the above manner. (refer sequence exceptions.txt)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        




More information about the Esb-java-dev mailing list