Re: [Carbon-dev] Error building trunk

[Amila Suriarachchi]

I also got this exception when building the registry component since now
component-mgt is removed. Please update those references as well.

thanks,
Amila.

On Mon, Oct 3, 2011 at 8:37 AM, Pradeep Fernando  wrote:

> Hi,
>
> we were in the process of re-factoring the component manager code. Now its
> called feature manager.
>
> thanks,
> --Pradeep
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] [Architecture] Revamping Message Routing Mediators in ESB

[Srinath Perera]

Are we agreeing to Revamping? Hiranya, do you have any concerns?

On Tue, Oct 4, 2011 at 12:15 PM, Amila Suriarachchi  wrote:
>
>
> On Tue, Oct 4, 2011 at 11:45 AM, Srinath Perera  wrote:
>>
>> +1 .. if we can replace all with one mediator .. that is great! but we
>> have to carefully design the syntax to make sure final result is
>> natural for all cases.
>
> I think there are two ends for this. One is making it general. Other think
> is make common case simple.
>
> Current filter (it actually does some thing like if) mediator configurations
> can be as follows.
>
>  
>   
>   
>    
>    
>   
>   
>    
>
> former 'xpath' is referred to an xpath returning a boolean while the
> 'source' attribute refer to an xpath returning a text value. Here it has
> tried to cover different specific scenarios which make that particular
> occasion to use it easily.
>
> But we if follow an method like BPEL by using another copy mediator (in fact
> I think these are not mediators but some language constructs). It would have
> written like this.
>
> 
>
> 
>   
>   
> 
>
> 
>   
>   
> 
>
> then it is more generic. And no need to repeat the xpath, source veriables
> with each mediator. But for a simple xpath based filter need to use another
> copy mediator etc ..
>
> thanks,
> Amila.
>
>
>
>
>
>>
>> --Srinath
>>
>> On Fri, Sep 30, 2011 at 3:03 PM, Kasun Indrasiri  wrote:
>> > Hi all,
>> > In the current ESB implementation we have couple of mediators for
>> > message
>> > routing. While 'Filter' and 'Switch' mediators provide basic level of
>> > message filtering, router mediator is also doing very similar to what
>> > filter/switch mediators do. The usage of Router mediator is rare and
>> > often
>> > got replaced by filter/switch mediators. So, IMO, Router Mediator is
>> > redundant, unless it provides some advance/complex routing logic
>> > support.
>> > In the ESB 4.0.0 release, we introduces 'Conditional Router', which is
>> > intended to route messages based on HTTP headers, query parameters and
>> > url.
>> > However, this doesn't support routing based on message payload. But
>> > unlike
>> > 'Router', the 'Conditional Router' introduces uses the concepts of
>> > 'Evaluators' (And, Or, Match, Equal, Not) that can be utilize to
>> > construct
>> > complex routing logics.
>> > eg:
>> >  
>> >                     
>> >                         
>> >                             
>> >                                 > > source="my_custom_header1" regex="foo.*"/>
>> >                                 > > regex="/services/StockQuoteProxy.*"/>
>> >                             
>> >                         
>> >                         
>> >                     
>> >                     
>> >                         
>> >                             
>> >                                 > > source="my_custom_header2" regex="bar.*"/>
>> >                                 > > value="qpv_foo"/>
>> >                                 
>> >                                     > > regex="/services/StockQuoteProxy.*"/>
>> >                                     > > source="my_custom_header3" regex="foo.*"/>
>> >                                 
>> >                                 
>> >                                     > > value="qpv_bar"/>
>> >                                 
>> >                             
>> >                         
>> >                         
>> >                     
>> > 
>> > So, we can easily add message level routing capability(so that we can
>> > drop
>> > Router mediator) to Conditional Router and with that we'll get the power
>> > of
>> > using evaluators for message level routing as well. Having bunch of
>> > mediators that's doing the similar thing, cause a negative effect on
>> > ESB's
>> > usability.
>> > (Most of the pointed listed here, were discussed during last code-review
>> > of
>> > Group-D.)
>> >
>> >
>> > [1] http://wso2.org/project/esb/java/4.0.0/docs/mediator_guide.html
>> >
>> > Thanks,
>> > --
>> > Kasun Indrasiri
>> > Associate Technical Lead
>> > WSO2, Inc.; http://wso2.com
>> > lean.enterprise.middleware
>> >
>> > cell: +94 71 536 4128
>> > Blog : http://kasunpanorama.blogspot.com/
>> >
>>
>>
>>
>> --
>> 
>> Srinath Perera, Ph.D.
>>   Senior Software Architect, WSO2 Inc.
>>   Visiting Faculty, University of Moratuwa
>>   Member, Apache Software Foundation
>>   Research Scientist, Lanka Software Foundation
>>   Blog: http://srinathsview.blogspot.com/
>> ___
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>



-- 

Srinath Perera, Ph.D.
   http://www.cs.indiana.edu/~hperera/
   http://srinathsview.blogspot.com/
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Starting Multiple ESB instances

[Hiranya Jayathilaka]

On Tue, Oct 4, 2011 at 8:25 PM, Senaka Fernando  wrote:

> Hi all,
>
> FYI, the documentation in [1] mentions that you need to set offset in
> carbon.xml, but this won't work properly for two ESB instances. You also
> need to change the NIO ports in axis2.xml, which is not mentioned in [1]
> (see "Running Multiple Instance of the WSO2 Carbon Servers in the Same
> Machine"). If this is a bug, can we please fix this for the upcoming
> release?
>

Already fixed

Thanks,
Hiranya


>
> [1]
> http://docs.wso2.org/display/ESB/Deploying+the+WSO2+ESB+on+Your+Infrastructure
>
> Thanks,
> Senaka.
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>


-- 
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Updated Invitation: [Code Review] [Group B] Message box core - connection reuse @ Tue Oct 4 10:30am - 11:30am (nu...@wso2.com)

[Manjula Rathnayake]

On Tue, Oct 4, 2011 at 2:41 PM, Manjula Rathnayake wrote:

> Hi all,
>
> Code review notes:
>
> 1. Current implementation of SQS(message-box) does not use JMS connection
> reuse. Instead, It creates queue connections(tcp connections) per message.
> The reason behind this is to handle visibility timeout using JMS transaction
> CLIENT_ACKNOWLEDGE mode. When a message is received, the queue connection is
> created and session created with CLIENT_ACKNOWLEDGE enabled. If the user
> does not delete the received message, the session is closed without
> acknowledge. As a result the received message will be available or visible
> to other users to receive again. If the user delete the message after
> receiving it, message is acknowledged. If we acknowledge a message in the
> middle of the queue, the messages up-to that message also acknowledged. This
> causes to use per connection per message.
>

As per offline chat with amila and going through the previous connection
cache code, We can implement the connection re-use. This is just a
correction to above statement. We can have connection cache enabled per user
and one session per message retrieval. And it is not one connection per
message, however In the current implementation, it is one connection per
message. We will implement this and update on this.

>
> Action item: There was an implementation to cache connection, and it was
> removed due to not working properly with multiple receivers. This should be
> fixed and tested.  And look for other alternative to implement above use
> case.
>
> 2. The behavior of some JMS API calls is different with different
> providers, ex. create persistent queues, queue receiver receive methods. So
> add comments on such methods used so that it can be identified fast.
>
> 3. Add error logs before throwing exceptions.
>
>
> After two weeks, these improvements will be reviewed again.
>
> If I have missed anything, please add comments.
>
> Thank you.
>
>
>
> On Tue, Oct 4, 2011 at 10:27 AM, Nuwan Bandara  wrote:
>
>> GROUP B, Reminder !!!
>>
>> On Tue, Oct 4, 2011 at 10:02 AM, Shammi Jayasinghe wrote:
>>
>>>  This event has been changed.
>>> more details 
>>> »
>>> [Code Review] [Group B] Message box core - connection reuse
>>> *Changed: *crcuible link : 
>>> https://wso2.org/crucible/cru/COMPONENT-63
>>>  *When*
>>> Tue Oct 4 10:30am – 11:30am Colombo
>>> *Where*
>>> #59 - Board Room (map
>>> )
>>> *Calendar*
>>> nu...@wso2.com
>>> *Who*
>>> •
>>> sha...@wso2.com - organizer
>>> •
>>> Chamara Ariyarathne
>>> •
>>> Achala Aponso
>>> •
>>> Deependra Ariyadewa
>>> •
>>> Dimuthu Leelarathne
>>> •
>>> Manjula Rathnayake
>>> •
>>> Nuwan Bandara
>>> •
>>> carbon-dev@wso2.org
>>> •
>>> Krishantha Samaraweera
>>> •
>>> Nuwan Wimalasekara
>>> •
>>> Sanjeewa Malalgoda
>>> •
>>> Anjana Fernando
>>> •
>>> Nandika Jayawardana
>>> •
>>> Ajith Vitharana
>>> •
>>> Thilini Ishaka
>>> •
>>> Jasintha Dasanayake
>>>
>>> Going?   
>>> ***Yes-
>>> Maybe-
>>> No
>>> ***more options 
>>> »
>>>
>>> Invitation from Google Calendar 
>>>
>>> You are receiving this email at the account nu...@wso2.com because you
>>> are subscribed for updated invitations on calendar nu...@wso2.com.
>>>
>>> To stop receiving these notifications, please log in to
>>> https://www.google.com/calendar/ and change your notification settings
>>> for this calendar.
>>>
>>
>>
>>
>> --
>> *Thanks & Regards,
>>
>> Nuwan Bandara
>> Senior Software Engineer
>> WSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware
>>
>> http://nuwan.bandara.co
>> *
>> 
>>
>
>
>
> --
> Manjula Rathnayaka
> Software Engineer
> WSO2, Inc.
> Mobi

[Carbon-dev] Starting Multiple ESB instances

[Senaka Fernando]

Hi all,

FYI, the documentation in [1] mentions that you need to set offset in
carbon.xml, but this won't work properly for two ESB instances. You also
need to change the NIO ports in axis2.xml, which is not mentioned in [1]
(see "Running Multiple Instance of the WSO2 Carbon Servers in the Same
Machine"). If this is a bug, can we please fix this for the upcoming
release?

[1]
http://docs.wso2.org/display/ESB/Deploying+the+WSO2+ESB+on+Your+Infrastructure

Thanks,
Senaka.

-- 
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

*Lean . Enterprise . Middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Why do we have trace.messages property in log4j property configs?

[Thilini Ishaka]

Hi All,

We have found that the wso2carbon-trace-messages.log does not contain any
trace logs after checking it with few products (BPS ,IS).
We have the JIRA at [1] for this and investigated further for the root
cause.

These are the findings.

We have *log4j.logger.trace.messages=TRACE,CARBON_TRACE_LOGFILE *property
and a value assigned, inside log4j.properties
The real use of a this property is to get messages of level *TRACE* or above
to the file specified in *CARBON_TRACE_LOGFILE**.*
With this configuration, we get an empty trace log file.

If we define this property as *log4j.logger.$package_name, *it prints logs
to the trace log file.

So, why do we named it as *trace.messages *and from where it is coming
from?

Please advice on this.

[1] https://wso2.org/jira/browse/CARBON-11079

Thanks

-- 

Regards

Thilini Ishaka
WSO2 Inc
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] Error while building carbon core in trunk

[Isuru Suriarachchi]

[INFO]

[INFO] Building WSO2 Carbon - Feature Manager Core
[INFO]task-segment: [clean, install]
[INFO]

[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting
/home/isuru/checkouts/wso2/carbon/core/feature-manager/org.wso2.carbon.feature.mgt.core/target
[INFO] [incremental-build:incremental-build {execution: default}]
[INFO] Verifying module descriptor ...
[INFO] Pom descriptor modification detected.
[INFO] Deleting
/home/isuru/checkouts/wso2/carbon/core/feature-manager/org.wso2.carbon.feature.mgt.core/target
[INFO] [clean:clean {execution: auto-clean}]
[INFO] Deleting
/home/isuru/checkouts/wso2/carbon/core/feature-manager/org.wso2.carbon.feature.mgt.core/target
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 15 source files to
/home/isuru/checkouts/wso2/carbon/core/feature-manager/org.wso2.carbon.feature.mgt.core/target/classes
[INFO] [scr:scr {execution: generate-scr-scrdescriptor}]
[FATAL ERROR] org.apache.felix.scrplugin.SCRDescriptorMojo#execute() caused
a linkage error (java.lang.NoClassDefFoundError) and may be out-of-date.
Check the realms:
[FATAL ERROR] Plugin realm =
app0.child-container[org.apache.felix:maven-scr-plugin:1.0.10]
urls[0] =
file:/home/isuru/.m2/repository/org/apache/felix/maven-scr-plugin/1.0.10/maven-scr-plugin-1.0.10.jar
urls[1] =
file:/home/isuru/.m2/repository/org/apache/felix/org.osgi.core/1.0.0/org.osgi.core-1.0.0.jar
urls[2] =
file:/home/isuru/.m2/repository/org/apache/felix/org.osgi.compendium/1.0.0/org.osgi.compendium-1.0.0.jar
urls[3] =
file:/home/isuru/.m2/repository/org/apache/felix/javax.servlet/1.0.0/javax.servlet-1.0.0.jar
urls[4] =
file:/home/isuru/.m2/repository/org/apache/felix/org.osgi.foundation/1.0.0/org.osgi.foundation-1.0.0.jar
urls[5] = file:/home/isuru/.m2/repository/asm/asm-all/3.0/asm-all-3.0.jar
urls[6] =
file:/home/isuru/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar
urls[7] =
file:/home/isuru/.m2/repository/org/apache/maven/maven-archiver/2.2/maven-archiver-2.2.jar
urls[8] =
file:/home/isuru/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
urls[9] = file:/home/isuru/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
urls[10] =
file:/home/isuru/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
urls[11] =
file:/home/isuru/.m2/repository/com/thoughtworks/qdox/qdox/1.8/qdox-1.8.jar
urls[12] = file:/home/isuru/.m2/repository/ant/ant/1.5.1/ant-1.5.1.jar
urls[13] = file:/home/isuru/.m2/repository/jmock/jmock/1.0.0/jmock-1.0.0.jar
urls[14] =
file:/home/isuru/.m2/repository/org/slf4j/slf4j-api/1.4.3/slf4j-api-1.4.3.jar
urls[15] =
file:/home/isuru/.m2/repository/org/slf4j/slf4j-simple/1.4.3/slf4j-simple-1.4.3.jar
[FATAL ERROR] Container realm = plexus.core
urls[0] =
file:/home/isuru/software/apache-maven-2.2.1/lib/maven-2.2.1-uber.jar
[INFO]

[ERROR] FATAL ERROR
[INFO]

[INFO] org/eclipse/core/runtime/IRegistryChangeListener
org.eclipse.core.runtime.IRegistryChangeListener
[INFO]

[INFO] Trace
java.lang.NoClassDefFoundError:
org/eclipse/core/runtime/IRegistryChangeListener
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$000(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
at java.lang.Class.getDeclaredMethods(Class.java:1791)
at
com.thoughtworks.qdox.JavaDocBuilder.createBinaryClass(JavaDocBuilder.java:201)
at
com.thoughtworks.qdox.JavaDocBuilder.getClassByName(JavaDocBuilder.java:126)
at
com.thoughtworks.qdox.model.ClassLibrary.getClassByName(ClassLibrary.java:37)
at com.thoughtworks.qdox.model.Type.getJavaClass(Type.java:146)
at
com.thoughtworks.qdox.model.JavaClass.getSuperJavaClass(JavaClass.java:86)
at
org.apache.felix.scrplugin.tags.qdox.QDoxJavaClassDescription.getSuperClass(QDoxJavaClassDescription.java:62)
at
org.apache.felix.scrplugin.tags.JavaClassDescriptionInherita

Re: [Carbon-dev] Updated Invitation: [Code Review] [Group B] Message box core - connection reuse @ Tue Oct 4 10:30am - 11:30am (nu...@wso2.com)

[Afkham Azeez]

Where are the notes?

On Tue, Oct 4, 2011 at 10:27 AM, Nuwan Bandara  wrote:

> GROUP B, Reminder !!!
>
> On Tue, Oct 4, 2011 at 10:02 AM, Shammi Jayasinghe wrote:
>
>>  This event has been changed.
>> more details 
>> »
>> [Code Review] [Group B] Message box core - connection reuse
>> *Changed: *crcuible link : 
>> https://wso2.org/crucible/cru/COMPONENT-63
>>  *When*
>> Tue Oct 4 10:30am – 11:30am Colombo
>> *Where*
>> #59 - Board Room (map
>> )
>> *Calendar*
>> nu...@wso2.com
>> *Who*
>> •
>> sha...@wso2.com - organizer
>> •
>> Chamara Ariyarathne
>> •
>> Achala Aponso
>> •
>> Deependra Ariyadewa
>> •
>> Dimuthu Leelarathne
>> •
>> Manjula Rathnayake
>> •
>> Nuwan Bandara
>> •
>> carbon-dev@wso2.org
>> •
>> Krishantha Samaraweera
>> •
>> Nuwan Wimalasekara
>> •
>> Sanjeewa Malalgoda
>> •
>> Anjana Fernando
>> •
>> Nandika Jayawardana
>> •
>> Ajith Vitharana
>> •
>> Thilini Ishaka
>> •
>> Jasintha Dasanayake
>>
>> Going?   
>> ***Yes-
>> Maybe-
>> No
>> ***more options 
>> »
>>
>> Invitation from Google Calendar 
>>
>> You are receiving this email at the account nu...@wso2.com because you
>> are subscribed for updated invitations on calendar nu...@wso2.com.
>>
>> To stop receiving these notifications, please log in to
>> https://www.google.com/calendar/ and change your notification settings
>> for this calendar.
>>
>
>
>
> --
> *Thanks & Regards,
>
> Nuwan Bandara
> Senior Software Engineer
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
> http://nuwan.bandara.co
> *
> 
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] Updated Invitation: [Code Review] [Group B] Message box core - connection reuse @ Tue Oct 4 10:30am - 11:30am (nu...@wso2.com)

[Manjula Rathnayake]

Hi all,

Code review notes:

1. Current implementation of SQS(message-box) does not use JMS connection
reuse. Instead, It creates queue connections(tcp connections) per message.
The reason behind this is to handle visibility timeout using JMS transaction
CLIENT_ACKNOWLEDGE mode. When a message is received, the queue connection is
created and session created with CLIENT_ACKNOWLEDGE enabled. If the user
does not delete the received message, the session is closed without
acknowledge. As a result the received message will be available or visible
to other users to receive again. If the user delete the message after
receiving it, message is acknowledged. If we acknowledge a message in the
middle of the queue, the messages up-to that message also acknowledged. This
causes to use per connection per message.

Action item: There was an implementation to cache connection, and it was
removed due to not working properly with multiple receivers. This should be
fixed and tested.  And look for other alternative to implement above use
case.

2. The behavior of some JMS API calls is different with different providers,
ex. create persistent queues, queue receiver receive methods. So add
comments on such methods used so that it can be identified fast.

3. Add error logs before throwing exceptions.


After two weeks, these improvements will be reviewed again.

If I have missed anything, please add comments.

Thank you.



On Tue, Oct 4, 2011 at 10:27 AM, Nuwan Bandara  wrote:

> GROUP B, Reminder !!!
>
> On Tue, Oct 4, 2011 at 10:02 AM, Shammi Jayasinghe wrote:
>
>>  This event has been changed.
>> more details 
>> »
>> [Code Review] [Group B] Message box core - connection reuse
>> *Changed: *crcuible link : 
>> https://wso2.org/crucible/cru/COMPONENT-63
>>  *When*
>> Tue Oct 4 10:30am – 11:30am Colombo
>> *Where*
>> #59 - Board Room (map
>> )
>> *Calendar*
>> nu...@wso2.com
>> *Who*
>> •
>> sha...@wso2.com - organizer
>> •
>> Chamara Ariyarathne
>> •
>> Achala Aponso
>> •
>> Deependra Ariyadewa
>> •
>> Dimuthu Leelarathne
>> •
>> Manjula Rathnayake
>> •
>> Nuwan Bandara
>> •
>> carbon-dev@wso2.org
>> •
>> Krishantha Samaraweera
>> •
>> Nuwan Wimalasekara
>> •
>> Sanjeewa Malalgoda
>> •
>> Anjana Fernando
>> •
>> Nandika Jayawardana
>> •
>> Ajith Vitharana
>> •
>> Thilini Ishaka
>> •
>> Jasintha Dasanayake
>>
>> Going?   
>> ***Yes-
>> Maybe-
>> No
>> ***more options 
>> »
>>
>> Invitation from Google Calendar 
>>
>> You are receiving this email at the account nu...@wso2.com because you
>> are subscribed for updated invitations on calendar nu...@wso2.com.
>>
>> To stop receiving these notifications, please log in to
>> https://www.google.com/calendar/ and change your notification settings
>> for this calendar.
>>
>
>
>
> --
> *Thanks & Regards,
>
> Nuwan Bandara
> Senior Software Engineer
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
> http://nuwan.bandara.co
> *
> 
>



-- 
Manjula Rathnayaka
Software Engineer
WSO2, Inc.
Mobile:+94 77 743 1987
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] HELP: Can HTTP 200 response include empty body?

[Hiranya Jayathilaka]

On Tue, Oct 4, 2011 at 1:41 PM, Charitha Kankanamge wrote:

> Folks,
>
> Is the body optional for HTTP 200 OK messages? In other words, is the
> following response valid?
>

HTTP entity is always optional regardless of the status code.

Thanks,
Hiranya


>
> HTTP/1.1 200 OK
> Server: Apache-Coyote/1.1
> Content-Length: 0
> Date: Tue, 04 Oct 2011 07:40:56 GMT
>
> Thanks!
> Charitha
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Re: [Carbon-dev] HELP: Can HTTP 200 response include empty body?

[Sadeep Jayasumana]

Hi,

On Tue, Oct 4, 2011 at 1:41 PM, Charitha Kankanamge wrote:

> Folks,
>
> Is the body optional for HTTP 200 OK messages? In other words, is the
> following response valid?
>

Yes. This is a valid response [1]. Specially, response to a HEAD request
always comes without an entity body.

[1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.1

Thanks,
Sadeep


>
> HTTP/1.1 200 OK
> Server: Apache-Coyote/1.1
> Content-Length: 0
> Date: Tue, 04 Oct 2011 07:40:56 GMT
>
> Thanks!
> Charitha
>
>
> ___
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
Sadeep Jayasumana

Software Engineer
WSO2 Inc.
Email - sad...@wso2.com
Mobile - +94 77 22 66 507
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

[Carbon-dev] HELP: Can HTTP 200 response include empty body?

[Charitha Kankanamge]

Folks,

Is the body optional for HTTP 200 OK messages? In other words, is the
following response valid?

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Length: 0
Date: Tue, 04 Oct 2011 07:40:56 GMT

Thanks!
Charitha
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev