Hi kasun,
I think he is built axiom from apache trunk :)
Lahiru
On Fri, May 7, 2010 at 9:43 AM, Kasun Indrasiri ka...@wso2.com wrote:
Try, checkout and building axiom from[1] and then rebuilding orbit.
Thanks.
[1]
http://svn.apache.org/repos/asf/webservices/commons/trunk/modules/axiom
On Fri, May 7, 2010 at 1:30 PM, Lahiru Gunathilake lah...@wso2.com wrote:
you get the same error if you check out
only org.wso2.carbon.mediator.dbreport.ui ? If you are not getting an error
just copy that directory to the place where you have the main platform check
out.
Yes.
So I guess I'm
HI All
Following things are added to the tool
Now it uses carbon data sources for getting the connection information
can generates multiple service(one service per table) as well as the
single service(one service for whole database) .
user can select the service/services generation
as per [1] .. after updating with a proxy service with proxy UI , any
attached policies to proxy are lost ... Also , if you have configure a
security scenario through the service management page to a proxy service ,
you can not update the synapse configuration from manage configuration
menu.
The JCR Testing for the javax.jcr package is still in progress.And was able
to get rid from errors and exceptions from registry workspace test.Actually
those were there, because there wasn't a retention manager in our
implementation.As it should be implemented in the carbon level ,I just
Source View for individual mediators was implemented.
New palette which is movable was implemented (which is suggested by supun).
A context menu was added to to the sequence design tree. We can use this
menu to insert mediators, remove mediators, view source of the design tree.
Thanks
Isuru
Isuru,
Please point me to the source svn location of this tool.
Thanks,
Ruwan
Isuru Loku Narangoda wrote:
Source View for individual mediators was implemented.
New palette which is movable was implemented (which is suggested by
supun).
A context menu was added to to the sequence design
