I have created a JCAM template with "setNumberRange" for an
attribute which does not work. However function such as setValue indeed works.
I believe it is a bug as I did debugged it uptill some extent. Is it a known
issue and does anybody has a workaround for this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Agreed, but given CAMV is not GA yet, it does not makes much sense making the
previous version deprecated. Also I have raised a feature request as to make
CAMV to be used such that it can be used prgramatically.
Anyhow the issue with attributes with jcam... is it a known issue as following
contraint is not getting honored:
I can confirm that this is a known issue. The setNumberRange was a late
addition to the CAM vocab and I am not sure that I implemented it for
Attributes.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
While I will be evaluating the CAMV for usage, we still are going ahead with
using JCAM due to our short timeliness. Can I request for a fix for
setNumberRange and other functions on Attributes on JCAM? I am happy to raise
a defect / support ticket for that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Please do submit a bug report, example files would be good.
I am not sure that you should be so concerned about the status of CAMV as most
OpenSource projects deliberately stay in beta for a long time until they are
genuinely happy with the code. My calling something Production does not
necessarily change the code quality. It might be better for you to nominate
the CAMV as production if it should pass your own tests.
I am nervous about changing JCAM as it has not been touched for a long time.
BTW it would be great to know a bit more about you and your project. For
example which company and application area.
Thanks
Martin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We are evaluating this for using it at one of the projects at Toyota Motor
Sales (TMS). I am happy to share the project details with you. You want me to
send it offline to you or post it here?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have created a JCAM template with "setNumberRange" for an
attribute which does not work. However function such as setValue indeed works.
I believe it is a bug as I did debugged it uptill some extent. Is it a known
issue and does anybody has a workaround for this?
Please note that JCAM is deprecated in latest release 1.6.9 of CAM Editor -
and CAMV is now the sole validation engine supported going forward.
We are moving to have CAMV to DA status and fully backward compatible with
JCAM functionally thru API.
We would appreciate help testing CAMV functionality here so that the next
release of the CAM 1.7 - then we can have CAMV to DA status for that too.
Agreed, but given CAMV is not GA yet, it does not makes much sense making the
previous version deprecated. Also I have raised a feature request as to make
CAMV to be used such that it can be used prgramatically.
Anyhow the issue with attributes with jcam... is it a known issue as following
contraint is not getting honored:
<as:constraint
action="setNumberRange(//star:Get/@maxItems,1-250)" />
Can you atleast confirn that this is a bug or I am not using the expressions
correctly? I am happy to use CAMV provided it is provide in time.
I can confirm that this is a known issue. The setNumberRange was a late
addition to the CAM vocab and I am not sure that I implemented it for
Attributes.
Thanks Robert for confirmation.
While I will be evaluating the CAMV for usage, we still are going ahead with
using JCAM due to our short timeliness. Can I request for a fix for
setNumberRange and other functions on Attributes on JCAM? I am happy to raise
a defect / support ticket for that.
Hi,
Please do submit a bug report, example files would be good.
I am not sure that you should be so concerned about the status of CAMV as most
OpenSource projects deliberately stay in beta for a long time until they are
genuinely happy with the code. My calling something Production does not
necessarily change the code quality. It might be better for you to nominate
the CAMV as production if it should pass your own tests.
I am nervous about changing JCAM as it has not been touched for a long time.
BTW it would be great to know a bit more about you and your project. For
example which company and application area.
Thanks
Martin
New version built on java 1.5 is now available.
Thanks
Martin
Hello Martin,
We are evaluating this for using it at one of the projects at Toyota Motor
Sales (TMS). I am happy to share the project details with you. You want me to
send it offline to you or post it here?