Is there any way to create Message Stores/Processors in the Carbon or Developer Studio?
I need to create them, add them to the CAR and deploy in the WSO2 ESB
Unfortunately Developer Studio does not support creation of Message Stores and Message Processors at the moment.
It is in our Road Map and we will include it in a future release.
Harshana
Developer Studio 3.2.0 version supports creation of Message Stores and Message Processors and they can be added to a CAR and deploy in the WSO2 ESB.
You can download Developer Studio 3.2.0 version from here.
Regards,
Asanka Sanjeewa.
Related
Is possible to add a built custom mediator to the WSO2 Developer Studio palette?
The idea is avoid the error: Unkown synapse configuration tag, At line X. when i trying to edit an API or Proxy that has the reference in its sequence.
I am using WSO2 EI Tooling version 6.3.0.
Thanks in advance.
It is possible to add a custom mediator into WSO2 Developer Studio. However, this requires quite a lot of implementation for both wso2-synapse and devstudio-tooling-esb, as WSO2 Developer Studio has been developed on top of the Eclipse GMF framework adhering to the ecore model.
This is a custom mediator implementation, which had been incorporated into Developer Studio recently.
I just downloaded WSO2 Developer Studio for Mac 64bit. I tried setting up a MongoDB data source. However, the MongoDB option no longer exists. Has WSO2 discontinued MongoDB support in DSS or is there some way to re-enable it?
WSO2 didn't discontinue MongoDB support in DSS 3.5.1. You can add Mongo DB data source in the data service. It's available in the management console as well.
Thanks,
Madhawa
Using wso2bps-3.5.1, wso2das-3.0.1 and Developer Studio 3.8.0
I'm following a guideline for Monitoring a BPEL Process with WSO2 DAS. I recieve this from inside Developer Studio and my .bpel file:
Error: Extension "http://wso2.org/bps/monitoring/publisher" is not supported by this implementation.
<bpel:extensions>
<bpel:extension namespace="http://wso2.org/bps/monitoring/publisher" mustUnderstand="yes"/>
</bpel:extensions>
WSO2 Developer Studio uses Eclipse bpel plugin to add support for bpel creation for WSO2 BPS. This BAM publishing bpel extension activity that you are referring to, is a custom extension developed by WSO2 and default bpel editor is not aware of this extension. This is why it gives syntax errors when you add this extension activity from the source view.
However, you should be able to export and deploy the CAR file without any issues regardless of the syntax errors.
According to this, there's a possibility to add support for custom extension activities in bpel editor.
Hence, I have raised a jira in WSO2 BPS Tooling jira for this feature.
Thanks.
I would like to know if is there is any separate development studio available for wso2 esb.
If available can you provide me a link where i can download wso2 esb studio for development.
Yes. You can use WSO2 Developer Studio. Please check the Installation Guide, Quick Start Guide and Samples.
Please check Creating ESB Artifacts User Guide from WSO2 Developer Studio Documentation.
I hope this helps.
Using WSO2 developer studio is one time stop to create different types of artifact projects. There is a separate project type called ESB Config projects which will be useful to your requirement. You can refer the product documentation which Isuru pointed.
I made a sequence in the wso2 esb portal using an envolepe enrich mediator which source was a key from registry. When I moved this code to the eclipse carbon studio 1.0.14 it failed and the enrich mediator instruction got empty.
Is not it supported in this version? Is there a walkaround for this?
Carbon Studio 1.0.14 supports both ESB 3.0.1 and ESB 4.0.0. By default is it configured for ESB 3.0.1.
With ESB 3.0.1, there was no option to get the Enrich source from Registry. It was enabled in ESB 4.0.0. Therefore you need to configure Carbon Studio ESB editor for ESB 4.0.0.
You can do it with following steps.
Window -> Preferences
Expand Carbon Studio and Select ESB.
Select ESB 4.0.0 in the ESB Version drop down box and click on Apply and OK.
Close your Sequence editor and reopen the Sequence with ESB editor.
Then try to re-import the same configuration to Carbon Studio from source view.
Hope this helps!!
Thanks and Regards,
Harshana