On Sat, Nov 13, 2010 at 4:12 AM, David Borja wrote:
> Please!! i need help with this!! i.m going slightly mad! urgent!!, i.m
> doing a demo for a customer!!!
Is it possible to share the synapse.xml?
Thanks,
Hiranya
>
>
>
> Thanks!!
>
> Regards
>
>
> On Fri, Nov 12, 2010 at 5:06 PM, David Bor
Please!! i need help with this!! i.m going slightly mad! urgent!!, i.m doing
a demo for a customer!!!
Thanks!!
Regards
On Fri, Nov 12, 2010 at 5:06 PM, David Borja wrote:
>
> Hi Devs!!
>
> I am getting the following warning message:
>
> "Synapse received a response for the request with messag
Hi Devs!!
I am getting the following warning message:
"Synapse received a response for the request with message id:
urn:xxx but a callback is not registered (anymore) to
process this response".
Then a Read time out exception is thrown.
I am working with a TCP monitor and i can
Hi David,
This is a known issue from carbon studio side which is fixed now. This fix
will be available in Carbon Studio 1.0.1 release which will be out by next
week.
As a work-around what you can try out is, inside the Car file that you have
created, go to mediator bundle which is located inside
Fixed on the trunk. It was already fixed in 3.1.0 branch.
Thanks,
Hiranya
On Thu, Nov 11, 2010 at 1:16 PM, Prabath Abeysekera wrote:
>
> Hi,
>
> got the following compilation error while building components of carbon.
>
> [INFO]
> -
Yes, is 1.4.0-wso2v2
Regards
On Fri, Nov 12, 2010 at 3:43 PM, Hiranya Jayathilaka wrote:
>
>
> On Sat, Nov 13, 2010 at 2:04 AM, David Borja wrote:
>
>> Hiranya, i.m using WSO2 v3.0.1 and WSO2 Carbon Studio v1.0.0
>>
>
> In ESB 3.0.1 the synapse version was 1.4.0-wso2v2. Can you please verify
>
On Sat, Nov 13, 2010 at 2:04 AM, David Borja wrote:
> Hiranya, i.m using WSO2 v3.0.1 and WSO2 Carbon Studio v1.0.0
>
In ESB 3.0.1 the synapse version was 1.4.0-wso2v2. Can you please verify
that?
Thanks,
Hiranya
>
>
> Regards
>
>
> On Fri, Nov 12, 2010 at 3:27 PM, Hiranya Jayathilaka wrote:
>
Hiranya, i.m using WSO2 v3.0.1 and WSO2 Carbon Studio v1.0.0
Regards
On Fri, Nov 12, 2010 at 3:27 PM, Hiranya Jayathilaka wrote:
> Hi David,
>
> On Sat, Nov 13, 2010 at 1:47 AM, David Borja wrote:
>
>>
>>
>> Hi Devs!
>>
>> I'm getting a ClassNotFoundException:
>> org.apache.synapse.mediators.A
Hi David,
On Sat, Nov 13, 2010 at 1:47 AM, David Borja wrote:
>
>
> Hi Devs!
>
> I'm getting a ClassNotFoundException:
> org.apache.synapse.mediators.AbstractMediator when i deploy the .car
> application exported from Eclipse WSO2 Studio.
>
> I have created a class called CustomHeaderMediator th
Hi Devs!
I'm getting a ClassNotFoundException:
org.apache.synapse.mediators.AbstractMediator when i deploy the .car
application exported from Eclipse WSO2 Studio.
I have created a class called CustomHeaderMediator that extends
AbstractMediator, then i have created an artifact ESB Mediator with th
On Sat, Nov 13, 2010 at 1:10 AM, Hiranya Jayathilaka wrote:
> The ReaderInputStream class is only available in the transport branch used
> in the 3.1.0 branch. It's no longer available in transports trunk. This
> class has a comment which says:
>
> // NOTE: Remove this class once Commons IO 2.0 is
The ReaderInputStream class is only available in the transport branch used
in the 3.1.0 branch. It's no longer available in transports trunk. This
class has a comment which says:
// NOTE: Remove this class once Commons IO 2.0 is available (see IO-158)
In Carbon trunk we have a dependency to Commo
[INFO] [compiler:compile]
[INFO] Compiling 184 source files to
/home/hiranya/Projects/Java/carbon-platform/trunk/core/org.wso2.carbon.registry.core/target/classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
---
Wouldn't it be multi-tenanted if we simply configure the scope and
Registry tenant for each correctly?
Paul
On 12 November 2010 16:05, Hiranya Jayathilaka wrote:
> Hi Charitha,
>
> On Fri, Nov 12, 2010 at 4:21 PM, Charitha Kankanamge
> wrote:
>>
>> On Fri, Nov 12, 2010 at 3:03 PM, Senaka Fernan
You'll need to set the Content-Type header appropriately in the JMS proxy.
Rajika
On Fri, Nov 12, 2010 at 5:45 PM, Chintana Wilamuna wrote:
> Hi,
>
> Messages that ESB receives over JMS with Qpid are base64 encoded. Is
> it the expected behaviour? If you need to extract info from the
> payload,
On Fri, Nov 12, 2010 at 5:45 PM, Chintana Wilamuna wrote:
> Hi,
>
> Messages that ESB receives over JMS with Qpid are base64 encoded. Is
> it the expected behaviour? If you need to extract info from the
> payload, how can you do that?
>
What's your ESB configuration like?
Thanks,
Hiranya
>
Hi,
Messages that ESB receives over JMS with Qpid are base64 encoded. Is
it the expected behaviour? If you need to extract info from the
payload, how can you do that?
-Chintana
--
Chintana Wilamuna
Associate Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
phone: +94 7
Hi all
Find the BAM RC15 here [1].
[1]http://builder.wso2.org/~carbon/releases/carbon/3.0.1/bam/RC15/
Thanks
ajithn
___
Carbon-dev mailing list
Carbon-dev@wso2.org
https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
On Fri, Nov 12, 2010 at 4:21 PM, Charitha Kankanamge wrote:
>
> On Fri, Nov 12, 2010 at 3:03 PM, Senaka Fernando wrote:
>
>>
>>
>> On Fri, Nov 12, 2010 at 12:48 PM, Hiranya Jayathilaka
>> wrote:
>>
>>>
>>>
>>> On Fri, Nov 12, 2010 at 12:39 PM, Charitha Kankanamge >> > wrote:
>>>
Hirany
On Fri, Nov 12, 2010 at 3:03 PM, Senaka Fernando wrote:
>
>
> On Fri, Nov 12, 2010 at 12:48 PM, Hiranya Jayathilaka wrote:
>
>>
>>
>> On Fri, Nov 12, 2010 at 12:39 PM, Charitha Kankanamge
>> wrote:
>>
>>>
>>> Hiranya,
>>>
>>> AFAIK, there is no way for tenant admin to configure discovery proxy
>
On Fri, Nov 12, 2010 at 12:48 PM, Hiranya Jayathilaka wrote:
>
>
> On Fri, Nov 12, 2010 at 12:39 PM, Charitha Kankanamge
> wrote:
>
>>
>> Hiranya,
>>
>> AFAIK, there is no way for tenant admin to configure discovery proxy since
>> the setting is in axis2.xml. I think this should be enabled by def
21 matches
Mail list logo
