from:"Isuru Suriarachchi"

Hi Nuwan/Anjana,

As you know, we are trying to ship AS with Carbon core at least by the end
of next week and we are targeting an RC from the new branch by Wednesday.
So we'll have to fix all L1's and L2's related to MS, Jaggery and DS
components by Wednesday and freez the code. Is that possible? Please let us
know if there are any concerns..

Thanks,
~Isuru

-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Branch : Clean repo build error on jaggery script engine module

Any idea??

[ERROR] Failed to execute goal on project org.jaggeryjs.scriptengine: Could
not resolve dependencies for project
org.jaggeryjs:org.jaggeryjs.scriptengine:bundle:0.9.0: Failure to find
org.wso2.wsf.javascript:axiom-e4x:jar:2.0.1.SNAPSHOT in
http://dist.wso2.org/maven2/ was cached in the local repository, resolution
will not be reattempted until the update interval of wso2-maven2-repository
has elapsed or updates are forced - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Branch : Error while building features/jaggery

I can see plenty of SNAPSHOT versions in the features/jaggery/pom.xml.
Please fix..

[ERROR] Plugin org.wso2.maven:carbon-p2-plugin:1.5-SNAPSHOT or one of its
dependencies could not be resolved: Failed to read artifact descriptor for
org.wso2.maven:carbon-p2-plugin:jar:1.5-SNAPSHOT: Failure to find
org.wso2.maven:carbon-p2-plugin:pom:1.5-SNAPSHOT in
http://dist.wso2.org/maven2 was cached in the local repository, resolution
will not be reattempted until the update interval of
wso2-maven2-repository-1 has elapsed or updates are forced - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.


-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Branch : commons module versions

Currently the commons modules are versioned as follows..

modulecommons-vfs/2.0-wso2v4/module
modulecommons/balana/1.0.0-wso2v1/module
modulecommons/siddhi/1.0.0-wso2v1/module
modulecommons/throttle/3.3.0-wso2v1/module
modulecommons/wsdlvalidator/1.2.0-wso2v1/module

This -wso2v1 part is redundant because these are already wso2 projects. We
never used it in earlier releases. Although this is not a major issue,
better to fix..

Thanks,
~Isuru

-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Shall we ship a jax-rs application by default for super tenant?

2012-07-16 Thread Isuru Suriarachchi

+1. Please go ahead..

Thanks,
~Isuru

On Mon, Jul 16, 2012 at 7:54 PM, Supun Malinga sup...@wso2.com wrote:

 Hi,

 How about $subject. Currently at initial startup jax-rs applications page
 is empty. This would help usability as well.

 thanks,
 --
 Supun Malinga,

 Software Engineer,
 WSO2 Inc.
 http://wso2.com
 http://wso2.org
 email - sup...@wso2.com sup...@wso2.com
 mobile - 071 56 91 321




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Carbon classes no longer visible to webapps

2012-07-10 Thread Isuru Suriarachchi

Hi Tharindu,

The fix you guys has done yesterday has broken the JAX* support in AS :).

I've fixed it properly and committed to trunk few minutes back. Please
check and let me know if there's an issue.

Thanks,
~Isuru

On Tue, Jul 10, 2012 at 4:46 PM, Tharindu Mathew thari...@wso2.com wrote:

 Hi,

 This is working perfectly now, and is part of the BAM Alpha 3 release.
 Thanks Azeez and Pradeep.


 On Mon, Jul 9, 2012 at 4:33 PM, Pradeep Fernando prad...@wso2.com wrote:

 Hi,

 No. As changes were done sometime ago, (weeks ago). If you are reffering
 to appserver support, then No as well. They are local to me.

 --Pradeep




 --
 Regards,

 Tharindu

 blog: http://mackiemathew.com/
 M: +9459908


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Carbon classes no longer visible to webapps

2012-07-10 Thread Isuru Suriarachchi

On Tue, Jul 10, 2012 at 5:51 PM, Tharindu Mathew thari...@wso2.com wrote:

 How can that happen? We were just re-using the same feature, to deploy a
 JAXRS web app in BAM.

 Anyway, which part did you fix? Kernel?


orbit and kernel..




 On Tue, Jul 10, 2012 at 5:44 PM, Isuru Suriarachchi is...@wso2.comwrote:

 Hi Tharindu,

 The fix you guys has done yesterday has broken the JAX* support in AS :).

 I've fixed it properly and committed to trunk few minutes back. Please
 check and let me know if there's an issue.

 Thanks,
 ~Isuru

 On Tue, Jul 10, 2012 at 4:46 PM, Tharindu Mathew thari...@wso2.comwrote:

 Hi,

 This is working perfectly now, and is part of the BAM Alpha 3 release.
 Thanks Azeez and Pradeep.


 On Mon, Jul 9, 2012 at 4:33 PM, Pradeep Fernando prad...@wso2.comwrote:

 Hi,

 No. As changes were done sometime ago, (weeks ago). If you are
 reffering to appserver support, then No as well. They are local to me.

 --Pradeep




 --
 Regards,

 Tharindu

 blog: http://mackiemathew.com/
 M: +9459908


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




 --
 Regards,

 Tharindu

 blog: http://mackiemathew.com/
 M: +9459908




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] C-App synchronization in a Carbon cluster

On Mon, Jul 9, 2012 at 10:55 AM, Muhammed Shariq sha...@wso2.com wrote:


 On Fri, Jul 6, 2012 at 6:05 PM, Isuru Suriarachchi is...@wso2.com wrote:

 Hi all,

 I'm trying to fix [1]. Here's the root cause for this issue..

 Imagine a Carbon cluster with 2 nodes where the svn based deployment
 synchronizer (DS) is configured. When a C-App is deployed to node1, it is
 extracted and individual artifacts are copied into respective hot
 directories. When the DS runs for the first time, it copies the C-App into
 node2 and it will be deployed there. When the DS runs again in node1, it
 will try to copy the individual artifacts to node2. But node2 already has
 those artifacts as the C-App id already deployed in node2. Therefore an svn
 conflict occurs.

 To resolve this issue, there are two possible options..

 1. Keeping all artifacts coming from C-Apps out of the repository
 (repository/deployment/server)
 2. Keeping the original C-App out of the repository

 Initially I tried option 1 above and programetically called the relevant
 deployers for individual artifacts. But this creates lot of problems with
 some artifacts (Ex: ESB stuff). Therefore, I'm trying to solve the initial
 problem using option 2 above.

 I've taken the carbonapps directory out of repository/deployment/server
 directory and kept it as repository/carbonapps (we can change this if
 needed). Still the carbonapps directory has hot deployment capabilities.
 But it won't be synchronized by the DS. So when a C-App is deployed into
 node 1, it will be extracted and only the individual artifacts will be
 copied into the repository. When the DS runs, all needed artifacts will be
 synced to node 2. Therefore, functionality wise, there won't be any issues
 on node 2.

 But if someone logs into the management console of node 2 and go to the
 C-App list, nothing will be listed. Is this something we have to fix?
 Because anyway in a RW/RO cluster, user can't use the management console of
 the slave node.


 Also we will lose the relationship between the C-App and its artifacts
 right? For example, now if we delete the C-App, then all its dependent
 artifacts will get undeployed automatically etc. But as per 2nd solution,
 in node 2 the dependent artifacts will be independent resources, so if we
 want to undeploy the C-App, we should manually remove the
 dependent artifacts from the respective lists.


No that won't be the case, the relationship between the C-App and it's
artifacts will be there on node 1. So when the C-App is deleted on node 1,
all respective arficats will be deleted. When the DS runs, it will make
sure all those will be deleted at node 2 as well. You can't use the
management console of node 2 in any case.

Thanks,
~Isuru


 Of course functionality wise there shouldn't be any issues ...


 WDYT??

 Thanks,
 ~Isuru

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

 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Thanks,
 Shariq.
 Phone: +94 777 202 225




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] C-App synchronization in a Carbon cluster

On Sat, Jul 7, 2012 at 11:01 AM, Kasun Gajasinghe kas...@wso2.com wrote:

 Hi Isuru,

 I'd like to add a third option to the list for consideration. :)

 How about doing the synchronization between cluster nodes AFTER the
 C-App's extracted artifacts are deployed?


This is kind of not possible with the current implementation. That is
because, C-App doesn't know when the individual artifacts will get
deployed. It just copies the artifacts into hot directories.

And also the synchronization will be called for each and every deployment
cycle, it doesn't know whether there's a C-App to be deployed..

Thanks,
~Isuru


 I'm not sure whether it's possible to do with the current architecture,
 but if it is, then I think things will be easier.
 But with this option, there could be issues in node 2. That's because node
 2 will also try to deploy the C-App as well in addition to its artifacts!
 Hope that can be fixed!

 WDYT?

 Thanks,
 --KasunG

 To resolve this issue, there are two possible options..

 1. Keeping all artifacts coming from C-Apps out of the repository
 (repository/deployment/server)
 2. Keeping the original C-App out of the repository

 Initially I tried option 1 above and programetically called the
 relevant deployers for individual artifacts. But this creates lot of
 problems with some artifacts (Ex: ESB stuff). Therefore, I'm trying to
 solve the initial problem using option 2 above.

 I've taken the carbonapps directory out of repository/deployment/server
 directory and kept it as repository/carbonapps (we can change this if
 needed). Still the carbonapps directory has hot deployment capabilities.
 But it won't be synchronized by the DS. So when a C-App is deployed into
 node 1, it will be extracted and only the individual artifacts will be
 copied into the repository. When the DS runs, all needed artifacts will be
 synced to node 2. Therefore, functionality wise, there won't be any issues
 on node 2.


 I see a possible issue with option2.

 Currently it is possible to deploy 3rd party dependencies to Carbon
 Servers using JavaLibraryArtifact C-App Artifact type and Carbon Server
 extensions such as Custom Mediators, Registry Handlers, filters, etc via
 C-Apps. When the C-App is deployed in a server, those artifacts gets
 deployed in to the repository/components/dropins location but not the
 repository.


 Deploying artifacts into dropins is a major issue! It does not work for
 tenants, so is broken anyway. Anything that does not work in multi-tenant
 mode in terms of deployment, can safely be considered to be broken.


 If we go ahead with option 2 to avoid C-Apps getting picked by DS, how
 can we handle the syncing of aforementioned Artifact types across a
 cluster?

 Thanks and Regards,
 Harshana


 But if someone logs into the management console of node 2 and go to the
 C-App list, nothing will be listed. Is this something we have to fix?
 Because anyway in a RW/RO cluster, user can't use the management console of
 the slave node.

 WDYT??

 Thanks,
 ~Isuru

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

 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Harshana Martin
 Senior Software Engineer
 WSO2 Inc. : http://wso2.com ; http://wso2.org
 Mobile: +94 716 062 650
 Profile: https://www.google.com/profiles/harshana05
 Blog: http://harshana05.blogspot.com
 Twitter: http://twitter.com/harshana05



 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




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


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 *Kasun Gajasinghe*
 Software Engineer;
 Development Technologies Team, WSO2 Inc.; http://wso2.com ,
 *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
 *linked-in: *http://lk.linkedin.com/in/gajasinghe*
 *
  *blog: **http://blog.kasunbg.org* http://blog.kasunbg.org*
 twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg*
 *


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise

Re: [Dev] JNDI lookup wont work inside a web-app

As Kishanthan has explained in his last reply, this is not something broken
and this is how Tomcat is supposed to work. Therefore, I think we have to
have a meeting on this and decide what to do.

Thanks,
~Isuru

On Fri, Jul 6, 2012 at 11:44 PM, Dinusha Senanayaka dinu...@wso2.comwrote:

Hi Kishanthan/ AS Team,

Today App-factory team raised this issue again and they also need to have
same requirement. (The capability of accessing resources( inside a wep-app)
that registered with JNDI via carbon component using default InitialContext
of carbon ). We need to discuss and come-up with a solution for this.

Regards,
Dinusha.

On Thu, May 31, 2012 at 3:51 PM, Kishanthan Thangarajah
kishant...@wso2.com wrote:

On Wed, May 30, 2012 at 1:44 PM, Dinusha Senanayaka dinu...@wso2.comwrote:

Here, what we want is to use the same transaction-manager that has
expose by the transaction-manager component inside the web-app. But by
defining it as a resource in server.xml or context.xml , it register a new
transaction manager to use in wep-app rather using it from
transaction-manager component. So we loss the need of having
transaction-manager carbon component.

AFAIK, in previous releases, these resources (TransactionManager, etc)
are registered with tomcat via the context descriptor file
(CARBON_HOME/lib/tomcat/conf/context.xml).

But according to the current implementation in trunk, we are registering
those resources to Carbon's InitialContext via a carbon component
(transaction-manager) and we want those resources to be accessible
everywhere including webapps also. This is the requirement. But as I said
earlier, this will not work as we can see that we are trying to access a
resource which is not registered with tomcat.

So I think the solution for this would be, when registering the resource
via carbon, we have to somehow make those available to tomcat global
resources.

Kishanthan.

Regards,
Dinusha.

On Tue, May 29, 2012 at 11:36 AM, Isuru Suriarachchi is...@wso2.comwrote:

According to this, all our global resources can be registered in the
tomcat server.xml and can be looked up from anywhere. So we can make the
above resources work by doing this.

But if we want to allow users to register and look up resources through
the carbon context, we have to register those resources in the same context
as the server.xml resources. Then only those can be made global.

Thanks,
~Isuru

On Tue, May 29, 2012 at 10:44 AM, Kishanthan Thangarajah
kishant...@wso2.com wrote:

This can be done. We have to first register JNDI resources for webapps
context. Then we can lookup for them. As Paul mentioned, registering those
resources can done in two ways. They can be either global or per webapp.
If
it is global, you have place them under GlobalNamingResources tag in
tomcat's server.xml (catalina-server.xml in our case) file. Then they can
be referenced in webapp via linking them in the context.xml file of
webapp.

Eg - ResourceLink name=jdbc/MyDataSource
global=jdbc/MyDataSource
type=com.atomikos.jdbc.AtomikosDataSourceBean/

If it is per webapp, then they can be registered by placing them in
the context.xml file of the webapp it self.

Eg - Resource name=TransactionManager auth=Container
type=com.atomikos.icatch.jta.UserTransactionManager
factory=org.apache.naming.factory.BeanFactory /

Other properties for these resources should go inside each respective
Resource tags. Make sure those classes used to define resource-type are in
the classpath. Then have a reference for those resources in the web.xml of
the webapp.

Eg - resource-ref
descriptionYour Description/description
res-ref-namejdbc/MyDataSource/res-ref-name
res-typecom.atomikos.jdbc.AtomikosDataSourceBean/res-type
res-authContainer/res-auth
/resource-ref

I'm currently writing an article on recent tomcat improvements, so
it's better to include these details in there as-well.

Thanks,
Kishanthan.
Ref -
http://tomcat.apache.org/tomcat-7.0-doc/jndi-resources-howto.html

On Mon, May 28, 2012 at 3:55 PM, Kishanthan Thangarajah
kishant...@wso2.com wrote:

On Mon, May 28, 2012 at 2:51 PM, Isuru Suriarachchi
is...@wso2.comwrote:

On Mon, May 28, 2012 at 2:45 PM, Paul Fremantle p...@wso2.comwrote:

If that is the way its meant to work, then we need a way to
register things like DataSources and Transaction context into the
webapps
JNDI.

There is some good docs on how this works in Tomcat here:

http://tomcat.apache.org/tomcat-6.0-doc/jndi-resources-howto.html#context.xml_configuration

In Tomcat it seems you can define JNDI entries either locally in
the web.xml or globally and then link to them.

+1. This should work for us and looks like it's the correct way of
doing this. Kishanthan, please look into this..

I will have a look at this and provide an update. Created a jira to
track this [1

Re: [Dev] C-App synchronization in a Carbon cluster

On Mon, Jul 9, 2012 at 5:07 PM, Srinath Perera srin...@wso2.com wrote:

 Hi Isuru,

 For the release, can we ask users to run the cluster in a mode where only
 one node write to the SVN repo and other nodes will just read?


I think we always recommend only one R/W node in a cluster.



 Also, please explain your fixes to someone/ commit them to the new trunk
 once we are done with the release.


Sure, will do..


 I think those fixes are the right long time answer to this problem.


+1

Thanks,
~Isuru



 --Srinath


 On Mon, Jul 9, 2012 at 5:00 PM, Isuru Suriarachchi is...@wso2.com wrote:



 On Mon, Jul 9, 2012 at 3:21 PM, Srinath Perera srin...@wso2.com wrote:

 Hi Isuru,

 In a review we talked about possibility of not deploying artifacts
 inside the CApp back to repo, but deploying them by extracting them into a
 temp directory and invoking the respective deployers directly, without
 using the hot deployment. IMHO, that is the clean way to handle CApp
 deployments.

 I think we agreed for the above.


 Yes, actually I implemented it more than month ago and I still have the
 patches attached to [1]. As I described during the meeting, the issue with
 that approach is handling ESB artifacts. The solution proposed for that was
 to lock the ESB UI if there's a C-App deployed. But in addition to that,
 there can be many edge cases of that approach. As we are at the end of the
 release cycle, after a discussion with Azeez, I just thought of handling it
 in the manner described above. Because it will need only C-App related
 fixes.

 Thanks,
 ~Isuru

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



 Can we solve this problem by doing the above?

 --Srinath

 On Fri, Jul 6, 2012 at 6:05 PM, Isuru Suriarachchi is...@wso2.comwrote:

 Hi all,

 I'm trying to fix [1]. Here's the root cause for this issue..

 Imagine a Carbon cluster with 2 nodes where the svn based deployment
 synchronizer (DS) is configured. When a C-App is deployed to node1, it is
 extracted and individual artifacts are copied into respective hot
 directories. When the DS runs for the first time, it copies the C-App into
 node2 and it will be deployed there. When the DS runs again in node1, it
 will try to copy the individual artifacts to node2. But node2 already has
 those artifacts as the C-App id already deployed in node2. Therefore an svn
 conflict occurs.

 To resolve this issue, there are two possible options..

 1. Keeping all artifacts coming from C-Apps out of the repository
 (repository/deployment/server)
 2. Keeping the original C-App out of the repository

 Initially I tried option 1 above and programetically called the
 relevant deployers for individual artifacts. But this creates lot of
 problems with some artifacts (Ex: ESB stuff). Therefore, I'm trying to
 solve the initial problem using option 2 above.

 I've taken the carbonapps directory out of repository/deployment/server
 directory and kept it as repository/carbonapps (we can change this if
 needed). Still the carbonapps directory has hot deployment capabilities.
 But it won't be synchronized by the DS. So when a C-App is deployed into
 node 1, it will be extracted and only the individual artifacts will be
 copied into the repository. When the DS runs, all needed artifacts will be
 synced to node 2. Therefore, functionality wise, there won't be any issues
 on node 2.

 But if someone logs into the management console of node 2 and go to the
 C-App list, nothing will be listed. Is this something we have to fix?
 Because anyway in a RW/RO cluster, user can't use the management console of
 the slave node.

 WDYT??

 Thanks,
 ~Isuru

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

 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 
 Srinath Perera, Ph.D.
http://www.cs.indiana.edu/~hperera/
http://srinathsview.blogspot.com/




 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




 --
 
 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/
   Photos: http://www.flickr.com/photos/hemapani/
  Phone: 0772360902




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] C-App synchronization in a Carbon cluster

On Mon, Jul 9, 2012 at 3:21 PM, Srinath Perera srin...@wso2.com wrote:

 Hi Isuru,

 In a review we talked about possibility of not deploying artifacts inside
 the CApp back to repo, but deploying them by extracting them into a temp
 directory and invoking the respective deployers directly, without using the
 hot deployment. IMHO, that is the clean way to handle CApp deployments.

 I think we agreed for the above.


Yes, actually I implemented it more than month ago and I still have the
patches attached to [1]. As I described during the meeting, the issue with
that approach is handling ESB artifacts. The solution proposed for that was
to lock the ESB UI if there's a C-App deployed. But in addition to that,
there can be many edge cases of that approach. As we are at the end of the
release cycle, after a discussion with Azeez, I just thought of handling it
in the manner described above. Because it will need only C-App related
fixes.

Thanks,
~Isuru

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



 Can we solve this problem by doing the above?

 --Srinath

 On Fri, Jul 6, 2012 at 6:05 PM, Isuru Suriarachchi is...@wso2.com wrote:

 Hi all,

 I'm trying to fix [1]. Here's the root cause for this issue..

 Imagine a Carbon cluster with 2 nodes where the svn based deployment
 synchronizer (DS) is configured. When a C-App is deployed to node1, it is
 extracted and individual artifacts are copied into respective hot
 directories. When the DS runs for the first time, it copies the C-App into
 node2 and it will be deployed there. When the DS runs again in node1, it
 will try to copy the individual artifacts to node2. But node2 already has
 those artifacts as the C-App id already deployed in node2. Therefore an svn
 conflict occurs.

 To resolve this issue, there are two possible options..

 1. Keeping all artifacts coming from C-Apps out of the repository
 (repository/deployment/server)
 2. Keeping the original C-App out of the repository

 Initially I tried option 1 above and programetically called the relevant
 deployers for individual artifacts. But this creates lot of problems with
 some artifacts (Ex: ESB stuff). Therefore, I'm trying to solve the initial
 problem using option 2 above.

 I've taken the carbonapps directory out of repository/deployment/server
 directory and kept it as repository/carbonapps (we can change this if
 needed). Still the carbonapps directory has hot deployment capabilities.
 But it won't be synchronized by the DS. So when a C-App is deployed into
 node 1, it will be extracted and only the individual artifacts will be
 copied into the repository. When the DS runs, all needed artifacts will be
 synced to node 2. Therefore, functionality wise, there won't be any issues
 on node 2.

 But if someone logs into the management console of node 2 and go to the
 C-App list, nothing will be listed. Is this something we have to fix?
 Because anyway in a RW/RO cluster, user can't use the management console of
 the slave node.

 WDYT??

 Thanks,
 ~Isuru

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

 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 
 Srinath Perera, Ph.D.
http://www.cs.indiana.edu/~hperera/
http://srinathsview.blogspot.com/




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] AppServer JAXRS sample deployment failure

2012-07-08 Thread Isuru Suriarachchi

Are you trying offline? Sometimes those samples fail when the remote
schemas can't accessed.. We have to fix that..

Thanks,
~Isuru

On Sun, Jul 8, 2012 at 3:41 PM, Afkham Azeez az...@wso2.com wrote:

 I was able to deploy the simple JAXRS sample once, but subsequently I
 cannot deploy any JAXRS sample. Even the new JAXRS sample 02 throws the
 following error.

 [2012-07-08 15:33:03,642]  INFO
 {org.springframework.beans.factory.xml.XmlBeanDefinitionReader} -  Loading
 XML bean definitions from class path resource [META-INF/cxf/cxf.xml]
 [2012-07-08 15:34:20,426]  WARN
 {org.springframework.beans.factory.xml.XmlBeanDefinitionReader} -  Ignored
 XML validation warning
 org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema
 document 'http://www.springframework.org/schema/beans/spring-beans.xsd',
 because 1) could not find the document; 2) the document could not be read;
 3) the root element of the document is not xsd:schema.
  at
 org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
 Source)
 at org.apache.xerces.util.ErrorHandlerWrapper.warning(Unknown Source)
  at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
 at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
  at
 org.apache.xerces.impl.xs.traversers.XSDHandler.reportSchemaWarning(Unknown
 Source)
 at
 org.apache.xerces.impl.xs.traversers.XSDHandler.getSchemaDocument(Unknown
 Source)
  at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown
 Source)
 at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source)
  at
 org.apache.xerces.impl.xs.XMLSchemaValidator.findSchemaGrammar(Unknown
 Source)
 at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown
 Source)
  at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown
 Source)
 at
 org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
 Source)
  at
 org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown
 Source)
 at
 org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
 Source)
  at
 org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
 Source)
 at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
  at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
 at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
  at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
 at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
  at
 org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:75)
 at
 org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:388)


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




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [G-Reg] Can't deploy car files in latest pack.

2012-07-08 Thread Isuru Suriarachchi

This is fixed now..

Thanks,
~Isuru

On Sat, Jul 7, 2012 at 5:38 PM, Isuru Suriarachchi is...@wso2.com wrote:

 Hi Ajith,

 This should be due to the change i made yesterday. I just realized that I
 didn't fix the car file uploader to deploy the car file to the new
 location. I'll fix that. Until then, please copy the car file manually to
 CARBON_HOME/repository/carbonapps directory without using the UI.

 Thanks,
 ~Isuru

 On Sat, Jul 7, 2012 at 1:20 AM, Ajith Vitharana aji...@wso2.com wrote:


 Hi All,

 I'm trying to reproduce the issue [1] in latest G-Reg pack. But that car
 file doesn't deploy in G-Reg.
 And also I can't see any errors or warning at backend.

 [1]https://wso2.org/jira/browse/REGISTRY-999

 --
 Ajith Vitharana.
 WSO2 Inc. - http://wso2.org
 Email  :  aji...@wso2.com
 Mobile : +94714631794





 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [G-Reg] Can't deploy car files in latest pack.

2012-07-07 Thread Isuru Suriarachchi

Hi Ajith,

This should be due to the change i made yesterday. I just realized that I
didn't fix the car file uploader to deploy the car file to the new
location. I'll fix that. Until then, please copy the car file manually to
CARBON_HOME/repository/carbonapps directory without using the UI.

Thanks,
~Isuru

On Sat, Jul 7, 2012 at 1:20 AM, Ajith Vitharana aji...@wso2.com wrote:


 Hi All,

 I'm trying to reproduce the issue [1] in latest G-Reg pack. But that car
 file doesn't deploy in G-Reg.
 And also I can't see any errors or warning at backend.

 [1]https://wso2.org/jira/browse/REGISTRY-999

 --
 Ajith Vitharana.
 WSO2 Inc. - http://wso2.org
 Email  :  aji...@wso2.com
 Mobile : +94714631794





-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] C-App synchronization in a Carbon cluster

Hi all,

I'm trying to fix [1]. Here's the root cause for this issue..

Imagine a Carbon cluster with 2 nodes where the svn based deployment
synchronizer (DS) is configured. When a C-App is deployed to node1, it is
extracted and individual artifacts are copied into respective hot
directories. When the DS runs for the first time, it copies the C-App into
node2 and it will be deployed there. When the DS runs again in node1, it
will try to copy the individual artifacts to node2. But node2 already has
those artifacts as the C-App id already deployed in node2. Therefore an svn
conflict occurs.

To resolve this issue, there are two possible options..

1. Keeping all artifacts coming from C-Apps out of the repository
(repository/deployment/server)
2. Keeping the original C-App out of the repository

Initially I tried option 1 above and programetically called the relevant
deployers for individual artifacts. But this creates lot of problems with
some artifacts (Ex: ESB stuff). Therefore, I'm trying to solve the initial
problem using option 2 above.

I've taken the carbonapps directory out of repository/deployment/server
directory and kept it as repository/carbonapps (we can change this if
needed). Still the carbonapps directory has hot deployment capabilities.
But it won't be synchronized by the DS. So when a C-App is deployed into
node 1, it will be extracted and only the individual artifacts will be
copied into the repository. When the DS runs, all needed artifacts will be
synced to node 2. Therefore, functionality wise, there won't be any issues
on node 2.

But if someone logs into the management console of node 2 and go to the
C-App list, nothing will be listed. Is this something we have to fix?
Because anyway in a RW/RO cluster, user can't use the management console of
the slave node.

WDYT??

Thanks,
~Isuru

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

-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Creating Apache Axiom 1.2.11-wso2v1 branch

+1

Thanks,
~Isuru

On Fri, Jul 6, 2012 at 6:04 PM, Sagara Gunathunga sag...@wso2.com wrote:



 On Fri, Jul 6, 2012 at 5:50 PM, Shelan Perera she...@wso2.com wrote:

 Hi Devs,

 There are few fixes that needs to inherit from Axiom to DSS. Even
 though the current release Axiom version (1.2.13) included the changes some
 of the other dependent are not fully compatible with this new release.
 Therefore i am planning to branch as a solution and include those fixes.
 please holler if there are any concerns against it.


 +1

 I think that is the best option for time being, upgrading to 1.2.13 can
 effect to projects already on final testing stages.

 Thanks !



 Thanks

 --
 *Shelan Perera*

 Software Engineer
 **
 *WSO2, Inc. : wso2.com*
 lean.enterprise.middleware.

 *Home Page*  :shelan.org
 *Blog* : blog.shelan.org
 *Linked-i*n  :http://www.linkedin.com/pub/shelan-perera/a/194/465
 *Twitter* :https://twitter.com/#!/shelan

 *Mobile*  : +94 772 604 402



 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Sagara Gunathunga

 Technical Lead; WSO2, Inc.;  http://wso2.com
 V.P Apache Web Services ;  http://ws.apache.org/
 Blog ;  http://ssagara.blogspot.com


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Possible deployment synchronizer issues

While testing some other issue with the deployment synchronizer (DS), I
found the following scenarios in which there can be svn conflicts.

1. Synchronizing meta files. Consider the following sequence in a 2 node
Carbon cluster..

* foo.aar deployed in node 1
* DS syncs it to node 2
* foo.aar gets deployed in node 1 and foo.meta is created in node 1
* foo.aar gets deployed in node 2 and foo.meta is created in node 2
* DS tries to sync foo.meta in node 1 to node 2
* Conflict because foo.meta is already there in node 2

2. Deploying webapps. Now we've enabled exploded mode by default. So if a
foo.war is in webapps directory, foo directory will be created inside the
webapps directory.

* foo.war is deployed in node 1
* DS syncs it to node 2 before extraction
* both node 1 and node 2 deploys foo.war and creates foo directories under
webapps
* DS tries to sync foo directory from node 1 to node 2
* Conflict because the foo directory is already there in node 2

I think we have to heavily test these scenarios and fix all these issues
before we release. Charitha, have we tested DS on trunk? If not, shall we
create a plan?

Thanks,
~Isuru

-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Possible deployment synchronizer issues

On Fri, Jul 6, 2012 at 8:40 PM, Afkham Azeez az...@wso2.com wrote:

 Scenario 1 is something we addressed early in the development of the metal
 file model. Were you able to reproduce it? I think scenario 2 also should
 just work. Did you reproduce it?

I was able to reproduce both scenarios. But I'm not sure whether my local
DS setup is correct. Therefore, better to test these 2 scenarios on a beta
pack by some QA guy.

Thanks,
~Isuru

  --
 Afkham Azeez
 Sent from my phone
 On Jul 6, 2012 7:47 PM, Supun Malinga sup...@wso2.com wrote:



 On Fri, Jul 6, 2012 at 7:31 PM, Isuru Suriarachchi is...@wso2.comwrote:

 While testing some other issue with the deployment synchronizer (DS), I
 found the following scenarios in which there can be svn conflicts.

 1. Synchronizing meta files. Consider the following sequence in a 2 node
 Carbon cluster..

 * foo.aar deployed in node 1
 * DS syncs it to node 2
 * foo.aar gets deployed in node 1 and foo.meta is created in node 1
 * foo.aar gets deployed in node 2 and foo.meta is created in node 2
 * DS tries to sync foo.meta in node 1 to node 2
 * Conflict because foo.meta is already there in node 2


 Hmm...  this complicates things with MetaData Deployer as well. We need
 to include MetaFile sync into tests as well.

 thanks,


 2. Deploying webapps. Now we've enabled exploded mode by default. So if
 a foo.war is in webapps directory, foo directory will be created inside the
 webapps directory.

 * foo.war is deployed in node 1
 * DS syncs it to node 2 before extraction
 * both node 1 and node 2 deploys foo.war and creates foo directories
 under webapps
 * DS tries to sync foo directory from node 1 to node 2
 * Conflict because the foo directory is already there in node 2

 I think we have to heavily test these scenarios and fix all these issues
 before we release. Charitha, have we tested DS on trunk? If not, shall we
 create a plan?

 Thanks,
 ~Isuru

 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Supun Malinga,

 Software Engineer,
 WSO2 Inc.
 http://wso2.com
 http://wso2.org
 email - sup...@wso2.com sup...@wso2.com
 mobile - 071 56 91 321


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] C-App synchronization in a Carbon cluster

Harshana, good point.. Actually I had forgot about the lib artifacts.
Anyway as Azeez mentioned, we only allow lib artifacts for super tenant. So
it's kind of broken already.

If we want the libs to work with option 2, we can simply add a new deployer
for libs as well.. :)

Thanks,
~Isuru

On Sat, Jul 7, 2012 at 5:55 AM, Afkham Azeez az...@wso2.com wrote:



 On Sat, Jul 7, 2012 at 2:39 AM, Harshana Martin harsh...@wso2.com wrote:

 Hi Isuru,

 Please find my comments inline.

 On Fri, Jul 6, 2012 at 6:05 PM, Isuru Suriarachchi is...@wso2.comwrote:

 Hi all,

 I'm trying to fix [1]. Here's the root cause for this issue..

 Imagine a Carbon cluster with 2 nodes where the svn based deployment
 synchronizer (DS) is configured. When a C-App is deployed to node1, it is
 extracted and individual artifacts are copied into respective hot
 directories. When the DS runs for the first time, it copies the C-App into
 node2 and it will be deployed there. When the DS runs again in node1, it
 will try to copy the individual artifacts to node2. But node2 already has
 those artifacts as the C-App id already deployed in node2. Therefore an svn
 conflict occurs.

 To resolve this issue, there are two possible options..

 1. Keeping all artifacts coming from C-Apps out of the repository
 (repository/deployment/server)
 2. Keeping the original C-App out of the repository

 Initially I tried option 1 above and programetically called the relevant
 deployers for individual artifacts. But this creates lot of problems with
 some artifacts (Ex: ESB stuff). Therefore, I'm trying to solve the initial
 problem using option 2 above.

 I've taken the carbonapps directory out of repository/deployment/server
 directory and kept it as repository/carbonapps (we can change this if
 needed). Still the carbonapps directory has hot deployment capabilities.
 But it won't be synchronized by the DS. So when a C-App is deployed into
 node 1, it will be extracted and only the individual artifacts will be
 copied into the repository. When the DS runs, all needed artifacts will be
 synced to node 2. Therefore, functionality wise, there won't be any issues
 on node 2.


 I see a possible issue with option2.

 Currently it is possible to deploy 3rd party dependencies to Carbon
 Servers using JavaLibraryArtifact C-App Artifact type and Carbon Server
 extensions such as Custom Mediators, Registry Handlers, filters, etc via
 C-Apps. When the C-App is deployed in a server, those artifacts gets
 deployed in to the repository/components/dropins location but not the
 repository.


 Deploying artifacts into dropins is a major issue! It does not work for
 tenants, so is broken anyway. Anything that does not work in multi-tenant
 mode in terms of deployment, can safely be considered to be broken.


 If we go ahead with option 2 to avoid C-Apps getting picked by DS, how
 can we handle the syncing of aforementioned Artifact types across a
 cluster?

 Thanks and Regards,
 Harshana


 But if someone logs into the management console of node 2 and go to the
 C-App list, nothing will be listed. Is this something we have to fix?
 Because anyway in a RW/RO cluster, user can't use the management console of
 the slave node.

 WDYT??

 Thanks,
 ~Isuru

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

 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Harshana Martin
 Senior Software Engineer
 WSO2 Inc. : http://wso2.com ; http://wso2.org
 Mobile: +94 716 062 650
 Profile: https://www.google.com/profiles/harshana05
 Blog: http://harshana05.blogspot.com
 Twitter: http://twitter.com/harshana05



 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




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




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Upgrading Axiom version to 1.2.13

2012-07-05 Thread Isuru Suriarachchi

I'm not sure whether our Axis2 etc. versions will be compatible with the
latest Axiom version. Did you run all tests?

Thanks,
~Isuru

On Thu, Jul 5, 2012 at 3:03 PM, Shelan Perera she...@wso2.com wrote:

 Hi,

 I am planning to upgrade Axiom version in Orbit since there is an
 improvement added to that released version which is needed for DSS
 exception handling.
  Please holler if there are any concerns.

 Thanks

 --
 *Shelan Perera*

 Software Engineer
 **
 *WSO2, Inc. : wso2.com*
 lean.enterprise.middleware.

 *Home Page*  :shelan.org
 *Blog* : blog.shelan.org
 *Linked-i*n  :http://www.linkedin.com/pub/shelan-perera/a/194/465
 *Twitter* :https://twitter.com/#!/shelan

 *Mobile*  : +94 772 604 402



 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] CXF JSON support

2012-07-03 Thread Isuru Suriarachchi

On Mon, Jul 2, 2012 at 2:29 PM, Afkham Azeez az...@wso2.com wrote:

 Hi Isuru,
 Have we tested $subject?


Yes, we've already got JAX-RS JSON samples in AS..

Thanks,
~Isuru




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




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Updated CXF version to 2.6.1

2012-06-28 Thread Isuru Suriarachchi

Hi all,

I've updated the CXF version to 2.6.1 which is the latest release done few
weeks back. I ran all samples and fixed the issue I found in migration. But
if you'll find any issues related to this, please let me know.

Thanks,
~Isuru

-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Updated CXF version to 2.6.1

2012-06-28 Thread Isuru Suriarachchi

On Thu, Jun 28, 2012 at 8:17 PM, Andun Gunawardena an...@wso2.com wrote:

 Hi,

 The problem we suppose to correct by doing this change is not fixed yet,
 still the version of jaxb_2.1.7.wso2v1.jar is outdated. This jar also have
 to be updated o correct the problem.


This version update is not related to the problem you are talking about.
This is done to make AS support the latest CXF version. I'll fix your
problem by updating the jaxb version.



 Thanks
 Andun SLG

 On Thu, Jun 28, 2012 at 4:20 PM, Isuru Suriarachchi is...@wso2.comwrote:

 Hi all,

 I've updated the CXF version to 2.6.1 which is the latest release done
 few weeks back. I ran all samples and fixed the issue I found in migration.
 But if you'll find any issues related to this, please let me know.

 Thanks,
 ~Isuru

 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev





-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [kernal] Compilation failure

2012-06-26 Thread Isuru Suriarachchi

This was properly fixed by Pradeep yesterday..

Thanks,
~Isuru

On Tue, Jun 26, 2012 at 10:26 AM, Sumedha Rubasinghe sume...@wso2.comwrote:

 I also reported the same error on another thread.
 Going to do a mock implementation  commit to avoid compilation failure.


 On Tue, Jun 26, 2012 at 10:04 AM, Ajith Vitharana aji...@wso2.com wrote:


 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
 (default-compile) on project org.wso2.carbon.core: Compilation failure:
 Compilation failure:
 [ERROR]
 /home/ajith/wso2/builds/trunk/kernal/trunk/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/transports/metering/MeteredServletRequest.java:[38,7]
 org.wso2.carbon.core.transports.metering.MeteredServletRequest is not
 abstract and does not override abstract method getPart(java.lang.String) in
 javax.servlet.http.HttpServletRequest
 [ERROR]
 /home/ajith/wso2/builds/trunk/kernal/trunk/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/transports/metering/MeteredServletResponse.java:[32,7]
 org.wso2.carbon.core.transports.metering.MeteredServletResponse is not
 abstract and does not override abstract method getHeaderNames() in
 javax.servlet.http.HttpServletResponse
 [ERROR] - [Help 1]

 --
 Ajith Vitharana.
 WSO2 Inc. - http://wso2.org
 Email  :  aji...@wso2.com
 Mobile : +94714631794



 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 /sumedha
 +94 773017743

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] AS 5.0.0 Documentation

As we are getting closer to the release now it's time to concentrate on the
documentation as well. According to Nirdesha, she has already done the wiki
based documentation for AS 4.1.2 [1]. So we have to create a new doc for
5.0.0 and include all the new features and changes done for the existing
features.

I think with this new wiki based documentation, we don't need docs packs
through the build. Now we only need the context sensitive helps coming from
each component. Shall we remove doc pack generation from the build??

Thanks,
~Isuru

[1]
http://docs.wso2.org/wiki/display/AS412/WSO2+Application+Server+Documentation

-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] AS 5.0.0 Documentation

On Mon, Jun 25, 2012 at 1:05 PM, Senaka Fernando sen...@wso2.com wrote:

 Java API docs can't be written on the wiki docs, :). These are javadocs
 and need to be packed in this way, isn't it?


You don't have to write java docs on the wiki :). Host it somewhere and
point to that from the wiki based doc. Having java docs on a different
distribution and having other docs on the wiki is a mess. All should be in
a single place.

Thanks,
~Isuru



 Thanks,
 Senaka.


 On Mon, Jun 25, 2012 at 1:02 PM, Isuru Suriarachchi is...@wso2.comwrote:



 On Mon, Jun 25, 2012 at 1:00 PM, Senaka Fernando sen...@wso2.com wrote:

 Hi all,

 FYI, we have already removed docs from G-Reg distro, but we still build
 a docs pack that contains the release note, and the Java APIs, details on
 checking out source etc


 Why can't we move these also to the wiki based documentation and
 completely get rid of the docs pack?

 Thanks,
 ~Isuru


  (auto-generated by Maven), and several hyperlinks.

 Thanks,
 Senaka.


 On Mon, Jun 25, 2012 at 11:37 AM, Supun Malinga sup...@wso2.com wrote:



 On Mon, Jun 25, 2012 at 11:31 AM, Isuru Suriarachchi is...@wso2.comwrote:

 As we are getting closer to the release now it's time to concentrate
 on the documentation as well. According to Nirdesha, she has already done
 the wiki based documentation for AS 4.1.2 [1]. So we have to create a new
 doc for 5.0.0 and include all the new features and changes done for the
 existing features.

 I think with this new wiki based documentation, we don't need docs
 packs through the build. Now we only need the context sensitive helps
 coming from each component. Shall we remove doc pack generation from the
 build??

 +1
 lets make sure we incorporate all the stuff in doc packs in the wiki.

 thanks,


 Thanks,
 ~Isuru

 [1]
 http://docs.wso2.org/wiki/display/AS412/WSO2+Application+Server+Documentation

 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Supun Malinga,

 Software Engineer,
 WSO2 Inc.
 http://wso2.com
 http://wso2.org
 email - sup...@wso2.com sup...@wso2.com
 mobile - 071 56 91 321


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 *Senaka Fernando*
 Member - Integration Technologies Management Committee;
 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




 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




 --
 *Senaka Fernando*
 Member - Integration Technologies Management Committee;
 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




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] OSGi Fragment host problem when using package name instead of bundle symbolic name

In any case, you have to create a new orbit bundle if the original bundle
doesn't work. If it works without making it a fragment, I think that will
be even better.

Thanks,
~Isuru

On Mon, Jun 25, 2012 at 2:39 PM, Nirmal Fernando nir...@wso2.com wrote:



 On Mon, Jun 25, 2012 at 1:22 PM, Pradeep Fernando prad...@wso2.comwrote:

 Hi,

 So is it working once you specify the bundle name ?


 Yes!


 is so it is the
 correct behaviour AFAIK. Your fragment bundle get attached to the host
 bundle, not to a package. The version is optional.


 okay, but rocoto bundle provides otherwise! So probably we need to create
 (another) orbit bundle to wrap this up?




 thanks,
 --Pradeep




 --

 Thanks  regards,
 Nirmal

 Software Engineer- Platform Technologies Team, WSO2 Inc.
 Mobile: +94715779733
 Blog: http://nirmalfdo.blogspot.com/

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] AS 5.0.0 Documentation

Yes, all those Jaggery and MS docs should be added to the AS 5.0.0
documentation.

Thanks,
~Isuru

On Tue, Jun 26, 2012 at 10:25 AM, Yumani Ranaweera yum...@wso2.com wrote:

Do we include MS features also within AS Documentation. As I remember MS
had good documentation done on Host objects, js webservices annotation,
data binding, how to on creating to consuming a js service etc. Where would
they fit in.

[1] -
https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0Am89tsNpm9bfdEdyamJhNnJpOTJFWnYzM0VnQ1gxY1E#gid=0

Thanks,
-Yumani

On Mon, Jun 25, 2012 at 3:08 PM, Nirdesha Munasinghe nirde...@wso2.comwrote:

Hi Isuru,

I think we can do a feature-based documentation for AS 5.0.0 since all
AS-related features used in the older version are documented now. Using
them, I created this space manually (Homepage to be edited):

http://docs.wso2.org/wiki/display/AS500/WSO2+Application+Server+Documentation

Please refer to the information hierarchy and let me know if you are fine
with it. You can find the feature list and their space URLs here:

https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0Am89tsNpm9bfdEdyamJhNnJpOTJFWnYzM0VnQ1gxY1E#gid=0

Please let me know any new features which need to be added to AS 5.0.0.
Once the existing features are edited and new ones are added, we can
incorporate them and recreate the new documentation.

Regards,
-Nirdesha

On Mon, Jun 25, 2012 at 11:31 AM, Isuru Suriarachchi is...@wso2.comwrote:

As we are getting closer to the release now it's time to concentrate on
the documentation as well. According to Nirdesha, she has already done the
wiki based documentation for AS 4.1.2 [1]. So we have to create a new doc
for 5.0.0 and include all the new features and changes done for the
existing features.

I think with this new wiki based documentation, we don't need docs packs
through the build. Now we only need the context sensitive helps coming from
each component. Shall we remove doc pack generation from the build??

Thanks,
~Isuru

[1]
http://docs.wso2.org/wiki/display/AS412/WSO2+Application+Server+Documentation

--
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware

Thanks,

Nirdesha Munasinghe,
WSO2 Inc.
Web:http://wso2.com

Mobile: +94 776321920

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

--
*
*
*

Yumani Ranaweera*

--
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] AS 5.0.0 Documentation

On Tue, Jun 26, 2012 at 10:35 AM, Nuwan Bandara nu...@wso2.com wrote:

On Tue, Jun 26, 2012 at 10:27 AM, Isuru Suriarachchi is...@wso2.comwrote:

Yes, all those Jaggery and MS docs should be added to the AS 5.0.0
documentation.

Yes. need to add old MS docs as it is, since there are no functional
changes. I would say, for jaggery we give a introduction and pint to
jaggery online docs. no point duplicating them here wdyt ?

Thanks,
~Isuru

Regards,
/Nuwan

Thanks,
~Isuru

On Tue, Jun 26, 2012 at 10:25 AM, Yumani Ranaweera yum...@wso2.comwrote:

[1] -
https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0Am89tsNpm9bfdEdyamJhNnJpOTJFWnYzM0VnQ1gxY1E#gid=0

Thanks,
-Yumani

On Mon, Jun 25, 2012 at 3:08 PM, Nirdesha Munasinghe
nirde...@wso2.comwrote:

Hi Isuru,

http://docs.wso2.org/wiki/display/AS500/WSO2+Application+Server+Documentation

Please refer to the information hierarchy and let me know if you are
fine with it. You can find the feature list and their space URLs here:

https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0Am89tsNpm9bfdEdyamJhNnJpOTJFWnYzM0VnQ1gxY1E#gid=0

Please let me know any new features which need to be added to AS 5.0.0.
Once the existing features are edited and new ones are added, we can
incorporate them and recreate the new documentation.

Regards,
-Nirdesha

On Mon, Jun 25, 2012 at 11:31 AM, Isuru Suriarachchi is...@wso2.comwrote:

As we are getting closer to the release now it's time to concentrate
on the documentation as well. According to Nirdesha, she has already done
the wiki based documentation for AS 4.1.2 [1]. So we have to create a new
doc for 5.0.0 and include all the new features and changes done for the
existing features.

I think with this new wiki based documentation, we don't need docs
packs through the build. Now we only need the context sensitive helps
coming from each component. Shall we remove doc pack generation from the
build??

Thanks,
~Isuru

[1]
http://docs.wso2.org/wiki/display/AS412/WSO2+Application+Server+Documentation

--
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware

Thanks,

Nirdesha Munasinghe,
WSO2 Inc.
Web:http://wso2.com

Mobile: +94 776321920

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

--
*
*
*

Yumani Ranaweera*

--
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

--
*Thanks Regards,

Nuwan Bandara
Associate Technical Lead Member, MC, Development Technologies
WSO2 Inc. - lean . enterprise . middleware | http://wso2.com
blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
9629
*
http://www.nuwanbando.com/

--
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] AS 5.0.0 Documentation

Hi Nirdesha,

Here's a rough list of new features added in AS 5.0.0.

Webapp based JAX-WS support
JAX-RS support
Lazy loading for Services
Lazy loading for Web Applications
Jaggery
Javascript Services
Total Tomcat compliance

There are list of improvements also which should go under existing features.

Thanks,
~Isuru

On Mon, Jun 25, 2012 at 3:08 PM, Nirdesha Munasinghe nirde...@wso2.comwrote:

Hi Isuru,

http://docs.wso2.org/wiki/display/AS500/WSO2+Application+Server+Documentation

Please refer to the information hierarchy and let me know if you are fine
with it. You can find the feature list and their space URLs here:

https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0Am89tsNpm9bfdEdyamJhNnJpOTJFWnYzM0VnQ1gxY1E#gid=0

Please let me know any new features which need to be added to AS 5.0.0.
Once the existing features are edited and new ones are added, we can
incorporate them and recreate the new documentation.

Regards,
-Nirdesha

On Mon, Jun 25, 2012 at 11:31 AM, Isuru Suriarachchi is...@wso2.comwrote:

Thanks,
~Isuru

[1]
http://docs.wso2.org/wiki/display/AS412/WSO2+Application+Server+Documentation

--
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware

Thanks,

Nirdesha Munasinghe,
WSO2 Inc.
Web:http://wso2.com

Mobile: +94 776321920

--
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

2012-06-22 Thread Isuru Suriarachchi

Lakmali,

Can you please explain why we need this SuperTenantRolePlayer and why it
always returns false for isUltimateDestination()? Looks like, we can't
always return false here and have to figure out whether this is the
ultimate destination of the message. If the message is going into a tenant,
returning false is ok. But for the super tenant case, it should return
true. In any case, please look into this urgently and fix. This has
introduced a fundamental bug in addressing and RM.

Thanks,
~Isuru

On Fri, Jun 22, 2012 at 1:34 PM, Andun Gunawardena an...@wso2.com wrote:

 Hi All,

 I have notified that Sandesha2 module cant be engaged in the way which was
 described in 
 [1]http://wso2.org/project/app-server/4.1.2/docs/commodity_quote_guide.html.
 In the client side it shows the follwoing error,

 ERROR [2012-06-21 12:19:47,991] The endpoint reference (EPR) for the
 Operation not found is and the WSA Action = . If this EPR was previously
 reachable, please contact the server administrator.

 When I did a SOAP tracing in AS, I found that the Addressing module is
 not engaged properly in the response SOAP message. That causes the
 Sandesha2 handshaking protocol to crash by not having necessary EPRs. The
 following SOAP message is the SOAP message which was returned to the first
 handshaking SOAP message, and it doesn't have addressing headers.

 soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope
 
soapenv:Header /
soapenv:Body
   ns:greetResponse xmlns:ns=http://www.wso2.org/types;
  returnHello World, AndunSLG !!!/return
   /ns:greetResponse
/soapenv:Body
 /soapenv:Envelope

 In the org.apache.axiom.soap.impl.llom.SOAPHeaderImpl class's 127 line has
 the following Boolean check which have to return true for
 the correct excution,

 return (rolePlayer == null || rolePlayer.isUltimateDestination());

 But in the current carbon trunk, the rolePlayer object is a instance
 of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer. It has the
 method isUltimateDestination() implemented as follows,

 public boolean isUltimateDestination() {
 return false;
 }

 So because of that
 Axis2's org.apache.axis2.handlers.addressing.AddressingInHandler class
 disables the AddressignOutHandler. So no addressing happens at the out
 flow. That causes all the trouble in Addressing and Sandesha2. I put return
 true experimentally and that makes all the troubles back to normal. So is
 the implementation of public boolean isUltimateDestination()  is correct ?




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

2012-06-22 Thread Isuru Suriarachchi

On Fri, Jun 22, 2012 at 2:42 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:

 Hi,

 On Fri, Jun 22, 2012 at 2:18 PM, Isuru Suriarachchi is...@wso2.comwrote:

 Lakmali,

 Can you please explain why we need this SuperTenantRolePlayer and why it
 always returns false for isUltimateDestination()? Looks like, we can't
 always return false here and have to figure out whether this is the
 ultimate destination of the message. If the message is going into a tenant,
 returning false is ok. But for the super tenant case, it should return
 true. In any case, please look into this urgently and fix. This has
 introduced a fundamental bug in addressing and RM.


 We need to set the SuperTenantRolePlayer to invoke secure services by
 tenants. This was actually had been a module inside products previously
 (ex: AS org.wso2.stratos.appserver.deployment) and I just made it common by
 adding it as a stratos component. This was done as a fix for the issue [1].

 Previously this was only added to the services. Now after product-service
 merging this SuperTenantRolePlayer might be an issue to the products.


Yes, correct..


 Will look in this.


You can fix this either by not registering the Role Player for super tenant
or by writing the logic inside that method to determine whether it is
called by the super tenant or not.

Thanks,
~Isuru



 [1] 
 https://wso2.org/jira/browse/STRATOS-1953https://wso2.org/jira/browse/STRATOS-1953

 Thanks,
 Lakmali



 Thanks,
 ~Isuru

 On Fri, Jun 22, 2012 at 1:34 PM, Andun Gunawardena an...@wso2.comwrote:

 Hi All,

 I have notified that Sandesha2 module cant be engaged in the
 way which was described in 
 [1]http://wso2.org/project/app-server/4.1.2/docs/commodity_quote_guide.html.
 In the client side it shows the follwoing error,

 ERROR [2012-06-21 12:19:47,991] The endpoint reference (EPR) for the
 Operation not found is and the WSA Action = . If this EPR was previously
 reachable, please contact the server administrator.

 When I did a SOAP tracing in AS, I found that the Addressing module is
 not engaged properly in the response SOAP message. That causes the
 Sandesha2 handshaking protocol to crash by not having necessary EPRs. The
 following SOAP message is the SOAP message which was returned to the first
 handshaking SOAP message, and it doesn't have addressing headers.

 soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope
 
soapenv:Header /
soapenv:Body
   ns:greetResponse xmlns:ns=http://www.wso2.org/types;
  returnHello World, AndunSLG !!!/return
   /ns:greetResponse
/soapenv:Body
 /soapenv:Envelope

 In the org.apache.axiom.soap.impl.llom.SOAPHeaderImpl class's 127 line
 has the following Boolean check which have to return true for
 the correct excution,

 return (rolePlayer == null || rolePlayer.isUltimateDestination());

 But in the current carbon trunk, the rolePlayer object is a instance
 of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer. It has the
 method isUltimateDestination() implemented as follows,

 public boolean isUltimateDestination() {
 return false;
 }

 So because of that
 Axis2's org.apache.axis2.handlers.addressing.AddressingInHandler class
 disables the AddressignOutHandler. So no addressing happens at the out
 flow. That causes all the trouble in Addressing and Sandesha2. I put return
 true experimentally and that makes all the troubles back to normal. So is
 the implementation of public boolean isUltimateDestination()  is correct ?




 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




 --
 Lakmali Baminiwatta*
 *
 Software Engineer
 WSO2, Inc.: http://wso2.com
 lean.enterprise.middleware
 mobile:  +94 71 2335936
 *
 *




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] The Axis2 modules Addressing and Sandesha2 fails to engage, due the implementation of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer

2012-06-22 Thread Isuru Suriarachchi

On Fri, Jun 22, 2012 at 3:13 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:

 Hi Isuru,


 On Fri, Jun 22, 2012 at 2:58 PM, Isuru Suriarachchi is...@wso2.comwrote:



 On Fri, Jun 22, 2012 at 2:42 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:

 Hi,

 On Fri, Jun 22, 2012 at 2:18 PM, Isuru Suriarachchi is...@wso2.comwrote:

 Lakmali,

 Can you please explain why we need this SuperTenantRolePlayer and why
 it always returns false for isUltimateDestination()? Looks like, we can't
 always return false here and have to figure out whether this is the
 ultimate destination of the message. If the message is going into a tenant,
 returning false is ok. But for the super tenant case, it should return
 true. In any case, please look into this urgently and fix. This has
 introduced a fundamental bug in addressing and RM.


 We need to set the SuperTenantRolePlayer to invoke secure services by
 tenants. This was actually had been a module inside products previously
 (ex: AS org.wso2.stratos.appserver.deployment) and I just made it common by
 adding it as a stratos component. This was done as a fix for the issue [1].

 Previously this was only added to the services. Now after
 product-service merging this SuperTenantRolePlayer might be an issue to the
 products.


 Yes, correct..


 Will look in this.


 You can fix this either by not registering the Role Player for super
 tenant or by writing the logic inside that method to determine whether it
 is called by the super tenant or not.


 Thanks for the suggestions. If we don't register the Role Player for super
 tenant, stratos secure services will fail in its super tenant flow while
 trying to process must understand fields for security headers. Because the
 rampart is engaged for services, only in sub tenants flow.

 So I think we have to take the second approach.


I just looked into this and looks like we can't figure out whether the
incoming request is going to a service hosted in super tenant or to a
service hosted in a sub tenant. That is because isUltimateDestination()
doesn't have the message context or any other information.

Therefore we'll have to figure out a proper solution for this. Azeez, have
you got any idea?

Thanks,
~Isuru



 Thanks,
 Lakmali


 Thanks,
 ~Isuru



 [1] 
 https://wso2.org/jira/browse/STRATOS-1953https://wso2.org/jira/browse/STRATOS-1953

 Thanks,
 Lakmali



 Thanks,
 ~Isuru

 On Fri, Jun 22, 2012 at 1:34 PM, Andun Gunawardena an...@wso2.comwrote:

 Hi All,

 I have notified that Sandesha2 module cant be engaged in the
 way which was described in 
 [1]http://wso2.org/project/app-server/4.1.2/docs/commodity_quote_guide.html.
 In the client side it shows the follwoing error,

 ERROR [2012-06-21 12:19:47,991] The endpoint reference (EPR) for the
 Operation not found is and the WSA Action = . If this EPR was previously
 reachable, please contact the server administrator.

 When I did a SOAP tracing in AS, I found that the Addressing module is
 not engaged properly in the response SOAP message. That causes the
 Sandesha2 handshaking protocol to crash by not having necessary EPRs. The
 following SOAP message is the SOAP message which was returned to the first
 handshaking SOAP message, and it doesn't have addressing headers.

 soapenv:Envelope xmlns:soapenv=
 http://www.w3.org/2003/05/soap-envelope;
soapenv:Header /
soapenv:Body
   ns:greetResponse xmlns:ns=http://www.wso2.org/types;
  returnHello World, AndunSLG !!!/return
   /ns:greetResponse
/soapenv:Body
 /soapenv:Envelope

 In the org.apache.axiom.soap.impl.llom.SOAPHeaderImpl class's 127 line
 has the following Boolean check which have to return true for
 the correct excution,

 return (rolePlayer == null || rolePlayer.isUltimateDestination());

 But in the current carbon trunk, the rolePlayer object is a instance
 of org.wso2.carbon.stratos.deployment.SuperTenantRolePlayer. It has the
 method isUltimateDestination() implemented as follows,

 public boolean isUltimateDestination() {
 return false;
 }

 So because of that
 Axis2's org.apache.axis2.handlers.addressing.AddressingInHandler class
 disables the AddressignOutHandler. So no addressing happens at the out
 flow. That causes all the trouble in Addressing and Sandesha2. I put 
 return
 true experimentally and that makes all the troubles back to normal. So is
 the implementation of public boolean isUltimateDestination()  is correct ?




 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




 --
 Lakmali Baminiwatta*
 *
 Software Engineer
 WSO2, Inc.: http://wso2.com
 lean.enterprise.middleware
 mobile:  +94 71 2335936
 *
 *




 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




 --
 Lakmali Baminiwatta*
 *
 Software Engineer
 WSO2, Inc.: http://wso2.com

Re: [Dev] Exposing a JAX-RS service from a Carbon Component

2012-06-18 Thread Isuru Suriarachchi

This is something we must introduce in the next Carbon release. As I've
already explained to Tharindu and Thilina, even though we can expose JAX-RS
services through carbon components, those are not MTed. That is because the
service is registered in a CXF context which is not related to our Axis2
ConfigContext.

Currently MT enabled JAX-RS services only works through webapps. We have to
do a proper design and implement MT for non-webapp JAX-RS services.

Thanks,
~Isuru

On Thu, Jun 14, 2012 at 5:04 PM, Thilina Buddhika thili...@wso2.com wrote:

 I followed the approach taken by Tharindu to implement REST APIs in BAM
 with JAX-RS and it is working.

 Thanks,
 Thilina


 On Sun, Jun 10, 2012 at 9:07 PM, Senaka Fernando sen...@wso2.com wrote:

 Hi Tharindu,

 Yes. Ideally, the ability to reuse most of what you've done and build a
 JAX-RS service without having to go through the entire process. Or else
 we'll have to adopt the old eventing strategy. So, then once we decide to
 move this to kernel refactoring would become minimal.

 Thanks,
 Senaka.


 On Sun, Jun 10, 2012 at 8:52 PM, Tharindu Mathew thari...@wso2.comwrote:

 It's still not complete, but yes it should be installable as every
 feature.

 But if I'm not mistaken, what you are asking is the REST set up part of
 it re-usable as a feature, then no it is not. But, this probably can be
 done, let me look into that aspect as well, as I proceed with this.


 On Sun, Jun 10, 2012 at 8:31 PM, Senaka Fernando sen...@wso2.comwrote:



 On Sun, Jun 10, 2012 at 6:56 PM, Thilina Buddhika thili...@wso2.comwrote:



 On Sun, Jun 10, 2012 at 1:52 PM, Tharindu Mathew thari...@wso2.comwrote:

 This should be part of Core in the future. It is too late to include
 it now.

 I have gotten it to work in Carbon, but I had to do it from the
 ground up.

 If it's integrated into Core, we can put in some config file and
 expose a REST service. This would be very valuable as lots of components
 would want a REST service in the future. I believe it's too late to 
 include
 it now for C4.


 +1.


 +1.

 This is definitely a useful addition to the kernel. Is what you did a
 reusable feature that somebody can install if needed?

 Thanks,
 Senaka.


 Thanks,
 Thilina



 On Sun, Jun 10, 2012 at 1:48 PM, Pradeep Fernando 
 prad...@wso2.comwrote:

 Hi,

 I think we do. we re-used some bundles from the apache aries project.
 There isuruS used blueprint services. He is the right guy to answer
 this question.

 --Pradeep
 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Regards,

 Tharindu

 blog: http://mackiemathew.com/
 M: +9459908


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Thilina Buddhika
 Associate Technical Lead
 WSO2 Inc. ; http://wso2.com
 lean . enterprise . middleware

 phone : +94 77 44 88 727
 blog : http://blog.thilinamb.com

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 *Senaka Fernando*
 Member - Integration Technologies Management Committee;
 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




 --
 Regards,

 Tharindu

 blog: http://mackiemathew.com/
 M: +9459908




 --
 *Senaka Fernando*
 Member - Integration Technologies Management Committee;
 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




 --
 Thilina Buddhika
 Associate Technical Lead
 WSO2 Inc. ; http://wso2.com
 lean . enterprise . middleware

 phone : +94 77 44 88 727
 blog : http://blog.thilinamb.com

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Exposing a JAX-RS service from a Carbon Component

2012-06-18 Thread Isuru Suriarachchi

 list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 *Senaka Fernando*
 Member - Integration Technologies Management Committee;
 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




 --
 Thilina Buddhika
 Associate Technical Lead
 WSO2 Inc. ; http://wso2.com
 lean . enterprise . middleware

 phone : +94 77 44 88 727
 blog : http://blog.thilinamb.com

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev





 --
 Thilina Buddhika
 Associate Technical Lead
 WSO2 Inc. ; http://wso2.com
 lean . enterprise . middleware

 phone : +94 77 44 88 727
 blog : http://blog.thilinamb.com



 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Paul Fremantle
 CTO and Co-Founder, WSO2
 OASIS WS-RX TC Co-chair, VP, Apache Synapse

 UK: +44 207 096 0336
 US: +1 646 595 7614

 blog: http://pzf.fremantle.org
 twitter.com/pzfreo
 p...@wso2.com

 wso2.com Lean Enterprise Middleware

 Disclaimer: This communication may contain privileged or other
 confidential information and is intended exclusively for the addressee/s.
 If you are not the intended recipient/s, or believe that you may have
 received this communication in error, please reply to the sender indicating
 that fact and delete the copy you received and in addition, you should not
 print, copy, retransmit, disseminate, or otherwise use the information
 contained in this communication. Internet communications cannot be
 guaranteed to be timely, secure, error or virus-free. The sender does not
 accept liability for any errors or omissions.


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Lets schedule a milestone for Application Server with the recent changes

2012-06-17 Thread Isuru Suriarachchi

On Wed, Jun 13, 2012 at 5:54 PM, Kishanthan Thangarajah kishant...@wso2.com
 wrote:



 On Wed, Jun 13, 2012 at 2:29 PM, Nuwan Bandara nu...@wso2.com wrote:

 Hi Krishanthan  AS RMs,

 As we had a chat offline, shall we schedule a milestone for AS, somewhere
 during next week with the recent feature additions (Jaggery/MS) and Product
 + Service Merger.


 +1, There are some critical MT related issues in current trunk, which are
 now being addressed. Once those get fixed, we should be able to do this
 milestone release.


Kishanthan, what are the MT issues you are working on? And do we need more
time for those?

Thanks,
~Isuru



 Thanks,
 Kishanthan.



 --
 *Thanks  Regards,

 Nuwan Bandara
 Associate Technical Lead  Member, MC, Development Technologies
 WSO2 Inc. - lean . enterprise . middleware |  http://wso2.com
 blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763
 9629
 *
 http://www.nuwanbando.com/

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 *Kishanthan Thangarajah*
 Software Engineer,
 Development Technologies Team,
 WSO2, Inc.
 lean.enterprise.middleware

 Mobile - +94773426635
 Blog - *http://kishanthan.wordpress.com*
 Twitter - *http://twitter.com/kishanthan*


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Increasing AS version to 5.0

2012-06-04 Thread Isuru Suriarachchi

Hi all,

Currently we've kept the AS version for this release as 4.5.0. But looking
at the list of features we've added [1] and considering Jaggery and MS
additions, I think we should further increase it to 5.0.

WDYT??..

Thanks,
~Isuru

[1]
https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hiderequestId=10696

-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] More issues with statistics persistence!

2012-06-01 Thread Isuru Suriarachchi

Ah.. yes.. sorry I had not built system stats component. Issue went away
once the system stats component was built..

Thanks,
~Isuru

On Fri, Jun 1, 2012 at 6:08 PM, Afkham Azeez az...@wso2.com wrote:

 AbstractMethodError occurs when the interface method  implementation
 method are not the same.

 On Fri, Jun 1, 2012 at 6:04 PM, Kishanthan Thangarajah 
 kishant...@wso2.com wrote:

 java.lang.AbstractMethodError




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


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Class Not Found exception when deploying a JAX-RS service in a Carbon component

2012-05-31 Thread Isuru Suriarachchi

)
 at
 org.apache.cxf.jaxrs.JAXRSServerFactoryBean.create(JAXRSServerFactoryBean.java:144)
  ... 16 more
 Caused by: java.lang.NullPointerException
 at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:116)
  ... 24 more

 --
 Regards,

 Tharindu

 blog: http://mackiemathew.com/
 M: +9459908




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] JNDI lookup wont work inside a web-app

2012-05-29 Thread Isuru Suriarachchi

According to this, all our global resources can be registered in the tomcat
server.xml and can be looked up from anywhere. So we can make the above
resources work by doing this.

But if we want to allow users to register and look up resources through the
carbon context, we have to register those resources in the same context as
the server.xml resources. Then only those can be made global.

Thanks,
~Isuru

On Tue, May 29, 2012 at 10:44 AM, Kishanthan Thangarajah
kishant...@wso2.com wrote:

This can be done. We have to first register JNDI resources for webapps
context. Then we can lookup for them. As Paul mentioned, registering those
resources can done in two ways. They can be either global or per webapp. If
it is global, you have place them under GlobalNamingResources tag in
tomcat's server.xml (catalina-server.xml in our case) file. Then they can
be referenced in webapp via linking them in the context.xml file of webapp.

Eg - ResourceLink name=jdbc/MyDataSource
global=jdbc/MyDataSource
type=com.atomikos.jdbc.AtomikosDataSourceBean/

If it is per webapp, then they can be registered by placing them in the
context.xml file of the webapp it self.

Eg - Resource name=TransactionManager auth=Container
type=com.atomikos.icatch.jta.UserTransactionManager
factory=org.apache.naming.factory.BeanFactory /

Eg - resource-ref
descriptionYour Description/description
res-ref-namejdbc/MyDataSource/res-ref-name
res-typecom.atomikos.jdbc.AtomikosDataSourceBean/res-type
res-authContainer/res-auth
/resource-ref

I'm currently writing an article on recent tomcat improvements, so it's
better to include these details in there as-well.

Thanks,
Kishanthan.
Ref - http://tomcat.apache.org/tomcat-7.0-doc/jndi-resources-howto.html

On Mon, May 28, 2012 at 3:55 PM, Kishanthan Thangarajah
kishant...@wso2.com wrote:

On Mon, May 28, 2012 at 2:51 PM, Isuru Suriarachchi is...@wso2.comwrote:

On Mon, May 28, 2012 at 2:45 PM, Paul Fremantle p...@wso2.com wrote:

If that is the way its meant to work, then we need a way to register
things like DataSources and Transaction context into the webapps JNDI.

There is some good docs on how this works in Tomcat here:

http://tomcat.apache.org/tomcat-6.0-doc/jndi-resources-howto.html#context.xml_configuration

In Tomcat it seems you can define JNDI entries either locally in the
web.xml or globally and then link to them.

+1. This should work for us and looks like it's the correct way of doing
this. Kishanthan, please look into this..

I will have a look at this and provide an update. Created a jira to track
this [1].

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

Thanks,
~Isuru

Paul

On 28 May 2012 10:03, Isuru Suriarachchi is...@wso2.com wrote:

I had a discussion on this with Kicha and looks like the way it works
is correct. When jndi resources are registered in the webapp itself, those
get registered in it's own context and can be loaded anywhere within the
webapp. But when resources are registered in the initial context, those
are
not visible to the webapps. Looks like this is the correct behavior.

Can we please check whether this webapp works in previous releases?

Thanks,
~Isuru

On Mon, May 28, 2012 at 1:00 PM, Kishanthan Thangarajah
kishant...@wso2.com wrote:

Here are the findings on this issue so far.

In trunk, TransactionManager, UserTransaction etc, are getting bind
with InitialContext of javaUrlContextFactory[1] which handles the “java:”
namespace. This context is not bound to any thread or classloader. But
in a
webapp case, their context are isolated from each other and the
classloaders are bound to each webapps naming context. But the
initialContext from javaUrlContextFactory will not be accessible for
them.
This is why it fails when doing lookup within a webapp.

The javaUrlContextFactory first checks whether current thread or
classloader is bound to any context. If not, it will return the
intialContext. This is why the lookup within a service is successful
since
its class loader is not bound to any naming context. The lookup from any
BE
component also works fine.

So we have to think of a way to handle this issue.

@Dinusha, can you try whether this webapp works in previous releases?

Thanks,
Kishanthan.
[1]
http://grepcode.com/file/repo1.maven.org/maven2/org.apache.tomcat/tomcat-catalina/7.0.26/org/apache/naming/java/javaURLContextFactory.java#javaURLContextFactory.getInitialContext%28java.util.Hashtable%29

On Sun, May 27, 2012 at 11:47 AM, Dinusha Senanayaka
dinu...@wso2.com wrote:

Hi Kishanthan,

On Sun, May 27, 2012 at 12:07 AM, Kishanthan

Re: [Dev] JNDI lookup wont work inside a web-app

2012-05-28 Thread Isuru Suriarachchi

*


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Supun Malinga,

 Software Engineer,
 WSO2 Inc.
 http://wso2.com
 http://wso2.org
 email - sup...@wso2.com sup...@wso2.com
 mobile - 071 56 91 321





 --
 *Kishanthan Thangarajah*
 Software Engineer,
 Development Technologies Team,
 WSO2, Inc.
 lean.enterprise.middleware

 Mobile - +94773426635
 Blog - *http://kishanthan.wordpress.com*
 Twitter - *http://twitter.com/kishanthan*





 --
 *Kishanthan Thangarajah*
 Software Engineer,
 Development Technologies Team,
 WSO2, Inc.
 lean.enterprise.middleware

 Mobile - +94773426635
 Blog - *http://kishanthan.wordpress.com*
 Twitter - *http://twitter.com/kishanthan*


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] JNDI lookup wont work inside a web-app

2012-05-28 Thread Isuru Suriarachchi

On Mon, May 28, 2012 at 2:45 PM, Paul Fremantle p...@wso2.com wrote:

If that is the way its meant to work, then we need a way to register
things like DataSources and Transaction context into the webapps JNDI.

There is some good docs on how this works in Tomcat here:

http://tomcat.apache.org/tomcat-6.0-doc/jndi-resources-howto.html#context.xml_configuration

In Tomcat it seems you can define JNDI entries either locally in the
web.xml or globally and then link to them.

+1. This should work for us and looks like it's the correct way of doing
this. Kishanthan, please look into this..

Thanks,
~Isuru

Paul

On 28 May 2012 10:03, Isuru Suriarachchi is...@wso2.com wrote:

I had a discussion on this with Kicha and looks like the way it works is
correct. When jndi resources are registered in the webapp itself, those get
registered in it's own context and can be loaded anywhere within the
webapp. But when resources are registered in the initial context, those are
not visible to the webapps. Looks like this is the correct behavior.

Can we please check whether this webapp works in previous releases?

Thanks,
~Isuru

On Mon, May 28, 2012 at 1:00 PM, Kishanthan Thangarajah
kishant...@wso2.com wrote:

Here are the findings on this issue so far.

In trunk, TransactionManager, UserTransaction etc, are getting bind with
InitialContext of javaUrlContextFactory[1] which handles the “java:”
namespace. This context is not bound to any thread or classloader. But in a
webapp case, their context are isolated from each other and the
classloaders are bound to each webapps naming context. But the
initialContext from javaUrlContextFactory will not be accessible for them.
This is why it fails when doing lookup within a webapp.

The javaUrlContextFactory first checks whether current thread or
classloader is bound to any context. If not, it will return the
intialContext. This is why the lookup within a service is successful since
its class loader is not bound to any naming context. The lookup from any BE
component also works fine.

So we have to think of a way to handle this issue.

@Dinusha, can you try whether this webapp works in previous releases?

On Sun, May 27, 2012 at 11:47 AM, Dinusha Senanayaka
dinu...@wso2.comwrote:

Hi Kishanthan,

On Sun, May 27, 2012 at 12:07 AM, Kishanthan Thangarajah
kishant...@wso2.com wrote:

On Sat, May 26, 2012 at 3:05 PM, Dinusha Senanayaka
dinu...@wso2.comwrote:

Hi Kishanthan,

The way you suggested also didn't work for me. I guess, in your
sample wep-app, JNDI lookup has done for some data-source created within
Tomcat itself.

Can you share the webapp? I'll have a look into this.

Please find the attached web-app. It refers to the transaction-manager,
which has bind with JNDI, while transaction-manger bundle get start in
carbon sever.

Regards,
Dinusha.

Thanks,
Kishanthan.

Regards,
Dinusha.

On Sat, May 26, 2012 at 12:50 PM, Supun Malinga sup...@wso2.comwrote:

Hi Kishanthan,

Any idea why 'normal' jndi lookup doesn't work?
If I'm a user and want to do some jndi lookup insid ea webapp I
would follow the standard way. If that's not going to work I think we
better at least document this.

thanks,

On Sat, May 26, 2012 at 11:31 AM, Kishanthan Thangarajah
kishant...@wso2.com wrote:

Hi,
This was one the issue I encountered when trying to write some
webapps with webapp specific contextXml configuration where I store
some
JNDI resources in it. Normal lookup is as follow, which gives the
exception
when trying within a webapp,

Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup(java:comp/env);

But after some debugging at tomcat code level, I found a way to
overcome this. We have to use the catalina jndi context
implementation. Let
me give some insight.

Context initCtx = new InitialContext();
SelectorContext selectorContext = new
SelectorContext((HashtableString, Object) initCtx.getEnvironment(),
false);
Context envCtx = (Context)
selectorContext.lookup(java:comp/env);

Here the SelectorContext is the Catalina JNDI Context
implementation. First using the IntialContext environment we have to
build
the Catalina selector context, and then we can lookup from that. Can
you
please try this and let me know if it fails? You can take a look at the
webapp samples here [1].

Thanks,
Kishanthan.
[1]
https://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/as/modules/samples/product/TomcatWebApps/

On Fri, May 25, 2012 at 5:45 PM, Dinusha Senanayaka
dinu...@wso2.com wrote:

Hi All,

I have registered a object with JNDI and try to access it within a
web-app. But JNDI lookup get fails saying

Re: [Dev] Artifacts deployed through CApps take twice as long to start deploying

2012-05-27 Thread Isuru Suriarachchi

On Sun, May 27, 2012 at 7:03 PM, Afkham Azeez az...@wso2.com wrote:

 This is because in one deployment cycle the CAR deployer extracts the
 relevant artifacts, and in the 2nd cycle, the actual deployment happens.
 This gives the perception of slowness when CApps are used, e.g. when you
 are developing apps using DevStudio. Have we fixed this in the trunk so
 that the artifact deployment also takes place in the first cycle itself.


This is what we tried to address by directly calling particular deployers
from the C-App deployer. But it didn't work for ESB artifacts due to the
way ESB handles deployment. Please see the related thread on dev@.
Therefore, I haven't committed that change in trunk. So still we are
following the old deployment model in which the C-App deployer copies
individual artifacts into particular hot directories. So always it will
take two deployment cycles. First one for C-App and the second to
individual artifacts.

Thanks,
~Isuru




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




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Artifacts deployed through CApps take twice as long to start deploying

2012-05-27 Thread Isuru Suriarachchi

On Mon, May 28, 2012 at 11:00 AM, Afkham Azeez az...@wso2.com wrote:



 On Mon, May 28, 2012 at 10:18 AM, Isuru Suriarachchi is...@wso2.comwrote:



 On Sun, May 27, 2012 at 7:03 PM, Afkham Azeez az...@wso2.com wrote:

 This is because in one deployment cycle the CAR deployer extracts the
 relevant artifacts, and in the 2nd cycle, the actual deployment happens.
 This gives the perception of slowness when CApps are used, e.g. when you
 are developing apps using DevStudio. Have we fixed this in the trunk so
 that the artifact deployment also takes place in the first cycle itself.


 This is what we tried to address by directly calling particular deployers
 from the C-App deployer. But it didn't work for ESB artifacts due to the
 way ESB handles deployment. Please see the related thread on dev@.
 Therefore, I haven't committed that change in trunk. So still we are
 following the old deployment model in which the C-App deployer copies
 individual artifacts into particular hot directories. So always it will
 take two deployment cycles. First one for C-App and the second to
 individual artifacts.


 I think this is a blocker for Stratos or deployments with depsync. We need
 some sort of resolution for this.


+1. But other than calling deployers directly, I couldn't think of another
solution. Any other ideas?



 Thanks,
 ~Isuru




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




 --
 Isuru Suriarachchi
 Senior Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




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




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Impact of C-App deployer changes on ESB artifacts

2012-05-23 Thread Isuru Suriarachchi

Can someone from the ESB team put some input here please?

Thanks,
~Isuru

On Mon, May 21, 2012 at 4:26 PM, Selvaratnam Uthaiyashankar 
shan...@wso2.com wrote:

 One more thing we discussed was, ESB checks the dependency at the
 deployment time. For example, if a proxy service depends on a sequence, it
 validates whether the sequence exist when trying to deploy proxy service.
 (e.g proxy service in one car file and sequence in another car file.. now
 we have to order the car file deployment).

 We discussed this with Paul and the decision is, we should change this
 behavior so that the validation happens with first message arrived, not at
 the time of deployment. Hiranya, how hard is it to do that?

 Regards,
 Shankar


 On Mon, May 21, 2012 at 4:10 PM, Isuru Suriarachchi is...@wso2.comwrote:

 Hi all,

 As per few discussions we did on C-App deployment, we identified that the
 current C-App deployment process causes problems in cluster with deployment
 synchronizer. Currently the C-App deployer reads different artifacts and
 copy those into relevant hot directories in the Axis2 repository
 (repository/deployment/server/xxx). When these artifacts and the original
 C-App are synchronized to a different node, there are conflicts.

 So as a solution, I've already implemented a way in which the C-App
 extracts the individual artifacts into a temp directory and directly call
 the relevant deployer for the artifact. This works well for aar services
 etc. which won't get changed after first deployment. However, I wonder ESB
 artifacts will have a different impact on this because the user can edit
 the ESB configuration through the UI and then it internally get serialized
 to the original xml file in the repository. But in this new approach,
 original artifact will be in the temp directory. So will that be a problem
 from the ESB side?

 And also please let me know if there are any other possible downsides of
 this approach which you can think of.

 Thanks,
 ~Isuru

 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




 --
 S.Uthaiyashankar
 Senior Software Architect
 Chair, Management Committee – Cloud Technologies
 WSO2 Inc.
 http://wso2.com/ - lean . enterprise . middleware

 Phone: +94 714897591




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Impact of C-App deployer changes on ESB artifacts

2012-05-23 Thread Isuru Suriarachchi

After building the latest ESB trunk and testing a C-App which contains all
sorts of ESB artifacts, I found out the following behavior.

* C-App get extracted into tmp/xxxCapp directory
* C-App deployer calls individual ESB deployers and deploys all artifacts.
This works fine. But still the original artifacts are in tmp and not in
repository/deployement/server/synapse-configs.
* Now if the C-App is deleted, all artifacts get deleted as well.
* But if I go the source view and edit the configuration, all artifacts are
written to repository/deployement/server/synapse-configs directory
* Now if I try to delete the C-App there are all sorts of errors.

So it looks like, according to how ESB artifact deployment is handled, it's
hard to deploy a C-App without following the already existing approach
(copying individual artifacts into relevant hot directories).

Thanks,
~Isuru

On Mon, May 21, 2012 at 4:10 PM, Isuru Suriarachchi is...@wso2.com wrote:

 Hi all,

 As per few discussions we did on C-App deployment, we identified that the
 current C-App deployment process causes problems in cluster with deployment
 synchronizer. Currently the C-App deployer reads different artifacts and
 copy those into relevant hot directories in the Axis2 repository
 (repository/deployment/server/xxx). When these artifacts and the original
 C-App are synchronized to a different node, there are conflicts.

 So as a solution, I've already implemented a way in which the C-App
 extracts the individual artifacts into a temp directory and directly call
 the relevant deployer for the artifact. This works well for aar services
 etc. which won't get changed after first deployment. However, I wonder ESB
 artifacts will have a different impact on this because the user can edit
 the ESB configuration through the UI and then it internally get serialized
 to the original xml file in the repository. But in this new approach,
 original artifact will be in the temp directory. So will that be a problem
 from the ESB side?

 And also please let me know if there are any other possible downsides of
 this approach which you can think of.

 Thanks,
 ~Isuru

 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Integration test failures on Carbon core

2012-05-22 Thread Isuru Suriarachchi

I updated the entire trunk this morning and built from the scratch. Getting
the following test failure on carbon core and all other products. Any clue?

Results :

Failed tests:
  startServer(org.wso2.carbon.integration.tests.CarbonTestServerManager):
org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException:
java.lang.RuntimeException: Could not login to Carbon server within
6ms. portOffset=0

Tests run: 28, Failures: 1, Errors: 0, Skipped: 27

surefire report

---
Test set: TestSuite
---
Tests run: 28, Failures: 1, Errors: 0, Skipped: 27, Time elapsed: 69.405
sec  FAILURE!
startServer(org.wso2.carbon.integration.tests.CarbonTestServerManager)
 Time elapsed: 0 sec   FAILURE!
org.testng.internal.thread.ThreadExecutionException:
org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException:
java.lang.RuntimeException: Could not login to Carbon server within
6ms. portOffset=0
at
org.testng.internal.thread.FutureResultAdapter.get(FutureResultAdapter.java:25)
at
org.testng.internal.MethodInvocationHelper.invokeWithTimeoutWithNewExecutor(MethodInvocationHelper.java:242)
at
org.testng.internal.MethodInvocationHelper.invokeWithTimeout(MethodInvocationHelper.java:200)
at
org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:528)
at
org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
at
org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:277)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)



-- 
Isuru Suriarachchi
Senior Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Impact of C-App deployer changes on ESB artifacts

2012-05-21 Thread Isuru Suriarachchi

Hi all,

As per few discussions we did on C-App deployment, we identified that the
current C-App deployment process causes problems in cluster with deployment
synchronizer. Currently the C-App deployer reads different artifacts and
copy those into relevant hot directories in the Axis2 repository
(repository/deployment/server/xxx). When these artifacts and the original
C-App are synchronized to a different node, there are conflicts.

So as a solution, I've already implemented a way in which the C-App
extracts the individual artifacts into a temp directory and directly call
the relevant deployer for the artifact. This works well for aar services
etc. which won't get changed after first deployment. However, I wonder ESB
artifacts will have a different impact on this because the user can edit
the ESB configuration through the UI and then it internally get serialized
to the original xml file in the repository. But in this new approach,
original artifact will be in the temp directory. So will that be a problem
from the ESB side?

And also please let me know if there are any other possible downsides of
this approach which you can think of.

Thanks,
~Isuru

-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Merging Jaggery with AS

2012-05-21 Thread Isuru Suriarachchi

Hi all,

Are we going to merge Jaggery with AS for this release?

If so, Nuwan are there any gray areas in doing this? Should be straight
forward, isn't it?

~Isuru

-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Configuration sync issue in an ESB cluster for proxy services

2012-05-10 Thread Isuru Suriarachchi

On Thu, May 10, 2012 at 11:52 AM, Hiranya Jayathilaka hira...@wso2.comwrote:



 On Thu, May 10, 2012 at 11:33 AM, Isuru Suriarachchi is...@wso2.comwrote:



 On Thu, May 10, 2012 at 11:29 AM, Hiranya Jayathilaka 
 hira...@wso2.comwrote:

 Do we sync meta files across the cluster?


 Yes we do.. That is because for other service types, there's no way of
 replicating the configurations without syncing meta files.


 Is not synchronizing proxy service meta files an option here? In a SVN
 setup that should be pretty easy. But on a registry based setup we need to
 think it through.


But in some cases proxy services too will need the meta file. For example,
if caching module is engaged to the proxy service that information will
only be available in the meta file. Isn't it?

Thanks,
~Isuru



 Thanks,
 Hiranya



 Thanks,
 ~Isuru



 Thanks,
 Hiranya


 On Wed, May 9, 2012 at 12:49 PM, Isuru Suriarachchi is...@wso2.comwrote:

 Hi Hiranya,

 Charitha found this issue [1] which is related to syncing proxy service
 configurations. Here's the root cause for this..

 * When security is applied for the proxy service in the RW node, it
 updates the proxy.xml file and also the meta file
 * Deployment Synchronizer syncs the proxy.xml to RO node
 * RO node hot-updates the proxy.xml and in the process it touches the
 meta file
 * When DS tries to sync the meta file, a conflict occurs because node2
 has already touched it

 This doesn't happen for AAR services because the original .aar file
 never get changed when configurations are changed through the UI. So only
 the meta file will be updated and synced.

 We have to come up with a proper solution for this.

 Thanks,
 ~Isuru

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

 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




 --
 Hiranya Jayathilaka
 Senior Technical Lead;
 WSO2 Inc.;  http://wso2.org
 E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
 Blog: http://techfeast-hiranya.blogspot.com




 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




 --
 Hiranya Jayathilaka
 Senior Technical Lead;
 WSO2 Inc.;  http://wso2.org
 E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
 Blog: http://techfeast-hiranya.blogspot.com




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Configuration sync issue in an ESB cluster for proxy services

2012-05-09 Thread Isuru Suriarachchi

Hi Hiranya,

Charitha found this issue [1] which is related to syncing proxy service
configurations. Here's the root cause for this..

* When security is applied for the proxy service in the RW node, it updates
the proxy.xml file and also the meta file
* Deployment Synchronizer syncs the proxy.xml to RO node
* RO node hot-updates the proxy.xml and in the process it touches the meta
file
* When DS tries to sync the meta file, a conflict occurs because node2 has
already touched it

This doesn't happen for AAR services because the original .aar file never
get changed when configurations are changed through the UI. So only the
meta file will be updated and synced.

We have to come up with a proper solution for this.

Thanks,
~Isuru

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

-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] AWS orbit bundle missing in trunk

2012-05-04 Thread Isuru Suriarachchi

On Fri, May 4, 2012 at 2:08 PM, Ranga Siriwardena ra...@wso2.com wrote:

 Hi,

 In 3.2.0 branch we have aws.java.sdk orbit bundle and it is not there in
 the trunk. Any specific reason for this issue?
 We need this bundle for EC2 auto-scaling stuff. So shall we add this to
 trunk?


It should be graduated. If you want the same version, don't add it to trunk
and use the same version from the m2 repo. If you want to do changes to the
orbit, then only add it to the trunk.

Thanks,
~Isuru



 Thank You.
 Ranga.
 --
 Ranga Siriwardena
 Software Engineer
 WSO2 Inc.


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] HTTP session replication

2012-04-24 Thread Isuru Suriarachchi

+1, We've almost completed all the roadmap items for AS 4.5.0. As we've not
feature freezed yet, we can look into this.

Thanks,
~Isuru

On Tue, Apr 24, 2012 at 7:15 PM, Afkham Azeez az...@wso2.com wrote:

 With the Tomcat OSGification completed, we can finally implement support
 for HTTP session replication. We could tie into the underlying Tribes
 framework to do this. I believe we should write a Tomcat
 HttpSessionReplicationValve which will handle replication of sessions.
 Kishanthan can you own this? Even though this may look like an AppServer
 roadmap item, this is something that will get used throughout the platform.

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




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Carbon Alpha 4 packs for smoke testing

2012-04-24 Thread Isuru Suriarachchi

On Mon, Apr 23, 2012 at 2:15 PM, Kishanthan Thangarajah kishant...@wso2.com
 wrote:



 On Mon, Apr 23, 2012 at 11:07 AM, Supun Malinga sup...@wso2.com wrote:

 HI Kishanthan,

 Please note that ejb-services is still undergoing some major ui changes.
 Please omit it from smoke test. This will be ready in the next alpha pack.
 Also  some changes I made last night are not included in this pack.


 Smoke test results for AS.
 1. No start-up errors.
 2. There is an error in FlickerClient Sample when building and deploying
 [1].


Fixed it.

Thanks,
~Isuru


  Skipped testing EJB Sample as per request. Other samples works fine.

 Found an issue that when the server restarts, the session still remains
 without getting timeout (it doesn't redirect to the login page). This may
 be an issue related to remember me. This has been reported on
 several occasions [2].
 I will test the persistence related issues reported on the alpha3 pack
 with this pack and update the thread.

 Thanks,
 Kishanthan.
 [1] https://wso2.org/jira/browse/CARBON-12929
 [2] https://wso2.org/jira/browse/CARBON-12902



 thanks,


 On Mon, Apr 23, 2012 at 11:04 AM, Lakmali Baminiwatta 
 lakm...@wso2.comwrote:

 Hi,

 Done a smoke test for DSS. No errors in startup and all samples are
 running.

 Thanks,
 Lakmali


 On Mon, Apr 23, 2012 at 9:55 AM, Rajika Kumarasiri raj...@wso2.comwrote:

 CSG passed the smoke tests.

 Rajika

 On Mon, Apr 23, 2012 at 9:08 AM, Dimuthu Leelarathne dimut...@wso2.com
  wrote:

 Hi RMs,

 Please find candidates for Carbon 4.00 Alpha 4 packs here.


 http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-PRODUCTS-JOB1-66/artifact

 Please do a smoke test. Smoke test means

 1) No errors at startup
 2) All samples are running

 thanks,
 dimuthu

 --
 Dimuthu Leelarathne
 Technical Lead

 WSO2, Inc. (http://wso2.com)
 email: dimut...@wso2.com

 Lean . Enterprise . Middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev



 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev






 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Supun Malinga,

 Software Engineer,
 WSO2 Inc.
 http://wso2.com
 http://wso2.org
 email - sup...@wso2.com sup...@wso2.com
 mobile - 071 56 91 321




 --
 *Kishanthan Thangarajah*
 Software Engineer,
 Development Technologies Team,
 WSO2, Inc.
 lean.enterprise.middleware

 Mobile - +94773426635
 Blog - *http://kishanthan.wordpress.com*
 Twitter - *http://twitter.com/kishanthan*


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Blocker] JAX-WS Problems in AS 4.1.x

2012-04-18 Thread Isuru Suriarachchi

On Thu, Apr 19, 2012 at 1:37 AM, Senaka Fernando sen...@wso2.com wrote:

 Hi all,

 Please disregard. I used the wrong attribute. Sorry for the noise. For the
 benefit of all, the proper way is @WebService(serviceName =
 ShoppingService). The name attribute is actually for the Port.


Anyway thanks for trying out and let us know if there are actual bugs :)

Thanks,
~Isuru



 Thanks,
 Senaka.


 On Thu, Apr 19, 2012 at 1:32 AM, Senaka Fernando sen...@wso2.com wrote:

 Hi all,

 I have annotated a service named ShoppingService with the following
 annotation: @WebService(name = ShoppingService). But this shows up as
 ShoppingServiceService, which is crazy. Why do we add a Service part
 behind the default name of a class?

 IMHO, this is a blocker for JAX-WS support. I got this with AS 4.1.2. Is
 this something fixed on the trunk?

 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




 --
 *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


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error when sending a mail

2012-04-17 Thread Isuru Suriarachchi

)
  at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:175)
 at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:474)
  at
 org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:119)
 at org.wso2.carbon.rhino.c0._c0((wso2):16)
  at org.wso2.carbon.rhino.c0.call((wso2))
 at
 org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:401)
  at
 org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3003)
 at org.wso2.carbon.rhino.c0.call((wso2))
  at org.wso2.carbon.rhino.c0.exec((wso2))
 at
 org.wso2.carbon.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:472)
  ... 23 more
 Caused by: org.wso2.carbon.scriptengine.exceptions.ScriptException:
 javax.mail.MessagingException: IOException while sending message;
   nested exception is:
 javax.activation.UnsupportedDataTypeException: no object DCH for MIME
 type multipart/mixed;
  boundary==_Part_0_1260258275.1334659642237
 at
 org.wso2.carbon.hostobjects.email.EmailHostObject.jsFunction_send(EmailHostObject.java:397)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
  at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:160)
 ... 32 more
 Caused by: javax.mail.MessagingException: IOException while sending
 message;
   nested exception is:
  javax.activation.UnsupportedDataTypeException: no object DCH for MIME
 type multipart/mixed;
  boundary==_Part_0_1260258275.1334659642237
 at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:625)
  at javax.mail.Transport.send0(Transport.java:169)
 at javax.mail.Transport.send(Transport.java:98)
  at
 org.wso2.carbon.hostobjects.email.EmailHostObject.jsFunction_send(EmailHostObject.java:395)
  ... 37 more
 Caused by: javax.activation.UnsupportedDataTypeException: no object DCH
 for MIME type multipart/mixed;
  boundary==_Part_0_1260258275.1334659642237
 at
 javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:877)
  at javax.activation.DataHandler.writeTo(DataHandler.java:302)
 at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1350)
  at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1683)
 at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:585)
  ... 40 more


 --
 *Thanks  Regards,

 Nuwan Bandara
 Senior Software Engineer
 WSO2 Inc. | http://wso2.com
 lean . enterprise . middleware

 http://nuwan.bandara.co
 *
 http://www.nuwanbando.com/

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Sameera Jayasoma
 Technical Lead and Product Manager, WSO2 Carbon

 WSO2, Inc. (http://wso2.com)
 email: same...@wso2.com
 blog: http://tech.jayasoma.org

 Lean . Enterprise . Middleware




 --
 *Thanks  Regards,

 Nuwan Bandara
 Senior Software Engineer
 WSO2 Inc. | http://wso2.com
 lean . enterprise . middleware

 http://nuwan.bandara.co
 *
 http://www.nuwanbando.com/




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Alpha 3 packs

2012-04-16 Thread Isuru Suriarachchi

Hi Kishanthan,

Please do the smoke test on AS. In addition to Dimuthu's points please test
the persistence as well.

If the pack looks good, let's release this as M3.

Thanks,
~Isuru

On Mon, Apr 16, 2012 at 12:52 PM, Dimuthu Leelarathne dimut...@wso2.comwrote:


 Hi Azeez,

 On Mon, Apr 16, 2012 at 12:50 PM, Afkham Azeez az...@wso2.com wrote:




 Don't all the products have tests which test all the samples? If not,
 this is the time to start adding those tests, while doing the smoke
 testing. It will make the life of the RMs easier when the next series of
 packs become available.



 Not yet. But as we discussed on the last meeting RMs are trying to get
 there.

 thanks,
 dimuthu



 Please report the above 2 points for your products.

 thanks,
 dimuthu

 --
 Dimuthu Leelarathne
 Technical Lead

 WSO2, Inc. (http://wso2.com)
 email: dimut...@wso2.com

 Lean . Enterprise . Middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*

 *
 *
 *Lean . Enterprise . Middleware*




 --
 Dimuthu Leelarathne
 Technical Lead

 WSO2, Inc. (http://wso2.com)
 email: dimut...@wso2.com

 Lean . Enterprise . Middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Alpha 3 packs

2012-04-16 Thread Isuru Suriarachchi

On Mon, Apr 16, 2012 at 2:44 PM, Kishanthan Thangarajah kishant...@wso2.com
 wrote:

 Hi,
 1. There are some loader constraint violations with four of the
 Jaxws-jaxrs samples, when deploying.
 (wsdl_first_jaxws, async_jaxws, handlers_jaxws, mtom_jaxws). [1].


I've fixed these issues.. Please check on the next build..

Thanks,
~Isuru


 2. No start-up errors.

 Persistence level issues for service QoS configuration.
 1. Reliable messaging configuration changes are not reflected when server
 restarted.
 2. When updating Policies manually through editor, they are also not
 reflected in the respective QoS configuration after server is restarted.

 Found that in service metafiles, some of the old configurations are still
 there along with the new configarations even after they are updated. I will
 create jiras for the above persistence level issues.

 Thanks,
 Kishanthan.
 [1] https://wso2.org/jira/browse/CARBON-12805

 On Mon, Apr 16, 2012 at 1:28 PM, Isuru Suriarachchi is...@wso2.comwrote:

 Hi Kishanthan,

 Please do the smoke test on AS. In addition to Dimuthu's points please
 test the persistence as well.

 If the pack looks good, let's release this as M3.

 Thanks,
 ~Isuru


 On Mon, Apr 16, 2012 at 12:52 PM, Dimuthu Leelarathne 
 dimut...@wso2.comwrote:


 Hi Azeez,

 On Mon, Apr 16, 2012 at 12:50 PM, Afkham Azeez az...@wso2.com wrote:




 Don't all the products have tests which test all the samples? If not,
 this is the time to start adding those tests, while doing the smoke
 testing. It will make the life of the RMs easier when the next series of
 packs become available.



 Not yet. But as we discussed on the last meeting RMs are trying to get
 there.

 thanks,
 dimuthu



 Please report the above 2 points for your products.

 thanks,
 dimuthu

 --
 Dimuthu Leelarathne
 Technical Lead

 WSO2, Inc. (http://wso2.com)
 email: dimut...@wso2.com

 Lean . Enterprise . Middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * http://www.apache.org/**
 email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919
 blog: **http://blog.afkham.org* http://blog.afkham.org*
 twitter: 
 **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*

 *
 *
 *Lean . Enterprise . Middleware*




 --
 Dimuthu Leelarathne
 Technical Lead

 WSO2, Inc. (http://wso2.com)
 email: dimut...@wso2.com

 Lean . Enterprise . Middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




 --
 *Kishanthan Thangarajah*
 Software Engineer,
 Development Technologies Team,
 WSO2, Inc.
 lean.enterprise.middleware

 Mobile - +94773426635
 Blog - *http://kishanthan.wordpress.com*
 Twitter - *http://twitter.com/kishanthan*




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting javax.activation from the JDK

.carbon.integration.framework.utils.CodeCoverageUtils} -
 Generated Emma reports
Tests run: 40, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 281.355
sec  FAILURE!
[2012-04-05 14:56:10,252]  INFO
{org.wso2.carbon.integration.framework.utils.ServerUtils} -  Shutting down
server...
[2012-04-05 14:56:10,252]  INFO
{org.wso2.carbon.integration.framework.utils.ServerUtils} -  Shutting down
server...
[2012-04-05 14:56:10,253]  INFO
{org.wso2.carbon.integration.framework.utils.ServerUtils} -  Shutting down
server...
[2012-04-05 14:56:10,253]  INFO
{org.wso2.carbon.integration.framework.utils.ServerUtils} -  Shutting down
server...

Results :

Failed tests:
partnerServiceSecurityTest(org.wso2.bps.integration.tests.security.PartnerServiceSecurityTestCase):
Read timed out

Tests run: 40, Failures: 1, Errors: 0, Skipped: 0


On Thu, Apr 5, 2012 at 12:22 AM, Sameera Jayasoma same...@wso2.com wrote:

 HI Azeez,

 We had an offline discussion on this. This is the best solution for the
 problem that Isuru is facing. We should have done the same thing for the
 javax.xml.soap packages.

 Thanks,
 Sameera.


 On Thu, Apr 5, 2012 at 12:12 AM, Afkham Azeez az...@wso2.com wrote:

 Please run all product builds with integration tests. We have just one
 more day before the break

 --
 Afkham Azeez
 Sent from my phone
 On Apr 4, 2012 10:39 PM, Isuru Suriarachchi is...@wso2.com wrote:



 On Wed, Apr 4, 2012 at 9:50 PM, Afkham Azeez az...@wso2.com wrote:

 This WILL break a lot of stuff. Please don't commit this at this stage.
 Can you please delay this commit and run a full platform build first?


 No I fixed all breaks. I've already ran a full build up to AS without
 any issue. Even if we find issues related to this, it will be very easy to
 fix. So I think this won't cause any problems. WDYT??

 Thanks,
 ~Isuru



 Thanks
 Azeez

 On Wed, Apr 4, 2012 at 8:36 PM, Isuru Suriarachchi is...@wso2.comwrote:

 Hi all,

 Currently we get the javax.activation package from the following
 artifact and it comes through axiom.

 dependency
 groupIdjavax.activation/groupId
 artifactIdactivation/artifactId
 /dependency

 But with the CXF integration, I found that this implementation of
 javax.activation doesn't work for CXF and it only works with the API and
 the implementation provided by the JDK. So I removed the javax.activation
 export from axiom and took it from the JDK. And also I tested Axis2 MTOM
 support after this change and it worked fine.

 I'm going to commit this change and if you find any issue which is
 caused by this change, please let me know. Basically if some bundle is in
 INSTALLED state and when you try to start it if you see the following
 error, please let me know..

 osgi start 156
 org.osgi.framework.BundleException: The bundle
 org.wso2.carbon.dataservices.fileupload.stub_4.0.0.SNAPSHOT [156] could
 not be resolved. Reason: Missing Constraint: Import-Package:
 javax.activation; version=[1.1.0,2.0.0)
  at
 org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1327)
 at
 org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1311)
  at
 org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)

 You can get this fixed by adding the following config into the
 particular bundle..

 Import-Package
 javax.activation.*;version=[0.0.0, 1.0.0)
 /Import-Package

 I fixed all such bundles I found. But there can be more..

 Thanks,
 ~Isuru

 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




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




 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Sameera Jayasoma
 Technical Lead and Product Manager, WSO2 Carbon

 WSO2, Inc. (http://wso2.com)
 email: same...@wso2.com
 blog: http://tech.jayasoma.org


 Lean . Enterprise . Middleware




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http

Re: [Dev] Getting javax.activation from the JDK

attached.. it's a read timeout..

On Thu, Apr 5, 2012 at 3:10 PM, Waruna Ranasinghe war...@wso2.com wrote:

 Please attach the surefire reports.

 Thanks,
 Waruna


 On Thu, Apr 5, 2012 at 10:29 AM, Isuru Suriarachchi is...@wso2.comwrote:

 Ran all product builds with my changes. All products passes with tests
 expect BPS in which I found the following error. Not sure whether this is
 related to this change or not. Anyone from BPS team has an idea?

 Thanks,
 ~Isuru

 [2012-04-05 14:56:06,253]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
  [2012-04-05 14:56:06,253]  INFO - CarbonAuthenticationUtil - 'admin'
 logged in at [2012-04-05 14:56:06,0253] from IP address 10.100.3.147
 [2012-04-05 14:56:06,260]  INFO
 {org.wso2.carbon.integration.framework.LoginLogoutUtil} -  Successfully
 logged in : JSESSIONID=129BA841FE34D07B74FCD21DEBEB28DC; Path=/;
 Secure=null; HttpOnly=null
 [2012-04-05 14:56:06,277]  INFO
 {org.apache.axis2.deployment.ModuleDeployer} -  Deploying module: rampart -
 file:/home/isuru/.m2/repository/org/apache/rampart/wso2/rampart-core/1.6.1.wso2v4/rampart-core-1.6.1.wso2v4.jar
 [2012-04-05 14:56:06,277]  INFO
 {org.apache.axis2.deployment.ModuleDeployer} -  Deploying module: rampart -
 file:/home/isuru/.m2/repository/org/apache/rampart/wso2/rampart-core/1.6.1.wso2v4/rampart-core-1.6.1.wso2v4.jar
 [2012-04-05 14:56:06,281]  INFO
 {org.apache.axis2.deployment.ModuleDeployer} -  Deploying module: rahas -
 file:/home/isuru/.m2/repository/org/apache/rampart/wso2/rampart-trust/1.6.1.wso2v4/rampart-trust-1.6.1.wso2v4.jar
 [2012-04-05 14:56:06,281]  INFO
 {org.apache.axis2.deployment.ModuleDeployer} -  Deploying module: rahas -
 file:/home/isuru/.m2/repository/org/apache/rampart/wso2/rampart-trust/1.6.1.wso2v4/rampart-trust-1.6.1.wso2v4.jar
 [2012-04-05 14:56:07,318]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
  [2012-04-05 14:56:07,318]  INFO - CarbonServerManager - Gracefully
 shutting down WSO2 BPS...
 [2012-04-05 14:56:07,321]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
  [2012-04-05 14:56:07,321]  INFO - ServerManagement - Starting to switch to
 maintenance mode...
 [2012-04-05 14:56:09,632]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
  [2012-04-05 14:56:09,632]  INFO - ServerManagement - Stopped all transport
 listeners
 [2012-04-05 14:56:09,632]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
  [2012-04-05 14:56:09,632]  INFO - ServerManagement - Waiting for request
 service completion...
 [2012-04-05 14:56:09,634]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
  [2012-04-05 14:56:09,634]  INFO - ServerManagement - All requests have
 been served.
 [2012-04-05 14:56:09,634]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
  [2012-04-05 14:56:09,634]  INFO - ServerManagement - Waiting for
 deployment completion...
 [2012-04-05 14:56:09,635]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
  [2012-04-05 14:56:09,635]  INFO - ServerManagement - All deployment tasks
 have been completed.
 [2012-04-05 14:56:09,635]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
  [2012-04-05 14:56:09,635]  INFO - CarbonServerManager - Shutting down WSO2
 BPS...
 [2012-04-05 14:56:09,637]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
  [2012-04-05 14:56:09,637]  WARN - HttpConnection - HttpConnectionManager
 is null.  Connection cannot be released.
 [2012-04-05 14:56:09,637]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
  [2012-04-05 14:56:09,637]  INFO - TCPTransportSender - TCP Sender Shutdown
 [2012-04-05 14:56:09,638]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
  [2012-04-05 14:56:09,638]  INFO - CarbonServerManager - Shutting down OSGi
 framework...
 [2012-04-05 14:56:09,638]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
  [2012-04-05 14:56:09,638]  INFO - CarbonServerManager - Shutdown complete
 [2012-04-05 14:56:09,638]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
  [2012-04-05 14:56:09,638]  INFO - CarbonServerManager - Halting JVM
 [2012-04-05 14:56:09,638]  INFO
 {org.wso2.carbon.integration.framework.utils.ServerUtils} -  Server stopped
 successfully...
 Problem reading the inputStream
 java.io.IOException: Stream closed
  at
 java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:145)
 at java.io.BufferedInputStream.read1(BufferedInputStream.java:255)
  at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
 at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
  at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
 at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
  at java.io.InputStreamReader.read(InputStreamReader.java:167)
 at java.io.BufferedReader.fill

[Dev] Identity integration test failure

Is this a known issue? surefire report is attached..

[2012-04-05 18:39:13,695]  INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
[2012-04-05 18:39:13,695]  INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
[2012-04-05 18:39:13,695]  INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
[2012-04-05 18:39:13,695]  INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:61)
[2012-04-05 18:39:13,695]  INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:155)
[2012-04-05 18:39:13,695]  INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
[2012-04-05 18:39:13,695]  INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
[2012-04-05 18:39:13,695]  INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
[2012-04-05 18:39:13,695]  INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987)
[2012-04-05 18:39:13,695]  INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
[2012-04-05 18:39:13,695]  INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1600)
[2012-04-05 18:39:13,696]  INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[2012-04-05 18:39:13,696]  INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[2012-04-05 18:39:13,696]  INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
java.lang.Thread.run(Thread.java:619)
Tests run: 24, Failures: 1, Errors: 0, Skipped: 23, Time elapsed: 41.735
sec  FAILURE!

Results :

Failed tests:
  startServer(org.wso2.identity.integration.tests.ISTestServerManager):
org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException:
java.lang.AssertionError: Login failed!

Tests run: 24, Failures: 1, Errors: 0, Skipped: 23


-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
---
Test set: TestSuite
---
Tests run: 24, Failures: 1, Errors: 0, Skipped: 23, Time elapsed: 41.735 sec 
 FAILURE!
startServer(org.wso2.identity.integration.tests.ISTestServerManager)  Time 
elapsed: 0 sec   FAILURE!
org.testng.internal.thread.ThreadExecutionException: 
org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException: 
java.lang.AssertionError: Login failed!
at 
org.testng.internal.thread.FutureResultAdapter.get(FutureResultAdapter.java:25)
at 
org.testng.internal.MethodInvocationHelper.invokeWithTimeoutWithNewExecutor(MethodInvocationHelper.java:242)
at 
org.testng.internal.MethodInvocationHelper.invokeWithTimeout(MethodInvocationHelper.java:200)
at 
org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:528)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:277)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1083)
at org.testng.TestNG.run(TestNG.java:999)
at 
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:60)
at 
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:153)
at 
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute

Re: [Dev] Identity integration test failure

Looks like this is common for all products.. :(

2012/4/5 Isuru Suriarachchi is...@wso2.com

 Is this a known issue? surefire report is attached..

 [2012-04-05 18:39:13,695]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
 [2012-04-05 18:39:13,695]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
 [2012-04-05 18:39:13,695]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
 [2012-04-05 18:39:13,695]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:61)
 [2012-04-05 18:39:13,695]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:155)
 [2012-04-05 18:39:13,695]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
 [2012-04-05 18:39:13,695]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
 [2012-04-05 18:39:13,695]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
 [2012-04-05 18:39:13,695]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987)
 [2012-04-05 18:39:13,695]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
 [2012-04-05 18:39:13,695]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1600)
 [2012-04-05 18:39:13,696]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 [2012-04-05 18:39:13,696]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 [2012-04-05 18:39:13,696]  INFO
 {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 java.lang.Thread.run(Thread.java:619)
 Tests run: 24, Failures: 1, Errors: 0, Skipped: 23, Time elapsed: 41.735
 sec  FAILURE!

 Results :

 Failed tests:
   startServer(org.wso2.identity.integration.tests.ISTestServerManager):
 org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException:
 java.lang.AssertionError: Login failed!

 Tests run: 24, Failures: 1, Errors: 0, Skipped: 23


 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Identity integration test failure

When I restarted my machine, it started to work. Looks like something went
wrong locally. So nothing to worry..

On Thu, Apr 5, 2012 at 7:01 PM, Amila Jayasekara ami...@wso2.com wrote:

 Coming from Tomcat based (
 org.apache.catalina.authenticator.AuthenticatorBase ) authenticator.
 Also error in INFO level. Cant remember we getting this in old packs
 ?.

 Thanks
 AmilaJ

 On Thu, Apr 5, 2012 at 6:55 PM, Isuru Suriarachchi is...@wso2.com wrote:
  Looks like this is common for all products.. :(
 
 
  2012/4/5 Isuru Suriarachchi is...@wso2.com
 
  Is this a known issue? surefire report is attached..
 
  [2012-04-05 18:39:13,695]  INFO
  {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 
 org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
  [2012-04-05 18:39:13,695]  INFO
  {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
  [2012-04-05 18:39:13,695]  INFO
  {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
  [2012-04-05 18:39:13,695]  INFO
  {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 
 org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:61)
  [2012-04-05 18:39:13,695]  INFO
  {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 
 org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:155)
  [2012-04-05 18:39:13,695]  INFO
  {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
  [2012-04-05 18:39:13,695]  INFO
  {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
  [2012-04-05 18:39:13,695]  INFO
  {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
  [2012-04-05 18:39:13,695]  INFO
  {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 
 org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987)
  [2012-04-05 18:39:13,695]  INFO
  {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 
 org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
  [2012-04-05 18:39:13,695]  INFO
  {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 
 org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1600)
  [2012-04-05 18:39:13,696]  INFO
  {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  [2012-04-05 18:39:13,696]  INFO
  {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  [2012-04-05 18:39:13,696]  INFO
  {org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
  java.lang.Thread.run(Thread.java:619)
  Tests run: 24, Failures: 1, Errors: 0, Skipped: 23, Time elapsed: 41.735
  sec  FAILURE!
 
  Results :
 
  Failed tests:
startServer(org.wso2.identity.integration.tests.ISTestServerManager):
  org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException:
  java.lang.AssertionError: Login failed!
 
  Tests run: 24, Failures: 1, Errors: 0, Skipped: 23
 
 
  --
  Isuru Suriarachchi
  Technical Lead
  WSO2 Inc. http://wso2.com
  email : is...@wso2.com
  blog : http://isurues.wordpress.com/
 
  lean . enterprise . middleware
 
 
 
 
  --
  Isuru Suriarachchi
  Technical Lead
  WSO2 Inc. http://wso2.com
  email : is...@wso2.com
  blog : http://isurues.wordpress.com/
 
  lean . enterprise . middleware
 
 
  ___
  Dev mailing list
  Dev@wso2.org
  http://wso2.org/cgi-bin/mailman/listinfo/dev
 



 --
 Mobile : +94773330538




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Getting javax.activation from the JDK

2012-04-04 Thread Isuru Suriarachchi

Hi all,

Currently we get the javax.activation package from the following artifact
and it comes through axiom.

dependency
groupIdjavax.activation/groupId
artifactIdactivation/artifactId
/dependency

But with the CXF integration, I found that this implementation of
javax.activation doesn't work for CXF and it only works with the API and
the implementation provided by the JDK. So I removed the javax.activation
export from axiom and took it from the JDK. And also I tested Axis2 MTOM
support after this change and it worked fine.

I'm going to commit this change and if you find any issue which is caused
by this change, please let me know. Basically if some bundle is in
INSTALLED state and when you try to start it if you see the following
error, please let me know..

osgi start 156
org.osgi.framework.BundleException: The bundle
org.wso2.carbon.dataservices.fileupload.stub_4.0.0.SNAPSHOT [156] could
not be resolved. Reason: Missing Constraint: Import-Package:
javax.activation; version=[1.1.0,2.0.0)
 at
org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1327)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1311)
 at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)

You can get this fixed by adding the following config into the particular
bundle..

Import-Package
javax.activation.*;version=[0.0.0, 1.0.0)
/Import-Package

I fixed all such bundles I found. But there can be more..

Thanks,
~Isuru

-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting javax.activation from the JDK

2012-04-04 Thread Isuru Suriarachchi

On Wed, Apr 4, 2012 at 9:50 PM, Afkham Azeez az...@wso2.com wrote:

 This WILL break a lot of stuff. Please don't commit this at this stage.
 Can you please delay this commit and run a full platform build first?


No I fixed all breaks. I've already ran a full build up to AS without any
issue. Even if we find issues related to this, it will be very easy to fix.
So I think this won't cause any problems. WDYT??

Thanks,
~Isuru



 Thanks
 Azeez

 On Wed, Apr 4, 2012 at 8:36 PM, Isuru Suriarachchi is...@wso2.com wrote:

 Hi all,

 Currently we get the javax.activation package from the following artifact
 and it comes through axiom.

 dependency
 groupIdjavax.activation/groupId
 artifactIdactivation/artifactId
 /dependency

 But with the CXF integration, I found that this implementation of
 javax.activation doesn't work for CXF and it only works with the API and
 the implementation provided by the JDK. So I removed the javax.activation
 export from axiom and took it from the JDK. And also I tested Axis2 MTOM
 support after this change and it worked fine.

 I'm going to commit this change and if you find any issue which is caused
 by this change, please let me know. Basically if some bundle is in
 INSTALLED state and when you try to start it if you see the following
 error, please let me know..

 osgi start 156
 org.osgi.framework.BundleException: The bundle
 org.wso2.carbon.dataservices.fileupload.stub_4.0.0.SNAPSHOT [156] could
 not be resolved. Reason: Missing Constraint: Import-Package:
 javax.activation; version=[1.1.0,2.0.0)
  at
 org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1327)
 at
 org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1311)
  at
 org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)

 You can get this fixed by adding the following config into the particular
 bundle..

 Import-Package
 javax.activation.*;version=[0.0.0, 1.0.0)
 /Import-Package

 I fixed all such bundles I found. But there can be more..

 Thanks,
 ~Isuru

 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




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




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Class loading issues when deploying JAXWS webapps in latest AS

2012-04-04 Thread Isuru Suriarachchi

Hi Charitha,

I ran a full build and ran all JAX-WS samples on AS. All are working on
Linux + JDK 1.6. I'll try the samples on JDK 1.7. That should be the issue
here..

Thanks,
~Isuru

On Wed, Apr 4, 2012 at 1:12 PM, Isuru Suriarachchi is...@wso2.com wrote:

 I'll have a look into this..

 Thanks,
 ~Isuru

 On Wed, Apr 4, 2012 at 10:26 AM, Yumani Ranaweera yum...@wso2.com wrote:



 On Wed, Apr 4, 2012 at 9:43 AM, Yumani Ranaweera yum...@wso2.com wrote:



 On Tue, Apr 3, 2012 at 10:46 PM, Charitha Kankanamge 
 chari...@wso2.comwrote:

 Btw, I'm on windows.



 Getting the same exceptions in Ubuntu also.



 But its only async_jaxws that failed for me. jaxrs_basic worked and
 only failure was this [1].

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

 -Yumani



 Thanks,
 Yumani




 --
 Yumani Ranaweera
 Associate Technical Lead - QA
 WSO2, Inc. - http://wso2.org

 Email : yum...@wso2.com
 Cell: +94 077 7795242
 Blog   : http://yumani.blogspot.com/




 --
 Yumani Ranaweera
 Associate Technical Lead - QA
 WSO2, Inc. - http://wso2.org

 Email : yum...@wso2.com
 Cell: +94 077 7795242
 Blog   : http://yumani.blogspot.com/


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] AS distribution build failure

2012-04-02 Thread Isuru Suriarachchi

Latest AS distribution has the following build failure. Anyone changed
something related??..

[INFO] WSO2 Stratos  AppServer - Profile Generation .. SUCCESS [49.069s]
[INFO] WSO2 AppServer - Distribution Parent .. SUCCESS [0.057s]
[INFO] WSO2 AppServer - Distribution . FAILURE
[7:33.288s]
[INFO] WSO2 Stratos AppServer - Distribution . SKIPPED
[INFO] WSO2 AS - Integration Tests ... SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 13:23.265s
[INFO] Finished at: Mon Apr 02 15:17:41 IST 2012
[INFO] Final Memory: 276M/945M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached (4-dist)
on project wso2as: Failed to create assembly: File to filter not found:
/home/isuru/checkouts/wso2/trunk/new-carbon/platform/products/as/modules/distribution/product/target/wso2carbon-core-4.0.0-SNAPSHOT/bin/README.txt
(No such file or directory) - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn goals -rf :wso2as


-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Don't declare a plugin multiple times

2012-03-31 Thread Isuru Suriarachchi

+1 Good job..

On Fri, Mar 30, 2012 at 9:51 PM, Afkham Azeez az...@wso2.com wrote:

 Nice work Pradeeban. Thanks for taking up this task  fixing all these
 problems which were lingering for some time.

 Thanks
 Azeez

 On Fri, Mar 30, 2012 at 8:52 PM, Kathiravelu Pradeeban pradee...@wso2.com
  wrote:

 The attached patch fixes all the maven3 warnings and bad practices found
 in products/pom.xml's. Will commit it after finishing this full build with
 tests.

 Regards,
 Pradeeban.


 On Fri, Mar 30, 2012 at 3:47 PM, Kathiravelu Pradeeban 
 pradee...@wso2.com wrote:

 Also to avoid declaring the dependencies and versions multiple times,
 where there exists dependencies defined multiple times in a pom with
 different versions.
 I have already fixed all these maven3 violations. Will commit these
 after building with tests. So do *NOT* work on fixing these now. Just
 mentioning to the list for the completeness.

 For example, I can see the below, in many of the modules/distribution
 poms.

 *plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-antrun-plugin/artifactId
 version1.1/version
 executions
 execution
 idextract-docs-from-components/id
 phasepackage/phase
 goals
 goalrun/goal
 /goals
 configuration
 tasks
 ... ...
 /tasks
 /configuration
 /execution
 /executions
 /plugin

 plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-antrun-plugin/artifactId
 version1.1/version
 executions
 execution
 idclean_target/id
 phaseinstall/phase
 configuration
 tasks
 ... ...
 /tasks
 /configuration
 goals
 goalrun/goal
 /goals
 /execution
 /executions
 /plugin

 *Which actually should have been defined like this.

 *plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-antrun-plugin/artifactId
 version1.1/version
 executions
 execution
 idextract-docs-from-components/id
 phasepackage/phase
 goals
 goalrun/goal
 /goals
 configuration
 tasks
 ... ...
 /tasks
 /configuration
 /execution
 execution
 idclean_target/id
 phaseinstall/phase
 configuration
 tasks
 ... ...
 /tasks
 /configuration
 goals
 goalrun/goal
 /goals
 /execution
 /executions
 /plugin
 *
 Thank you.
 Regards,
 Pradeeban.
 --
 Kathiravelu Pradeeban.
 Software Engineer.
 Cloud Technologies Team.
 WSO2 Inc.

 Blog: [Llovizna] http://kkpradeeban.blogspot.com/
 M: +94 776 477 976




 --
 Kathiravelu Pradeeban.
 Software Engineer.
 Cloud Technologies Team.
 WSO2 Inc.

 Blog: [Llovizna] http://kkpradeeban.blogspot.com/
 M: +94 776 477 976


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




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


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware

Re: [Dev] Getting javax.xml.soap package from JDK for CXF

2012-03-31 Thread Isuru Suriarachchi

I've committed all changes related to this after running integration tests
in kernel and AS. If any of the other products are affected by this, please
let me know.

Thanks,
~Isuru

On Sat, Mar 31, 2012 at 10:09 AM, Isuru Suriarachchi is...@wso2.com wrote:

 Hi all,

 I had an issue while trying CXF handler samples due to javax.xml.soap
 package. In Carbon, currently we get javax.xml.soap api from geronimo-saaj
 api bundle and the saaj implementation is coming from axis2-saaj. But CXF
 works properly only with the JDK implementation of javax.xml.soap.

 In order to solve this problem, I wanted to let axis2 bind to geronimo and
 cxf bind to JDK. So I followed these steps.

 1. Currently, geronimo-saaj bundle is a fragment of the system bundle [1].
 First I made it a normal bundle as we no longer need it to be a fragment.
 2. geronimo-saaj bundle exports the javax.xml.soap package with version
 1.0.0. So I fixed axis2 bundle to import the 1.0.0 version.
 3. Added following lines to launch.ini to get the javax.xml.soap api and
 the implementation for the JDK.

 javax.xml.soap,\
 com.sun.xml.internal.messaging.saaj.soap.ver1_1,\
 com.sun.xml.internal.messaging.saaj.soap,\

 4. Imported javax.xml.soap version 0.0.0 from CXF bundle.

 Now the bundle wiring looks like this..

 osgi p javax.xml.soap
 javax.xml.soap; version=0.0.0org.eclipse.osgi_3.7.0.v20110613 [0]
   org.eclipse.core.expressions_3.4.300.v20110228 [73] imports
   org.eclipse.core.runtime_3.7.0.v20110110 [75] imports
   org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [99] imports
   tomcat_7.0.26.wso2v1 [322] imports  --- (CXF is a fragment
 of tomcat. Therefore it's shown through tomcat bundle)
 javax.xml.soap; version=1.0.0geronimo-saaj_1.3_spec_1.0.0.wso2v2 [1]
   axis2_1.6.1.wso2v5 [16] imports
   spring.framework_3.1.0.wso2v1 [318] imports
   wss4j_1.5.11.wso2v3 [328] imports

 Finally I tested both CXF handler samples and Axis2 Caching which uses
 saaj. Both seems to work properly.

 Now I'm gonna give a new version to geronimo saaj and un-graduate it and
 add it to orbit. Then I'll commit all above changes. If anyone can see any
 issues with this approach, please let me know.

 Thanks,
 ~Isuru

 [1]
 https://svn.wso2.org/repos/wso2/tags/carbon/3.1.0_chunk1_as_ms/orbit/geronimo-saaj_1.3_spec/1.0.0.wso2v2

 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting javax.xml.soap package from JDK for CXF

2012-03-31 Thread Isuru Suriarachchi

Oh.. I haven't added geronimo-saaj module into orbit root pom :(. Thanks
Pradeep for adding it. Everything should be fine now. Sorry for the
inconvenience..

Thanks,
~Isuru

On Sat, Mar 31, 2012 at 3:01 PM, Afkham Azeez az...@wso2.com wrote:

 Is the Bamboo kernel build failure a result of this change?

 On Sat, Mar 31, 2012 at 12:06 PM, Isuru Suriarachchi is...@wso2.comwrote:

 I've committed all changes related to this after running integration
 tests in kernel and AS. If any of the other products are affected by this,
 please let me know.

 Thanks,
 ~Isuru


 On Sat, Mar 31, 2012 at 10:09 AM, Isuru Suriarachchi is...@wso2.comwrote:

 Hi all,

 I had an issue while trying CXF handler samples due to javax.xml.soap
 package. In Carbon, currently we get javax.xml.soap api from geronimo-saaj
 api bundle and the saaj implementation is coming from axis2-saaj. But CXF
 works properly only with the JDK implementation of javax.xml.soap.

 In order to solve this problem, I wanted to let axis2 bind to geronimo
 and cxf bind to JDK. So I followed these steps.

 1. Currently, geronimo-saaj bundle is a fragment of the system bundle
 [1]. First I made it a normal bundle as we no longer need it to be a
 fragment.
 2. geronimo-saaj bundle exports the javax.xml.soap package with version
 1.0.0. So I fixed axis2 bundle to import the 1.0.0 version.
 3. Added following lines to launch.ini to get the javax.xml.soap api and
 the implementation for the JDK.

 javax.xml.soap,\
 com.sun.xml.internal.messaging.saaj.soap.ver1_1,\
 com.sun.xml.internal.messaging.saaj.soap,\

 4. Imported javax.xml.soap version 0.0.0 from CXF bundle.

 Now the bundle wiring looks like this..

 osgi p javax.xml.soap
 javax.xml.soap; version=0.0.0org.eclipse.osgi_3.7.0.v20110613 [0]
   org.eclipse.core.expressions_3.4.300.v20110228 [73] imports
   org.eclipse.core.runtime_3.7.0.v20110110 [75] imports
   org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [99] imports
   tomcat_7.0.26.wso2v1 [322] imports  --- (CXF is a
 fragment of tomcat. Therefore it's shown through tomcat bundle)
 javax.xml.soap; version=1.0.0geronimo-saaj_1.3_spec_1.0.0.wso2v2 [1]
   axis2_1.6.1.wso2v5 [16] imports
   spring.framework_3.1.0.wso2v1 [318] imports
   wss4j_1.5.11.wso2v3 [328] imports

 Finally I tested both CXF handler samples and Axis2 Caching which uses
 saaj. Both seems to work properly.

 Now I'm gonna give a new version to geronimo saaj and un-graduate it and
 add it to orbit. Then I'll commit all above changes. If anyone can see any
 issues with this approach, please let me know.

 Thanks,
 ~Isuru

 [1]
 https://svn.wso2.org/repos/wso2/tags/carbon/3.1.0_chunk1_as_ms/orbit/geronimo-saaj_1.3_spec/1.0.0.wso2v2

 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




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




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Getting javax.xml.soap package from JDK for CXF

2012-03-30 Thread Isuru Suriarachchi

Hi all,

I had an issue while trying CXF handler samples due to javax.xml.soap
package. In Carbon, currently we get javax.xml.soap api from geronimo-saaj
api bundle and the saaj implementation is coming from axis2-saaj. But CXF
works properly only with the JDK implementation of javax.xml.soap.

In order to solve this problem, I wanted to let axis2 bind to geronimo and
cxf bind to JDK. So I followed these steps.

1. Currently, geronimo-saaj bundle is a fragment of the system bundle [1].
First I made it a normal bundle as we no longer need it to be a fragment.
2. geronimo-saaj bundle exports the javax.xml.soap package with version
1.0.0. So I fixed axis2 bundle to import the 1.0.0 version.
3. Added following lines to launch.ini to get the javax.xml.soap api and
the implementation for the JDK.

javax.xml.soap,\
com.sun.xml.internal.messaging.saaj.soap.ver1_1,\
com.sun.xml.internal.messaging.saaj.soap,\

4. Imported javax.xml.soap version 0.0.0 from CXF bundle.

Now the bundle wiring looks like this..

osgi p javax.xml.soap
javax.xml.soap; version=0.0.0org.eclipse.osgi_3.7.0.v20110613 [0]
  org.eclipse.core.expressions_3.4.300.v20110228 [73] imports
  org.eclipse.core.runtime_3.7.0.v20110110 [75] imports
  org.eclipse.equinox.p2.garbagecollector_1.0.200.v20110510 [99] imports
  tomcat_7.0.26.wso2v1 [322] imports  --- (CXF is a fragment
of tomcat. Therefore it's shown through tomcat bundle)
javax.xml.soap; version=1.0.0geronimo-saaj_1.3_spec_1.0.0.wso2v2 [1]
  axis2_1.6.1.wso2v5 [16] imports
  spring.framework_3.1.0.wso2v1 [318] imports
  wss4j_1.5.11.wso2v3 [328] imports

Finally I tested both CXF handler samples and Axis2 Caching which uses
saaj. Both seems to work properly.

Now I'm gonna give a new version to geronimo saaj and un-graduate it and
add it to orbit. Then I'll commit all above changes. If anyone can see any
issues with this approach, please let me know.

Thanks,
~Isuru

[1]
https://svn.wso2.org/repos/wso2/tags/carbon/3.1.0_chunk1_as_ms/orbit/geronimo-saaj_1.3_spec/1.0.0.wso2v2

-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Errors when building AS

On Wed, Mar 28, 2012 at 12:00 PM, Manjula Rathnayake manju...@wso2.comwrote:



 On Wed, Mar 28, 2012 at 11:52 AM, Isuru Suriarachchi is...@wso2.comwrote:



 On Wed, Mar 28, 2012 at 11:18 AM, Manjula Rathnayake 
 manju...@wso2.comwrote:



 On Wed, Mar 28, 2012 at 11:12 AM, Kasun Gajasinghe kas...@wso2.comwrote:



 On Wed, Mar 28, 2012 at 10:27 AM, Manjula Rathnayake manju...@wso2.com
  wrote:



 On Tue, Mar 27, 2012 at 8:18 PM, Sinthuja Ragendran sinth...@wso2.com
  wrote:

 Hi,

 I'm also experiencing similar error mentioning '*requires 'package
 javax.xml.namespace [1.0.0,2.0.0)' but it could not be found*' when
 installing the Transport Management Feature in product-BAM2.


 Have we sorted out this issue? I checked in orbit,carbon and platform
 poms, but I could not find a place where we export javax.xml.namespace
 package.

 Any others getting this error? Or it is local to me?


 No, it's still there. I'm also facing this issue. I think Bamboo will
 start complaining sooner.


 I exported in orbit axiom bundle, I will check the build and commit if
 there is no concern regarding this change.


 But before that, we have to find out how this issue came up and due to
 which change. Better if Pradeep also can have a look into this..

 +1, I have done this change locally for getting packs to verify issues. We
 need to find out root cause, and how it worked earlier. And we could not
 figure out this with recent commit mails.


Looks like non of the Carbon core guys are around. I'll have a look into
this..

Thanks,
~Isuru



 Thank you.


 Thanks,
 ~Isuru



 thank you.


 Thank you.


 Installation failed.

 Cannot complete the install because one or more required items could
 not be found.
  Software being installed: WSO2 Carbon - Transport Management Feature
 4.0.0.SNAPSHOT (org.wso2.carbon.transport.mgt.feature.group 
 4.0.0.SNAPSHOT)
  Missing requirement: org.wso2.carbon.transport.mgt.stub
 4.0.0.SNAPSHOT (org.wso2.carbon.transport.mgt.stub 4.0.0.SNAPSHOT) 
 requires
 'package javax.xml.namespace [1.0.0,2.0.0)' but it could not be found
  Cannot satisfy dependency:
   From: WSO2 Carbon - Transport Management Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.transport.mgt.feature.group 4.0.0.SNAPSHOT)
   To: org.wso2.carbon.transport.mgt.ui.feature.group [4.0.0.SNAPSHOT]
  Cannot satisfy dependency:
   From: WSO2 Carbon - Transport Management UI Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.transport.mgt.ui.feature.group 4.0.0.SNAPSHOT)
   To: org.wso2.carbon.transport.mgt.stub [4.0.0.SNAPSHOT]

 Thanks,
 Sinthuja.



 On Tue, Mar 27, 2012 at 8:05 PM, Isuru Suriarachchi 
 is...@wso2.comwrote:

 Looks like you haven't built data services ui feature.. I built AS
 after updating the entire platform about 4 hours ago and it built 
 without
 any trouble..

 ~Isuru

 On Tue, Mar 27, 2012 at 7:35 PM, Manjula Rathnayake 
 manju...@wso2.com wrote:

 Hi all,

 Have we encountered this error?

 Cannot complete the install because one or more required items
 could not be found.
  Software being installed: Data Service Hosting Feature
 4.0.0.SNAPSHOT (org.wso2.carbon.dataservices.feature.group 
 4.0.0.SNAPSHOT)
  Missing requirement: org.wso2.carbon.dataservices.fileupload.stub
 4.0.0.SNAPSHOT (org.wso2.carbon.dataservices.fileupload.stub
 4.0.0.SNAPSHOT) requires 'package javax.xml.namespace [1.0.0,2.0.0)' 
 but it
 could not be found
  Cannot satisfy dependency:
   From: Data Service Hosting Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.dataservices.feature.group 4.0.0.SNAPSHOT)
   To: org.wso2.carbon.dataservices.ui.feature.group [4.0.0.SNAPSHOT]
  Cannot satisfy dependency:
   From: Data Service Hosting UI Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.dataservices.ui.feature.group 4.0.0.SNAPSHOT)
   To: org.wso2.carbon.dataservices.fileupload.stub [4.0.0.SNAPSHOT]


 Thank you.

 --
 Manjula Rathnayaka
 Software Engineer
 WSO2, Inc.
 Mobile:+94 77 743 1987

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev





 --
 Manjula Rathnayaka
 Software Engineer
 WSO2, Inc.
 Mobile:+94 77 743 1987

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 *Kasun Gajasinghe*
 Software Engineer; WSO2 Inc.; http://wso2.com

 ,
 *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
 *linked-in: *http://lk.linkedin.com/in/gajasinghe*
 *
  *blog: **http://blog.kasunbg.org* http://blog.kasunbg.org

 *
 twitter: **http://twitter.com/kasunbg* http://twitter.com/kasunbg

 *
 *




 --
 Manjula Rathnayaka
 Software Engineer
 WSO2, Inc.
 Mobile:+94 77 743 1987

Re: [Dev] Errors when building AS

OK, here's what I found so far.

* javax.xml.namespace package is taken from the JDK in our products (see
launch.ini)
* When a package is taken from the JDK, it's version is always 0.0.0
* So all the bundles which uses javax.xml.namespace package should import
it without specifying a version or with version 0.0.0
* Up to yesterday morning, all bundles which imports this package has
imported it without specifying a version
* But now, all stubs are importing javax.xml.namespace; version=
[1.0.0,2.0.0)
* When I have a look at poms of few stubs, there are no changes there and
no stub specifically import javax.xml.namespace in their bundle plugins
* AFAIK, maven bundle plugin adds import packages into MANIFEST.MF without
a version if there's no version specified
* But on current trunk, it adds the version [1.0.0,2.0.0) due to some
reason.

Now we have to find out the reason for this. Did anyone do any change
related to maven bundle plugin? May be a version change?

Thanks,
~Isuru

On Wed, Mar 28, 2012 at 12:15 PM, Isuru Suriarachchi is...@wso2.com wrote:



 On Wed, Mar 28, 2012 at 12:00 PM, Manjula Rathnayake manju...@wso2.comwrote:



 On Wed, Mar 28, 2012 at 11:52 AM, Isuru Suriarachchi is...@wso2.comwrote:



 On Wed, Mar 28, 2012 at 11:18 AM, Manjula Rathnayake 
 manju...@wso2.comwrote:



 On Wed, Mar 28, 2012 at 11:12 AM, Kasun Gajasinghe kas...@wso2.comwrote:



 On Wed, Mar 28, 2012 at 10:27 AM, Manjula Rathnayake 
 manju...@wso2.com wrote:



 On Tue, Mar 27, 2012 at 8:18 PM, Sinthuja Ragendran 
 sinth...@wso2.com wrote:

 Hi,

 I'm also experiencing similar error mentioning '*requires 'package
 javax.xml.namespace [1.0.0,2.0.0)' but it could not be found*' when
 installing the Transport Management Feature in product-BAM2.


 Have we sorted out this issue? I checked in orbit,carbon and platform
 poms, but I could not find a place where we export javax.xml.namespace
 package.

 Any others getting this error? Or it is local to me?


 No, it's still there. I'm also facing this issue. I think Bamboo will
 start complaining sooner.


 I exported in orbit axiom bundle, I will check the build and commit if
 there is no concern regarding this change.


 But before that, we have to find out how this issue came up and due to
 which change. Better if Pradeep also can have a look into this..

 +1, I have done this change locally for getting packs to verify issues.
 We need to find out root cause, and how it worked earlier. And we could not
 figure out this with recent commit mails.


 Looks like non of the Carbon core guys are around. I'll have a look into
 this..

 Thanks,
 ~Isuru



 Thank you.


 Thanks,
 ~Isuru



 thank you.


 Thank you.


 Installation failed.

 Cannot complete the install because one or more required items could
 not be found.
  Software being installed: WSO2 Carbon - Transport Management
 Feature 4.0.0.SNAPSHOT (org.wso2.carbon.transport.mgt.feature.group
 4.0.0.SNAPSHOT)
  Missing requirement: org.wso2.carbon.transport.mgt.stub
 4.0.0.SNAPSHOT (org.wso2.carbon.transport.mgt.stub 4.0.0.SNAPSHOT) 
 requires
 'package javax.xml.namespace [1.0.0,2.0.0)' but it could not be found
  Cannot satisfy dependency:
   From: WSO2 Carbon - Transport Management Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.transport.mgt.feature.group 4.0.0.SNAPSHOT)
   To: org.wso2.carbon.transport.mgt.ui.feature.group [4.0.0.SNAPSHOT]
  Cannot satisfy dependency:
   From: WSO2 Carbon - Transport Management UI Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.transport.mgt.ui.feature.group 4.0.0.SNAPSHOT)
   To: org.wso2.carbon.transport.mgt.stub [4.0.0.SNAPSHOT]

 Thanks,
 Sinthuja.



 On Tue, Mar 27, 2012 at 8:05 PM, Isuru Suriarachchi 
 is...@wso2.comwrote:

 Looks like you haven't built data services ui feature.. I built AS
 after updating the entire platform about 4 hours ago and it built 
 without
 any trouble..

 ~Isuru

 On Tue, Mar 27, 2012 at 7:35 PM, Manjula Rathnayake 
 manju...@wso2.com wrote:

 Hi all,

 Have we encountered this error?

 Cannot complete the install because one or more required items
 could not be found.
  Software being installed: Data Service Hosting Feature
 4.0.0.SNAPSHOT (org.wso2.carbon.dataservices.feature.group 
 4.0.0.SNAPSHOT)
  Missing requirement: org.wso2.carbon.dataservices.fileupload.stub
 4.0.0.SNAPSHOT (org.wso2.carbon.dataservices.fileupload.stub
 4.0.0.SNAPSHOT) requires 'package javax.xml.namespace [1.0.0,2.0.0)' 
 but it
 could not be found
  Cannot satisfy dependency:
   From: Data Service Hosting Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.dataservices.feature.group 4.0.0.SNAPSHOT)
   To: org.wso2.carbon.dataservices.ui.feature.group
 [4.0.0.SNAPSHOT]
  Cannot satisfy dependency:
   From: Data Service Hosting UI Feature 4.0.0.SNAPSHOT
 (org.wso2.carbon.dataservices.ui.feature.group 4.0.0.SNAPSHOT)
   To: org.wso2.carbon.dataservices.fileupload.stub [4.0.0.SNAPSHOT]


 Thank you.

 --
 Manjula Rathnayaka
 Software Engineer
 WSO2, Inc.
 Mobile:+94 77 743 1987

Re: [Dev] [Commits] [Carbon-platform] svn commit r124089 - carbon/platform/trunk/service-stubs

Hi Nirmal,

Can you please tell me the exact stub which needs WSDL 2.0 for stub
generation. We have to handle this properly to handle the
javax.xml.namespace issue.

Thanks,
~Isuru

On Tue, Mar 27, 2012 at 2:16 PM, nir...@wso2.com wrote:

 Author: nirmal
 Date: Tue Mar 27 04:46:04 2012
 New Revision: 124089
 URL: http://wso2.org/svn/browse/wso2?view=revrevision=124089

 Log:
 Adding woden dependency. This is needed for WSDL2.0

 Modified:
   carbon/platform/trunk/service-stubs/pom.xml

 Modified: carbon/platform/trunk/service-stubs/pom.xml
 URL:
 http://wso2.org/svn/browse/wso2/carbon/platform/trunk/service-stubs/pom.xml?rev=124089r1=124088r2=124089view=diff

 ==
 --- carbon/platform/trunk/service-stubs/pom.xml (original)
 +++ carbon/platform/trunk/service-stubs/pom.xml Tue Mar 27 04:46:04 2012
 @@ -261,12 +261,18 @@
 artifactIdaxiom/artifactId
version${orbit.version.axiom}/version
 /dependency
 +dependency
 +groupIdorg.apache.woden.wso2/groupId
 +artifactIdwoden/artifactId
 +version${orbit.version.woden}/version
 +/dependency
/dependencies


 properties
 orbit.version.wsdl4j1.6.2.wso2v2/orbit.version.wsdl4j
 -   orbit.version.xmlschema1.4.7.wso2v1/orbit.version.xmlschema
 +   orbit.version.xmlschema1.4.7.wso2v1/orbit.version.xmlschema
 +orbit.version.woden1.0.0.M8-wso2v1/orbit.version.woden
 /properties
  /project

 ___
 Commits mailing list
 comm...@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/commits




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Errors when building AS

I just built the platform up to AS and looks like everything is fine..

Thanks,
~Isuru

On Wed, Mar 28, 2012 at 3:17 PM, Isuru Suriarachchi is...@wso2.com wrote:

 OK, found the issue and fixed it. This has been introduced by the addition
 of the woden dependency into the service stubs root pom. It introduces a
 versioned javax.xml.namespace package. So maven bundle plugin adds it's
 version into the manifest.

 Please take an svn up in platform/service-stubs/pom.xml and build. Please
 let me know if there are more issues. In the mean while I'll try to
 properly handle the woden introduciton.

 Thanks,
 ~Isuru


 On Wed, Mar 28, 2012 at 2:57 PM, Manjula Rathnayake manju...@wso2.comwrote:

 Hi,

 I was trying removing features from products and was able to build when
 following  features are not there.

 For greg -- human task, uddi, system.statistics
 For IS -- system.statistics

 thank you.

 On Wed, Mar 28, 2012 at 2:24 PM, Kathiravelu Pradeeban 
 pradee...@wso2.com wrote:



 On Wed, Mar 28, 2012 at 2:12 PM, Isuru Suriarachchi is...@wso2.comwrote:

 OK, here's what I found so far.

 * javax.xml.namespace package is taken from the JDK in our products
 (see launch.ini)
 * When a package is taken from the JDK, it's version is always 0.0.0
 * So all the bundles which uses javax.xml.namespace package should
 import it without specifying a version or with version 0.0.0
 * Up to yesterday morning, all bundles which imports this package has
 imported it without specifying a version
 * But now, all stubs are importing javax.xml.namespace; version=
 [1.0.0,2.0.0)
 * When I have a look at poms of few stubs, there are no changes there
 and no stub specifically import javax.xml.namespace in their bundle plugins
 * AFAIK, maven bundle plugin adds import packages into MANIFEST.MF
 without a version if there's no version specified
 * But on current trunk, it adds the version [1.0.0,2.0.0) due to some
 reason.

 Now we have to find out the reason for this. Did anyone do any change
 related to maven bundle plugin? May be a version change?


 I did a version declaration in carbon/orbit/trunk/pom.xml for the plugin
 to be 2.3.7, to address the maven3 warnings, in the commit 124152.
 We are looking into this to see whether that could be the case.

 Regards,
 Pradeeban.



 Thanks,
 ~Isuru

 On Wed, Mar 28, 2012 at 12:15 PM, Isuru Suriarachchi is...@wso2.comwrote:



 On Wed, Mar 28, 2012 at 12:00 PM, Manjula Rathnayake 
 manju...@wso2.com wrote:



 On Wed, Mar 28, 2012 at 11:52 AM, Isuru Suriarachchi 
 is...@wso2.comwrote:



 On Wed, Mar 28, 2012 at 11:18 AM, Manjula Rathnayake 
 manju...@wso2.com wrote:



 On Wed, Mar 28, 2012 at 11:12 AM, Kasun Gajasinghe kas...@wso2.com
  wrote:



 On Wed, Mar 28, 2012 at 10:27 AM, Manjula Rathnayake 
 manju...@wso2.com wrote:



 On Tue, Mar 27, 2012 at 8:18 PM, Sinthuja Ragendran 
 sinth...@wso2.com wrote:

 Hi,

 I'm also experiencing similar error mentioning '*requires
 'package javax.xml.namespace [1.0.0,2.0.0)' but it could not be 
 found
 *' when installing the Transport Management Feature in
 product-BAM2.


 Have we sorted out this issue? I checked in orbit,carbon and
 platform poms, but I could not find a place where we export
 javax.xml.namespace package.

 Any others getting this error? Or it is local to me?


 No, it's still there. I'm also facing this issue. I think Bamboo
 will start complaining sooner.


 I exported in orbit axiom bundle, I will check the build and commit
 if there is no concern regarding this change.


 But before that, we have to find out how this issue came up and due
 to which change. Better if Pradeep also can have a look into this..

 +1, I have done this change locally for getting packs to verify
 issues. We need to find out root cause, and how it worked earlier. And we
 could not figure out this with recent commit mails.


 Looks like non of the Carbon core guys are around. I'll have a look
 into this..

 Thanks,
 ~Isuru



 Thank you.


 Thanks,
 ~Isuru



 thank you.


 Thank you.


 Installation failed.

 Cannot complete the install because one or more required items
 could not be found.
  Software being installed: WSO2 Carbon - Transport Management
 Feature 4.0.0.SNAPSHOT (org.wso2.carbon.transport.mgt.feature.group
 4.0.0.SNAPSHOT)
  Missing requirement: org.wso2.carbon.transport.mgt.stub
 4.0.0.SNAPSHOT (org.wso2.carbon.transport.mgt.stub 4.0.0.SNAPSHOT) 
 requires
 'package javax.xml.namespace [1.0.0,2.0.0)' but it could not be 
 found
  Cannot satisfy dependency:
   From: WSO2 Carbon - Transport Management Feature
 4.0.0.SNAPSHOT (org.wso2.carbon.transport.mgt.feature.group 
 4.0.0.SNAPSHOT)
   To: org.wso2.carbon.transport.mgt.ui.feature.group
 [4.0.0.SNAPSHOT]
  Cannot satisfy dependency:
   From: WSO2 Carbon - Transport Management UI Feature
 4.0.0.SNAPSHOT (org.wso2.carbon.transport.mgt.ui.feature.group
 4.0.0.SNAPSHOT)
   To: org.wso2.carbon.transport.mgt.stub [4.0.0.SNAPSHOT]

 Thanks,
 Sinthuja.



 On Tue, Mar 27, 2012 at 8:05

Re: [Dev] [Commits] [Carbon-platform] svn commit r124089 - carbon/platform/trunk/service-stubs

On Wed, Mar 28, 2012 at 3:33 PM, Nirmal Fernando nir...@wso2.com wrote:

 Hi Isuru,

 On Wed, Mar 28, 2012 at 3:21 PM, Isuru Suriarachchi is...@wso2.comwrote:

 Hi Nirmal,

 Can you please tell me the exact stub which needs WSDL 2.0 for stub
 generation. We have to handle this properly to handle the
 javax.xml.namespace issue.


 As discussed off-line, I will put this woden dependency inside the POMs of
 required stubs and remove it from parent POM.


Ok great..



 Thanks.


 Thanks,
 ~Isuru


 On Tue, Mar 27, 2012 at 2:16 PM, nir...@wso2.com wrote:

 Author: nirmal
 Date: Tue Mar 27 04:46:04 2012
 New Revision: 124089
 URL: http://wso2.org/svn/browse/wso2?view=revrevision=124089

 Log:
 Adding woden dependency. This is needed for WSDL2.0

 Modified:
   carbon/platform/trunk/service-stubs/pom.xml

 Modified: carbon/platform/trunk/service-stubs/pom.xml
 URL:
 http://wso2.org/svn/browse/wso2/carbon/platform/trunk/service-stubs/pom.xml?rev=124089r1=124088r2=124089view=diff

 ==
 --- carbon/platform/trunk/service-stubs/pom.xml (original)
 +++ carbon/platform/trunk/service-stubs/pom.xml Tue Mar 27 04:46:04 2012
 @@ -261,12 +261,18 @@
 artifactIdaxiom/artifactId
version${orbit.version.axiom}/version
 /dependency
 +dependency
 +groupIdorg.apache.woden.wso2/groupId
 +artifactIdwoden/artifactId
 +version${orbit.version.woden}/version
 +/dependency
/dependencies


 properties
 orbit.version.wsdl4j1.6.2.wso2v2/orbit.version.wsdl4j
 -   orbit.version.xmlschema1.4.7.wso2v1/orbit.version.xmlschema
 +
 orbit.version.xmlschema1.4.7.wso2v1/orbit.version.xmlschema
 +orbit.version.woden1.0.0.M8-wso2v1/orbit.version.woden
 /properties
  /project

 ___
 Commits mailing list
 comm...@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/commits




 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




 --

 Thanks  regards,
 Nirmal

 Software Engineer- Platform Technologies Team, WSO2 Inc.
 Mobile: +94715779733
 Blog: http://nirmalfdo.blogspot.com/




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Compilation failure in stratos/usage component

:[20,50]
package org.wso2.carbon.bam.core.summary.generators does not exist

[ERROR]
/home/isuru/checkouts/wso2/trunk/new-carbon/platform/components/stratos/usage/org.wso2.carbon.usage.summary.generator/src/main/java/org/wso2/carbon/usage/summary/generator/MeteringSummaryGeneratorFactory.java:[26,56]
cannot find symbol
symbol: class SummaryGeneratorFactory
public class MeteringSummaryGeneratorFactory implements
SummaryGeneratorFactory {

[ERROR]
/home/isuru/checkouts/wso2/trunk/new-carbon/platform/components/stratos/usage/org.wso2.carbon.usage.summary.generator/src/main/java/org/wso2/carbon/usage/summary/generator/MeteringSummaryGeneratorFactory.java:[36,11]
cannot find symbol
symbol  : class SummaryGenerator
location: class
org.wso2.carbon.usage.summary.generator.MeteringSummaryGeneratorFactory

[ERROR]
/home/isuru/checkouts/wso2/trunk/new-carbon/platform/components/stratos/usage/org.wso2.carbon.usage.summary.generator/src/main/java/org/wso2/carbon/usage/summary/generator/internal/UsageSummaryGeneratorServiceComponent.java:[64,20]
cannot find symbol
symbol  : class SummaryGeneratorFactory
location: class
org.wso2.carbon.usage.summary.generator.internal.UsageSummaryGeneratorServiceComponent


-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Build failures in Gadget IDE

To start with, some maven plugin and the gadget ide stub were not added to
relevant root poms. I added those and committed.. But now I get the
following error. Looks like the stub is given a wrong version..

Please fix ASAP..


[INFO] WSO2 Carbon - Gadget IDE - UI . FAILURE [0.283s]
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 3.655s
[INFO] Finished at: Tue Mar 27 15:12:23 IST 2012
[INFO] Final Memory: 40M/482M
[INFO]

[ERROR] Failed to execute goal on project org.wso2.carbon.gadget.ide.ui:
Could not resolve dependencies for project
org.wso2.carbon:org.wso2.carbon.gadget.ide.ui:bundle:4.0.0-SNAPSHOT: The
repository system is offline but the artifact
org.wso2.carbon:org.wso2.carbon.gadget.ide.stub:jar:4.0.0-SNAPSHOT is not
available in the local repository. - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]


-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] AS build is totally busted

$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.axis2.deployment.DeploymentException: Service
[AdminManagementService] is trying expose in tranpsorts: transports
transporthttps/transport
/transports and which is/are not available in Axis2
at
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:441)
at
org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
... 43 more
Caused by: org.apache.axis2.AxisFault: Service [AdminManagementService] is
trying expose in tranpsorts: transports
transporthttps/transport
/transports and which is/are not available in Axis2
at
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:353)
... 44 more
[2012-03-27 16:04:47,064]  WARN
{org.apache.axis2.deployment.ServiceBuilder} -  Service [ ApplicationAdmin]
is trying to expose in a transport : https and which is not available in
Axis2
[2012-03-27 16:04:47,064] ERROR
{org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} -  Error building
service from bundle : Symbolic Name: org.wso2.carbon.application.mgt,Bundle
Version: 4.0.0.SNAPSHOT, ID: 130
org.apache.axis2.deployment.DeploymentException: Service [ApplicationAdmin]
is trying expose in tranpsorts: transports
transporthttps/transport
/transports and which is/are not available in Axis2
at
org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:106)
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:217)
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
at
org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:439)
at
org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:191)
at
org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
at org.e

-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] For release managers - we need packs for testing today

I fixed this build error. But the product is not testable and someone has
badly broken it..

On Tue, Mar 27, 2012 at 3:35 PM, Isuru Suriarachchi is...@wso2.com wrote:

 I locally built the platform to check the AS build failure. I found many
 build breaks and sent mails for those. Some maven modules are not added to
 root poms etc..

 Anyway now I'm building the AS product to check what has gone wrong. Will
 let you know once it is fixed..

 Thanks,
 ~Isuru


 On Tue, Mar 27, 2012 at 3:31 PM, Dimuthu Leelarathne dimut...@wso2.comwrote:

 Hi,

 AS is one of the five packs that we use for testing of kernel, so we need
 to wait for the AS. Sine we can't trigger a build for AS alone, we have to
 wait for it to be fixed then trigger the build again, for all products.

 As long as we have AS, ESB, Greg and Stratos Manager we cannot test.

 Until that we have to delay the testing.

 thanks,
 dimuthu


 On Tue, Mar 27, 2012 at 3:22 PM, Shammi Jayasinghe sha...@wso2.comwrote:

 Hi Release managers,

Since we have packs on bamboo[1], you can do smoke tests  on them.
 [1]
 http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-PRODUCTS-3/artifact
 Thanks
 Shammi


 On Fri, Mar 23, 2012 at 11:29 AM, Shammi Jayasinghe sha...@wso2.comwrote:

 Hi Samisa,

 Platform build was broken again. With this way , I am not sure
 whether we will  be able to issue packs to QA today.

 Thanks
 Shammi

 On Fri, Mar 23, 2012 at 7:27 AM, Samisa Abeysinghe sam...@wso2.comwrote:

 $subject - via Bamboo...

 Thanks,
 Samisa...

 Samisa Abeysinghe
 VP Engineering
 WSO2 Inc.
 http://wso2.com
 http://wso2.org


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Best Regards,*

 Shammi Jayasinghe*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com,
 mobile: +94 71 4493085





 --
 Best Regards,*

 Shammi Jayasinghe*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com,
 mobile: +94 71 4493085



 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Dimuthu Leelarathne
 Technical Lead

 WSO2, Inc. (http://wso2.com)
 email: dimut...@wso2.com

 Lean . Enterprise . Middleware




 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware




-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Error while running AS integration tests

Hi Dinusha,

I can see the following error while running AS integration tests. This is
printed on server startup and looks like related to transaction manager.
There are no test failures due to this. But please have a look..

[2012-03-27 18:00:01,744]  INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
 [2012-03-27 18:00:01,742]  INFO
{org.wso2.carbon.tomcat.internal.Activator} -  registering the JNDI stream
handler
[2012-03-27 18:00:01,777] ERROR
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
 javax.naming.NoInitialContextException: Need to specify class name in
environment or system property, or as an applet parameter, or in an
application resource file:  java.naming.factory.initial
[2012-03-27 18:00:01,777] ERROR
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
[2012-03-27 18:00:01,777] ERROR
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
[2012-03-27 18:00:01,777] ERROR
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325)
[2012-03-27 18:00:01,777] ERROR
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
javax.naming.InitialContext.lookup(InitialContext.java:392)
[2012-03-27 18:00:01,777] ERROR
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -   at
org.wso2.carbon.transaction.manager.TransactionManagerComponent.setUserTransaction(TransactionManagerComponent.java:106)

Thanks,
~Isuru

-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Important] New Emma based code coverage framework