Results 1 to 6 of 6

Thread: Web-ContextParams: webAppRootKey, SpringExtender-Attribute

  1. #1
    Join Date
    Oct 2008
    Posts
    0

    Default Web-ContextParams: webAppRootKey, SpringExtender-Attribute

    Hello,

    Petclinic example has some manifest headers which I don't understand:

    Web-ContextParams: webAppRootKey;param-value:="petclinic.root"
    SpringExtender-Attribute: Petclinic

    How do they work during bundle initialization?

    Which values should I put there when I have two Web modules in my PAR,
    one of which imports another.

    (I have problems with this case, so want to clarify all configurations first)

    --
    Olex

  2. #2
    Join Date
    Oct 2008
    Posts
    493

    Default Web-ContextParams: webAppRootKey, SpringExtender-Attribute

    Hi Olex,

    Unfortunately the sample is a little bit out of step with the Platform and it's using incorrect manifest headers in its Web module. A new version of the Petclinic sample that corrects this will be published soon.

    Andy.

  3. #3
    Join Date
    Oct 2008
    Posts
    0

    Default Web-ContextParams: webAppRootKey, SpringExtender-Attribute

    Ok, thank you.

    Waiting for new sample

    Olex

  4. #4
    Join Date
    Oct 2008
    Posts
    493

    Default Web-ContextParams: webAppRootKey, SpringExtender-Attribute

    Olex,

    Rather than waiting for the new sample to be published here's a copy of the Petclinic Web module's MANIFEST.MF that's been trimmed down to only what's needed:

    Manifest-Version: 1.0
    Bundle-ManifestVersion: 2
    Bundle-SymbolicName: org.springframework.petclinic.web
    Bundle-Name: Petclinic Sample Web Module
    Bundle-Vendor: SpringSource Inc.
    Import-Library: org.springframework.spring;version="[2.5,2.6)"
    Import-Bundle: com.springsource.org.apache.taglibs.standard;versi on="[1.1.2,1.1.2]"
    Import-Package: org.springframework.petclinic.domain,
    org.springframework.petclinic.repository
    Platform-ModuleType: Web
    Web-ContextPath: petclinic
    Web-DispatcherServletUrlPatterns: *.do

    The SpringExtender-Attribute header is an old header that's not needed/supported so this has been removed.
    The Web-ContextParams header wasn't needed in this case, so it's been removed too. It allows you to specify the equivalent of web.xml's <context-param> entries. For example a manifest header of:

    Web-ContextParams: javax.faces.DEFAULT_SUFFIX;param-value:=".xhtml",foo;param-value:="bar"

    Is equivalent to the following in web.xml:

    <context-param>
    <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
    <param-value>.xhtml</param-value>
    </context-param>
    <context-param>
    <param-name>foo</param-name>
    <param-value>bar</param-value>
    </context-param>

    I hope this helps. Let us know if you have any further questions.

    Andy

  5. #5
    Join Date
    Oct 2008
    Posts
    0

    Default Web-ContextParams: webAppRootKey, SpringExtender-Attribute

    Thank you, Andy

    I cleaned up manifests, but it seems like a bug exists
    https://issuetracker.springsource.com/browse/PLATFORM-30

    BR, Olex

  6. #6
    Join Date
    Oct 2008
    Posts
    0

    Default Web-ContextParams: webAppRootKey, SpringExtender-Attribute

    *I think* that I have a similar issue ...

Posting Permissions

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