Metadata phrase meaning

1. What does this metadata phrase mean: "Return light detected, compulsory mode?" The specific image matters little but I am looking at one taken with a Nikon D700 and a SB900 flash bounced from an umbrella with the unit connected to the camera with a SC28 cable.
2. Is there a reference souce for the properties in the metadata fields?

I don't do Nikon, but it sounds like the flash was set to fire regardless of any auto setting, and that light from the flash was reflected from something and seen by the camera.

Similar Messages

What does all does metadata fields mean?

So far, I haven't yet created a personalized Metadata Preset for all my photos because I don't understand most of the fields, what they exactly mean and where is that value going to be displayed/read by.
Can anyone help me on that or point to me to an article or guide about each metadata field editable in Lightroom?
For instance, Basic Info has fields like "Caption", "Rating", "Label" and Copy Name". Well, I believe Caption is the photo name (if we decide to give it one), Rating is self explanatory but Label and Copy Name I have no clue what are they for and where are they going to be used, etc...
IPTC Content, IPTC Copyright, IPTC Creator, IPTC Image and IPTC Status, what are all these for and what about each of their fields, I don't know what they mean and what are they for, where they will be read/used, all that...
After understanding what all those fields mean, which ones do you recommend to fill for a preset or how do you do it with your photos? I mean, I believe IPTC Image is something to do with a respective image, so, if I have a bunch of images from different countries, places and whatever, it makes no sense to have a preset for that unless I'm importing a bunch of photos from a specific place. But I'm talking about a more general preset that you use for all or most of your photos. What should I fill?
But more importantly, I need/want to understand all those fields, what are they for and how they will be used, etc, but the most important thing in all of this is to know what each field means, otherwise, I won't be able to know if I want to provide that information or not and if I know what to write there.
P.S: Try not to confuse me a lot ;)

See: http://www.iptc.org/IPTC4XMP/
Download: http://www.iptc.org/download/public/IPTCCore-CSPanelsOnly.zip

Do LR4's random metadata warnings mean something serious?

(LR4.1 on a 2011 iMac with 16GB RAM, running OS 10.7.4)
I am doing my first big job in LR4, and am worried by the way that metadata conflict warning flags (of two types: 'Error writing metadata' and 'Metadata was changed externally') are appearing and reappearing randomly on my image thumbnails. There is absolutely no consistency in which images are affected. I imagine the problem may be caused initially because I used to apply a couple of presets on import - a copyright line, and also camera-specific Develop settings. These were created in Lightroom 2: most of the 14,000 images in my Lightroom catalogue predate my upgrade to LR3 in October (I went to LR4 at the end of April, and 4.1 a week ago; I didn't notice this problem in LR3, but I didn't do much work in that version of the program, so it may have been present and I just didn't notice).
As I say, not all images are affected; but those that are have nothing particular in common. (Whereas most of my photographs will have had the presets applied on import, or else later - when I came up with the new camera-specific defaults, I also applied them retrospectively to all images I hadn't yet processed individually.)
My frustration is not just that this problem exists in the first place: if it is caused by the import presets, I've deleted the develop one (and triple-checked that nothing other than Lightroom's own processing defaults is being applied), and recreated the copyright one, throwing the original away. However, when I try to clear the flags, by clicking on them and OK'ing the dialog box, or doing command-S and OK'ing that way, they sprout up again either immediately or soon after; sometimes on the same images as before, sometimes on other ones.
I've got 'automatically save to XMP' checked as a preference (have had for years, so all my images have XMP files beside them). Although Lightroom imagines the images have also been edited in another program, the vast majority are NEF raw files, and I don't use any other image viewing or editing programs. (There are also a few Photoshop files that may or may not have flags.)
How I've tried to solve it:
1. Doing lots of saves - either selecting all the images in a folder or collection and doing a manual save or clicking the flag and OK'ing the dialog box; or selecting only the images affected and doing the same; or going through one by one, ditto. But whatever I do, more flags sprout on the same or other images in the folder (although sometimes after several saves, they seem to vanish for good).
2. Throwing LR's preferences away. Since this made no difference, I retrieved and reinstated them.
3. Deleting all user presets in Develop, plus the copyright one for Import. (I do have Print and FTP presets, which I hope I don't have to throw away as well. I'm not using those modules at the moment, though.)
4. Realized there was no point on optimizing the catalogue, since that happens automatically, alongside checking its integrity and backing it up, every time I quite Lightroom - which I do after every work session, to ensure I'm fully backed up.
5. At some point in all this, I also restarted my Mac (after I'd deleted the preferences, I think).
6. I have excluded the LR catalog from my Time Machine back-ups, although there was an interruption to this for a few days this week, after I upgraded to LR4.1 (and now I'm worrying that in fact this might date back to my upgrade to LR4 in April). But presumably the catalog isn't corrupt, or I'd get a warning during the regular checks on its integrity?
What's really worrying me, is that this weird behaviour means that there's some instability in Lightroom that'll mean the work I've done on my images is compromised in some way, and I'll lose it.
How can I get rid of these random (incorrect) warnings permanently?
(I did post on this last week, but didn't realize how pervasive and peristent the problem was. I rang Adobe for support on 7 June and got cut off twice; they haven't responded to the case they opened when I was cut off the second time. I tried phoning them three times this morning, and couldn't get through - I was cut off again, twice; the other time I just got dead air. Their phone system seems to be completely up the creek. When I did manage to speak to someone, the sound kept going - which the techie seemed oblivious to, no matter that I kept telling him I couldn't hear him.
I'm really worried that the intensive work I'm doing in Lightroom at the moment will all go to waste, so I'm holding back when I really need to take advantage of the few days I have free right now to do the work.)

Thanks, everyone, for your suggestions.
John: I back up the catalogue (and optimize/check its integrity) every time I quit Lightroom - which is why excluding it from Time Machine isn't the end of the world. I did rename the catalogue early on in my troubleshooting process - as you say, I didn't like the fact I felt out of control of it.
I tried synchronizing a folder that had some flags: when I'd done there were three flags in the folder. (I have unclicked - and clicked and then unclicked - the 'unsaved metadata' checkbox in View Options: as I say, Lightroom shouldn't be displaying these flags at all.)
Rob: Thanks for understanding why I'm fretting! I've checked my XMP sidecars, as you suggest, and they have read and write privileges. I then checked the last-modified date on the XMPs that came up with flags after I'd synchronized that folder. One of them displayed the time I'd just synchronized the folder (it's one I haven't worked on apart from applying a blanket preset in LR2, and then a blanket update to PV2012 in LR4, as I've done to all the images I haven't yet worked on individually); the other two showed the time (I presume) I worked on them yesterday. I selected these three and applied command-S: they then showed, correctly, that they'd been modified a minute before. So far, that folder's now flag-free. (As I said in my original post, the flags sometimes do seem to vanish if I save enough times - and they're unpredictable, not necessarily appearing on the same images in a collection or folder as before I do I group save/clear conflict.)
Mollysnoot: I don't see how the Mac OS would be doing this (although who knows - I'm not a software expert). I don't have any other programs open that can modify images. And since these flags can reappear instantly when I've dealt with the conflict - before I've had time to take a breath, even - I don't think they represent any actual modifications.

What does the phrase 'got your back' mean, please ?

You urge me to:
"Now get the mobile browser that’s got your back"
Could someone kindly explain what this phrase means, if anything (it does not appear in Urban Dictionary nor American Heritage 2006), though I would guess it is a US usage. Many thanks

Hi ardj
i did not find neither in dictionaries, answer from an old american friend :
"it is something reliable and it won't let you down"
thank you

Annoture - Metadata Bridging Solution for Aperture and iView

Aperture and iView users:
I just released Annoture, a metadata bridging solution for Aperture and iView MediaPro! With Annoture, you’re just a click away from sharing metadata between these two popular image management and cataloguing applications. Spend more time working with your decisive moments than worrying about double-entry and incomplete metadata!
Annoture lets you transfer annotations from iView MediaPro catalogs to Aperture projects and albums and back. This two-way transfer of IPTC and metadata information means you are not tied to any one application for your image management and workflow needs. Annoture also features a modular interface that can be extended to support additional applications in the future.
http://www.tow.com/software/annoture/
Users of Aperture and iView can download a fully-functional version of Annoture. The unregistered version will occasionally display a reminder to register, and all images processed in Aperture by Annoture will have a custom “Annotated with Annoture!” tag added. You can remove these items with the full version after purchasing and entering your license code.
Enjoy!
-adam

Congratulations on getting this working and available so quickly! I bet many late nights went into this
It's definitely providing some motivation for me to learn more Applescript...

How to make metadata changes stick when having made the mistake of updating while Match was running?

I've painfully come to realize that much my tedious process to add composer to 4,000+ tracks where this was missing, was done while Match was running.
I have a Time Machine backup of the library that contains the changes, but if I restore this, Match insists on downloading the old metadata (which means deleting the composer data). Is there any way to force Match to update the cloud data based on this backup of the library file?
I really don't want to have to locate and add this data again...!

For ringtones, iTunes > Preferences > General >Import Settings... button > choose Import using AAC encoder to enable Create AAC version from .m4a and mp3 files.

Confused Metadata after import from catalogue

I have two catalogues on this machine. I just imported one into the other in order to merge them. The images in each catalogue have never been in the other.
After the import, most, but not I think all, imported images have an icon either saying either:
The metadata for this photo has been changed by both Lightroom and another application. Should Lightroom import settings from disk or overwrite disk settings with those from the catalog?
or
The metadata for this photo has been changed by another application. Should Lightroom import settings from disk or overwrite disk settings with those from the catalog?
My confusion is because I can't see how either of these statements can be true for most of the photos, which have either lived in one or the other LR catalogue all their lives. Unless by "another application" it is just referring to another instance of LR in the past?
I also don't understand whether "overwrite settings ... with those from the catalog" means using the metadata in the current catalogue, which came from the old catalogue (and which I therefore want), or whether it means overwrite the images embedded metadata with the (blank) metadata in the new catalogue after importing.
Assuming Metadata really means literally that, and not Keywords or presence in Collections etc, then it's no biggy, as I don't use Metadata very much. But still, can someone guide me through the safest option for the 6000 imported photos?
thanks
Nic
Amateur user, LR3.6, Mac OSX 10.6.8

Ian-
After reading your post, I did some reading, and now I get how to us LR's Paint tool!
With only your jpeg selected in the Library module, go to grid mode displaying the other images you want to copy the keywords to. Select the Paint tool in the tool strip, and If you don't see it, select Metadata>Enable painting.
On the right-hand panel, there is a Keywording text box with a comma-delimited list of keywords in the selected jpeg. Use your pointer to select all the list, then copy.
Make sure the paint tool is set for Keywords, then click in the dim little text box next to the Paint: Keywords selection labels. It should turn white: copy the list into that text box.
Now, click on each picture in the grid you want the list applied to and it happens! A message comes up. The spray paint icon changes to an eraser, so if you want to remove the keywords from an image, just click it.
Pretty cool tool!
Tony

Google safe browsing: meaning of "malicious software being downloaded and installed without user consent"

As an example, see http://www.google.com/safebrowsing/diagnostic?site=google.com
What does this phrase mean? Is it a browse-and-get-owned exploit? Is it for outdated browsers, or modern browsers too? Does it require specific vulnerable plugins to be active, such as Java?

Read the following about "drive-by downloads". Item 2 at the top of the page. User does not need to click on something on the infected page for a download to occur. Simply visiting the page is enough for the download to occur.
*https://en.wikipedia.org/wiki/Drive-by_download
You can also read this (3rd paragraph under "Delivery Methods").
*https://en.wikipedia.org/wiki/Web_threat

Encryption (Filenames/metadata, what to encrypt, resizing)

I've already decided to use an unencrypted root, either loop-aes or LUKS/dm-crypt to encrypt my swap (I will benchmark to decide), loop-aes/EncFS/LUKS to encrypt /tmp (or I will use tmpfs, since I have 6GB of RAM... any opinions?), and either LUKS, loop-aes, or TrueCrypt for my personal /home. /var/tmp will be an EncFS.
First, as mentioned above, any advice from those with experience on making a separate /tmp to encrypt with traditional methods vs. using tmpfs for /tmp (6GB RAM)? What kinds of operations use /tmp the most (I know optical disc writing does) (this will help to benchmark with/without tmpfs), and to what extent? Same questions for /var/tmp? I know tmpfs will automatically move lesser-used stuff to swap instead of main RAM - does it do this well, and does it adjust how much it does that depending on how much free RAM there is?
Second, I know TrueCrypt will encrypt filesystem metadata (the important thing being file names), and EncFS does since late last year. I'm pretty sure LUKS/dm-crypt and loop-aes also do, but I'm not 100% sure. Is anyone certain they do?
Third, any comments on how I've decided to set up my system? Are there any places I'm missing to encrypt?
And fourth, any info on resizing any of the above encryption setups (on block devices on LVM) would be very much appreciated.
Thanks!!
NOTE: I'm also considering just encrypting everything except probably /usr... it would be simpler, that's for sure. We'll have to see what the damage is in terms of speed.
NOTE 2: I will definitely post my results so others can see when I'm done. I will be running the benchmarks on both a quad-core with 7,200rpm hard drives and an elderly ThinkPad with a Pentium M Banias and a 5,400rpm drive. I'll also do a few quick benches to see whether the differences between file system change when encryption is used.... this'll be "fun".
I'm also asking these questions here, for any reading this that are also interested.

If someone takes it, puts it into another computer, and looks at each sector.
I know some encryption methods don't encrypt filesystem metadata, which means filenames, permissions, etc.. eCryptfs didn't until recently, for example. I know TrueCrypt does, but I'm not 100% sure that LUKS and Loop-AES work.
And to you, I recommend you find a way to encrypt /var/tmp and /tmp... if you burn something to DVD, for example, that's on your encrypted partition, the temp files will be stored in /tmp. Now your encrypted stuff has been written unencrypted to your hard drive, and can be recovered at least partially without too much trouble. /tmp can be a tmpfs (swap and RAM are used), but /var/tmp needs to be persistent - a separate encrypted partition, or eCryptfs (might be too slow).
Last edited by Ranguvar (2009-02-17 20:12:56)

Metadata rejected ("3.2 Apps with placeholder text will be rejected")

Hi everybody,
I have a problem with Apple but I hope that I can find someone here who has faced the same matter and can help me!
Some weeks ago I sent my first app (the publication is a single-app catalogue) to iTunes Connect and everything was smooth (it has been accepted and placed in the App Store in 5 days).
Instead last week I sent another similar publication (a single-app catalogue created in the same way as the first one) but the app has been rejeceted for this reason:
3.2: Apps with placeholder text will be rejected
Oct 21, 2011 03:38 PM. From Apple.
3.2
We found that your app and/or its metadata does not appear to include final content, which is not in compliance with the App Store Review Guidelines.
Specifically, we noticed that the app metadata does not include a description of the app's features.
While your iTunes Connect Application State will show as Metadata Rejected, we do NOT require a new binary if you only need to change your metadata. (A new binary is required only when you have to also make changes within the app.)
If you only need to change your metadata, please visit iTunes Connect, Manage Your Applications, and revise the appropriate metadata values or settings, then click Save. After saving, click "Save," then click "Submit New Metadata" in the top right.
Actually I do not understand what they mean with "placeholder text" but above all I would like to ask to someone expert - I rely on BOB! - (I am a newby to DPS and Apple) if this means that I have to re-create from the start the app from the Folio Builder changing something in Indesign or if they just mean I have to modify something in iTunes Connect without touching the binary file.
I am in a great confusion because they say the "app metadata" does not include a description of the app's features but I do not know how can I change the "metadata" within the app (in fact I believe that when they refer to the "app metadata" the mean the "metadata" inside the app and not the metadata that I add in iTunes Connect).
The doubt that I have now is that maybe the last update of the Viewer Builder or of the Folio Builder has changed something that now generates this issue?
Of course I am contacting also Apple for this issue, but in the meanwhile it would be a relief for me to hear a suggestion from here!
Thank you to anyone for any reply!

app metadata is the description text you enter while adding your app into
iTunes connect.
as is in the statement, for doing metadata changes, you don't need to submit
a new binary (aka .zip file containing your folio)
add more details of the feature of you app into the description in iTunes
connect aand you should be fine.
there is no 'metadata' inside tje binary of your app that you can change.
but Bob can add sth. to this eventually.
—Johannss
(mobil gesendet)
Am 22.10.2011 11:40 schrieb "Pierluis" <[email protected]>:
Metadata rejected ("3.2 Apps with placeholder text will be rejected") created by
Pierluis <http://forums.adobe.com/people/Pierluis> in *Digital Publishing
Suite* - View the full discussion<http://forums.adobe.com/message/3984939#3984939>

Compile-Time Reflection/Metadata access?

Hey I hear for netbeans there is an extension (or maybe it is built in) to do reflection/access metadata at compile time.
Anyone hear about this or know where I can find more info on this? Or maybe it is for a different IDE or a stand alone tool?
compile-time access would be ideal since J2ME doesn't have run-time reflection/metadata access. A lot better than no access at all :)

Ok everyone, if I was writing a java compiler, I'd for sure need compile-time reflection/metadata access right? And instead of writing the compiler from scratch and having to write those tools myself I can write a sub-compiler that runs within the existing java compilation process and accesses the tools and functionality of the compiler itself. So then I just proved it is not an irrelevant concept and that it is in-fact very important. The concept of a programming language is independent of the specific language.
Yes well more specifically how about I say 'how do I get access to the compile-time reflection/metadata tools that are part of the NetBeans java compiler (or whatever compiler NetBeans uses)'?
Ok DrClap. The mere fact that even a single programming language supports compile-time reflection/metadata access means it can be applied to java as well. And you also failed to mention that the Wikipedia article doesn't call out which specific languages support compile-time reflection/metadata access, because it is a language-independent concept. Java itself is considered 'higher-level' so I'm not sure why you want to claim compile-time anything is irrelevant.
And my industry colleagues aren't hear because I'm the only one working the weekend. We talked about this before the weekend and I forgot to get further info or a link to a website.
Thanks ejp!
I gave ejp 5 points since I have to do a little bit of reading to see if those tools/apis are what I'm looking for (5 points left). Looks promising though. Either way if I don't get anything better by tomorrow I'll give ejp the other 5.
And sorry everyone I'm not very subtle when it comes to forum conversation.

What does this mean? listening?

what do these phrases mean?
Firewall[37]: Stealth Mode connection attempt to TCP 192.168.1 from 161.11.13
or
Firewall[37]: Safari is listening from ::ff:0.0:0 uid = 501 proto=6
Message was edited by: supercatey

Just turn on WPA security on your wireless router, and use a password that is not in any dictionary, and then you can pretty much assume nobody's going to be able to join your network.
Oh, and that last IP address in your log?
May 24 11:12:03 ***s-computer Firewall50: Stealth Mode connection attempt to TCP 192.168.0.196:49489 from 17.254.2.136:443
Looked it up at arin.net and it belongs to...
Search ARIN WHOIS for: 17.254.2.136
OrgName: Apple Computer, Inc.
OrgID: APPLEC-3
Address: 20740 Valley Green Drive, MS32E
City: Cupertino
StateProv: CA
PostalCode: 95014
Country: US
NetRange: 17.0.0.0 - 17.255.255.255
CIDR: 17.0.0.0/8
NetName: APPLE-WWNET
NetHandle: NET-17-0-0-0-1
Parent:
NetType: Direct Assignment
NameServer: NSERVER.APPLE.COM
NameServer: NSERVER2.APPLE.COM
NameServer: NSERVER.EURO.APPLE.COM
NameServer: NSERVER.ASIA.APPLE.COM
Comment:
RegDate: 1990-04-16
Updated: 2000-05-23
RTechHandle: ZA42-ARIN
RTechName: Apple Computer, Inc.
RTechPhone: +1-408-974-7777
RTechEmail: [email protected]

DNG, XMP, and Exporting

The following pertains to Lightroom 1.1 (and possibly only to the Mac version on an Intel Mac with OS 10.4.10).
I have searched Lightroom 1.1 Help, the knowledge-base, this forum, and elsewhere for simple instruction on how to do either of the following:
Task #1: Create a separate XMP sidecar file from a DNG file for which the metadata relating to picture adjustments made in the Develop module has been embedded in the DNG file or stored in the Lightroom database.
Task#2: Export a DNG file (for which the development metadata has been embedded in the DNG file or stored in the Lightroom database) while at the same time creating a separate XMP file that contains the development metadata.
I did some experimenting relating to Task #2:
In Lightroom, I set the exposure of a DNG file to +4.00 in the Develop module, then switched to the Library module and clicked on the menu item "Metadata > Update DNG Preview & Metadata", and then exported with "Original" selected as the file format. Immediately after this, I set the exposure to -4.00, without updating, and then exported with "Original" selected as the file format. Immediately after this, I exported with "DNG" selected as the file format.
Here's what I found:
1. Looking at the thumbnail preview for each in Mac OS 10.4.10's Finder window: Exports 1 & 2 look like the picture did the last time I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. with +4.00 exposure). Export 3 looks like the picture did at the time of the second and third exports (i.e. with -4.00 exposure). Opening any of these files within Mac OS X's Preview application shows the original state of the file without ANY of the development adjustments made before exporting.
2. Looking at the pictures in Adobe Camera Raw 3.7 (because I have only Photoshop CS2): Export 1 looks like the picture did the last time I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. with +4.00 exposure). Exports 2 & 3 look like the picture did at the time of the second and third exports (i.e. with -4.00 exposure). No subsequent changes occur by going on to open the files within Photoshop CS2 after they are displayed in ACR 3.7.
3. Looking at the pictures after re-importing into Lightroom: Export 1 looks like the picture did the last time I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. with +4.00 exposure). Export 3 looks like the picture did at the time of the second and third exports (i.e. with -4.00 exposure). For a few seconds, export 2 looks like the picture did the last time I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. with +4.00 exposure). Then it switches to look like the picture did at the time of the second and third exports (i.e. with -4.00 exposure). It seems this has something to do with thumbnail previews being already embedded in the files and with Lightroom displaying them temporarily before updating them.
4. All three exports, when re-imported into Lightroom, begin with two snapshots already in the Snapshots panel of the Develop module: "Import" & "Import 2". "Import" is the original file condition when the file was first imported into Lightroom (before any of my export experiments). "Import 2" is the state of the file at the time I exported it, not the state when I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. "Import 2" is with -4.00 exposure) EVEN IF THE CATALOG IS DELETED AND A NEW ONE CREATED BEFORE IMPORTING THESE, THE SAME THING OCCURS.
In none of these scenarios was an XMP file created. This had me wondering whether XMP files were possible at all in conjunction with DNG files. On to...
Task #1:
Now, as I was beginning to think that the only solution for creating XMP files from DNG files was to have Lightroom set up to maintain metadata in XMP files instead of in its own database (i.e. full-time XMP files as opposed to XMP files created only when exporting), I tried to alter settings in Lightroom's preferences, clicking menu

(to Lee Jay: Yes, as I found out.) Here's the rest of my post:
...items and buttons in this sequence: Preferences > General > Go to Catalog Settings > Metadata. Nothing I tried with the settings there would induce Lightroom to create XMP files alongside DNGs.
AFTER MORE WORK WITH JPGs AND CANON RAW FILES (.CR2), I FOUND THAT I COULD CREATE XMP FILES FOR THE CANON RAW FILES ONLY.
My conclusions are:
1. Lightroom writes separate XMP sidecar files for 3rd-party proprietary RAW formats only. This view is supported by the verbiage under these headings in Lightroom Help: "About metadata and XMP" and "Synchronize metadata with Adobe Camera Raw and Bridge".
2. This means that, for other formats, enabling the following catalog settings under Preferences does not result in separate XMP files: "Write develop settings to XMP for JPG, TIFF, and PSD", "Automatically write changes into XMP".
3. Also, for the other formats, enabling these catalog settings either does not alter the files at all or else alters them in a way that shows up only within Lightroom, Photoshop CS3, and any other applications that use Adobe Camera 4.0 or later. My additional export/re-import experimentation with JPGs in Lightroom suggests the latter is the case.
4. In Lightroom settings and documentation, "to XMP", "into XMP", etc. mean "to the XMP data embedded within the file", "into the XMP data embedded within the file", etc., except for those cases in which the associated file format is 3rd-party proprietary RAW, where these phrases mean "to a/the separate XMP sidecar file", "into a/the separate XMP sidecar file", etc.
5. The problem that seems to remain is that, apparently, not all non-Adobe software that can read DNG files is able to view changes made to these files by Lightroom (e.g. Mac OS X Preview).

Problem in deploying and packaging the application and web component.......

i am new to j2ee!! i am using sun application server 8 2005Q1(for j2ee)
i have deployed my application successfully!!!!!
yet i found an error(404) when i called it thro my web browser
i am using oracle as my back end
anybody plz help me as soon as possible.........

Hi,
I am not sure what some of your phrases mean but i want to clarify a couple of things.
0) Be happy to make the switch
1) SJAS contains a webserver, where iPlanet appserver did not and one was forced to put a webserver in front of the appserver.
2) The iplanet webserver plugin was configured to forward all request which have /NasApp to the appserver, using the KCP protocol, SJAS LB plugin is configured on a webapplication context root base using http and or https protocol.
3) If your logic needs the HTML pages (which is doubtful in a proper design) the pages must reside on the appserver.
4) Deployment to SJAS can be done through asadmin CLI, deploytool or webbased admin GUI instead of just putting the EAR in the autodeploy directory.
HTH Robert

Why are letter documents defaulting to folio when I try to print?

A couple of my coworkers are having this problem, wherein I forward them a PDF and they open it with the free Adobe, and when they try to print it, the printer waits for a promt for a special size of paper. After doing some digging, the size it's looking for is the folio or 8.5x13 size paper. We can simply put letter in the tray but it seems to try to resize the document to fit on the folio so we lose the bottom chunk of the document. If I print it from mine though, it has no problem printing as letter. This happens with several people, but not all. Going into the settings, we can't find anything indicating why it would print this size. Even when we try to force it to print letter by selecting it, and the tray with letter paper, it still ends up changing it to the folio size and taking paper exclusively from the multipurpose tray. The printer we are using if it's relevant is the Kyocera Taskalfa 4550ci. We just can't seem to pin down the source of this, so we don't know how to fix it. We have already tried asking our printer company, as well as our IT support, none of whom can seem to solve or find the source of the problem. This doesn't happen in any other program, only with Adobe. I'm a relatively basic user so please just assume I don't know what any shortcuts or short form phrases mean. Thanks for your time!

I think I did mention it was the free version. Under Help the staff having the problems is Adobe Reader XI (am I in the totally wrong place in the forum? It's super confusing trying to navigate here, sorry). And it is Windows.

Metadata phrase meaning

Similar Messages

Maybe you are looking for