Hi Maciek, Yes if the list of processes grows then the wsdl will have new operations too. There will be some changes anyway. But that's not resolve the problem...
Then i want to use BPEL because of existing interface to design it (NetBean/eclipse for example). When i said that list can grows... i mean that i want to give a solution that can be upgraded easily, not by created a full smx assembly with an http and ode service unit...perhaps is that i will need to do :'( Peoples that will grow up that list are developers but i would like that they don't have lot's of work to do it... Maciek Prochniak wrote: > > But if process list grows with time, then also wsdl would have to > change? So you'll need some changes anyway? > > Anyway, if you're using smx I think it's really best solution to use > e.g. camel, which is (contrary to bpel ;)) perfectly suited for such > purposes > > br, > maciek > -- View this message in context: http://old.nabble.com/One-Wsdl-and-one-endpoint-for-multiple-BPEL-processes-tp28080175p28092988.html Sent from the Apache Ode User mailing list archive at Nabble.com.
