Building Project

[ccunningham]

Hi,

We are working on a large scale distributed media project and are looking at replacing the sun xacml implementation we currently use with the heras-af implementation. However, we are facing a number of problems that I am hoping you will be able to help us with.

The main problem we face is that we are unable to build the project from the SVN checkout (Revision 1183) due to missing artefacts.
Since there are no complete build instructions that I can find (apart from those included at in the thesis entitled HERAS-AF XACML 2.0 Implentation), we installed maven and tried to build each of the projects in turn. As there were missing artefacts we added the herasaf snapshots/repositories to our maven root configuration file (settings.xml) and were more successful in the number of projects that would compile - however, these all failed on testing. Are there some configuration files missing from the SVN repository? If we browse the maven repository using the artifactory browser, some of these artefacts are present. Are there more complete build instructions available?

Additionally, there is a dependency on using postgresql as a backend store in the project - how easy it would be to swap this out? We have our own more generic way of storing and persisting policies which we would like to continue to use.

Regards,

Christina

[René Eggenschwiler]

Hi Christina,

We didn't experience problems with artefact dependencies so far. You mention a very interesting behaviour.
We only used standard libraries and open source libraries which are all available in the community.
It could be that we added some libs to our Maven repository because they were not in the Maven Repo available.
But we didn't use any propretiary libs.
From that point of view you should be easily able to resolve our dependencies and build the project.

Important is only that you use only our XACML implementation (which can be found at http://svn.herasaf.org/herasaf-xacml/*).
If you check out all modules of it...
herasaf-xacml, herasaf-xacml-assembly, herasaf-xacml-conformancetests, herasaf-xacml-core, herasaf-xacml-evaluatablepreprocess, herasaf-xacml-integrationtests, herasaf-xacml-locator, herasaf-xacml-pdp, herasaf-xacml-persistence, herasaf-xacml-referenceloader and herasaf-xacml-stresstests
...you should be able to build by running "mvn clean install" on the module "herasaf-xacml". It will then build all submodules too.

For the other components (PAP, PEP etc..) we can not garuantee yet that all libs are completely resolvable.
But the XACML implementation should build by itself.
Missing artefacts could be e.g. libs from Sun (javax.*) because they need to be downloaded manually.

If you still experience difficulties with our dependencies, we would be happy to help you.
To be able to reproduce your build problems it would be necessary for us to see your Maven output (to check which artefacts are missing).
Maybe you would also send us your Maven settings and pom files.

Regards,
René

[René Eggenschwiler]

Hi Christina,

I answered your second question about the database in: http://forum.herasaf.org/index.php/topic,33.0.html

Regards,
René

[ccunningham]

Hi René,

I have tried to build the herasaf-xacml project as before - the build fails during testing (I have supplied the -P disableALL switch which doesn't turn testing off) and therefore the jar file isn't built. I have attached the output of the build and the maven settings.xml file.

I have found the binaries on the artifactory respository browser so I will use those for now.

Regards,

Christina

[René Eggenschwiler]

Hi Christina,

This is weird. The test which is failing is: testWrongInput(org.herasaf.xacml.core.dataTypeAttribute.impl.test.TestTimeDataTypeAttribute) in herasaf-core.

I checked our code and I don't see anything suspicious. This test runs fine on my maschine and our build and test systems.

That test doesn't use any DB nor Spring.

Can you please provide us the Junit and surefire report for that test?

We will  have a detailed look at it.

Unfortunately I'm going to holiday this afternoon. I'll be back next week.
But Florian will have a look at your issues. I already informed him.

Regards,
René

[ccunningham]

Hi,

Testing result files attached.

If you need any other information, just let me know.

Thanks,


Christina

[Florian Huonder]

Hi Christina,

It seems at first glance that this is a environment-depending failure because of our Time class (http://svn.herasaf.org/herasaf-xacml/trunk/herasaf-xacml-core/src/main/java/org/herasaf/xacml/core/types/Time.java).

Could you provide me with some information about your environment (Maven-Version, Operating System, Java Version, ...)?

I try to have a look at it as soon as possible (Probably tomorrow).

Regards,
Florian

[ccunningham]

Hi Florian,

Information as requested:

Maven version: 2.0.9
Java version: 1.6.0_14
OS name: "linux" version: "2.6.28-13-generic" arch: "i386" Family: "unix" (kubuntu 9.04)

I had wondered about this as it seems that most people posting to the forums are using Windows OS.

Thanks,


Christina

[Florian Huonder]

Hi Christina,

Unfortunately our build server runs on windows. We are not ready with testing on a unix-based system.
Further the implementation is based on Java 1.5.

I assume that the reason for your build failure is because of a different implementation of the used XMLGregorianCalendar in unix or Java 1.6.
Maybe it accepts more calendar-string-formats then the one in Java 1.5 (or Windows).

I had also a look at the regular expression that checks for validity of the strings (in the Time (org.herasaf.xacml.core.types.Time.java) datatype) regarding the XACML specification (that says it should be a http://www.w3.org/2001/XMLSchema#time type), for me it looks ok.

I suggest you to test with Java 1.5 first. If that works, fine. If the problem occurs because of Windows/Unix, then I must have a deeper look into it.

Let me know your results.

Regards,
Florian

[ccunningham]

Hi Florian,

Yes, that seems to build against java 1.5.

Regards,


Christina