首页 \ 问答 \ 使用Spring.net进行xVal验证(xVal validation with Spring.net)

使用Spring.net进行xVal验证(xVal validation with Spring.net)

 我已经开始使用xVal作为ASP.Net MVC应用程序的验证框架。 我使用Spring.Net IoC容器将应用程序保存在一起。  
 我按照Steve Sanderson博客上的说明进行操作，以使服务器端验证工作正常。 但是当我尝试让客户端工作时，我得到以下运行时异常：  
Spring.Objects.Factory.NoSuchObjectDefinitionException was unhandled by user code
 
 Message =“没有定义名为'Scripts'的对象：找不到对象[Scripts]的定义”  
 我认为这是因为Site.Masterpage中包含以下代码：  
<script type="text/javascript" src="<%= ResolveUrl("~/Scripts/jquery-1.2.6.js")%>"></script>
<script type="text/javascript" src="<%= ResolveUrl("~/Scripts/jquery.validate.js")%>"></script>
<script type="text/javascript" src="<%= ResolveUrl("~/Scripts/xVal.jquery.validate.js")%>"></script>
 
 哪个尝试解决〜/ Scripts /使用Spring。  
 如何让Spring处理这个问题（即配置XML中的内容），或者我在Site.Master中更改了什么，这样就不会发生这种情况？ 

I have started to play with xVal as my validation framework for an ASP.Net MVC application. I use the Spring.Net IoC container to hold the app together.  
I have followed the instructions on Steve Sanderson's blog to get server side validation working fine. But when I try to get client side working, I get the following runtime exception: 
Spring.Objects.Factory.NoSuchObjectDefinitionException was unhandled by user code
 
Message="No object named 'Scripts' is defined : Cannot find definition for object [Scripts]" 
I presume this is because the Site.Masterpage has the following code in it: 
<script type="text/javascript" src="<%= ResolveUrl("~/Scripts/jquery-1.2.6.js")%>"></script>
<script type="text/javascript" src="<%= ResolveUrl("~/Scripts/jquery.validate.js")%>"></script>
<script type="text/javascript" src="<%= ResolveUrl("~/Scripts/xVal.jquery.validate.js")%>"></script>
 
Which is trying to resolve ~/Scripts/ using Spring.  
How do I get either Spring to cope with this (i.e. what goes into the config XML), or what do I change in Site.Master so this does not happen?

原文：https://stackoverflow.com/questions/827091

更新时间：2022-10-06 15:10

最满意答案

 两者之间确实没有区别，但编译器在涉及到浮点计算时习惯于采取一些自由度。 例如，编译器可以自由使用更高的精度来计算中间结果，但更高的结果仍然意味着不同，因此结果可能会有所不同。  
 有些编译器提供的开关总是会降低额外的精度，并将所有中间结果转换为规定的浮点数（比如64位双精度数）。 然而，这会使代码变慢。  
 在具体的数字45.33不能完全用浮点值表示（这是一个二进制表示的周期数，它将需要无限的位数）。 当乘以100这个值可能是你没有得到一个整数，但是非常接近的东西（正好在下面或正上方）。  
 int转换或铸造是使用截断和非常接近4533但以下将成为4532 ，当上述将成为4533 ; 即使这种差异非常小，比如说1E-300 。  
 为避免出现问题，请务必考虑数字精度问题。 如果你正在做一个依赖于浮点数的确切值的计算，那么你正在使用错误的工具。 

There is indeed no difference between the two, but compilers are used to take some freedom when it comes down to floating point computations. For example compilers are free to use higher precision for intermediate results of computations but higher still means different so the results may vary. 
Some compilers provide switches to always drop extra precision and convert all intermediate results to the prescribed floating point numbers (say 64bit double-precision numbers). This will make the code slower, however. 
In the specific the number 45.33 cannot be represented exactly with a floating point value (it's a periodic number when expressed in binary and it would require an infinite number of bits). When multiplying by 100 this value may be you don't get an integer, but something very close (just below or just above). 
int conversion or cast is performed using truncation and something very close to 4533 but below will become 4532, when above will become 4533; even if the difference is incredibly tiny, say 1E-300. 
To avoid having problems be sure to account for numeric accuracy problems. If you are doing a computation that depends on exact values of floating point numbers then you're using the wrong tool.

使用Spring.net进行xVal验证(xVal validation with Spring.net)

最满意答案

相关问答

如何在Java中将一个double转换为int，将其舍入？(How to cast a double to an int in Java by rounding it down?)[2021-12-21]

在C ++中将Double转换为String时的精度损失(Loss of Precision when Converting Double to String in C++)[2023-01-13]

错误：可能损失精度(Error: Possible Loss Of Precision)[2022-06-02]

直接将double结果赋值给int时的精度损失/舍入差异(Precision loss / rounding difference when directly assigning double result to an int)[2022-10-09]

精度损失(Loss of precision)[2022-08-20]

将long或BigInteger乘以double而不会损失精度(Multiply long or BigInteger by double without loss of precision)[2022-05-22]

奇怪的双舍入问题(Strange double rounding issue)[2023-02-11]

int64_t再次加倍到int64_t，精度损失(int64_t to double to int64_t again, loss of precision)[2023-05-29]

在快速分割双打时失去精度(Loss of precision when dividing doubles in swift)[2023-04-29]

精度损失？(Loss of precision?)[2023-01-25]

相关文章

最新问答