We currently use EJB3 and we want to implement OSS/J FM API.
We have already spent time to analyse the common API Reference implementation 1.5
and we thought that several things will certainly change a lot with EJB3 (attributeManager and globaly attributes management for exemple).

Is that correct ? and is it something scheduled regarding a RI of OSS/J APIs with J2SE5 and EJB3 ?

thanks in advance for your answer.

Best regards,

Pierre Jourdat
JDSU

Pierre,
Yes the javaEE 5 (EJB3) and javaSE  >= 5  are definitively part of the roadmap of the OSSJ initiative.
As you already seen, some anticipation work have been delivered as part of the OSS Common API 1.5 Reference Implementation. The RI validates the current OSSJ Design Guidelines, but alignment to the latest stable java EE and SE will be necessary. And yes, it will require some change in the java profiles to align and ease the implementation, but the main principles will remain.
The OSSJ Artichect group and especially myself, as OSS Common API Specification leader, already started working on this new Design Guidelines including Java and WS profiles.

Your experience in this area as well can also influence/benefit to these future directions/guidelines.
Don't hesitate to contact me in case you would like to share/submit improvement to the OSS Common API in this area.

Best Regards
Vince
OSS Common API Star Spec leader

Hi Vince ...

Is there by chance a proposed schedule as to when this effort related to moving to EJB3 might be complete?  Failing that perhaps there is a document that is available that discusses just where the changes are likely to be seen in this regard. 

Thanks,
Don

Hi,

I'm using the proposed reference implementation of the inventory API 1.5 using EJB3 to implement new entitys. Is there any news on this RI?

I don't know how to deal with characteristics and specification values. I've got a requisit of dealing with dinamic attributes. How will i presist new specification value's attribute during runtime?

Thanks,
Fernando

Hi,

The "how to implement....." question is not intented to be answered by the OSS/J specs. Implementators of the spec are free to do the implementation that suits them best as long as the specs are not violated.

A possibility (and are defninitly other/better ways to do it) for characteristics would be to have a CharacteristicsValue table that has the key of the (in  this case) specification class as foreigh key. This way you can find the charactericstic values that belong to a specification using the key of the specification.

Regards,
Gero