Announcement Announcement Module
No announcement yet.
Login commond configuration with WASCE Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Login commond configuration with WASCE


    Any one tried to run the springBlaseDs M2 with spring security deployed on Websphere application server community edition ?

    I guess we need to change the login command class in service config file.
    currently my channelset.login works fine with spring blazeds M2 + spring security on Tomcat,but the same does not run on WASCE v2, So I tried to set the login command to WebSphere server, but login send failed error. I think we need to modify or write some extra code to map to our server.

    Can any one guide me on how to do it.

    please help me.

  • #2
    You should not need to configure a Websphere-specific login command. Can you provide more detail on what errors you saw when using the same setup as on Tomcat?


    • #3

      Hi Jeremy ,

      thanks and now I am able to run the project in WASCE v2.

      1)Once I added geronimo-web.xml it worked, but the strange thing, when I was deploying SpringBlazeDs M1, it was not looking for geronimo-web.xml

      may be some thing to do with M2 +security

      But now it need that file. once I added that file to my project it worked.

      My server was throwing java.lang.OutOfMemoryError: PermGen space when I tried to publish through WTP, even after increasing the heap size etc ,
      some how when I exported it as WAR directly (thru web console) it worked.