Hi Miyuru, Thank you for reporting.
I will have a look and do the required doc changes. Best Regards, Nisrin Nisrin Sheriff Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. mobile: +94 776 24 84 56 http://wso2.com On Thu, Feb 19, 2015 at 9:46 AM, Miyuru Dayarathna <[email protected]> wrote: > Hi, > > I have found several places in the ESB 4.8.1 documentation that could be > improved. I have listed those below. > > 1) Sample 61 ( > https://docs.wso2.com/display/ESB481/Sample+61%3A+Routing+a+Message+to+a+Dynamic+List+of+Recipients > ) > > I got an error ("An error occurred while trying to update. This could be > due to invalid configurations.") when using the configuration listed on the > above web page while trying to update the Service Bus Configuration through > WSO2 ESB Management Console. Even for version 4.9.0 documentation the same > configuration is listed. However, the contents of the synapse_sample_61.xml > file on the ESB 4.9.0 distribution is different from the configuration > information listed on the Sample 61 documentation pages for both these > versions. I was able to run the sample using the synapse_sample_61.xml > configuration file located in the ESB 4.9.0 distribution. Therefore, it > would be good if you could replace the content of the documentation with > the properly functioning configuration information that could be found from > synapse_sample_61.xml file on ESB 4.9.0 distribution. > > 2) Sample 255 ( > https://docs.wso2.com/display/ESB481/Sample+255%3A+Switching+from+FTP+Transport+Listener+to+Mail+Transport+Sender > ) > > The original sample posted on the above URL does not work as expected. > > Since we are using FTP over VFS we need to specify the full path to the > input folder to make the sample work. i.e., > > vfs:ftp://<user>:<password>@127.0.0.1/<full path to the input folder> > > 3) Sample 53 ( > https://docs.wso2.com/display/ESB481/Sample+53%3A+Using+Failover+Endpoints+to+Handle+Peak+Loads > ) > > Although the documentation states that the messages are directed to the > server that is restarted, that seems not working in sample 53. After > shutting down all the three Axis2 servers, the client displays the message > “COULDN'T SEND THE MESSAGE TO THE SERVER.” and waits. But after running all > the three Axis2 servers again and after waiting more than 60 seconds, the > application seems not resuming its work. The client does not restart > printing on to the console. Therefore, The following statement mentioned in > the documentation ( > https://docs.wso2.com/display/ESB481/Sample+53%3A+Using+Failover+Endpoints+to+Handle+Peak+Loads > ) need to be amended accordingly. > > "Therefore, if you have restarted any of the stopped servers and have > stopped all other servers, messages will be directed to the server that is > restarted." > > > -- > Thanks, > Miyuru Dayarathna > Senior Technical Lead > Mobile: +94713527783 > Blog: http://miyurublog.blogspot.com > > -- > You received this message because you are subscribed to the Google Groups > "WSO2 Documentation" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/a/wso2.com/d/optout. >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
