here's another big mess...has anyone noticed that the new ctp changed the way the web service prooxies are generated? well, if you use the traditional pathx/js, then you're in deep trouble (btw, if you use something like <atlas:ServiceReference Path="path" />, you're also in trouble).
the problem is that the path to the web service isn't added to the proxy as happened before. so, if you're using the servicereference class, you'll have to set the inlineproxy to true; if you're using html pages, you'll have to add the missing code by hand: namespace.class.path = "path to web service";
what i'd like to know is why this changed was made (yes, i believe that there must be some reasoning for this to happen)...what i really don't understandis why this wasn't announced on the atlas blogs...i'm starting to get really upset here...i mean, several bugs go unfixed and at least one breaking change is introduced withouth being documented...