Some Tips on Subversion

As the first post in 2012,thought of sharing some confusing error messages which will appear while going to commit on Subversion.This blog-post will continue further as I found more such svn warnings.

1)Aborting commit- has no Ancestry information

Eg: .../rootFolder/svnProject$ svn commit .
svn: '/path/to/my/rootFolder' has no ancestry information

Reason:

While SVN checking for folder structure,if some parts of the folder tree above the folder being commited have svn metadata and some do not,this error will appear.

Solution:

Check the ancestor folders (especially above the folder reported in the commit failure message) and if you find an .svn/ folder in any of them,remove it. Alternatively, move the folder another location where it has no ancestor folder with .svn/ within it.

2) Aborting commit: remains in tree-conflict

Reason:

a) A file/directory is locally deleted but exists and is modified in the repository
b) A file/directory was locally modified but is deleted in the repository.
c) A file locally modified, but had been renamed in the repository.

Solution:

Keep a backup of the file/directory you are going to commit in other place,and delete the file/directory you tried to commit.Then take a svn up of it.

Comments

Convert an InputStream to XML

For that we can use DocumentBuilder class in java. By using the method parse(InputStream) ; A new DOM Document object will return. InputStream input; DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); DocumentBuilder parser = factory.newDocumentBuilder(); Document dc= parser.parse(input); In the above code segment,by using the created Document object,the corresponding XML file for the inputStream can be accessed. References: http://www.w3schools.com/dom/dom_intro.asp http:// download.oracle.com/javase/1.4.2/docs/api/javax/xml/parsers/DocumentBuilder.html

Concat two xml values with XSLT

The use-case described in this blog-post,is there's an WSO2 ESB node setup to proxy an incoming message to a particular back-end endpoint. Before delivering the message to the back-end endpoint,from the ESB node itself,this incoming message need to processed and change its inside xml payload format. For eg: Below is the incoming message <?xml version="1.0" encoding="UTF-8"?> <CinemaHall name="liberty"> <OwnerData> <Name>John Smith</Name> <openedDate>12/12/80</openedDate> <quality>good</quality> </OwnerData> <CinemaHallData> <rows>100</rows> <seats> <seat>50</seat> <seat>60</seat> </seats> </CinemaHallData> </CinemaHall> This message need to be changed as below; <?xml version="1.0" encoding="UTF-8"?> <CinemaHall name="liberty"...

CORS support from WSO2 API Manager 2.0.0

Cross-origin resource sharing (CORS) is a mechanism that allows restricted resources on a web page to be requested from another domain outside the domain from which the first restricted resource was served. For example, an HTML page of a web application served from http://domain-a.com makes an <img src > request for a different domain as 'domain-b.com' to get an image via an API request. For security reasons, browsers restrict cross-origin HTTP requests initiated from within scripts as in above example and only allows to make HTTP requests to its own domain. To avoid this limitation modern browsers have been used CORS standard to allow cross domain requests. Modern browsers use CORS in an API container - such as XMLHttpRequest or Fetch - to mitigate risks of cross-origin HTTP requests.Thing to note is it's not only sufficient that the browsers handle client side of cross-origin sharing,but also the servers f...

Open Space

Search This Blog