URLAction expects an explicit URLBeanName in Rewrite but Prettyfaces didn't

Splash Forums PrettyFaces Users URLAction expects an explicit URLBeanName in Rewrite but Prettyfaces didn't

This topic contains 3 replies, has 2 voices, and was last updated by  Christian Kaltepoth 1 year, 8 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #26545

    deepak
    Participant

    We have @com.ocpsoft.pretty.faces.annotation.URLAction scattered throughout the application. When I try to migrate from PrettyFaces 3.3 to Rewrite, these actions come back with an error message:

    com.ocpsoft.pretty.PrettyException: Exception occurred while processing <page:#{[class].method}> Cannot find name of bean ‘class’! You should place a @URLBeanName annotation on this class to let PrettyFaces know its name.

    If I add @URLBeanName annotation to “class” it works fine.

    However in PrettyFaces 3.3, the page actions used to work without the @URLBeanName annotations. I believe this is the expected behavior in Rewrite too, since we have the class marked up using standard JSF mechanism with @ManagedBean annotation.

    Is this a bug in Rewrite?

    • This topic was modified 1 year, 8 months ago by  deepak.
    #26547

    Did you add rewrite-integration-faces to your dependencies? If not, could you try to do so?

    #26551

    deepak
    Participant

    Thanks, adding rewrite-integration-faces fixed it for me.

    I had wrongly assumed that the rewrite-integration-faces wouldn’t be needed if I was following the “PrettyFaces compatibility module” strategy outlined at https://github.com/ocpsoft/rewrite/blob/master/documentation/src/main/asciidoc/migration/prettyfaces3.asciidoc#strategy-1-prettyfaces-compatibility-module

    I initially had added rewrite-servlet and rewrite-config-prettyfaces.

    #26552

    Nice to hear it is working for you now.

    You are correct. This is missing in the migration guide. I’ll add a note about this.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

Comments are closed.