On 11/24/14, 1:07 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Then my assumption was correct. In the ant build they bundled the content >of the other modules into each opt module. I’m not sure I understand. The classes in flex-messaging-opt.jar are not in the other jars in the Ant build of BlazeDS, and the source for those classes is in the modules/opt folder. I would agree that it would be bad for a class to be in more than one jar and would be interested in figuring out a way to avoid such a situation, but I’m not seeing it here. Here’s what I see in the JAR. ~/apache-tomcat-6.0.41/webapps/samplewebapp/WEB-INF/lib$ jar -tf ~/flex-messaging-opt.jar META-INF/ META-INF/MANIFEST.MF flex/ flex/messaging/ flex/messaging/security/ flex/messaging/security/TomcatLogin.class flex/messaging/security/TomcatLoginCommand.class flex/messaging/security/TomcatLoginHolder.class flex/messaging/security/TomcatValve$TomcatLoginImpl.class flex/messaging/security/TomcatValve.class flex/messaging/vendors.properties META-INF/DEPENDENCIES META-INF/LICENSE META-INF/NOTICE META-INF/maven/ META-INF/maven/org.apache.flex.blazeds/ META-INF/maven/org.apache.flex.blazeds/flex-messaging-opt-tomcat6/ META-INF/maven/org.apache.flex.blazeds/flex-messaging-opt-tomcat6/pom.xml META-INF/maven/org.apache.flex.blazeds/flex-messaging-opt-tomcat6/pom.prope rties ~/git/flex/master/flex-blazeds$ find . -name Tom*.java ./modules/opt/src/tomcat/flex/messaging/security/Tomcat7Valve.java ./modules/opt/src/tomcat/flex/messaging/security/TomcatLogin.java ./modules/opt/src/tomcat/flex/messaging/security/TomcatLoginCommand.java ./modules/opt/src/tomcat/flex/messaging/security/TomcatLoginHolder.java ./modules/opt/src/tomcat/flex/messaging/security/TomcatValve.java ./modules/opt/src/tomcat/flex/messaging/security/TomcatValve4150.java -Alex
