Have to admit that I have never used the opt packages. BlazeDS itself is in the 4 packages core, common, proxy and remoting. The opt packages seem to be some sort of convenience classes for linking the tomcat4 login mechanism with that of BlazeDS. I disabled those modules for "jrun", "oracle", "weblogic" and "websphere" as you need the core libs of these containers in order to build and these are not available publically.
The WAR was probably the tournkey option, that outputs a war archive to immediate experimenting. I think this must have been part of that insanely old BlazeDS release. If we need it we would probably have to re-implement it. Regarding the flex-rds-server.jar ... I have never heard of this nor have I ever had to use it. Could this eventually be a leftover from the livecycle server which had the "realtime" stuff in it? But I thought the Flex SDK only relied on the flex-messageing-commons or core and not the rest ... I never even knew that this rds-jar existed. Chris ________________________________________ Von: Alex Harui <aha...@adobe.com> Gesendet: Freitag, 21. November 2014 02:53 An: dev@flex.apache.org Betreff: Re: Updated Flex-SDK to use apache-flex blazeds :-) I spent the afternoon trying to get Apache Flex BlazeDS to work with Adobe Flash Builder 4.7 and Apache Flex SDK 4.13.0. I know very little about BlazeDS. My goal was to follow this article [1] I eventually got it to work, but I hit 3 things: 1) Neither the Ant build on apacheflexbuilds nor the Maven build on builds.a.o seems to be creating a .WAR file. Do we need to do that? 2) The donated code does not contain the source or binary for flex-rds-server.jar. I could not find the source in the Adobe repos. It isn’t even in the Flash Builder code base. It is used for Flash Builder integration. I don’t know if the other IDEs use it or not. You don’t need it to build projects, just for the Data stuff in FB. Question: Do we want to own it? I think it might be an Eclipse plug-in. Can we ship an Apache Flex BlazeDS without it? 3) The artifacts on builds.a.o is not creating jars in modules/opt which I seemed to need to get BlazeDS to start up in Tomcat 6. Does that make sense? The Ant build on apacheflexbuilds does create modules/opt jars in its artifacts. To me, issues 1 and 3 are related to the discussion of how to do Maven builds on builds.a.o. Should the build.a.o scripts just re-package artifacts from apacheflexbuilds? Does that even make sense? Are WAR files typical Maven artifacts? Should only the Ant build create the WAR file? -Alex [1] http://www.adobe.com/devnet/flex/articles/flashbuilder_blazeds.html
