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

Passing end-user details from client to real backend endpoint via JWT token

In real-world business system,WSO2 API Manager useful on exposing company APIs, in a secured and controlled manner with the features provided by APIManager as; OAuth support [To secure API invocations] Throttling support [To control API invocations] Monitoring support [To track API usage] More technically what happening is when a user sends a particular API request,it will goes to WSO2 APIManager node and from there,the request will route to the real implemented back-end endpoint of the particular API and get back the response and returned it to the API invoked user. There can be a use-case,that this back-end endpoint may expect the details of API invoked user as to pass those details to some internal company usage as; Additional authentication/authorization Track usage data from an internal system. So how to support above requirement from WSO2 AM. There comes the use of JSON Web Token[JWT] implementation done inside WSO2 AM. JWT is a means of representing claims to...

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"...

How to rollback/commit processing messages from WSO2 ESB when enabled JMS transaction

This blog post describes the below use-case where WSO2 ESB 4.6.0 act as the intermediate channel in-between two JMS queues. The Use-case First messages will be de-queue to a proxy service deployed in WSO2 ESB from an queue in ActiveMQ message broker. Then inside ESB,the incoming messages will undergo with some message mediation flow and then the message will be send to another JMS queue deployed in JBoss server. Inside the ESB,following failures could be happen; a) Failures during message mediation process failure inside ESB [for example if you use dbreportmediator/lookup mediator inside mediation flow,some times failures can happen due to database connection failures] b) Message sending failure,due to endpoint is unavailability.[For example,the JBoss ...

Open Space

Search This Blog