• 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: ERJavaMail and system properties
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ERJavaMail and system properties


  • Subject: Re: ERJavaMail and system properties
  • From: Anjo Krank <email@hidden>
  • Date: Sun, 2 Mar 2008 21:23:40 +0100

Yes it was my fault. Did not know that I have to call first ERJavaMail.sharedInstance().finishInitialization() and ERJavaMail.sharedInstance().initializeFrameworkFromSystemProperties()

You don't. You have to init via the props. That it works this way is pure chance.


Cheers, Anjo


Am 02.03.2008 um 20:50 schrieb Sergio Sánchez Maffet:

Sorry for the last empty message... ;-)

Thank you!

Yes it was my fault. Did not know that I have to call first ERJavaMail.sharedInstance().finishInitialization() and ERJavaMail.sharedInstance().initializeFrameworkFromSystemProperties()

It is working now.

On 02.03.2008, at 09:12, Mike Schrag wrote:

my system properties are not recognized by ERJavaMail.
It complains with the following message:

When setting 'er.javamail.centralize=true' (which means you just test sending mails), you must also give a valid 'er.javamail.adminEmail=email@hidden ' to which the mails are sent.

I have already tried to set them in code just before mail delivery starts.
Only ERJavaMail and ERExtensions frameworks are linked into my project.
define "set them in code". If you're trying to set system properties in code, you're probably "too late" to do it. Once the framework has initialized, it does not look at the values in code. You should either set them in your Properties file, set them as -D system properties on the commandline, or set them via the API on ERJavaMail.sharedInstance() after the framework has initialized. The recommended method is to set them in Properties. If you set system properties, you will need to call ERJavaMail .sharedInstance().initializeFrameworkFromSystemProperties() (never tried this, but it should work). Again, though, I would just set them in your Properties file.

ms
_______________________________________________
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

_______________________________________________ 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

_______________________________________________ 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
References: 
 >ERJavaMail and system properties (From: Sergio Sánchez Maffet <email@hidden>)
 >Re: ERJavaMail and system properties (From: Mike Schrag <email@hidden>)
 >Re: ERJavaMail and system properties (From: Sergio Sánchez Maffet <email@hidden>)

  • Prev by Date: Re: ERJavaMail and system properties
  • Next by Date: [OT] JSF vs. WebObjects
  • Previous by thread: Re: ERJavaMail and system properties
  • Next by thread: [OT] JSF vs. WebObjects
  • Index(es):
    • Date
    • Thread