Wildfly target should be Java EE 7

[esteveavi]

Hi,

In chapter 2, the Wildfly target spec should be Javva EE 7 instead of Java EE6 Full Profile Certification, is it?

Regards.

[aslakknutsen]

True, WildFly targets EE7.

@ALRubinger The current link here doesn't make sense anymore, and WildFly is not 100% in Fedora yet. Any other url to point to? Not sure why we're linking to Fedora in the first place?

Not sure if previously-known as JBoss Application Server 7 is correct either. Previously known as JBoss Application Server.. ?

[ALRubinger]

@aslakknutsen WildFly supports EE7 as of 8.0.0.CR1; could we update the app to use this version instead, and then in turn update book references to be in-line w/ EE-7? Unless we take that step, we're really only OK to claim EE6 compliance.

[aslakknutsen]

@ALRubinger the section in question is about WildFly, not CED. If our app is EE6 compliant doesn't change that WildFly is compliant with EE7.

I believe I tried a CR1 upgrade before, but some of the mail stuff failed for 'some reason'. I'll reinvestigate.

[ALRubinger]

The version of WildFly we're using is not EE6 compliant, however. :)

[ALRubinger]

s/EE6/EE7 above. :)

[aslakknutsen]

@ALRubinger it's not EE6 certified either :) And we're not talking about a specific v. And even CR1 is not EE7 certified(Passing the TCK is not enough).

I think we should change that line to say something like targets ee7.

That CED targets EE 6 should be in here somewhere; https://github.com/arquillian/continuous-enterprise-development/blob/master/Chapter04-RequirementsAndExampleApplication.asciidoc

[ALRubinger]

+1 on "targets EE7". Odd, it used to be that promoting TCK passing was prohibited until certification went through.

I think these changes make sense. Assign back to me. We'll have to make these changes both here and manually via the production team. I've added tag 1.0.0-beta-1 to act as the diff for us before we pushed to prod.

[aslakknutsen]

https://jcp.org/en/procedures/jcp2_9

1.4 COMPATIBILITY TESTING The Spec Lead is responsible for defining the process whereby the TCK is used to certify implementations of the JSR as compatible. The Maintenance Lead must submit to the PMO at least quarterly a list of all implementations that have been certified as compatible and that have been released publicly or commercially. The PMO will publish this information on the JCP Website. If the Spec Lead submits the information in the form of a pointer to an already published list the PMO may choose simply to reference that list rather than duplicate it.

TCK license terms must permit implementors to freely and publicly discuss the testing process and detailed TCK test results with all interested parties.

The world moves forward :)

[ALRubinger]

https://twitter.com/WildFlyAS/status/422656055118532608

pwned. :D

[aslakknutsen]

lol.. well there you go :)