Elements 12 & Lightroom 4 issues

I just purchased Elements 12 and use it with Lightroom 4. I can transfer a file to Elements with ease but when I try to transfer it back by hitting file/save, it opens a dialogue box instead of transfering me back to Lightroom and then I have to import it again. Can anyone help?

It should show the same filename that was created by Lightroom, usually has "-edit" in the name, and the same folder as the original.
If that's not what you see, you'll have to give us more details,  specifically the name and folder of the file created by Lightroom and the name and folder that PSE wants to use fit the save.

Similar Messages

  • PS Elements/Lightroom issues

    Hi, Could anyone help me with an issue using Lightroom and PS Elements. When I move from Lightroom to edit in PS Elements, I loose my saved image. It does not show back in Lightroom as everyone tells me it should. I have tho save it somewhere else. Any ideas would be welcome. Thanks Barry from MM

    You need to start the round trip from LR as follows and use the save command (Ctrl+S) not save as:
    1) Ctrl+E in the Library to export selected image with develop settings (I choose PSD) or right-click and choose Open In PSE
    2) Edit in PSE; then Ctrl+S to replace (overwrite) Lightroom export copy
    3) Ctrl+W to close in PSE and update Lightroom thumbnail.
    On Mac OSX Cmd+E; Cmd+S; Cmd+W
    The important point is to overwrite the LR export copy by using File >> Save (Ctlr+S) because if you use “Save As” you create a new document which LR knows nothing about.

  • Premiere Elements 13 issue with the mouse on When I select a clip of video and move to a different place in my time line, Premiere Elements 13, will not release the clip rom the mouse.    The clip follows my mouse movements and goes to other places in my

    Premiere Elements 13 issue with the mouse on MAC OSX Yosemite 10.10.1
    When I select a clip of video and move to a different place in my time line, Premiere Elements 13, will not release the clip from the mouse.
    The clip follows my mouse movements and goes to other places in my time line.
    I try to delete these extra insertions, but the mouse will not release the clip.
    Action I’ve taken: I’ve re-installed Premiere Elements 13. Problem remains.
    This issue has consumed too much of my time and does not go away.  It ruins my video.
    Help please.
    Thanks

    I tried using the Guest Account on my Mac. In the Guest Account, Illustrator works perfect!
    Then I started wondering what processes (tools/tweaks) I run by default on my account. Turned out the problem was called by a little background tool called RightZoom. RightZoom let's the green 'zoom' button always maximize your current window.
    So thanks! Problem solved!

  • Is there a phone number I can call to talk to a live person about help with Lightroom issues ?

    Is there a phone number I can call to talk to a live person about help with Lightroom issues ?

    well the reason I wanted to talk to someone live because it would take forever to explain everything on here But anyway, here goes. I have an HP Pavilion Notebook with Intel Core i5-323om CPU @2.60 GHz and 8 gb ram 64bit. I am trying to run Lightroom 5.7 on my laptop and having major issues. I use an external hard drive for the storage of my photos. When I try to use Lightroom I run into many issues: Flickering of the screen, freezing up, slow, the loading circle just goes round and round lol. If I go to the washroom or leave the computer for even a minute it freezes up. I have to keep pressing Ctr/alt/delete to bring it back when it flickers. I have to constantly exit out of the program and restart it to be able to edit even just a couple of photos and then it starts acting up again.
    I have tried un-installing and re-installing, updating everything on my pc, changing compatibility settings, updating development settings, I even took the laptop into have it looked at and they did all kinds of updates etc...and still couldn't figure out why it wasn't working for me. I have gone through the lists of troubleshooting for LR problems and there just seem to be nothing that works.....I have made new catalogues, moved them, tried using the software on my pc without the EHD, etc etc.......I have tried EVERYTHING...I think.....so I was looking for some answers as to why this is happening....

  • Photoshop Elements & Lightroom Set-Up

    Hi! 
    I have Adobe Photoshop Elements 11, Premiere Elements 11, Lightroom 4, an external hard drive, and a MacBook Pro, but I'm not sure where to start. 
    1. I'm particularly wondering if I should download the software onto my computer, and put my photos onto the external hard drive (I thought it would be best to put my photos on the external hard drive, as to save my computer's memory, but am not sure if the software will be able to access the photos there)?  What is the best set-up?
    2. If the software on the computer can "find" the photos on the external hard drive, will the photos essentailly be saved onto my computer when I edit them with the software?  If so, wouldn't this slow down my computer (or is there a way around this)?
    3. Do these programs (e.g. Photoshop, Elements, Lightroom) work together?  If so, how do I set them up to do this and use them this way?
    4. How do I transfer the photos from my old computer to the external hard drive? 
    5. How do I transfer the photos from my phone to the external hard drive?
    6. Do you have any other set-up or organization tips/resources?
    Thanks a bunch!
    A

    I don't want to seem flippant, but that's exactly what I did - Actually I set up 2 presets here (one for Adobe RGB & one for sRGB).
    As I stated previously, I set these up on 2 different computers (a MacPro and a MacBook Pro), each computer running a different version of OS-X (Lion & Mavericks, respectively).
    I have successfully set up several external editors using various stand-alone programs - they all still work -- with the exception of Photoshop Elements 12.

  • What level of Photoshop (Elements, Lightroom, CS6) would I need

    We have 8" x 10" radiochromic film (like conventional x-ray film, except that it self develops without chemical solutions) that has a reflective backing built in (doubles the path length through the sensitive emulsion).
    I want to do a reflective scan (very easy with VueScan) and then do two things to the resulting TIFF file:
    1. Use a histogram to adjust the black and white levels to optimize contrast for the image.
    2. Change the greyscale range to a color range using a linear transformation (i.e., 0 = black, goes to red; 255= white, goes to blue) for easier viewing .
    What level of Photoshop (Elements, Lightroom, CS6) would I need to do this?
    Thank you

    For simple file manipulation Photoshop Elements would be enough and in your case the best.

  • LEAD Codec for MotionJPEG-Premiere Elements Playback Issues

    There are several reports online (here and elsewhere) recommending installing LEAD Codec for MotionJPEG-Premiere Elements Playback Issues. Most, if not all, of the feedback is that it works and is only $10 USA dollars.
    Today I went in search of that codec at LEAD Technologies and could not find a $10 LEAD Codec.
    http://www.leadtools.com/SDK/Multimedia/Multimedia-MCMP-MJPEG-codec.htm
    Instead, I found a bunch of kits priced at way over $100.00.
    From the chat service at that web site, I discovered that the LEAD codec is no longer sold separately. In order to get that codec, you would have to buy the Multimedia SDF Kit (priced $595.00).
    Any workaround suggestions
    OR
    pay the $595.00 to get the LEAD Codec
    OR
    go the file conversion route for the MotionJPEG?
    ATR

    ATR,
    Great news!
    On the PrPro forum, it's been 100% for MainConcept, and 99% for Morgan. One user could not get the Morgan to work on his/her system, but that could well have been OE on that poster's part. Still, those are not bad odds, and the 'cost" of the Morgan is better...
    Just glad that it worked for you.
    Good luck,
    Hunt

  • Can I get a phone contact number for Adobe Premire Elements tech issue?

    Can I get a phone contact number for Adobe Premire Elements tech issue?

    If your issue is about purchasing or downloading or installing a product, then Adobe Support is available via Chat.
    If it is about how to use the product to do something then the forums and web and video tutorials are the ways to get your questions answered.

  • Is it possible for one camera to work and one not in lightroom and be a lightroom issue? Nikon says

    My son and I purchased Nikon D7100s.  Mine works fine.  He was having trouble getting his raw files into lightroom 4.4.  He came over to my house and used my computer still having the same issues.  He can read the raw fine in ViewNX2 but not in his lightroom, my lightroom or elements 11.  Nikon says it is an issue with Adobe...Is this possible?  He is probably going to return the camera...

    Strange coincidence:
    Earlier this evening I was on the Exiftool homepage to download a new version. And I noticed a repair tool I had never seen before and have no use for since I don't own a Nikon camera. And then I came here and saw your thread...
    You may want to try the tool here:
    http://owl.phy.queensu.ca/~phil/exiftool/fix_corrupted_nef.html
    Phil Harvey only writes that it repairs file from D4, D600, D800, D800E and D3200. But it is worth trying anyway, I think. If it doesn't work, contact him. He often implements changes very fast.
    Your son may also want to consider if he should continue using Nikon software to download the photos from the camera. This excerpt from the above mentioned link doesn't sound very reassuring:
    [Note that Nikon doesn't learn from their mistakes, and a similar problem happened 2 years ago with an older version of Nikon Transfer and the D5000 -- read here. The moral is: Don't use Nikon Transfer or any other utility that modifies the file to download your precious images!]

  • Photoshop Elements, Lightroom and Nik Software Lightroom Edition experience working together?

    I have Photoshop Elements 10 and number of plugins, like Topaz Labs ones. I have also just acquired Lightroom. I do want to get CS5 eventually but that is not in the near future.
    I am thinking of getting Nik Software's Complete Collection. It does not support Elements 10, but it does support Lightroom. So solution seems easy, just use it in Lightroom. That solution could also result in $200 saving as edition that includes support for Photoshop and Lightroom is right now $399 while one that supports just Lightroom (and Aperture but that is not of relevance to me as I am a Windows user) is $199.
    However, I do not want to lose benefits of other plugins I have so going with solely Lightroom edition means increased going back and forth between Photoshop and Lightroom.
    So question for those experienced with 3 of these together: Do you foresee issues with getting edition that just supports Lightroom? What things I might feel are missing / might frustrate me with this approach?

      I’ve not used Nik Software but have used Lightroom and PSE together and the two programs integrate well. If Elements was already installed Lightroom should automatically recognize it as your external editor otherwise you need to set up external handling in Lightroom preferences.
    I assume any changes made in Lightroom with a Nik plug in will register as part of the Lightroom Develop settings. Is that how it should work?
    My usual routine is to highlight an image in the Lightroom Library and then
    1) Press Ctrl+E to edit in photoshop - choose PSD with Lightroom settings
    2) Image opens automatically in PSE Editor
    3) Do further editing in PSE and press Ctrl+S to save an overwrite the Lightroom export copy. Click OK
    4) Press Ctrl+W to close the saved PSD file which automatically updates the Lightroom thumbnail.
    It all works quite seamlessly. Use the PSD copy in light room to export a jpeg or any other format of your choosing.
     

  • WebI report on SAP Mobile BI for iOS that contains a chart with element linking issue

    Hi gurus. I have the following issue:
    I have element linking based filters on my chart # 1 to filter values on chart # 2.  It worked fine on Ipad. And it worked fine on BI Launch Pad.
    But after some time I check my webi report and it stopped working on IPAD.
    Filters are not shown on the graph.
    However it still works fine on BI LaunchPad
    Have you faced this issue before?
    Using: BI mobile 5.1.12
    Before, example:
    After some time, I opened sap mobile and it is not showing up the filter anymore
    Now: We upgraded to SAP Bi Mobile 6.0.8.12 but issue persists.
    Could you do the test?
    Steps to reproduce:
    Create a simple Webi report with a table.
    Copy that table and paste it to the report.
    Turn the original table into a column chart
    Add element linking from the chart to table. (When user filters on the chart it should change the table as well)
    Test that the element link works in BI LaunchPad.
    Save the report to the Mobile category and test on iPad.
    Open report on iPad
    Tap chart bars. Yellow filters, that are supposed to show up, are not displayed.

    Hi Erika,
    Is this report element linking defined as 'All Objects' or 'Single Object' in Webi.
    I ask this that report element linking on 'All Objects' is not supported yet. This support is expected to come in later releases.
    However, if this is single object then it should be working. Can you verify this on latest app store build and confirm. If still it does not work for you, then please raise a support ticket for the same.
    Regards,
    Ashutosh

  • ACR 4.1 Issue - Lightroom Issue with Nikon D40x Raw Files

    I am running Windows Vista and CS3 and am trying to process Nikon D40x raw files (NEFs) using ACR 4.1. The images come up properly in Bridge. However, when I try to add metadata using a metadata template, I get the error: "There was an error writing metadata to DSC_130.NEF." When I try to rotate an image in Bridge, I get the same error. If I try to do a Batch Rename, the name does not change. If I double-click on the image, it opens properly in ACR and the image can be rotated in ACR, and it then appears rotated in Bridge.
    I also tried importing the D40x images in Lightroom. The following error appeared: "Problem Importing Files. The following files were not imported. The files appear to be unsupported or damaged."

    Jeff,
    I installed camera raw.8bi (size is 10,187kb)in
    c:\Program Files\Common Files\Adobe\Plug-Ins\CS3\File Formats
    I'm beginning to think this is a Windows Vista issue. I just installed ACR 4.1 on my XP laptop and it works fine. For both the Vista machine and the laptop, my raw files are on an external drive. If I move the raw files on the Vista machine from the external drive to the c: drive, there is no problem. I'm exploring whether there is some permissions issue in Vista that is not allowing me to write to the raw files if they are on an external drive. Ain't new operating systems just great fun!
    Thanks!

  • Adobe photoshop elements 12 issue

    my adobe photoshop elements 12 organizer keeps stopping? anyone know why?

    For what it's worth: On my PC running 64-bit Windows 7, I found that PSE 12.0's Organizer simply stopped working (crashed) for no apparent reason from time to time. After updating to PSE 12.1 a few weeks ago, Organizer hasn't crashed a single time. Whether 12.1 addressed stability issues, I have no idea. Perhaps it's just my imagination, but 12.1 does seem to be more stable.

  • WSDL, custom datatypes, fault element name issues

    Hello all,
    I am having a LOT of problems with BEAs webservices. I am posting
    this here in the hope that someone can help me and tell me what I am
    doing incorrectly. I am running
    WebLogic Server 7.0 SP1 Mon Sep 9 22:46:58 PDT 2002 206753
    WebLogic XMLX Module 7.0 SP1 Mon Sep 9 22:54:41 PDT 2002 206753
    Background:
    My goal is to make my company's product web services aware. I take an
    EJB, try to run it through the standard ant tasks and generate a web
    services accessible EJB. Sounds pretty easy, but complex types seem
    to make this quite difficult.
    I have been able to create a web service accessible EJB (only since
    7.0.1), but I am quite unhappy with the quality of what I am able to
    produce.
    I have a datatype which acts as a key, but it does not follow the
    javabeans idiom - i.e. it does not have a default constructor or
    accessor methods and I am not in the position to change it. I have
    created a codec for this class which works and an xml schema (both by
    hand). Its name is AgentKey. I have also had to use the autotyper to
    create codecs and typemapping entries for java.util.Properties,
    I can connect using the WebLogic classes and I am now trying to
    interact using MS Excel and Apache's Axis as my test clients.
    Issues:
    My first question deals with generating a client. There seem to be
    two ways to generate a client. Firstly via the <client> subtask of
    <servicegen><service>, the second way via <clientgen> task. Since I
    am using a custom data type (AgentKey) I have to manually insert the
    AgentKey schema into the web-services.xml file generated by
    servicegen. When I try to generate a client via the
    servicegen/service/client task there is no opportunity for me to
    insert this datatype schema information and I therefore get the
    following messages (lots of them, but I'm only including one):
    [servicegen] WARNINIG: Unable to find a javaType for the xmlType:['java:net.agentis.apml.runtime']:AgentKey.
    Make sure that you have registered this xml type in the type mapping
    [servicegen] Using SOAPElement instead
    BTW: I am also receiving the same problem with java.util.Properties.
    BTW: WARNING is misspelt
    If I attempt to generate a client class via the <clientgen> task, I
    need to supply either a wsdl or ear file as a parameter. I cannot
    supply a wsdl file because I haven't deployed the EAR yet (and I don't
    want to until the EAR has the client classes in it), and I can't
    supply the EAR because I want the ear to include the client classes.
    It is a bit of a catch 22 situation. Is there a solution I can't see?
    NOTE: it would be very, very nice if you added a schemaMapping
    attribute to the <servicegen/service> task so the web-services.xml
    file didn't have to be manually hacked. Something similar to the
    typemapping attribute already in the servicegen/service task would do
    it.
    My next problem deals with the validity of the WSDL. I am seeing that
    the WSDL created has exceptions defined multiple times. I saw a
    message from Manjo saying that it looked like a bug. I agree and
    would like to get a copy of the patch. On a more significant note,
    when is either SP2 or 7.1 due for release?
    Another problem with the WSDL (once you have cleansed the multiple
    exception messages) is that the fault elements of the
    binding/operation elements require names and they don't have any. For
    example, this is straight from the deployed EJB WSDL file:
    <binding name="ExampleAgentPortSoapBinding" type="tns:ExampleAgentPort">
    <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="serviceWithPrimitiveDatatypes">
    <soap:operation soapAction="" style="rpc"/>
    <input>
    <soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
    </input>
    <output>
    <soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
    </output>
    <fault>
    <soap:body use="encoded" namespace="http://sillyurl.com/reallysilly"
    encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
    </fault>
    </operation>
    <operation ...
    The schema definition at http://schemas.xmlsoap.org/wsdl/ says the
    fault element require a name attribute:
    <complexType name =" tBindingOperationFault">
    <complexContent>
    <extension base="wsdl:tExtensibleDocumented">
    <attribute name="name" type="NCName" use="required"/>
    </extension>
    </complexContent>
    </complexType>
    The name of the fault should be the same name as the fault in the
    portType definition. In my example the name is "AgentisException" as
    evidenced by this snippet:
    <portType name="ExampleAgentPort">
    <operation name="serviceWithPrimitiveDatatypes">
    <input message="tns:serviceWithPrimitiveDatatypes"/>
    <output message="tns:serviceWithPrimitiveDatatypesResponse"/>
    <fault name="AgentisException" message="tns:AgentisException"/>
    </operation>
    Once these changes have been made then the WSDL will validate. Are
    there plans to fix these bugs?
    On a different note, when I try to interact with a method that uses a
    custom data type, such as AgentKey, via the "WebLogic Webservice
    standard testing home page" the custom data type without a default
    constructor cannot be rendered correctly. For instance, the AgentKey
    value is:
    <!-- Do not know how to create a sample instance for this part due to the following
    exception:java.lang.InstantiationException: net.agentis.apml.runtime.AgentKey.
    Pls replace this with the correct XML before invoking the service. --->
    <agentKey/>
    Since I can't deploy a valid WSDL, I can't get either Axis or Excel to
    connect to my web services.
    When I attempt to invoke Axis' (beta 1.1) wsdl2java I recieve the
    following message.
    java.io.IOException: ERROR: Fault is missing a name= attribute in operation
    "serviceWithPrimitiveDatatypes", in binding {http://sillyurl.com/reallysilly}ExampleAgentPortSoapBinding.
    This seems understandable considering the issues I mentioned earlier.
    Unfortunately Excel doesn't really give me anything to go with. If I
    type in the WSDL URI then it will give me a list of methods I can
    invoke, but if I try to add the service I get the very unhelpful "The
    Web Service References Tool could not generate the requested code.
    Any changes that were made to your project have been rolled back."
    Any help with those two issues would be greatly appreciated also.
    One final issue is that I cannot seem to fix is taskdef'ing
    <servicegen> properly from Ant. I can do the actual taskdef but then
    it cannot find classes from within the weblogic.jar. If I run the
    setExamplesEnv.cmd first the I don't need to do the taskdef and
    everything works fine. Has anyone else had this issue? (we can't run
    that command on our clients desktops before we build our build scripts
    - anyway, I've put it down to one of those weird Ant classpath
    issues.)
    In summary:
    Problems I can see and would like some help on are:
    - multiple exception messages
    - fault operations with no name
    - the ability to generate client code with complex data types before
    the EAR is deployed.
    Could the product team add
    - a clean way to add in schema datatypes without having to manually
    hack the web-services.xml file.
    I know this has been quite a long email, but it has been months in the
    making. Anyone's time would be greatly appreciated.
    Mark Mansour
    Agentis Software
    [email protected]

    Hi Mark,
    From your base post:
    My next problem deals with the validity of the WSDL. I am seeing that
    the WSDL created has exceptions defined multiple times. I saw a
    message from Manjo saying that it looked like a bug. I agree and
    would like to get a copy of the patch. On a more significant note,
    when is either SP2 or 7.1 due for release?I would recommend starting here with support since getting valid WSDL seems to be the root of most of
    your issues.
    Concerning the upcoming release, I believe it is scheduled for late this quarter; contact Michael
    ([email protected]) for more information.
    Also, at the bottom of this post:
    I would just like to see an automated way to do this (I've had to write my own
    utility to do this for me :(Does the autotype ant task help in this situation? Have you taken a look at this?
    http://e-docs.bea.com/wls/docs70/webserv/anttasks.html#1080062
    Thanks,
    Bruce
    Mark Mansour wrote:
    Hiya Bruce,
    I will try and get some time to follow this up with the support people too.
    In response:
    Problems I can see and would like some help on are:
    - multiple exception messages
    In your client code, you can set the following property to avoid the exceptionmessages so that the typemapping
    registry can be setup.
    //dont parse wsdl till we set the typemapping
    System.setProperty( "weblogic.webservice.servicenamechecking","false" );
    This is not a client issue. The WSDL is generating incorrect WSDL. Here is a
    little snippet :
    <message name="AgentisException" >
    <part name="AgentisException" xmlns:partns="http://www.w3.org/2001/XMLSchema"
    type="partns:string" />
    </message>
    <message name="setTraceLevel" >
    <part name="agentKey" xmlns:partns="java:net.agentis.apml.runtime" type="partns:AgentKey"
    />
    <part name="intVal" xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:int"
    />
    </message>
    <message name="AgentisException" >
    <part name="AgentisException" xmlns:partns="http://www.w3.org/2001/XMLSchema"
    type="partns:string" />
    </message>
    As you can see the AgentisException is defined twice (in my real WSDL it is redefined
    every time a method has the AgentisException in its interface (which in my case
    is 5 times))
    - fault operations with no nameI believe the fault issues that you have raised have been addressed in the upcomingrelease that will be
    available for beta testing shortly. Contact [email protected] if you
    want to participate in the beta.
    great. Is there any ETA on the final release date?
    - the ability to generate client code with complex data types before
    the EAR is deployed.
    There is an example to show how to do this: http://dev2dev.bea.com/direct/webservice/dyncmplx.zip
    Unfortunately this doesn't solve my problem. I still don't have an EAR or WSDL
    file from which I can generate a client to be included in the final EAR file that
    gets deployed to the server. My original post explains this a bit better.
    Could the product team add
    - a clean way to add in schema datatypes without having to manually
    hack the web-services.xml file.
    Take a look at http://dev2dev.bea.com/direct/webservice/wswa.html#qz50 and others
    in this area.
    This was more in reference to the building of the web services in the first place
    rather than registering custom datatypes at runtime. The manual procedure is
    documented at http://edocs.bea.com/wls/docs70/webserv/customdata.html#1058102,
    I would just like to see an automated way to do this (I've had to write my own
    utility to do this for me :(
    Hope this helps,
    Bruce
    Thanks Bruce.
    Mark

  • Fault element name issues

    Back in January I noticed a post concerning generated WSDL files and fault
    element not containing a required attribute "name".
    I seem to be having the same problem in WLS8.1
    Can this be possible since it was fixed in version 7SP2?
    After I generate the web service, when I try to generate a JAXRPC client
    (via the JavaSoft web services toolkit), it complains that the WSDL file is
    invalid because there are <FAULT> elements without name attributes.
    Also, I'm having a problem using the clientgen Ant task, its having an error
    generating types. This worked 2 days ago when I was running 8.1beta, but
    since I upgraded to 8.1 it no longer works.
    M
    "Bruce Stephens" <[email protected]> wrote in message
    news:[email protected]...
    Hi Mark,
    From your base post:
    My next problem deals with the validity of the WSDL. I am seeing that
    the WSDL created has exceptions defined multiple times. I saw a
    message from Manjo saying that it looked like a bug. I agree and
    would like to get a copy of the patch. On a more significant note,
    when is either SP2 or 7.1 due for release?I would recommend starting here with support since getting valid WSDLseems to be the root of most of
    your issues.
    Concerning the upcoming release, I believe it is scheduled for late thisquarter; contact Michael
    ([email protected]) for more information.
    Also, at the bottom of this post:
    I would just like to see an automated way to do this (I've had to write
    my own
    utility to do this for me :(Does the autotype ant task help in this situation? Have you taken a lookat this?
    http://e-docs.bea.com/wls/docs70/webserv/anttasks.html#1080062
    Thanks,
    Bruce
    Mark Mansour wrote:
    Hiya Bruce,
    I will try and get some time to follow this up with the support people
    too.
    >>
    In response:
    Problems I can see and would like some help on are:
    - multiple exception messages
    In your client code, you can set the following property to avoid the
    exception
    messages so that the typemapping
    registry can be setup.
    //dont parse wsdl till we set the typemapping
    System.setProperty(
    "weblogic.webservice.servicenamechecking","false" );
    >>>
    >>
    This is not a client issue. The WSDL is generating incorrect WSDL.Here is a
    little snippet :
    <message name="AgentisException" >
    <part name="AgentisException"xmlns:partns="http://www.w3.org/2001/XMLSchema"
    type="partns:string" />
    </message>
    <message name="setTraceLevel" >
    <part name="agentKey"xmlns:partns="java:net.agentis.apml.runtime" type="partns:AgentKey"
    />
    <part name="intVal"xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:int"
    />
    </message>
    <message name="AgentisException" >
    <part name="AgentisException"xmlns:partns="http://www.w3.org/2001/XMLSchema"
    type="partns:string" />
    </message>
    As you can see the AgentisException is defined twice (in my real WSDL itis redefined
    every time a method has the AgentisException in its interface (which inmy case
    is 5 times))
    - fault operations with no nameI believe the fault issues that you have raised have been addressed in
    the upcoming
    release that will be
    available for beta testing shortly. Contact [email protected]
    if you
    want to participate in the beta.
    great. Is there any ETA on the final release date?
    - the ability to generate client code with complex data types before
    the EAR is deployed.There is an example to show how to do this:
    http://dev2dev.bea.com/direct/webservice/dyncmplx.zip
    >>
    Unfortunately this doesn't solve my problem. I still don't have an EARor WSDL
    file from which I can generate a client to be included in the final EARfile that
    gets deployed to the server. My original post explains this a bitbetter.
    >>
    Could the product team add
    - a clean way to add in schema datatypes without having to manually
    hack the web-services.xml file.
    Take a look at http://dev2dev.bea.com/direct/webservice/wswa.html#qz50
    and others
    in this area.
    This was more in reference to the building of the web services in thefirst place
    rather than registering custom datatypes at runtime. The manualprocedure is
    documented athttp://edocs.bea.com/wls/docs70/webserv/customdata.html#1058102,
    I would just like to see an automated way to do this (I've had to writemy own
    utility to do this for me :(
    Hope this helps,
    Bruce
    Thanks Bruce.
    Mark

    Please try 8.1 sp1, it is strictly wsdl spec complaint. It generates
    <fault> with name.. Clientgen requires fault name to correctly parse wsdl.
    thanks,
    -Neal
    "Mark Fine" <[email protected]> wrote in message
    news:[email protected]...
    Back in January I noticed a post concerning generated WSDL files and fault
    element not containing a required attribute "name".
    I seem to be having the same problem in WLS8.1
    Can this be possible since it was fixed in version 7SP2?
    After I generate the web service, when I try to generate a JAXRPC client
    (via the JavaSoft web services toolkit), it complains that the WSDL fileis
    invalid because there are <FAULT> elements without name attributes.
    Also, I'm having a problem using the clientgen Ant task, its having anerror
    generating types. This worked 2 days ago when I was running 8.1beta, but
    since I upgraded to 8.1 it no longer works.
    M
    "Bruce Stephens" <[email protected]> wrote in message
    news:[email protected]...
    Hi Mark,
    From your base post:
    My next problem deals with the validity of the WSDL. I am seeing that
    the WSDL created has exceptions defined multiple times. I saw a
    message from Manjo saying that it looked like a bug. I agree and
    would like to get a copy of the patch. On a more significant note,
    when is either SP2 or 7.1 due for release?I would recommend starting here with support since getting valid WSDLseems to be the root of most of
    your issues.
    Concerning the upcoming release, I believe it is scheduled for late thisquarter; contact Michael
    ([email protected]) for more information.
    Also, at the bottom of this post:
    I would just like to see an automated way to do this (I've had to write
    my own
    utility to do this for me :(Does the autotype ant task help in this situation? Have you taken a
    look
    at this?
    http://e-docs.bea.com/wls/docs70/webserv/anttasks.html#1080062
    Thanks,
    Bruce
    Mark Mansour wrote:
    Hiya Bruce,
    I will try and get some time to follow this up with the support people
    too.
    In response:
    Problems I can see and would like some help on are:
    - multiple exception messages
    In your client code, you can set the following property to avoid the
    exception
    messages so that the typemapping
    registry can be setup.
    //dont parse wsdl till we set the typemapping
    System.setProperty(
    "weblogic.webservice.servicenamechecking","false" );
    >
    This is not a client issue. The WSDL is generating incorrect WSDL.Here is a
    little snippet :
    <message name="AgentisException" >
    <part name="AgentisException"
    xmlns:partns="http://www.w3.org/2001/XMLSchema"
    type="partns:string" />
    </message>
    <message name="setTraceLevel" >
    <part name="agentKey"xmlns:partns="java:net.agentis.apml.runtime" type="partns:AgentKey"
    />
    <part name="intVal"
    xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:int"
    />
    </message>
    <message name="AgentisException" >
    <part name="AgentisException"
    xmlns:partns="http://www.w3.org/2001/XMLSchema"
    type="partns:string" />
    </message>
    As you can see the AgentisException is defined twice (in my real WSDL
    it
    is redefined
    every time a method has the AgentisException in its interface (which
    in
    my case
    is 5 times))
    - fault operations with no nameI believe the fault issues that you have raised have been addressed
    in
    the upcoming
    release that will be
    available for beta testing shortly. Contact [email protected]
    if you
    want to participate in the beta.
    great. Is there any ETA on the final release date?
    - the ability to generate client code with complex data types
    before
    the EAR is deployed.There is an example to show how to do this:
    http://dev2dev.bea.com/direct/webservice/dyncmplx.zip
    Unfortunately this doesn't solve my problem. I still don't have an
    EAR
    or WSDL
    file from which I can generate a client to be included in the final
    EAR
    file that
    gets deployed to the server. My original post explains this a bitbetter.
    Could the product team add
    - a clean way to add in schema datatypes without having to manually
    hack the web-services.xml file.Take a look at
    http://dev2dev.bea.com/direct/webservice/wswa.html#qz50
    and others
    in this area.
    This was more in reference to the building of the web services in thefirst place
    rather than registering custom datatypes at runtime. The manualprocedure is
    documented at
    http://edocs.bea.com/wls/docs70/webserv/customdata.html#1058102,
    I would just like to see an automated way to do this (I've had to
    write
    my own
    utility to do this for me :(
    Hope this helps,
    Bruce
    Thanks Bruce.
    Mark

  • Adobe Lightroom Issues

    Has anyone had any issues running Adobe Lightroom v1.2 in Leopard? Most notably not allowing you to get into the print module.

    Yeah, the Print module doesn't work at all for me. (v1.2)
    There's the odd graphical glitch here and there, mostly in the History panel in the Develop module, but everything else seems OK.

Maybe you are looking for