Re: Problem with JMS Transport

Hi Amila, On Sat, Jan 29, 2011 at 11:45 AM, Amila Suriarachchi < amilasuriarach...@gmail.com> wrote: > if those properties are not meaning full in JMS then the correct way is to > remove from the synapse layer. Synapse does the jms transport sender > invocation. So it should not send any unrelate

Re: Problem with JMS Transport

if those properties are not meaning full in JMS then the correct way is to remove from the synapse layer. Synapse does the jms transport sender invocation. So it should not send any unrelated stuff. thanks, Amila. On Fri, Jan 28, 2011 at 10:18 AM, Hiranya Jayathilaka wrote: > Hi Folks, > > Many

Re: Enabling crypto caching in Rampart by-default

+1 thanks, Amila. On Fri, Jan 28, 2011 at 12:56 PM, Thilina Mahesh Buddhika < thilin...@gmail.com> wrote: > Hi Devs, > > At the moment, Rampart do have the support for caching of crypto objects. > Enabling crypto caching provides a significant performance gain to Rampart, > as it is not required

Re: Axis2 deployment mechanism for POJOs

Hi Pradeep, thanks for replying. I have read about pojo deployment, and I understand what you are saying. My problem is, that I find the literature on this matter, inconsistent. For example, articles describing the deployment of pojo, mention to place it in the pojo directory and if the pojo is

[jira] Assigned: (AXIS2-2477) Unusual service name/epr is presented when a pojo annotation class is deployed

[ https://issues.apache.org/jira/browse/AXIS2-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Eranga Suriarachchi reassigned AXIS2-2477: Assignee: Isuru Eranga Suriarachchi (was: Deepal Jayasinghe) > Unu

[jira] Reopened: (AXIS2-2477) Unusual service name/epr is presented when a pojo annotation class is deployed

[ https://issues.apache.org/jira/browse/AXIS2-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Eranga Suriarachchi reopened AXIS2-2477: -- > Unusual service name/epr is presented when a pojo annotation class is >

Build failed in Hudson: Axis2 #621

See Changes: [isurues] Adding an instanceof check to prevent a possible ClassCastException -- [...truncated 12739 lines...] [INFO] --- maven-deploy-plugin:2.5:deploy (default-deploy) @ axis2-webapp

Build failed in Hudson: Axis2 » Apache Axis2 - Root #621

See -- [HUDSON] Archiving to /home/hudson/hudson/jobs/Axis2/modules/org.apache.axi

Re: Enabling crypto caching in Rampart by-default

+1 Thanks & regards, -Prabath On Fri, Jan 28, 2011 at 12:56 PM, Thilina Mahesh Buddhika wrote: > Hi Devs, > At the moment, Rampart do have the support for caching of crypto objects. > Enabling crypto caching provides a significant performance gain to Rampart, > as it is not required to read the

Re: Axis2 deployment mechanism for POJOs

hi comments inline, On Thu, Jan 27, 2011 at 1:17 PM, am am wrote: > Hi Deepal thanks for reply: >>Only at the starting time or does it work runtime as well? > What do you mean? If the clients can use the service? I can see the wsdl and > I tried a service call and it works. > Also is a services.x