Yes, wsf plugins work fine when replacing
org.wso2.wsf.ide.wtp.ext-2.3-plugin.jar in the WSAS-2.3-RC2 with the one
hosted at http://ww2.wso2.org/~sandakith/wsf_plugins_2.3_rc1/ . I just
checked and issue should be in the build.
regards
Charitha
Lahiru Sandakith wrote:
Hi All,
The build
[
https://wso2.org/jira/browse/WSAS-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed WSAS-779.
Verified and closed the bug
Spring beans class loading issue
Components: samples
Environment: winxp, jdk15,
Reporter: Charitha Kankanamge
Assignee: Afkham Azeez
Priority: Critical
Following exception thrown when running commodityquote client with scenario 14
or 15. I have used service.jks and user = bob
[
https://wso2.org/jira/browse/WSAS-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed WSAS-772.
Resolution: Fixed
Issue has been fixed by Ruchith. Verified in WSAS-2.3-RC1 and closed the bug
[
https://wso2.org/jira/browse/WSAS-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed WSAS-761.
Resolution: Fixed
Issue has been fixed by Sanka. Verified and closed the bug.
Module policies
[
https://wso2.org/jira/browse/WSAS-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed WSAS-760.
Resolution: Fixed
This issue has been fixed in the latest build. Verified and closed the bug
[
https://wso2.org/jira/browse/WSAS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed WSAS-767.
Resolution: Fixed
Verified and closed the bug
Removel of Registartion link on home page
Reporter: Charitha Kankanamge
Assignee: Saminda Wishwajith Abeyruwan
Priority: Blocker
Cannot load spring beans via WSAS management console due to the following
exception. This is a regression issue due to the spring spring-beans-2.*
version included in the latest WSAS builds
2.0.0.9, winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Afkham Azeez
Select version service
Select try it
Click on 'getVersion'
You will get 'null' as response. Firebug shows http 404 as the response.
--
This message is automatically generated by JIRA.
-
If you think
Affects Versions: 2.3
Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Rohitha Fernando
Priority: Critical
Following exception thrown when running commodityquote sample with security
scenario 2 (Sign only)
org.apache.axis2.AxisFault
: Bug
Components: core
Affects Versions: Nightly
Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Afkham Azeez
Attachments: BaseDataTypesDocLitWrappedService.aar
Following compile error occurs when generating client with default
Issue Type: Bug
Components: data-services
Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: sumedha rubasinghe
Priority: Blocker
see $summary
--
This message is automatically generated by JIRA.
-
If you think
[
https://wso2.org/jira/browse/WSAS-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed WSAS-736.
Verified and closed the bug
Policies cannot be engaged to services via WSAS
: Charitha Kankanamge
Assignee: Afkham Azeez
Priority: Blocker
Following exception thrown when invoking a service with POX security enabled.
ERROR [2008-06-02 16:09:20,531] Authentication Failure
org.apache.axis2.AxisFault: Authentication Failure
at
org.wso2
[
https://wso2.org/jira/browse/WSAS-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge reopened WSAS-681:
--
This issue occurs again in WSAS-2.3 QA builds. Reopened the bug.
Grouped by element and Rowname
[
https://wso2.org/jira/browse/WSAS-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge resolved WSAS-764.
--
Resolution: Fixed
This issue has been fixed by Saminda.
Mavenexception thrown and build fails
[
https://wso2.org/jira/browse/WSAS-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed WSAS-764.
Verified and closed the bug
Mavenexception thrown and build fails when running mvn eclipse:eclipse
[
https://wso2.org/jira/browse/WSAS-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed WSAS-756.
Verified in the latest WSAS build and closed the bug.
Access throttling has been broken
[
https://wso2.org/jira/browse/WSAS-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed WSAS-731.
Verified and closed the bug
tomcat 6.* manual configuration steps are not included in the installation
[
https://wso2.org/jira/browse/WSAS-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge resolved WSAS-739.
--
Resolution: Duplicate
Duplicates with WSAS-753
ClassNotFoundException
[
https://wso2.org/jira/browse/WSAS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed WSAS-569.
Resolution: Fixed
The related Axis2 issue has been fixed. Verified in latest WSAS and closed the
bug
[
https://wso2.org/jira/browse/WSAS-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge resolved WSAS-754.
--
Resolution: Fixed
This issue has been fixed by Sanka.
Address location is given as http
[
https://wso2.org/jira/browse/WSAS-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed WSAS-754.
Verified and closed the bug
Address location is given as http://ws.apache.org/axis; in the generated
[
https://wso2.org/jira/browse/WSAS-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed WSAS-755.
Verified and closed the bug
Node connects to cluster though clustering is disabled in axis2.xml
[
https://wso2.org/jira/browse/WSAS-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed WSAS-740.
Verified in a WSAS-2.3 QA build and closed the issue
Data service deployment fails in WSAS trunk
: WSO2 WSAS
Issue Type: Bug
Components: core
Affects Versions: Nightly
Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Sanka Samaranayake
Priority: Critical
Attachments: sec-con.JPG
Following exception thrown
Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Afkham Azeez
Priority: Minor
Following exception can be seen in WSAS startup console when removing a faulty
service. The faulty service is successfully removed from console though
Reporter: Charitha Kankanamge
Assignee: indika kumara
Priority: Blocker
Attachments: Access_throttling_service.aar
Access throttling functionality does not seem to work.
Steps to reproduce:
===
1. Deploy the attached service
2. Send more than 10
.org/jira/browse/WSAS-760
Project: WSO2 WSAS
Issue Type: Bug
Components: data-services
Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: sumedha rubasinghe
Fix For: Nightly
Following exception thrown when
Components: core
Affects Versions: Nightly
Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Afkham Azeez
Priority: Blocker
Module policies are not loaded and not shown in the module policies page.
Throttle module has a default policy
/WSAS-764
Project: WSO2 WSAS
Issue Type: Bug
Affects Versions: Nightly
Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Saminda Wishwajith Abeyruwan
1. Go to WSDLCode page
2. Enter a public wsdl uri as address and generate
://wso2.org/jira/browse/WSAS-753
Project: WSO2 WSAS
Issue Type: Bug
Affects Versions: Nightly
Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Afkham Azeez
Priority: Blocker
Attachments
[
https://wso2.org/jira/browse/WSAS-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge updated WSAS-754:
-
Attachment: sampleaxis1.wsdd
sampleaxis1service.jar
Attached axis1 resources
Components: clustering
Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Afkham Azeez
Priority: Critical
My WSAS instance gets the cluster membership even though clustering has been
disabled in asxis2.xml
--
This message
Hi Samisa,
Samisa Abeysinghe wrote:
Afkham Azeez wrote:
The changes are persisted to the WSAS DB, so when you restart it, it
will be automatically applied.
I just tried this again, but it does not seem to work. I have to
re-enable sec on the service :(
I tried with WSAS-Snapshot on
Hi Devs,
I'm experiencing the following build issue in WSAS trunk. I got the
latest updates of WSS4j, Rampart, Axis2, Axiom, WSO2 Commons/AdminUI and
built them.
Build environment is winxp/jdk15/maven 2.0.8
Downloading:
http://ws.zones.apache.org/repository2/org/wso2/wsas/wso2wsas-core/
[
https://wso2.org/jira/browse/WSAS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=16548#action_16548
]
Charitha Kankanamge commented on WSAS-745:
--
I tried with adding the following element
: servlet-edition
Affects Versions: Nightly
Environment: winxp, jdk15. websphere6.1
Reporter: Charitha Kankanamge
Assignee: Afkham Azeez
Priority: Blocker
I tried to install WSAS-snapshot(Built using Axis2-1.4) on webSphere 6.1.
However
[
https://wso2.org/jira/browse/WSAS-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed WSAS-742.
Fix Version/s: Nightly
Resolution: Fixed
Fixed by Nandana. Verified and closed the bug
Components: servlet-edition
Affects Versions: Nightly
Environment: Weblogic 9.2, ubuntu, jdk15
Reporter: Charitha Kankanamge
Assignee: Afkham Azeez
Priority: Blocker
Attachments: wl-error.JPG
'Console has received an error. Please refer
[
https://wso2.org/jira/browse/WSAS-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge updated WSAS-743:
-
Summary: Cannot log in to management console when WSAS is deployed on
Weblogic (was: Cannot log
/browse/WSAS-742
Project: WSO2 WSAS
Issue Type: Bug
Components: core
Affects Versions: Nightly
Environment: WSAS-Snapshot based on Axis2-1.4, winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Nandana Mihindukulasooriya
Issue Type: Bug
Components: Administration Console
Affects Versions: NIGHTLY
Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Ruwan Linton
Attachments: esb.JPG
See the attached screen shot. I'm getting 'Null entity
URL: https://wso2.org/jira/browse/WSAS-739
Project: WSO2 WSAS
Issue Type: Bug
Affects Versions: Nightly
Environment: winxp, jdk15, WSAS with Axis2-1.4 RC4
Reporter: Charitha Kankanamge
Assignee: Lahiru Sandakith
Priority
: Nightly
Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: sumedha rubasinghe
Priority: Blocker
Following exception throws when deploying sample data service.
INFO [2008-04-07 17:54:49,812] The DataServiceSample1.dbs service, which
Hi Hartmut,
You need to configure RepositoryLocation as follows.
RepositoryLocationhttp://localhost:8080/wso2registry/resources/wsas-repo//RepositoryLocation
regards
Charitha
Keith Chapman wrote:
The problem looks to be in the url you've used. You have used the atom
url. Charitha will have
The last updated date of WSAS nightly builds is 2008-01-24. See
http://wso2.org/downloads/wsas/nightly-build
regards
Charitha
___
Wsas-java-dev mailing list
Wsas-java-dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
[
https://wso2.org/jira/browse/COMMONS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge updated COMMONS-61:
---
Component/s: Mercury
Mercury: server fails to respond when restarting response channel
/COMMONS-62
Project: WSO2 Commons
Issue Type: Bug
Components: Mercury
Reporter: Charitha Kankanamge
Assignee: Amila Suriarachchi
In the current implementation, RM source is unable to terminate sequence by
sending a message with an empty body
Commons
Issue Type: Bug
Components: Mercury
Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Amila Suriarachchi
According to the RM Spec;
'The timing of acknowledgments can be advertised using policy and
acknowledgments can
[
https://wso2.org/jira/browse/COMMONS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed COMMONS-57.
--
Verified and closed the bug
Mercury:Server responds with 202 and client gets AxisFault when an RM
[
https://wso2.org/jira/browse/COMMONS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed COMMONS-57.
--
Verified and closed the bug
Mercury:Server responds with 202 and client gets AxisFault when an RM
Type: Bug
Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Amila Suriarachchi
Following exception thrown when invoking RMClient in which RMSequenceoffer
property has not been specified.
faultstringjava.lang.NullPointerException/faultstring
Key: COMMONS-57
URL: https://wso2.org/jira/browse/COMMONS-57
Project: WSO2 Commons
Issue Type: Bug
Components: Mercury
Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Amila Suriarachchi
As far
[
https://wso2.org/jira/browse/WSAS-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge resolved WSAS-732.
--
Assignee: Charitha Kankanamge (was: Afkham Azeez)
Resolution: Not a bug
Hi Abhilash,
You
Issue Type: Bug
Reporter: Charitha Kankanamge
Assignee: Afkham Azeez
see $summary
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more
[
http://wso2.org/jira/browse/WSAS-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge updated WSAS-723:
-
Attachment: tracer.JPG
Attached screen shot
OMException occurs when accessing Soap tracer after
WSAS
Issue Type: Bug
Affects Versions: 2.2
Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Afkham Azeez
This strange issue occurs when navigating to Soap Tracer page after invoking an
Excel or CSV data service.
Steps to reproduce
[
http://wso2.org/jira/browse/WSAS-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed WSAS-721.
Resolution: Invalid
This is invalid. Application scope was missing in the configuration. Sorry
[
http://wso2.org/jira/browse/WSAS-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge closed WSAS-722.
Resolution: Fixed
This is due to capitalizing Other in throttle type=IP. Closed the bug.
custom
/REGISTRY-225
Project: WSO2 Registry
Issue Type: Bug
Environment: winxp, jdk15,WSO2 Registry 1.0 RC2, IE 6
Reporter: Charitha Kankanamge
Assignee: Chathura Ekanayake
Please see the attached screen shot. Following JS error appears when trying to
edit
[
http://wso2.org/jira/browse/REGISTRY-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge updated REGISTRY-225:
-
Attachment: reg-js-error.JPG
Attached screen shot.
JS error appears and the existing
[
http://wso2.org/jira/browse/REGISTRY-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge reopened REGISTRY-56:
-
Reopening the bug since the issue occurs again with 1.0-RC2
same role can be assign
[
http://wso2.org/jira/browse/REGISTRY-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charitha Kankanamge updated REGISTRY-56:
Priority: Critical (was: Minor)
Increased the priority due to the fact that the issue re
URL: http://wso2.org/jira/browse/REGISTRY-220
Project: WSO2 Registry
Issue Type: Bug
Environment: derby-10.3.2.1, winxp, tomcat6, jdk15
Reporter: Charitha Kankanamge
Assignee: Chathura Ekanayake
Priority: Blocker
[ http://wso2.org/jira/browse/WSAS-721?page=all ]
Charitha Kankanamge updated WSAS-721:
-
Attachment: spring.xml
SpringBeans.jar
attached spring service resources
Problem with SpringBeans - Response is blank when invoking
Type: Bug
Environment: ubuntu
Reporter: Charitha Kankanamge
Assigned To: Chathura Ekanayake
Priority: Critical
Following error occurs when adding admin role to a non-admin user.
Could not add the user admin to the role admin. Caused by: Error adding user
Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assigned To: Afkham Azeez
Priority: Critical
I got the following exception when tried to invoke an axis1 service in REST way.
org.xml.sax.SAXException: Bad envelope tag: addition
[ http://wso2.org/jira/browse/WSAS-682?page=all ]
Charitha Kankanamge closed WSAS-682.
Data services: Invoking a data service which includes MySQL functions
--
Key
[ http://wso2.org/jira/browse/WSAS-611?page=comments#action_14969 ]
Charitha Kankanamge commented on WSAS-611:
--
Verified and closed the issue
Data services connection pooling for JDBC
[ http://wso2.org/jira/browse/WSAS-611?page=all ]
Charitha Kankanamge closed WSAS-611.
Data services connection pooling for JDBC
-
Key: WSAS-611
URL: http://wso2.org/jira
[ http://wso2.org/jira/browse/WSAS-547?page=all ]
Charitha Kankanamge closed WSAS-547.
Update tools documentation to include include information about the Console
UI tools
[ http://wso2.org/jira/browse/WSAS-559?page=all ]
Charitha Kankanamge closed WSAS-559.
Verified in WSAS-2.2-RC1 and closed the bug.
MEX: wsdl1.1 doc is not available in Sample service (HelloService3
[ http://wso2.org/jira/browse/WSAS-537?page=comments#action_14973 ]
Charitha Kankanamge commented on WSAS-537:
--
Verified and closed the bug
Broken Link in documentation - Continuous Integration
[ http://wso2.org/jira/browse/WSAS-537?page=all ]
Charitha Kankanamge closed WSAS-537.
Broken Link in documentation - Continuous Integration
-
Key: WSAS-537
URL
[ http://wso2.org/jira/browse/WSAS-430?page=all ]
Charitha Kankanamge closed WSAS-430.
Data service configuration preview is not shown
---
Key: WSAS-430
URL: http://wso2
[ http://wso2.org/jira/browse/WSAS-518?page=comments#action_14974 ]
Charitha Kankanamge commented on WSAS-518:
--
Closed the bug
Security faults are not captured by soap tracer
[ http://wso2.org/jira/browse/WSAS-502?page=comments#action_14975 ]
Charitha Kankanamge commented on WSAS-502:
--
Closed the bug
Javascriptservice tryit returns an object element
[ http://wso2.org/jira/browse/WSAS-707?page=all ]
Charitha Kankanamge closed WSAS-707.
Resolution: Fixed
This issue has been fixed by Azeez. Verified and closed the bug.
WSAS shutdown fails on tomcat
[ http://wso2.org/jira/browse/WSAS-703?page=all ]
Charitha Kankanamge closed WSAS-703.
Resolution: Fixed
This issue has been fixed by Saminda. Verified and closed the bug.
org.apache.axis2.phaseresolver.PhaseException: Did not find the desired
[ http://wso2.org/jira/browse/WSAS-704?page=all ]
Charitha Kankanamge updated WSAS-704:
-
Priority: Critical (was: Blocker)
NoClassDefFoundError: org/apache/xerces/parsers/DOMParser in WSAS servlet
distro (Tomcat 5.5.2
WSAS shutdown fails on tomcat
-
Key: WSAS-707
URL: http://wso2.org/jira/browse/WSAS-707
Project: WSO2 WSAS
Issue Type: Bug
Environment: winxp, jdk15, tomcat 6/5.5.2
Reporter: Charitha
[ http://wso2.org/jira/browse/WSAS-708?page=all ]
Charitha Kankanamge closed WSAS-708.
Resolution: Duplicate
closed the duplicate bug.
WSAS shutdown fails on tomcat
-
Key: WSAS-708
[ http://wso2.org/jira/browse/WSAS-697?page=all ]
Charitha Kankanamge closed WSAS-697.
Verified in WSAS-2.2-RC1 and closed the bug.
Data service: Row namespace cannot be updated using the wizard
MTOM sample does not have a run-client.bat
--
Key: WSAS-705
URL: http://wso2.org/jira/browse/WSAS-705
Project: WSO2 WSAS
Issue Type: Bug
Components: samples
Reporter: Charitha
[ http://wso2.org/jira/browse/WSAS-625?page=all ]
Charitha Kankanamge closed WSAS-625.
Verified in WSAS-2.2-RC1 and closed the bug
data service hotupdate does not handle re-established db connections
[ http://wso2.org/jira/browse/WSAS-681?page=all ]
Charitha Kankanamge closed WSAS-681.
Verified in WSAS-2.2-RC1 and closed the bug
Grouped by element and Rowname of the output mapping should be optional
attributes if SQL insert or update statement
[ http://wso2.org/jira/browse/WSAS-699?page=all ]
Charitha Kankanamge closed WSAS-699.
Verified in WSAS-2.2-RC1 and closed the bug
Data service UI: IN/OUT Type and Ordinal values are blank when editing input
parameters of a data service query
[ http://wso2.org/jira/browse/WSAS-646?page=all ]
Charitha Kankanamge closed WSAS-646.
Verified in WSAS-2.2-RC1 and closed the bug
Issues of the 'Add New Query' step of the data service wizard
[ http://wso2.org/jira/browse/WSAS-683?page=all ]
Charitha Kankanamge closed WSAS-683.
Verified in WSAS-2.2-RC1 and closed the bug
Data service: SQL Server JDBC driver is
com.microsoft.sqlserver.jdbc.SQLServerDriver
STS sample fails with a NPE
---
Key: WSAS-702
URL: http://wso2.org/jira/browse/WSAS-702
Project: WSO2 WSAS
Issue Type: Bug
Environment: winxp, jdk15, WSAS-2.2-RC1
Reporter: Charitha Kankanamge
[ http://wso2.org/jira/browse/WSAS-620?page=all ]
Charitha Kankanamge closed WSAS-620.
Verified in WSAS-2.2 latest builds and closed the bug.
Code gen fails if data service includes sql queries with insert or update
statements (Queries
[ http://wso2.org/jira/browse/WSAS-696?page=all ]
Charitha Kankanamge closed WSAS-696.
Verified in WSAS-2.2 latest build and closed the bug
com.ctc.wstx.exc.WstxParsingException: Non-default namespace can not map to
empty URI error occurs when
[ http://wso2.org/jira/browse/WSAS-626?page=all ]
Charitha Kankanamge closed WSAS-626.
Verified in WSAS-2.2 latest builds and closed the bug.
Issue with sql insert or update in data services
[ http://wso2.org/jira/browse/WSAS-480?page=all ]
Charitha Kankanamge closed WSAS-480.
Verified and closed the bug.
Service level parameters of the WSDD are not shown in the WSAS management
console
[ http://wso2.org/jira/browse/WSAS-673?page=all ]
Charitha Kankanamge closed WSAS-673.
Verified and closed the issue
Gracefule shutdown/restart
--
Key: WSAS-673
URL: http://wso2.org/jira
[ http://wso2.org/jira/browse/WSAS-632?page=all ]
Charitha Kankanamge closed WSAS-632.
Verified in WSAS-2.2-RC1 and closed the bug
jax-ws service invocation fails with an AxisFault
[ http://wso2.org/jira/browse/WSAS-692?page=all ]
Charitha Kankanamge closed WSAS-692.
Verified in WSAS-2.2-RC1 and closed the bug.
Shutdown and restart links are not clickble in IE7
[ http://wso2.org/jira/browse/WSAS-645?page=all ]
Charitha Kankanamge closed WSAS-645.
Verified in WSAS-2.2-RC1 and closed the bug
User is allowed to proceed through the data service wizard even if the
mandatory Data Source is not selected
[ http://wso2.org/jira/browse/WSAS-634?page=all ]
Charitha Kankanamge closed WSAS-634.
Agree with Saminda's explanation and this issue will not bother users since the
workaround is obvious. Closing the bug.
Dataservice UI: Data source Type window
501 - 600 of 648 matches
Mail list logo
