JBJCA-201 - New validation rules

[jeff.zhang]

We will use this thread to discuss mew validation rules.

We have these rules:

      "mcf.MCF",
      "mcf.MCFHashCode",
      "mcf.MCFEquals",
      "mcf.MCFConfigProperties",
      "mc.MC",
      "mc.MCGetMetaData",
      "ra.RANull",
      "ra.RA",
      "ra.RAHashCode",
      "ra.RAEquals",
      "ra.RAConfigProperties",
      "cf.CFNull",
      "cf.CFSerializable",
      "cf.CFReferenceable",
      "as.ASConfigProperties",
      "ao.AOConfigProperties"

[jesper.pedersen]

We should check the packaging requirements too.

For example - if .class are packaged directly inside the .RAR archive instead of inside a .JAR archive (Chapter 20.2.0.1, WARN).

[jesper.pedersen]

Another area is to check if all required classes are actually packaged in the .RAR archive - or in the container environment.

This mean that we should check for ClassNotFoundException - which is an ERROR rule.

It would be best to activate this rule in the standalone configuration first.

[jeff.zhang]

https://jira.jboss.org/jira/browse/JBJCA-262 for track this

[vickyk]

Jeff, what is the status of this task?

I am planning to work on this task, please confirm if you have not already started with it yet.

[jeff.zhang]

Hi Vicky.

We have some rules in the code base.

And I am working on using ValidationClass to replace ValidationObejct. After that I will add other rules.

Please feel free to add new rules. Rules like testcases, more are better