Has "Publish for Approval" in Aperture ever worked?

Has anyone ever been able to get "Publish for Approval" to work in Aperture? We've been struggling with it for a week, and can't seem to get it going.
If anyone out there has been successful, I'd love to hear how.
Thanks,
David

I'm not using RAID or NFS. My startup drive is the standard 160GB SATA internal of a G5 formatted as Journaled HFS+.
I have filevault activated on a 2nd account on this computer, but not on the active account.
Publish was working with the above drive configurations. The only things that have changed since it was working is the uprade to Aperture 2 and a range of various software updates that came through after installing 10.5.2 and Aperture 2.
I am using Time Machine, which I activated around the same time as I started using Aperture 2, which was when Publish stopped working. However, Time Machine is only set to backup the desktop, docs and music folders of my home account, plus a 2nd internal drive. But I thought it was worth mentioning.
As I wrote in the email (to Sal), Publish doesn't fail right away for me, it happens after several images have been processed, then I get a -1700 applescript error.

Similar Messages

Publish for Approval - has anybody got this working?

Hi guys,
I just heard about Publish for Approval and thought I would take it for a spin. But I can't get it going.
Whenever I start the publish for approval application it asks for questions which aren't in the notes. Like where is Aperture-Submit.acgi? I have tried selecting the acgi dispatcher, aperture itself and the publish for approval application. It doesn't seem to matter what you choose. It then presents the panel, you fill in the guff and hit publish. It then re-displays the preferences panel, set to Sharing and tells me on a different dialog box:
Setup Error
Use of Publish for Approval system requires that Personal Web Sharing be active.
But it is!!
The box is ticked and the status just above the stop button shows:
Personal Web Sharing on
I'm new to Apple but I am missing something obvious here?
I think if the instructions said this was really complex and hard to do, I might feel a bit better. But it talks about how easy it is supposed to be.....
Please help a frustrated user.
Paul M

I'm not using RAID or NFS. My startup drive is the standard 160GB SATA internal of a G5 formatted as Journaled HFS+.
I have filevault activated on a 2nd account on this computer, but not on the active account.
Publish was working with the above drive configurations. The only things that have changed since it was working is the uprade to Aperture 2 and a range of various software updates that came through after installing 10.5.2 and Aperture 2.
I am using Time Machine, which I activated around the same time as I started using Aperture 2, which was when Publish stopped working. However, Time Machine is only set to backup the desktop, docs and music folders of my home account, plus a 2nd internal drive. But I thought it was worth mentioning.
As I wrote in the email (to Sal), Publish doesn't fail right away for me, it happens after several images have been processed, then I get a -1700 applescript error.

Publish for Approval - not working with 10.5.4 & Aperture 2.1?

Trying to use Publish for Approval, have turned on Web Sharing and selected images in AP2.1. Have a wired ethernet connection to my wireless router. But only get "Finder got an error: The operation could not be completed. (-8068)".
Anyone having any luck with this or know where I can reach the developer?

Now it's giving me other troubles. Got as far as 104 of 1323 images and hit AppleScript Error: Timeout. On subsequent attempts, it's hit AppleScript Error: Can't make <class docf> "[filename]" of alias "[boodrive]:Library:Documents:[gallery name]:images:" into type alias. (-1700).
Bummer.

Aperture & Publish for Approval fails with webserver . . .

I'm trying to get Publish for Approval working with Aperture. We are able to load the webpage on the client's browser, she can select an image, but when she hits "submit," Safari can't open the page "because the server is not responding."
10.5.4, Aperture 2.1.1, Publish for Approval 1.5. The Apache2 error log:
Mon Aug 04 13:58:20 2008 warn Init: Session Cache is not configured hint: SSLSessionCache
Mon Aug 04 13:58:21 2008 notice Digest: generating secret for digest authentication ...
Mon Aug 04 13:58:21 2008 notice Digest: done
Mon Aug 04 13:58:21 2008 notice Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.7l DAV/2 configured -- resuming normal operations
Mon Aug 04 13:58:46 2008 notice caught SIGTERM, shutting down
Mon Aug 04 13:58:46 2008 warn Init: Session Cache is not configured hint: SSLSessionCache
Mon Aug 04 13:58:46 2008 notice Digest: generating secret for digest authentication ...
Mon Aug 04 13:58:46 2008 notice Digest: done
Mon Aug 04 13:58:46 2008 notice Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.7l DAV/2 configured -- resuming normal operations
Mon Aug 04 14:13:20 2008 error http://client 192.168.93.10 File does not exist: /Library/WebServer/Documents/favicon.ico, referer: http://192.168.93.10/1941/index.html
Mon Aug 04 15:56:17 2008 error http://client 192.168.93.10 client denied by server configuration: /Users/david/Sites/
Mon Aug 04 16:26:59 2008 error http://client 65.96.217.170 File does not exist: /Library/WebServer/Documents/favicon.ico, referer: http://71.232.115.230/1941/index.html
Mon Aug 04 16:28:17 2008 error http://client 65.96.217.170 _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/40.html
Mon Aug 04 16:28:59 2008 error http://client 65.96.217.170 _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/index.html
Mon Aug 04 16:33:17 2008 warn http://client 65.96.217.170 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/40.html
Mon Aug 04 16:33:17 2008 error http://client 65.96.217.170 Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/40.html
Mon Aug 04 16:33:59 2008 warn http://client 65.96.217.170 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
Mon Aug 04 16:33:59 2008 error http://client 65.96.217.170 Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
Mon Aug 04 16:38:17 2008 warn http://client 65.96.217.170 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/40.html
Mon Aug 04 16:38:59 2008 warn http://client 65.96.217.170 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
Mon Aug 04 17:16:56 2008 error http://client 65.96.217.170 _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/index.html
Mon Aug 04 17:17:55 2008 error http://client 65.96.217.170 _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/02.html
Mon Aug 04 17:21:56 2008 warn http://client 65.96.217.170 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
Mon Aug 04 17:21:56 2008 error http://client 65.96.217.170 Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
Mon Aug 04 17:22:55 2008 warn http://client 65.96.217.170 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/02.html
Mon Aug 04 17:22:55 2008 error http://client 65.96.217.170 Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/02.html
Mon Aug 04 17:26:56 2008 warn http://client 65.96.217.170 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
Mon Aug 04 17:27:55 2008 warn http://client 65.96.217.170 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/02.html
Mon Aug 04 18:03:28 2008 notice caught SIGTERM, shutting down
Mon Aug 04 18:04:30 2008 warn Init: Session Cache is not configured hint: SSLSessionCache
httpd: Could not reliably determine the server's fully qualified domain name, using Russia.local for ServerName
Mon Aug 04 18:04:31 2008 notice Digest: generating secret for digest authentication ...
Mon Aug 04 18:04:31 2008 notice Digest: done
Mon Aug 04 18:04:31 2008 notice Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.7l DAV/2 configured -- resuming normal operations
Mon Aug 04 18:47:55 2008 error http://client 192.168.93.10 _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://192.168.93.10/1941/index.html
Mon Aug 04 18:52:55 2008 warn http://client 192.168.93.10 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://192.168.93.10/1941/index.html
Mon Aug 04 18:52:55 2008 error http://client 192.168.93.10 Premature end of script headers: Aperture-Submit.acgi, referer: http://192.168.93.10/1941/index.html
Mon Aug 04 18:57:55 2008 warn http://client 192.168.93.10 Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://192.168.93.10/1941/index.html
We've opened ports 80 and 443 on the firewall, and tried to approve and submit locally, with the same results.
If anyone has any ideas on how to get this to work, it would be great. We have a lot to submit, and the client really would like to do it on line.
Thanks,
David

Thanks for your input guys.
We discovered that we originally had used Publish for Approval 1.1, and subsequently have changed to version 1.5, which no longer uses the third party app.
Unfortunately, we still have the same problem, the client's browser stops loading when he or she hit's the "submit" button.
---> Could the installation of the 1.1 and third party app have left some preferences that need to be deleted or settings that need to be reset?
---> The error message on the client's web browser now states that the "server unexpectedly dropped the connection." Trying again later is not successful.
The error logs for Apache2 from the most recent attempt are different than with the 1.1 version of the software:
[Tue Aug 05 11:56:50 2008] [error] [client 76.24.22.217] File does not exist: /Library/WebServer/Documents/favicon.ico, referer: http://71.232.115.230/1941/index.html
[Tue Aug 05 11:57:50 2008] [error] [client 76.24.22.217] File does not exist: /Library/WebServer/Documents/1941/images/blank.gif, referer: http://71.232.115.230/1941/12.html
[Tue Aug 05 11:58:18 2008] [error] [client 76.24.22.217] _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/12.html
[Tue Aug 05 12:03:18 2008] [warn] [client 76.24.22.217] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/12.html
[Tue Aug 05 12:03:18 2008] [error] [client 76.24.22.217] Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/12.html
[Tue Aug 05 12:08:18 2008] [warn] [client 76.24.22.217] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/12.html
I don't know much about this, I just want my client to be able to approve the images through the Aperture interface.
Thanks again, I really appreciate the help.
David

Publish for Approval - the new plug-in - doesn't work with Leopard

This aperture plug-in arrived for download just a few days before Leopard arrived. It worked great with Tiger. It doesn't work at all with Leopard. It appears that Leopard comes with a new version of Apache Server and it doesn't work with the Publish for Approval plugin. Does anyone know if and when an update will be released?

I'm not seeing the Java plugin in the plugins list in the System Details list.
Did you install the 32 bit Java version?
Do you see the Java plugin in "Firefox/Tools > Add-ons > Plugins"?
*https://support.mozilla.org/kb/Troubleshooting+plugins
*http://kb.mozillazine.org/Java

"Publish for Approval" fails on submit

I'm trying to get Publish for Approval working with Aperture. We are able to load the webpage on the client's browser, she can select an image, but when she hits "submit," Safari can't open the page "because the server is not responding."
10.5.4, Aperture 2.1.1, Publish for Approval 1.5. The Apache2 error log:
[Mon Aug 04 13:58:20 2008] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Mon Aug 04 13:58:21 2008] [notice] Digest: generating secret for digest authentication ...
[Mon Aug 04 13:58:21 2008] [notice] Digest: done
[Mon Aug 04 13:58:21 2008] [notice] Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.7l DAV/2 configured -- resuming normal operations
[Mon Aug 04 13:58:46 2008] [notice] caught SIGTERM, shutting down
[Mon Aug 04 13:58:46 2008] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Mon Aug 04 13:58:46 2008] [notice] Digest: generating secret for digest authentication ...
[Mon Aug 04 13:58:46 2008] [notice] Digest: done
[Mon Aug 04 13:58:46 2008] [notice] Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.7l DAV/2 configured -- resuming normal operations
[Mon Aug 04 14:13:20 2008] [error] [client 192.168.93.10] File does not exist: /Library/WebServer/Documents/favicon.ico, referer: http://192.168.93.10/1941/index.html
[Mon Aug 04 15:56:17 2008] [error] [client 192.168.93.10] client denied by server configuration: /Users/david/Sites/
[Mon Aug 04 16:26:59 2008] [error] [client 65.96.217.170] File does not exist: /Library/WebServer/Documents/favicon.ico, referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 16:28:17 2008] [error] [client 65.96.217.170] _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/40.html
[Mon Aug 04 16:28:59 2008] [error] [client 65.96.217.170] _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 16:33:17 2008] [warn] [client 65.96.217.170] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/40.html
[Mon Aug 04 16:33:17 2008] [error] [client 65.96.217.170] Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/40.html
[Mon Aug 04 16:33:59 2008] [warn] [client 65.96.217.170] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 16:33:59 2008] [error] [client 65.96.217.170] Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 16:38:17 2008] [warn] [client 65.96.217.170] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/40.html
[Mon Aug 04 16:38:59 2008] [warn] [client 65.96.217.170] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 17:16:56 2008] [error] [client 65.96.217.170] _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 17:17:55 2008] [error] [client 65.96.217.170] _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://71.232.115.230/1941/02.html
[Mon Aug 04 17:21:56 2008] [warn] [client 65.96.217.170] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 17:21:56 2008] [error] [client 65.96.217.170] Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 17:22:55 2008] [warn] [client 65.96.217.170] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/02.html
[Mon Aug 04 17:22:55 2008] [error] [client 65.96.217.170] Premature end of script headers: Aperture-Submit.acgi, referer: http://71.232.115.230/1941/02.html
[Mon Aug 04 17:26:56 2008] [warn] [client 65.96.217.170] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/index.html
[Mon Aug 04 17:27:55 2008] [warn] [client 65.96.217.170] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://71.232.115.230/1941/02.html
[Mon Aug 04 18:03:28 2008] [notice] caught SIGTERM, shutting down
[Mon Aug 04 18:04:30 2008] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
httpd: Could not reliably determine the server's fully qualified domain name, using Russia.local for ServerName
[Mon Aug 04 18:04:31 2008] [notice] Digest: generating secret for digest authentication ...
[Mon Aug 04 18:04:31 2008] [notice] Digest: done
[Mon Aug 04 18:04:31 2008] [notice] Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.7l DAV/2 configured -- resuming normal operations
[Mon Aug 04 18:47:55 2008] [error] [client 192.168.93.10] _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL., referer: http://192.168.93.10/1941/index.html
[Mon Aug 04 18:52:55 2008] [warn] [client 192.168.93.10] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://192.168.93.10/1941/index.html
[Mon Aug 04 18:52:55 2008] [error] [client 192.168.93.10] Premature end of script headers: Aperture-Submit.acgi, referer: http://192.168.93.10/1941/index.html
[Mon Aug 04 18:57:55 2008] [warn] [client 192.168.93.10] Timeout waiting for output from CGI script /Library/WebServer/CGI-Executables/Aperture-Submit.acgi, referer: http://192.168.93.10/1941/index.html
We've opened ports 80 and 443 on the firewall, and tried to approve and submit locally, with the same results.
If anyone has any ideas on how to get this to work, it would be great. We have a lot to submit, and the client really would like to do it on line.
Thanks,
David

It looks like your webserver is not set up correctly. You might get better responses in the Networking and the Web forum - this is the Leopard Automator forum.

Publish for Approval with .Mac

If anyone has used the new "Publish for Approval" AppleScript and has found a way to publish these pages to a .Mac account/web page, would you tell me how you did it. I have been waiting for something like this forever but dont want to have to leave my computer on all the time to run as a server for these pages.
What seems to be the issue is that it creates a web page from the Personal Web Sharing in Settings and uses your mac as a server, the only way people can get on is if your mac is active and allowing connections.
http://automator.us/aperture/publish/?sr=hotnews

I'm not the developer of this interesting looking package, but it doesn't look like it's something that will work with .Mac at all.
The web pages is creates rely on an application to be running on the machine that's serving the web page (which, as it's designed, would be your local Mac). This application needs to receive approvals from the web page events, and also needs to be on your machine so that it can use AppleScript to set the metadata in your Aperture library so that the approved pictures show up in the smart group. Neither of these are possible if the site is served on .Mac.
In theory, this could run on a remote machine, since AppleScript can target processes on remote machines. But to make it work, you'd still need the CGI application on the server, and you'd also need to open your Mac to allow remote AppleScript execution over the Internet (which gets into network setup, probably secure SSH tunnels, etc). Your Mac would also still need to be on, and allowing this connection, otherwise Aperture wouldn't be notified when someone approved pictures.
To make a short story long, it won't work with .Mac.

Modify "Publish for Approval" web page?

Is there a way to modify the "Publish for Approval" web page in Aperture?
The original package includes a PNG file you can modify to put your logo on, but nothing else.
Thanks for any input.
David

I'm not the developer of this interesting looking package, but it doesn't look like it's something that will work with .Mac at all.
The web pages is creates rely on an application to be running on the machine that's serving the web page (which, as it's designed, would be your local Mac). This application needs to receive approvals from the web page events, and also needs to be on your machine so that it can use AppleScript to set the metadata in your Aperture library so that the approved pictures show up in the smart group. Neither of these are possible if the site is served on .Mac.
In theory, this could run on a remote machine, since AppleScript can target processes on remote machines. But to make it work, you'd still need the CGI application on the server, and you'd also need to open your Mac to allow remote AppleScript execution over the Internet (which gets into network setup, probably secure SSH tunnels, etc). Your Mac would also still need to be on, and allowing this connection, otherwise Aperture wouldn't be notified when someone approved pictures.
To make a short story long, it won't work with .Mac.

Offline running - can "GetResources() for an embedded file ever work?

This question has come up in various guises in the past, but has often then become confused with other issues (see [t-5123126] ) so I've not been able to find a useful answer. I've tried to bring the problem down to the essentials, and just want to know if what I'm trying to do can ever work, or if I should just abandon Web Start for this particular need.
Our app is J2SE Swing and creates a Derby database locally on a PC. The application then captures keyed data and stores it on the local database. Persistence is via JPA (provider was Toplink, now EclipseLink).
The data capture is performed using laptops running the application "offline" with no network connection. This is because the location has no network access of any description. Periodically, each laptop is reconnected to upload its data to a central server.
To help with software distribution, we are using Java Web Start. All the jars are signed and the .jnlp file specifes offline usage is allowed.
When running the application while connected to the network, there are no issues - everything works fine.
When running offline, the application starts up so the Java Web Start caching is working and the code is obviously accessible. However, it throws a MalformedURLException within the EclipseLink code (which we do not wish to modify). The actual statement is:
Enumeration resources = classLoader.getResources("META-INF/persistence.xml"); META-INF/persistence.xml exists within one of the jar files specified as resources in the .jnlp file.
The classloader in question is the Java Web Start classloader ( com.sun.jnlp.JNLPClassLoader) which presumably retrieves classes and resources from the remote server or from the cache depending on how the app is being run. In online mode, the persistence.xml resource is found ok, in offline a MalformedURLException is thrown.
My question: is this a fundamental "restriction" of the Web Start environment in offline mode? i.e. it can't load resources such as this xml file from a cached jar using the format shown?. My feeling is that this is just the way it is, and I should move on and try another form of software distribution, but it seems a shame to abandon Web Start as it otherwise meets our needs.
Any relevent experience of this problem would be appreciated.
Edited by: GrayMan on Aug 21, 2009 8:20 AM

A system we're developing make use of a similar setup. I'm not sure if you run into this problem, but the classes in our app uses persistence annotations and do not rely on the orm.xml mapping file. After solving the persistence.xml show stopper, I could see that the application had really slow startup times in offline mode. By looking at the access logs in online mode, I could see that the app was requesting META-INF/orm.xml and META-INF/eclipselink-orm.xml. In online mode, the web server simply returned HTTP 404 with much delay. In offline mode, this resulted in really slow startup times due to timeouts for the mentioned requests.
Creating valid xml files bundling them into the jar file of course didn't help.
I successfully disabled lookup for eclipselink-orm.xml by specifying the following entry in persistence.xml:
<property name="eclipselink.exclude-eclipselink-orm" value="true"/>
To disable lookup for orm.xml, I modified the method loadStandardMappingFiles(String) in org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.MetadataProcessor (eclipselink 1.1.0).
Perhaps this is useful for someone else also.

For the first time ever... firefox has been crashing all day... is it suddenly not compattable with my windows 7? or what is going on? which version would work best for me?

today for the first time ever... firefox will not work.. it constantly is going to not responding... and i have never had this problem before... is it suddenly not compatible with windows 7? what is best suited for windows seven users?

Drrhythm2 wrote:
What's the best solution for this? I
Copy the entire /Music/iTunes/ folder from her old compouter to /Music/ in her account on this new computer.

Work flow - user is not reciving mail,once CREDIT MEMO submits for approval

Hi All,
Please find the issue as below.
User created the credit memo and submitted for approval. user is expecting the mail in his mail-box, once he submitted the credit memo for approval and same way once approver approved the credit memo, user is expecting mail such that credit memo has been approved.
He informed that previously he is receiving the mails as expected.
Now all of sudden he is not receiving mails.
I have checked work flow mailer, mailer is up and running.
I have gone through the wf_notifications table, here i can see that MAIL_STATUS column having value of "MAIL".
even i have gone through WF_USERS table this particular user is existing and status is "ACTIVE".
But user is not yet received any mail.
Kindly some one help me to sort out this issue.
Thanks in Advance.
Edited by: user627525 on Jun 8, 2011 5:58 AM

Thanks RK for your quick reply.
I was gone through the details you have provided. every thing is fine as expected.
Later i have checked workflow mailer, it was down, due to that notifications are not reached to users/customers.once it is up and running mail notifications sent to respective users successfully.
Many Thanks.

Publishing problem for v.10 and above - works fine in v.9

Hi,
I have this strange issue when I try to publish for v. 10 or above (which I need to get support for TLFTextFields). It works fine in v. 9. My Flash application runs, but there are two critical differences (making it unusable):
i) there is a complex vector (a geographical map, with each country or map area in a different color) which is either rendered as a bitmap and looks very blocky, or it does not display at all. Even when it is not visible, mouse-over events for each map area still trigger. This map should be displayed as a vector, and is displayed correctly in v. 9.
ii) the width no longer stretches to full-screen - but remains fixed width.
All I'm doing is publishing one version up - no other changes. It looks a bit as if I am publishing in AIR for iOS, but I'm not - I selected Flash Player 10.3 (or 11.1, 11.2, 11.3, 11.4 - all the same results).
I tried uninstalling and reinstalling Flash, deleting and restoring default preferences, copying the code into a whole new Flash file, removing TLFTextFields. Nothing has worked so far.
Many thanks for any advice!
Frank

Here is a list of deprecated elements of AS3.
Some classes that would work under Flash 9 wont work when targeting 10:
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/deprecated.html
Maybe that gives You an idea, where the problem lies
This gives useful tips when using non-latin charctersets and swapping languages on the fly, that are loaded from xml files.
http://www.mikeziray.com/2009/10/19/dynamic-textfields-in-flash-as3-and-their-bugs/

UWL for Manager : Multiple work items for approval

Hi Experts, We have a scenario when the line manager is approving the leave workitems in his UWL. And the UWL has multiple leave workitems pending for approval. When the line manager click on any of the work item in the UWL, The UWL opens the items which was first creared in the UWL rather than the one which the line manager clciked. Then line manager has to navigate to the desired work item by clicking on next button. Is their any funtionality / customization available to get only the work item which is clicked in the UWL. Please advise. Regards, IFF

I had the same issue and spent a long time correcting it including opening a OSS request with sap.
It took a combination of all almost all the notes above (1807724 is included in our current release so we didn't have to install).
But nothing worked for us until SAP directed me to the following note http://service.sap.com/sap/support/notes/1733095 that was the final fix to all our problems.
One other thing to note is from the time we implemented the correction for note: 1946640 had changed from its original so if you implemented it before revision 3 came out you may need to update.
Hope this helps,
Martha.

Dynamically embedded swf, has it ever worked

I have to repost it. Wondering what adobe will say about it.
I have tried this for a couple of days. I created a swf object in window.onload (also tried to create it directly while the script was loaded ), then call an AS function from JS. statically embedded swf works for both IE8 and FF, FF also fine for dynamically loading. In IE, this call externalinterface.call("echo", "as returns " + b); always shows "as returns false". The callback function has never worked in other approches with dynamic creation. Anyone has good experience?
Thanks.
//js
<script language="javascript">
var containerready=false,flashready=false;
function addLoadEvent(func) {var oldonload = window.onload; if (typeof window.onload != 'function') {
window.onload = func; } else { window.onload = function() { if (oldonload) { oldonload(); } func(); }}
function embedswf(){
var a,swf="<object classid='clsid:d27cdb6e-ae6d-11cf-96b8-444553540000'";
swf+=" codebase='http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=10, 0,0,0'";
swf+=" width='215' height='318' id='testswf1' align='middle'>";
swf+=" <param name='allowScriptAccess' value='always' />";
swf+=" <param name='allowFullScreen' value='false' />";
swf+=" <param name='movie' value='testswf1.swf' />";
swf+=" <param name='quality' value='high' />";
swf+=" <param name='wmode' value='transparent' />";
swf+=" <embed src='testswf1.swf' quality='high' wmode='transparent' width='215' height='318' name='testswf1' align='middle' allowScriptAccess='always' allowFullScreen='false' type='application/x-shockwave-flash' pluginspage='http://www.adobe.com/go/getflashplayer' /></object>";
a=document.createElement("div");
a.id="swfholder";
a.innerHTML=swf;
document.body.appendChild(a);
containerready=true;
window.setTimeout(callas, 100);
} addLoadEvent(embedswf); function echo(p){ alert(p)} function callas()
// alert("callas:containerready="+containerready+";fl ashready="+flashready);
containerready=true;
if(flashready){
var a=getswf();
a&&(a.flashfunc())
return
window.setTimeout(callas, 100);
} function setflashready()
flashready=true;
function getcontainerready()
//alert("getcontainerready:g31="+containerready+";fl ashready="+flashready);
return containerready;
function getswf()
if (navigator.appName.indexOf("Microsoft") != -1)
return window["testswf1"];
else
return document["testswf1"];
} </script> //as
import flash.external.ExternalInterface; flash.system.Security.allowDomain("*"); var rtm:Timer = new Timer(500);
startTest(); function f0():void {
ExternalInterface.call("echo", "one");
function timerHandler(event:TimerEvent):void
if (isContainerReady())
rtm.stop();
rtm.removeEventListener(TimerEvent.TIMER, timerHandler);
setupCallbacks();
function startTest():void
if (ExternalInterface.available)
try
if (isContainerReady())
setupCallbacks();
else
rtm.addEventListener(TimerEvent.TIMER, timerHandler);
rtm.start();
catch(error:Error) {
trace("An Error occurred: " + error.message + "\n");
else
trace("External interface is not available for this container.");
function isContainerReady():Boolean
var b:Boolean = ExternalInterface.call("getcontainerready");
ExternalInterface.call("echo", "as returns " + b);
return b;
} function setupCallbacks():void
ExternalInterface.call("echo","setupcallback");
ExternalInterface.addCallback("flashfunc", f0);
ExternalInterface.call("setflashready");

has it ever worked or is an Adobe bug? anyone knows?

Alpha property not working on TextField when publish for Reader 9

Hi,
I have a movie that is working fine when I publish for Reader 10, but when I publish for Reader 9, the code that assigns an alpha property to my TextFields stops working. I have a previous movie, which I probably did in CS4, that uses similar code to fade in and out TextFields. It was published for Reader 9 and works fine.Is it possible that something has changed in CS5 (note, I'm not using TLF text boxes, only dynamic TextFields)?
Here's an example of the code I'm using:
stop();
import fl.transitions.Tween;
import fl.transitions.TweenEvent;
import fl.transitions.easing.*;
import flash.events.*;
import flash.text.*;
import flash.text.TextFormat;
import flash.utils.Timer;
import flash.display.MovieClip;
import flash.display.Sprite;
var txtFormat1:TextFormat = new TextFormat();
txtFormat1.font = "Optima";
txtFormat1.color = 0x000000;
txtFormat1.bold = false;
txtFormat1.size = 16;
txtFormat1.leading = 2;
var subtitle:TextField = new TextField();
subtitle.autoSize = TextFieldAutoSize.CENTER;
subtitle.selectable = false;
subtitle.defaultTextFormat = txtFormat1;
var fadeInSubtitle:Tween;
addChild(subtitle);
subtitle.x = stage.stageWidth / 2 - subtitle.width / 2;
subtitle.y = stage.stageHeight / 2 - subtitle.height / 2;
subtitle.alpha = 0;
subtitle.text = "What is the most important question in";
fadeInSubtitle = new Tween(subtitle,"alpha",None.easeNone,0,1,3,true);

Thanks.
Just curious: Is there a reason why the alpha on the TextFields worked without embedding fonts when publishing for Flash Player 10? Does it handle text, even when it's not TLF, differently than Flash Player 9?

Has "Publish for Approval" in Aperture ever worked?

Similar Messages

Maybe you are looking for