Results 1 to 4 of 4

Thread: c:import and the model

  1. #1

    Default c:import and the model

    I've got following setup:

    <form:form>
    <some widgets>
    <c:import url="b.jsp"/>
    <form:form>

    with b.jsp
    ...
    <form:input etc>....
    ...

    This triggers below error for b.jsp, which i presume is to be expected because the page doesn't have the model available as it didn't pass by the controller.

    2006-09-14 15:04:59,487 ERROR Neither Errors instance nor plain target object for bean name 'null' available as request attribute

    Is there a way around this ? My forms get quite big and complex so i'ld like to split them accross different templates. Using tiles is not an option.

    Thanks
    Jorg

  2. #2

    Default

    Jira has a ticket for this already:

    http://opensource.atlassian.com/proj...rowse/SPR-2284

  3. #3
    Join Date
    Apr 2006
    Location
    Canada
    Posts
    164

    Default

    Turning b.jsp into a tag file may solve the problem; it certainly provides a better component model than a simple include / import.

    BTW, the c:import tag is notorious for leaking file handles - be sure to review resource usage if considering using it.
    Chris Lee (blog)
    Principal Consultant
    Digital Ascent Inc.

  4. #4

    Default

    maybe comething different like

    <jsp:include page="..."/>

    or even

    <%@ include file=".."%>

    suitable?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •