On Tue, Mar 8, 2011 at 11:22 AM, Thilina Buddhika wrote:
> In addition to these, shall we include org.wso2.carbon.authenticator.proxy
> bundle as well ?
>
> This contains the stubs generated for default Carbon Authenticator Service,
> which is required when invoking Carbon admin services.
>
> If
In addition to these, shall we include org.wso2.carbon.authenticator.proxy
bundle as well ?
This contains the stubs generated for default Carbon Authenticator Service,
which is required when invoking Carbon admin services.
If this bundle is available directly, users do not have to code generate
a
On Tue, Mar 8, 2011 at 10:33 AM, Afkham Azeez wrote:
> Nothing specific to AS if you include the axis2-client JAR. Nothing
> specific to Stratos as well. carbon-base and its dependencies would be
> needed to support the Carbon programming model.
Same for BPS, You can talk to management api throu
Nothing specific to AS if you include the axis2-client JAR. Nothing specific
to Stratos as well. carbon-base and its dependencies would be needed to
support the Carbon programming model.
Azeez
On Mon, Mar 7, 2011 at 3:57 PM, Saminda Wijeratne wrote:
> Devs any help on this please?
>
> Saminda
>
Devs any help on this please?
Saminda
On Sat, Mar 5, 2011 at 9:12 AM, Saminda Wijeratne wrote:
>
>
> On Sat, Mar 5, 2011 at 7:06 AM, Afkham Azeez wrote:
>
>> Instead of the many JARs, why can't you simply use the axis2-client JAR?
>
> Will do.
>
>>
>> Also, from a programming model & client AP
On Sat, Mar 5, 2011 at 7:06 AM, Afkham Azeez wrote:
> Instead of the many JARs, why can't you simply use the axis2-client JAR?
Will do.
>
> Also, from a programming model & client API PoV, there is no difference
> between Carbon or Stratos Apps. So, to write an app that is deployed on
> Stratos
Instead of the many JARs, why can't you simply use the axis2-client JAR?
Also, from a programming model & client API PoV, there is no difference
between Carbon or Stratos Apps. So, to write an app that is deployed on
Stratos, you should never require anything additional.
On Fri, Mar 4, 2011 at 5:
What I meant by client side is that, for example when a user wants to
programatically work with our products (eg: using the registry API to talk
to the registry), he/she will need some libraries added to the classpath
(eg: org.wso2.carbon.registry.core). Any library as such goes along helping
a dev
Hi,
You need only client-side libraries?. If so I can add a list of libs in our
product specific components. What about dependencies etc?
On Fri, Mar 4, 2011 at 5:13 PM, Saminda Wijeratne wrote:
> The feature I'm creating here is helping developers add libraries to their
> projects using CS. I n
The feature I'm creating here is helping developers add libraries to their
projects using CS. I need to know what libraries needed generally & product
specific.
*General*
abdera-1.0.0.wso2v1.jar
axiom-1.2.9.wso2v1.jar
axis2-1.6.0.wso2v1.jar
commons-codec-1.3.0.wso2v1.jar
commons-collections-3.2.0
10 matches
Mail list logo