Aggregator

From:Sumedha Rubasinghe (sume...@wso2.com)List:org.wso2.architecture

Ratha, Let's have chat on this tomorrow morning. will sleep on this... /sumedha

On Thu, Sep 2, 2010 at 8:34 PM, ratha <rat...@wso2.com> wrote:

Hi all,

This is how BAM database is designed.. (# diagram) Currently we are able to track service stats using ActivityID(activity-->message-->operation-->service). For the message tracing requirement we need to track ESB messages too. ie: we need to map messages with sequence/endpoint/proxy. With the current design it is not possible, since we have FK (foreign key ) pointing only the operation table and activity table. How do we need to address this? Currently all three mediation data are stored in a single table as a key value pair(SERVER_USER_DATA table) and we have separate dimension tables(hour/month..) for each mediation type. So , we fetch data from the common table to fill those dimension tables. _ Difficulties_

* We can not introduce a new column (FK) with existing message table to point mediation data.( There is no separate tables for Proxy, Endpoint,Sequence. All are stored in a common table as mentioned above. And when we try to save WSAS messages it wont be possible)

bam-db

Please share your thoughts..It is urgent..

Thanks. -Ratha.

_______________________________________________ Architecture mailing list Arch...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

From:ratha (rat...@wso2.com)List:org.wso2.architectureAttachments:Diagram1.png - 19k

Forgot to attach diagram.. ratha wrote:

Hi all,

This is how BAM database is designed.. (# diagram) Currently we are able to track service stats using ActivityID(activity-->message-->operation-->service). For the message tracing requirement we need to track ESB messages too. ie: we need to map messages with sequence/endpoint/proxy. With the current design it is not possible, since we have FK (foreign key ) pointing only the operation table and activity table. How do we need to address this? Currently all three mediation data are stored in a single table as a key value pair(SERVER_USER_DATA table) and we have separate dimension tables(hour/month..) for each mediation type. So , we fetch data from the common table to fill those dimension tables. _ Difficulties_

* We can not introduce a new column (FK) with existing message table to point mediation data.( There is no separate tables for Proxy, Endpoint,Sequence. All are stored in a common table as mentioned above. And when we try to save WSAS messages it wont be possible)

bam-db

Please share your thoughts..It is urgent..

Thanks. -Ratha.

_______________________________________________ Architecture mailing list Arch...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

From:ratha (rat...@wso2.com)List:org.wso2.architecture

Hi all,

This is how BAM database is designed.. (# diagram) Currently we are able to track service stats using ActivityID(activity-->message-->operation-->service). For the message tracing requirement we need to track ESB messages too. ie: we need to map messages with sequence/endpoint/proxy. With the current design it is not possible, since we have FK (foreign key ) pointing only the operation table and activity table. How do we need to address this? Currently all three mediation data are stored in a single table as a key value pair(SERVER_USER_DATA table) and we have separate dimension tables(hour/month..) for each mediation type. So , we fetch data from the common table to fill those dimension tables. _ Difficulties_

* We can not introduce a new column (FK) with existing message table to point mediation data.( There is no separate tables for Proxy, Endpoint,Sequence. All are stored in a common table as mentioned above. And when we try to save WSAS messages it wont be possible)

bam-db

Please share your thoughts..It is urgent..

Thanks. -Ratha.

_______________________________________________ Architecture mailing list Arch...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Declare servlet.api as provided Improvement Normal Open Unresolved Sanjaya Karunasena David Karlsen Fri, 20 Aug 2010 12:12:59 +0000 Fri, 20 Aug 2010 12:12:59 +0000 0 Estimated Complexity Novice Severity Major

java.lang.NoSuchMethodError: org.apache.axis2.deployment.util.PhasesInfo.setINPhases(Ljava/util/ArrayList;)V Bug High Open Unresolved Sanjaya Karunasena David Karlsen Fri, 20 Aug 2010 09:55:54 +0000 Fri, 20 Aug 2010 11:51:24 +0000 0 Current head seems to work fine with axis2 1.5.1 - any plans to release it? Estimated Complexity Novice Severity Blocker

Be more informative when lacking configuration Improvement Normal Open Unresolved Amila Suriarachchi David J. M. Karlsen Mon, 1 Mar 2010 17:27:16 +0000 Mon, 8 Mar 2010 06:18:00 +0000 0 0 minutes 0 minutes what is the missing file?

I tried with removing applicationContext.xml and axis2Config.xml
it gives a proper exception.

nested exception is java.io.FileNotFoundException: Could not open ServletContext resource [/WEB-INF/axis2Config.xml]
Caused by: java.io.FileNotFoundException: Could not open ServletContext resource [/WEB-INF/axis2Config.xml]
at org.springframework.web.context.support.ServletContextResource.getInputStream(ServletContextResource.java:99)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:307)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:290)

Add support to use custom wsdl file from META-INF (similar to org.apache.axis2.deployment.DeploymentEngine.DeploymentEngine) Improvement Normal Open Unresolved Sanjaya Karunasena Ruben Suarez Alvarez Thu, 17 Dec 2009 13:10:07 +0000 Thu, 17 Dec 2009 14:01:37 +0000 0 I forgot to specify SpringWebServiceBuilder patched is from wsf-spring version 1.5 Estimated Complexity Moderate Severity Minor

org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxParsingException: Unexpected close tag ; expected Bug Normal Open Unresolved Sanjaya Karunasena Mazhar PAtel Sun, 18 Oct 2009 09:50:45 +0000 Sun, 18 Oct 2009 09:50:45 +0000 0 5 hours 5 hours Estimated Complexity Moderate Severity Major

Using Custom WSDL files with Spring web services Improvement Low Open Unresolved Sanjaya Karunasena Eranga Jayasundera Sun, 16 Mar 2008 03:40:59 +0000 Thu, 17 Dec 2009 15:05:58 +0000 0 Could you please describe this patch bit more?

So this is not really a custom WSDL, it is to show the original WSDL as the developer wish to do so. Ability to auto generate the WSDL from the interface is just a feature we have inherited from Axis2.
Yes, but (as far as I know) currently WSF/Spring does not allow developers to show the original WSDL if they wish to do so. This patch gives that capability. You can see an alternative aproach here: https://wso2.org/jira/browse/WSFSPRING-4 Attachment License I agree to grant a license to WSO2 for this work for inclusion in WSO2 works as per the WSO2 Contributor License Agreement and the Apache License 2.0

Excluding Selected Operations Improvement Low Resolved Fixed Tharindu Mathew Eranga Jayasundera Tue, 11 Mar 2008 09:08:53 +0000 Thu, 13 Mar 2008 07:43:11 +0000 Thu, 13 Mar 2008 07:43:11 +0000 0 Patch Commited successfully. Thank you for the patch Eranga. Attachment License I agree to grant a license to WSO2 for this work for inclusion in WSO2 works as per the WSO2 Contributor License Agreement and the Apache License 2.0

Add support for ruby 1.9 Improvement Normal Open Unresolved Dimuthu Gamage Geoff Jacobsen Wed, 2 Dec 2009 04:13:27 +0000 Wed, 2 Dec 2009 04:13:27 +0000 1.0.0 Alpha Current (nightly) 1.0.0 Beta 1.0.0 RC1 1.0.0 Build System / Linux Build System / Windows 0 Estimated Complexity Moderate Severity Major

proxy operations for WSDL do not work Bug High Resolved Fixed Dimuthu Gamage Igor DOlinsek Mon, 7 Sep 2009 14:45:26 +0000 Tue, 8 Sep 2009 08:16:05 +0000 Tue, 8 Sep 2009 08:16:05 +0000 0 Hi,
The xslts are not working correctly in your ruby installation. What is the ruby version you are using?

Dimuthu Dimuthu,

thanks for your hint!

I am running ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32].

Indeed I was using an outdated version of libxslt.dll and when I placed the libxslt.dll 1.1.24 in the wsf_c/lib directory the wsdl 2.0 sample executed successfully (client has got the expected results from the server).

However, I have noted some error messages in both server and client logfiles:

Sever log:
-----------------

[Tue Sep 08 09:27:28 2009] [error] ..\..\util\src\class_loader.c(161) dlerror reason: Something went wrong loading the DLL. If you happen to see this message, please note that getting the exact error form Windows is a TODO. And if possible please help fix it. :)
[Tue Sep 08 09:27:28 2009] [error] ..\..\util\src\class_loader.c(161) dlerror reason: Something went wrong loading the DLL. If you happen to see this message, please note that getting the exact error form Windows is a TODO. And if possibleplease help fix it. :)

client log:
-----------------
[Tue Sep 08 09:29:11 2009] [error] ..\..\util\src\class_loader.c(161) dlerror reason: Something went wrong loading the DLL. If you happen to see this message, please note that getting the exact error form Windows is a TODO. And if possible
please help fix it. :)
[Tue Sep 08 09:29:11 2009] [error] ..\..\util\src\class_loader.c(161) dlerror reason: Something went wrong loading the DLL. If you happen to see this message, please note that getting the exact error form Windows is a TODO. And if possibleplease help fix it. :)
[Tue Sep 08 09:29:11 2009] [error] ..\..\axiom\src\om\om_element.c(452) node or namespace or om_element is NULL


Am I still missing something?
I have the iconv.dll, zlib1.dll, libxml2.dll in my wsf_c/lib path.

Regards
Igor

This was a known issue in loading windows dlls in axis2/c 1.3 which is used in wsf/ruby 1.1.0. This was fixed in the latest axis2/c, (but wsf/ruby needed to alter to be compatible with axis2/c changes).

You can ignore that entry in the log and continue. So I'm marking this as fixed.

Dimuthu Estimated Complexity Moderate Severity Blocker

Remove Hardcoding to Rails::CGIRequest Improvement High Open Unresolved Dimuthu Gamage Jürgen Mangler Sun, 18 Jan 2009 22:22:52 +0000 Sun, 18 Jan 2009 22:22:52 +0000 Current (nightly) WSService 0 4 hours 4 hours Attachment License I agree to grant a license to WSO2 for this work for inclusion in WSO2 works as per the WSO2 Contributor License Agreement and the Apache License 2.0 Estimated Complexity Novice Severity Major

wsdl11to20.xsl10.xsl -> wsdl2sig.xslt Bug Normal Open Unresolved Dimuthu Gamage Jürgen Mangler Mon, 12 Jan 2009 21:12:58 +0000 Mon, 12 Jan 2009 21:12:58 +0000 Current (nightly) 0 Estimated Complexity Moderate Severity Major

Updating the HTTP Request handling code to the new WSF/C SVN changes New Feature Normal Open Unresolved Dimuthu Gamage Dimuthu Gamage Mon, 5 Jan 2009 09:50:44 +0000 Mon, 5 Jan 2009 09:50:44 +0000 0 Estimated Complexity Moderate Severity Major

SAMLToken Support New Feature Normal Open Unresolved Dimuthu Gamage Timo Benk Mon, 13 Oct 2008 07:58:09 +0000 Mon, 13 Oct 2008 07:58:09 +0000 0 Estimated Complexity Moderate Severity Major

Setting custom SOAP Header New Feature Normal Open Unresolved Dimuthu Gamage Timo Benk Mon, 13 Oct 2008 07:54:29 +0000 Mon, 13 Oct 2008 07:54:29 +0000 0 Estimated Complexity Moderate Severity Major

guththila utf-8 problem in ruby Bug Normal Open Unresolved Nandika Jayawardana Mats Staffansson Thu, 18 Sep 2008 09:28:21 +0000 Fri, 12 Jun 2009 08:37:54 +0000 1.0.0 Build System / Linux 0 Estimated Complexity Moderate

Introducing 'CACert' option for the WSClient Improvement Normal Open Unresolved Dimuthu Gamage Dimuthu Gamage Fri, 15 Aug 2008 09:02:16 +0000 Fri, 15 Aug 2008 09:02:16 +0000 0 Estimated Complexity Moderate

Extend the client API to get and set http headers Improvement Normal Open Unresolved Dimuthu Gamage Dimuthu Gamage Fri, 15 Aug 2008 08:57:12 +0000 Fri, 15 Aug 2008 08:57:12 +0000 Current (nightly) Current (nightly) 0 Estimated Complexity Moderate