• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Switch from 5.3.3 to 5.4.3 breaks tomcat deployment
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Switch from 5.3.3 to 5.4.3 breaks tomcat deployment


  • Subject: Re: Switch from 5.3.3 to 5.4.3 breaks tomcat deployment
  • From: Ramsey Lee Gurley <email@hidden>
  • Date: Wed, 05 May 2010 23:08:13 -0400

On May 5, 2010, at 10:42 PM, Ken Anderson wrote:

> All,
>
> We're in the midst of converting some WO apps from 5.3.3 to 5.4.3.  Everything works well in Eclipse, but when we deploy to tomcat 5.5 via a .war file, the app basically does nothing.  Remote debugging shows that the Application constructor gets called, but the notification center never fires the appDidFinishLaunching event.
>
> We're using Java 1.6 if that matters...  Any thoughts?
>
> Thanks!
> Ken

Known issue if I'm not mistaken...

Begin forwarded message:

> Date: October 23, 2008 5:13:02 PM EDT
> To: Apple WO-Dev <email@hidden>
> Subject: Wonder App doesn't receive	"ApplicationDidFinishLaunchingNotification" notification when	deployed as a servlet
>
> I was banging my head on this, so I thought I would share it with the group:
>
> Our Wonder App doesn't receive "ApplicationDidFinishLaunchingNotification" notification when deployed as a servlet, this results in ERXRemoteSynchronizer not being started when initialized using ERXObjectStoreCoordinatorSynchronizer.initialize(); since initialization depends on that notification being received (Line 87 in ERXObjectStoreCoordinatorSynchronizer.java):
>
> NSNotificationCenter.defaultCenter().addObserver(this, new NSSelector("startRemoteSynchronizer", ERXConstant.NotificationClassArray), WOApplication.ApplicationDidFinishLaunchingNotification, null);
>
> You can bypass that by doing this instead
> ERXObjectStoreCoordinatorSynchronizer.synchronizer().initializeRemoteSynchronizer();
>
> As a confirmation I also overrode didFinishLaunching() from ERXApplication and that doesn't get called either when deployed as a servlet...
>
> Thanks,
>
> Saad
>

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Switch from 5.3.3 to 5.4.3 breaks tomcat deployment
      • From: Ken Anderson <email@hidden>
References: 
 >Switch from 5.3.3 to 5.4.3 breaks tomcat deployment (From: Ken Anderson <email@hidden>)

  • Prev by Date: Switch from 5.3.3 to 5.4.3 breaks tomcat deployment
  • Next by Date: Re: Custom EOSortOrdering for a WODisplayGroup
  • Previous by thread: Switch from 5.3.3 to 5.4.3 breaks tomcat deployment
  • Next by thread: Re: Switch from 5.3.3 to 5.4.3 breaks tomcat deployment
  • Index(es):
    • Date
    • Thread