On Thu, May 20, 2010 at 3:36 PM, Martin Gainty <[email protected]> wrote:
> can you file JIRA with WSDL and axis2.xml to replicate problem? > https://issues.apache.org/jira/browse/AXIS2 > Done - https://issues.apache.org/jira/browse/AXIS2-4722 Thanks, Hiranya > > > thank you > Martin Gainty > ______________________________________________ > Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité > > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene > Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte > Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht > dient lediglich dem Austausch von Informationen und entfaltet keine > rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von > E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. > > Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le > destinataire prévu, nous te demandons avec bonté que pour satisfaire informez > l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci > est interdite. Ce message sert à l'information seulement et n'aura pas > n'importe quel effet légalement obligatoire. Étant donné que les email > peuvent facilement être sujets à la manipulation, nous ne pouvons accepter > aucune responsabilité pour le contenu fourni. > > > > > > > ------------------------------ > Date: Thu, 20 May 2010 15:26:07 +0530 > Subject: Re: Questions on TCP Transport > From: [email protected] > To: [email protected] > > > BTW I came across a problem in the UDP transport when configuring the > transport globally in axis2.xml. The problem is in > the AbstractDatagramTransportListener class. The init method of this class > calls the init method of the super class. If the transport is globally > configured the super class will call the startEndpoint method. The > startEndpoint method attempts to call methods on the dispatcher object which > is not yet initialized. This leads to a NPE. Things work smoothly if the > transport was configured at service level. > > I think this is a bug that we should get fixed. > > Thanks, > Hiranya > > > On Thu, May 20, 2010 at 3:20 PM, Hiranya Jayathilaka <[email protected] > > wrote: > > > > On Thu, May 20, 2010 at 2:38 PM, Andreas Veithen < > [email protected]> wrote: > > On Thu, May 20, 2010 at 08:18, Hiranya Jayathilaka <[email protected]> > wrote: > > Hi Folks, > > I was trying to get the TCP transport working with Synapse. I was able to > > get a simple scenario working but I have a couple of questions. > > 1. It seems in order to use the TCP listener, one should enable both the > TCP > > listener and the sender in the axis2.xml. The TCPWorker specifically > checks > > for this condition. Is this check really necessary? > > 2. The transport only allows one server socket for all services. Why > don't > > we make it possible to configure the transport at service level? That way > > different services can have different server sockets. We can also use > that > > to push non-SOAP messages into services using TCP. > > I think both approaches are meaningful: > > * One socket for all services is a good approach when WS-Addressing is > used. > * One socket per service is required when WS-Addressing is not an option. > > Note that AbstractTransportListenerEx nicely supports both options. > > > Yes. I see that the UDP transport supports both approaches via the > AbstractTransportListenerEx. > > > Probably it's time to refactor the TCP transport to use > AbstractTransportListenerEx > > > +1... I will invest some time into this in the next couple of days. > > Thanks, > Hiranya > > > (which didn't exist at the time the TCP > transport was implemented). > > > If these improvements sound valid and acceptable I can provide some > patches. > > Thanks, > > Hiranya > > > > -- > > Hiranya Jayathilaka > > Senior Software Engineer; > > WSO2 Inc.; http://wso2.org > > E-mail: [email protected]; Mobile: +94 77 633 3491 > > Blog: http://techfeast-hiranya.blogspot.com > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > > > -- > Hiranya Jayathilaka > Senior Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > > > > -- > Hiranya Jayathilaka > Senior Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > ------------------------------ > Hotmail has tools for the New Busy. Search, chat and e-mail from your > inbox. Learn > more.<http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1> > -- Hiranya Jayathilaka Senior Software Engineer; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
