[ https://jira.jboss.org/jira/browse/JBESB-2896?page=com.atlassian.jira.plu... ] Kevin Conner reassigned JBESB-2896: ----------------------------------- Assignee: Daniel Bevenius (was: Kevin Conner) Sure, here you go. We need to do exactly the same as we do with the other dependencies, create an assert in conf/base-build.xml and have the quickstart include it. An example of this is what we currently do for remoting, see target 'assert-jbossremoting-version' and how that is used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-2896?page=com.atlassian.jira.plu... ] Daniel Bevenius commented on JBESB-2896: ---------------------------------------- I've added a target to conf/base-build.xml named assert-jbossws-identity-version which will check the version of jbossws-core.jar. But for the quickstart security_saml this is not enough as resource injection does not work with any version of jbossws on AS4.x. So I've added a target named assert-as5 and the security_saml quickstart uses that. The resource injection is only used in the "external" web service that is called by the last action in the quickstart, so saml support can still work with AS 4.x if one does not use a the org.jboss.identity.federation.core.wstrust.handlers.STSSaml20Handler. So if we add/modify other quickstarst to use saml in the ESB itself, we can use the target assert-jbossws-identity-version to detect the correct version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira