for(BmAccountDtl dtl:dtlList){
   if(StringUtils.isNotBlank(dtl.getOrderNo())){
    BmOrder order = bmOrderService.getBmOrderByOrderNo(dtl.getOrderNo());
    if(StringUtils.isNotBlank(order.getBankOrderNo())){
     map.put(order.getOrderNo(), order.getBankOrderNo());

//action中给map放值 key是orderNo,value是bankOrderNo
     System.out.println("orderNo="+order.getOrderNo()+"    bankOrderNo="+order.getBankOrderNo());
    }
   }
  }

<c:set value="${bmAccountDtl.orderNo}" var="orderNo"></c:set>
          <c:forEach items="${map}" var="m">
            <c:if test="${m.key==orderNo}">
             ${m.value }  这个就是与当前orderNo对应的value值
            </c:if>
          </c:forEach>

页面上取值orderNo是变化的 

It’s important to optimize any UIView layoutSubviews method you create, as it can be frequently called, and has the potential for creating recursion (triggering a setNeedsLayout from layoutSubviews can create a loop that will grossly affect your apps performance). Layout subviews is called once per run loop on any view that has had setNeedsLayout or setNeedsDisplayWithRect: called on it. So in addition to any time you manually call these methods, it can be useful to know when the UI framework calls setNeedsLayout/setNeedsDisplay as this will trigger layoutSubviews.

For this purpose, I will define a few view relationships:

• View1 – UIView class, root view for examples
• View1.1 – UIScrollView class, subview of View1
• View1.1.1 – UIView class, subview of View1.1 (No autoresize mask)
• View1.1.2 – UIView class, another subview of View1.1 (Autoresize mask – flexible width)

I then ran the following tests.  An X means the view was layed out

From this I surmise the following:

• init does not cause layoutSubviews to be called (duh)
• addSubview causes layoutSubviews to be called on the view being added, the view it’s being added to (target view), and all the subviews of the target view
• setFrame intelligently calls layoutSubviews on the view having it’s frame set only if the size parameter of the frame is different
• scrolling a UIScrollView causes layoutSubviews to be called on the scrollView, and it’s superview
• rotating a device only calls layoutSubview on the parent view (the responding viewControllers primary view)
• removeFromSuperview – layoutSubviews is called on superview only (not show in table)

Hopefully this is helpful information for you as well.

负责人代天麒，团队共四人，到场三人，给未到的伙计做了个人照片特写播放（回成都筹建公司申请短信资质）。项目定位：基于LBS的校园社交移动应用。校园匿名调情。

代是阳光小帅哥，上台时特地戴了一顶黄色草帽，后来递给一个搭档，搭档就向台下挥帽致意，煞是好玩，他们是”草帽海贼团“。据介绍，搭档之间，熟悉和友谊的时间在7至14年不等。

给倾心的校园美女发送匿名（生成自动编号）情书，有特定的校园坐标(地图+照片分享)，几公里范围圈内各种知会，带夜宵，课堂代点名等……

随后准备去四川高校先期推广。