• Post Reply Bookmark Topic Watch Topic
  • New Topic

Issues in dynamically configuring rampart configuration with axis2

 
Yogendran Gopalakrishnan
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi all,

My first post and am very glad to be here. I am currently working on a requirement where I need to be able to dynamically add rampart configuration to a service built using axis2. We ship out our service to many customers and they like to have customized certificates in custom paths and they need to be able to provide this information in a properties file, which I read and add the rampart configuration dynamically. I see that rampart supports dynamic configuration at both the client and the server sides. I first wish to try at the service side and then the client later on. One site caught my attention which is --> http://blog.rampartfaq.com/2009/08/can-we-avoid-duplicating-crypto-info.html

I have done exactly as mentioned in the site. I have configured a rampartconfig call back class and mentioned it in my services.xml as below,




==========================================================================================
==========================================================================================

My com.my.my1.servlet.AmandaRampartConfigCallbackHandlerImpl class is as below,



As you can see, I have implemented the RampartConfigCallbackHandler and in the implemented method "update", I have put out a simple sysout. The problem is that my call back class is not at all called. I am at a loss to understand why this is so. While I try to resolve this issue, anyone with knowledge on this, please review and let me know where I have gone wrong. The sample code here has a definition similar to mine, but they have had no issues in getting their callback class called. Their services.xml does look a lot different than mine (mine being axis2 perhaps?)

Any assistance will be appreciated.

 
Yogendran Gopalakrishnan
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I was able to resolve this, basically I did not have a policy.xml definition in my services.xml as a result of which rampart was not able to call my callback class. Sorry been very busy, I will post more details next week with code samples so that it is of help to others who may run into a similar issue.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!