jump to navigation

svn can not check out a directory only; any work arroud? October 28, 2007

Posted by sandakith in Open Source, Tooling.

Ever needed to do a quick trivial fix to a single file, and its obvious you will never break the code. But to do that need you need to check out that particular file. But sadly svn seems can not check out a single file al0ne.  So what are our options here.. Checking out the whole directory structure that fills out your disk space (Maybe you feel negative to donate that much space) .  No..

Actually you can use :  svn checkout –non-recursive  <location>

This will only checkout the exact location contents without going into them recursively. Not the perfect solution but works for me every time.


WSO2 Oxygen Tank KB on “Set up WSO2 WSAS in Eclipse” October 27, 2007

Posted by sandakith in Eclipse, Open Source, Tooling.
add a comment

How do I Set up WSO2 WSAS in Eclipse IDE for My Development needs ?

Find the person to ‘Blame’ when code break : svn blame October 19, 2007

Posted by sandakith in Open Source, Tooling.
1 comment so far

So this is true, try svn blame and blame the person who own the line that breaks the latest code base. This will list the all the line numbers with the code owner of that line who changed it lastly with the revision number. This is really cool stuff and very much usefull.

See the example code chunk from WSO2 WSAS Project with ‘svn blame’.

5694 dims * http://www.apache.org/licenses/LICENSE-2.0
5694 dims *
5694 dims * Unless required by applicable law or agreed to in writing, software
5694 dims * distributed under the License is distributed on an “AS IS” BASIS,
5694 dims * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
5694 dims * See the License for the specific language governing permissions and
5694 dims * limitations under the License.
5352 sandakith */
5694 dims
5352 sandakith package org.wso2.wsas.installer;
5352 sandakith
5352 sandakith import java.io.File;
5352 sandakith import java.io.IOException;
5352 sandakith
5352 sandakith import org.wso2.utils.FileManipulator;
5352 sandakith import org.wso2.utils.InputReader;
5352 sandakith
5352 sandakith /**
5381 ruchith * This class contributes the WSAS Eclipse WTP Plugin installation
5352 sandakith */
5352 sandakith public class EclipseWTPPluginInstaller {
5352 sandakith
5531 azeez private static FileManipulator fileMan = new FileManipulator();
5352 sandakith
5352 sandakith private EclipseWTPPluginInstaller() {
5352 sandakith }
5352 sandakith
7290 sandakith public static void install(String wsasHome) throws InstallationException {
5352 sandakith System.out.println(“\nStarting WSAS Eclipse WTP Plugin installation…”);
5352 sandakith
5352 sandakith // Get the $WTP_HOME dir
5352 sandakith String wtpHomeDir = System.getProperty(“WTP_HOME”);
5553 sandakith System.out.println(“Please shutdown the Eclipse instance, If Already Running..”);
5352 sandakith while (wtpHomeDir == null || wtpHomeDir.trim().length() == 0) {
5352 sandakith System.out.print(“Please enter Eclipse WTP Home : “);
5352 sandakith try {
5531 azeez wtpHomeDir = InputReader.readInput();

Google search on Google? October 17, 2007

Posted by sandakith in Funny.
add a comment

Funny example of how Google would need to optimize their own page if they wanted to be found by their own search engine.

WSO2 WSAS 2.1 released October 15, 2007

Posted by sandakith in Open Source.
add a comment

The WSO2 WSAS team is pleased to announce the release of WSO2 WSAS v2.1


* This release can be downloaded from http://wso2.org/projects/wsas/java

* Maven2 binary distribution download
– Group Id : org.wso2.wsas
– Artifact Id : wso2wsas
– Version : 2.1
– Type : zip
– WSO2 Maven2 Repository URL : http://dist.wso2.org/maven2/

* Maven2 source distribution download
– Group Id : org.wso2.wsas
– Artifact Id : wso2wsas
– Version : 2.1
– Type : zip
– Classifier : src
– WSO2 Maven2 Repository URL : http://dist.wso2.org/maven2/

WSO2 WSAS v2.1 – Release Note – 10th October 2007

WSO2 WSAS v2.1 is the Enterprise ready Web services engine powered by
Apache Axis2. It is a lightweight application server for Web services
that incorporates leading open source components into a simple,
easy-to-use and highly performant package.

What is new in WSAS v2.1

* Data services support for RDBMS, MS-Excel(97-2003),CSV and JNDI data

* WSAS IDE – Eclipse IDE integration
– JAVA2WSDL form completion of all round web services cycle
through IDE.
– Inclusion of offline Web Services Archive build feature with
all resources.
– Introduction of WSAS Tools from IDE (Validators AAR/MAR, WSDL
Converter 1.1->2.0).
– All the WSAS Preferences now persist through Eclipse Preferences.
– Debug features now can be configured from preferences.
– Various Bug fixes and improvements

* Easy to use tools in the WSAS console
– WSDL2Java
– Java2WSDL
– WSDL 1.1 to WSDL 2.0 converter
– Try it for public WSDLs (1.1/2.0)
– AAR/MAR Validators

* Full support for WS-Security, WS-Trust, WS-Policy and
WS-SecureConversation and XKMS. Extended security with support for
WS-Security, WS-Trust, WS-Policy and WS-SecureConversation with
additional means for secure Web-based communications using public key
infrastructure (PKI) with XKMS. This release of WSO2 WSAS also includes
an inbuilt SecurityTokenService as defined in WS-Trust specification.

* Various bug fixes since the WSAS 2.0 release.

Known Issues

(1). POJO to Web service feature is still at an experimental stage.
One can upload jar/zip file and can create an AAR out of it.
If you uploaded a jar/zip file which has a services.xml file in its
META-INF directory, when its transformed into AAR its services.xml
will be replaced by the generated services.xml. In addition to this,
the user cannot associate any library dependencies or web content with
the generated AAR file.

Due to limitations in Axis2, method overloading is not supported, and
hence the WSDL for services where methods are overloaded cannot be
generated. Hence all WSDL based functionality related to services will
not work for such services.

(2). WS-Policy support is still in experimental stage and limited to
single port scenarios.

(3). You cannot have two different versions of the Apache Sandesha2
module in the system.

(4). A
true entry has
been added to the HTTP & HTTPS transportSenders in order to overcome
some issues with some browsers. In case of interoperability failures,
please change the value of this parameter to false and retry.

5. The ‘Try It’ feature does not work for MTOM enabled services.

6. Persistent Reliable Messaging support is experimental. Thus it might
not provide QoS expected, during every possible interruption scenario.

7. When daemon.sh is used in Gentoo kernel that runs on Intel processors
with 32/64 bit, users probably have to rename the native binaries with
the proper name as given in error message.

Reporting Problems

Issues can be reported using the public JIRA available at

Contact us

WSO2 WSAS developers can be contacted via mailing lists:
For Users : wsas-java-user@wso2.org
For Developers : wsas-java-dev@wso2.org
For details on subscriptions see http://www.wso2.org/projects/wsas/java#mail

Alternatively, questions can also be raised in the forums:
For Users : http://www.wso2.org/forum/181
For Developers : http://www.wso2.org/forum/184

Axis2 Web Services tools inside Eclipse WTP October 12, 2007

Posted by sandakith in Eclipse, Open Source, Tooling.

My article on Eclipse with Axis2 hit 13000 on WSO2 OT October 3, 2007

Posted by sandakith in Eclipse, Open Source, Tooling.
add a comment


Developing Web Services Using Apache Axis2 Eclipse Plugins – Part 1
Apache Axis2 Eclipse Plugins allow Web service developers to easily and speedily expose the … First) and Bottom-up (Code First) approach using Axis2 Eclipse Plugins. The tutorial is written for Eclipse SDK v3.2 and Axis2 Eclipse Plugin v1.3.