[ http://wso2.org/jira/browse/ESBJAVA-104?page=all ]
indika kumara updated ESBJAVA-104:
----------------------------------
Fix Version/s: 1.7
changed the fix version to 1.7
> Dependencies should not be allowed to be removed while there are live
> references to them
> ----------------------------------------------------------------------------------------
>
> Key: ESBJAVA-104
> URL: http://wso2.org/jira/browse/ESBJAVA-104
> Project: WSO2 ESB
> Issue Type: New Feature
> Affects Versions: 1.0-beta-2-b1
> Environment: Windows XP, JDK1.5, Firefox 1.5.0.11
> Reporter: Evanthika Amarasiri
> Assigned To: Ruwan Linton
> Fix For: 1.7
>
>
> When trying to delete an endpoint refered by a sequence, no error messages
> are given. Below is what actually happens when you try to invoke such a
> sequence which refers a non-existing endpoint
> 1. Create an endpoint
> 2. Create a sequence with a reference to the above created endpoint
> 3. Send a request to the above endpoint and the results will be retrieved
> successfully
> 4. Now remove the endpoint from the system and try to send the request once
> more
> 5. You will get a Null pointer exception
> *********************************************************************************************************************************
> java.lang.NullPointerException
> at
> org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:87)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:49)
> at
> org.apache.synapse.mediators.filters.InMediator.mediate(InMediator.java:54)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:49)
> at
> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:89)
> at
> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:147)
> at
> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:49)
> at
> org.apache.synapse.mediators.base.SynapseMediator.mediate(SynapseMediator.java:69)
> at
> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:86)
> at
> org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:61)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:497)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:328)
> at
> org.apache.axis2.transport.nhttp.ServerWorker.processPost(ServerWorker.java:164)
> at
> org.apache.axis2.transport.nhttp.ServerWorker.run(ServerWorker.java:152)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:534)
> *********************************************************************************************************************************
>
> 6. Therefore the ESB Management Console itself should not allow to remove
> endpoints which are being refered by some other entities (sequences, proxy
> services)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
