You should be using Synapse config editor. That would have saved most of these trouble.
On Thu, Sep 26, 2013 at 12:40 AM, Asela Pathberiya <[email protected]> wrote: > Hi all, > > I tried to do this using APIM 1.4.0 and it works. But is there any > recommend way to achieve this? Because I have come across several issues > while i am trying to do. Please let me know whether i am in the correct > path. > > 1. Create a API in the API publisher > > 2. Now i want to edit the API configuration to do some changes to support > for this use case. > > 3. In Publisher, there is not way to edit API config. so login to > management console. User has no permission to edit API config > > 4. Login as admin user and edit it. But it was also not > successful...(May be som issue in the XML UI editor) > You need to use the Synapse config editor (not the API editor in Admin console) . > > 5. Then file system is used. it works. > > 6. Need to add new sequence for API flow, it is not allow to do using > publisher and management console and need to use file system. > Here again you need to use the Synapse config editor. In 1.5.0, there is an option to attach this to API through publisher UI (provided that added sequence extension definitions are in correct registry location). > > Are we recommend dev- studio for APIM ? sorry i did not try it.... > > 7. API is edited using publisher and all changes that i have done with API > config has been reverted. > API configuration can take full benefit of underlying Synapse semantics. There is no way for us to support all of that through Publisher UI. However we are going to add all ESB endpoint support in next release. This is a known issue. Marking hand edited ones & not allowing them to be edited through Publisher UI is an option. But it can be argued either way. > If we want to expose SOAP as REST API, we may need to edit API config or > add additional sequences. Basically API publisher is not much useful to > implement this. I guess it is ok to improve to do this type of common use > cases using API publisher? > Just using SOAP endpoint & sending the envelop in the body (without any custom modifications) does not work? > > Thanks, > Asela. > > Thanks & Regards, > Asela > > ATL > Mobile : +94 777 625 933 > -- /sumedha m: +94 773017743 b : bit.ly/sumedha
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
