[ http://wso2.org/jira/browse/ESBJAVA-388?page=all ]
Evanthika Amarasiri closed ESBJAVA-388.
---------------------------------------
Assignee: (was: indika kumara)
Fixed in build 1.6-QA-B1. Even after restarting the ESB server, the dblookup
mediator property remains the same. The issue will be closed
> dbLookup mediator properties changed after restarting the ESB server
> --------------------------------------------------------------------
>
> Key: ESBJAVA-388
> URL: http://wso2.org/jira/browse/ESBJAVA-388
> Project: WSO2 ESB
> Issue Type: Bug
> Components: Sequences Management
> Affects Versions: NIGHTLY
> Environment: Ubuntu7.04, Firefox2.0.0.9, JDK1.5.0_12
> Reporter: Evanthika Amarasiri
> Fix For: NIGHTLY
>
> Attachments: synapse.xml
>
>
> Below are the steps to reproduce the issue
> 1. Created a sequence with a dbLookup mediator which contains MySql
> connection properties (sample_360_mysql)
> 2. Saved the sequence, saved the configuration and restarted the server.
> 3. When logged in to the Administrator console once more, the connection
> properties have changed from MySQL to derby. In my configuration, I have
> another sequence with a dbLookup mediator with derby connection properties as
> well. (sample_360)
> Attached herewith is my synapse configuration.
--
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
