No proxy for elements in an FC Bundle

I've had this problem (randomly, it would seem), since we started using the FC Server 18 months ago. It's always been annoying but now it's impacting our workflow.
Here's the scenario:
Someone annotates an interview and an editor makes sub-clips from the annotations and uploads the FC Bundle to the server. The sub-clips show up as elements but DO NOT have proxies so no one and look at them using the client.
When I try to re-analyze the clip - nothing happens. Nothing happens on the client end - no jobs are spawned. And nothing happens on the server ends - Compressor remains silent and no new processes are started.
Help! This has gone from mildly annoying to a real show stopper.

Still confused as to what a bundle is then... I uploaded the FC project and all of the files in the browser are uploaded with it into a new folder on our edit-in-place device called "projectnamefcpmedia".
The assets are most definitely uploaded. I can see them in the folder on the edit-in-place device and the media is properly linked (to the edit-in-place device) when I check out the project.
We very rarely upload assets on their own. We usually upload them as part of an FC project file because most of our assets are only used in a single project. Most of the time the element (as well as the asset) has a proxy but we've found that, if the element doesn't have a proxy, there is no way of creating one even though it's properly linked and it displays a proxy as an asset.

Similar Messages

Error while creating a deployable proxy for a URL in NWDS

Hi ,
There is a requirement for calling a webservice in the .NET platform from JAVA using NWDS. The webservice of the server is pinged using the URL of the webservice. when the URL is passed in the WS navigator of CRD ( that is Development Server) , the response is retreived successfully . The version of NWDS is 7.0.23.
we are facing problem when we are trying to create a Deployable proxy in NWDS by using the following steps :
1) Create a Development Component
2) Select the Deployable Proxy
3) Create the Client Proxy Defintion of the created DC
At step 3 , when we giving the url or WSDL link like "http:// www3.authoring.syngenta/newswebservice.asmx?WSDL" (this is just for example) , it is showing as "Invalid wsdl or wsdl not found " . so that we are not able to procees further.
When we are trying to create proxy the for the WSDL link like " http:// www.authoring.syngenta/newswebservice.asmx?WSDL" , we are able to create successfully.
can anyone suggest why we are able to create the proxy for the URL "http:// www.authoring.syngenta/newswebservice.asmx?WSDL" and not for the other URL.
Any pointers or suggestions are very helpful.
Thanks and Regards,
Sreedevi

Late response I know, but I have solved a similar problem recently and thought I would share.
Firstly, the problem is not with the namespace. The "Namespace ..." part is just stating the namespace the "Incorrect Value" has. So this error is complaining about the value "Unknown" - which isn't very helpful.
It appears the SAP SE80 importer does not like elements like the following because it can't understand <s:element ref="s:schema" />. It appears this is a common thing to be included in .NET generated WSDLs.
<s:element minOccurs="0" maxOccurs="1" name="GetCursDynamicResult">      <s:complexType>          <s:sequence>               <s:element ref="s:schema" />               <s:any />          </s:sequence>     </s:complexType></s:element>
SAP will also not like this example as it does not support mixed content (see: http://www.w3schools.com/schema/schema_complex_mixed.asp)
<s:element minOccurs="0" maxOccurs="1" name="SaldoXMLResult">
     <s:complexType mixed="true">
          <s:sequence>
               <s:any />
          </s:sequence>
     </s:complexType>
</s:element>
You can "Fix" the problem in both cases by removing the offending text in a local copy of the WSDL file so remove line 4 in the first example and change line 2 in the second to <s:complexType> the proxy can then be generated. No idea if the resulting service will be fully operational though!

Failed to create Proxy for EMFBuilder Service

Hi,
Am installing Eclipse Gemini & Eclipselink as JPA provider in Felix container.
Both bundles are installed fine. After having my persistence bundle that has entity classes & persistence.xml, am getting below error.
Though the persistence bundle also installed with Active status & EntityManagerFactory got initialized, still getting the below error.
Need someone's help on this as soon as possible.
Thanks
Mani
*** FATAL ERROR *** ServicesUtil - Failed to create proxy for EMFBuilder service
28.06.2015 09:17:51.013 *ERROR* [OsgiInstallerImpl] ERROR: EventDispatcher: Erro
r during dispatch. (java.lang.RuntimeException: ServicesUtil - Failed to create
proxy for EMFBuilder service: )
java.lang.RuntimeException: ServicesUtil - Failed to create proxy for EMFBuilder
service:
at org.eclipse.gemini.jpa.GeminiUtil.fatalError(GeminiUtil.java:133)
at org.eclipse.gemini.jpa.ServicesUtil.createEMFBuilderProxy(ServicesUti
l.java:483)
at org.eclipse.gemini.jpa.ServicesUtil.registerEMFBuilderService(Service
sUtil.java:286)
at org.eclipse.gemini.jpa.ServicesUtil.registerEMFServices(ServicesUtil.
java:157)
at org.eclipse.gemini.jpa.GeminiManager.registerPersistenceUnits(GeminiM
anager.java:262)
at org.eclipse.gemini.jpa.PersistenceBundleExtender.registerPersistenceU
nitsInBundle(PersistenceBundleExtender.java:292)
at org.eclipse.gemini.jpa.PersistenceBundleExtender.bundleChanged(Persis
tenceBundleExtender.java:390)
at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerC
allback(EventDispatcher.java:869)
at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(
EventDispatcher.java:790)
at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(Event
Dispatcher.java:515)
at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4409)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:2142)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2070)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:976)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:963)
at org.apache.sling.installer.core.impl.tasks.BundleStartTask.execute(Bu
ndleStartTask.java:93)
at org.apache.sling.installer.core.impl.OsgiInstallerImpl.executeTasks(O
sgiInstallerImpl.java:733)
at org.apache.sling.installer.core.impl.OsgiInstallerImpl.run(OsgiInstal
lerImpl.java:247)
at java.lang.Thread.run(Thread.java:724)
Caused by: java.lang.IllegalArgumentException: interface org.osgi.service.jpa.En
tityManagerFactoryBuilder is not visible from class loader
at java.lang.reflect.Proxy.getProxyClass0(Proxy.java:487)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:722)
at org.eclipse.gemini.jpa.ServicesUtil.createEMFBuilderProxy(ServicesUti
l.java:480)
... 17 more

Try turning on debug and posting the output. See here for instructions.
-Mike

How do I move Photoshop Elements and PS Premier bundle to new computer

I bought a new computer and would like to move Photoshop Elements and PS Premier bundle to the new computer. What is the procedure?
Thanks,
Jimmy

Sorry Claudio, I was in the wrong forum. Thanks for bringing it to my attention.
Jimmy

I am facing error while running Quickpay in Fusion payroll that "The input value Periodicity is missing for element type KGOC_Unpaid_Absence_Amount. Enter a valid input value". Any idea?

I am facing error while running Quickpay in Fusion payroll that "The input value Periodicity is missing for element type KGOC_Unpaid_Absence_Amount. Enter a valid input value". Any idea?

This is most probably because the Periodicity input value has been configured as "Required" and no value has been input for it.
Please enter a value and try to re-run Quick Pay.

[Error ORABPEL - 10900]... : Can not find definition for element 'process'

Hi,
When I try to deploy a bpel process using JDeveloper I'm having the following xml parse error:
Error(21):
[Error ORABPEL-10900]: xml parser error
[Description]: in line 21 of "file:/C:/JDeveloper/jdev/mywork/NERGA/CriarProjectoSA/bpel/CriarProjectoSA.bpel", XML parsing failed because file:/C:/JDeveloper/jdev/mywork/NERGA/CriarProjectoSA/bpel/CriarProjectoSA.bpel<Line 21, Column 63>: XML-24538: (Error) Can not find definition for element 'process'.
[Potential fix]: Fix the invalid XML.
I don't understand why... Any idea?

Ok.
This is my BPEL code. The sapattern tags are from a program that is generating part of the code. The JDeveloper doesn't show any error, I only get the error when I try to deploy.
<?xml version = "1.0" encoding = "UTF-8" ?>
<process name="CriarProjectoSA"
targetNamespace="http://xmlns.oracle.com/CriarProjectoSA"
suppressJoinFailure="no"
xmlns="http://xmlns.oracle.com/CriarProjectoSA"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:ns4="http://xmlns.oracle.com/CriarProjectoSA"
xmlns:ns7="http://xmlns.oracle.com/bpel/services/IdentityService/xpath"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ns5="http://schemas.oracle.com/xpath/extension"
xmlns:ns6="http://xmlns.oracle.com/bpel/workflow/xpath"
xmlns:ns11="http://www.oracle.com/XSL/Transform/java/oracle.tip.esb.server.headers.ESBHeaderFunctions"
xmlns:ns9="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc"
xmlns:ns1="http://xmlns.oracle.com/ValidacaoProjectos"
xmlns:ns3="http://www.nerga.pt" xmlns:ns2="http://tempuri.org/"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:ns10="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
xmlns:ns8="http://schemas.xmlsoap.org/ws/2003/03/business-process/">

<sapattern>
<guid>41207640-d934-480f-902a-b3764f3d9c9f</guid>
</sapattern>
<partnerLinks>
<partnerLink name="client" partnerLinkType="ns4:CriarProjectoSA"
myRole="CriarProjectoSAProvider"/>
<partnerLink name="NergaIS" partnerLinkType="ns2:ServiceSoap_PL"
myRole="ServiceSoap_Role" partnerRole="ServiceSoap_Role"/>
<partnerLink name="ValidacaoProjectos"
partnerLinkType="ns1:ValidacaoProjectos"
myRole="ValidacaoProjectosRequester"
partnerRole="ValidacaoProjectosProvider"/>
<sapattern>

<guid>e728e550-f404-47bf-aa13-72429480cbc6</guid>
<guid>3111d1af-0b31-4d02-b3fc-73d14ce95405</guid>
<guid>e9cdca59-888a-4e67-af54-a63ce2347ad3</guid>
</sapattern>
</partnerLinks>
<variables>
<variable name="outputVariable"
messageType="ns4:CriarProjectoSAResponseMessage"/>
<variable name="inputVariable"
messageType="ns4:CriarProjectoSARequestMessage"/>
<sapattern>

<guid>2503e820-3add-4cd1-bbc5-5cc5fff57090</guid>
<guid>8bcc3532-46b7-4e88-816f-72ecdaee76ab</guid>
</sapattern>
<variable name="invocaVP_initiate_InputVariable"
messageType="ns1:ValidacaoProjectosRequestMessage"/>
<variable name="recebeVP_onResult_InputVariable"
messageType="ns1:ValidacaoProjectosResponseMessage"/>
<variable name="InvocaAdicionarProjecto_InputVariable"
messageType="ns2:AdicionarProjectoSoapIn"/>
<variable name="InvocaAdicionarProjecto_OutputVariable"
messageType="ns2:AdicionarProjectoSoapOut"/>
</variables>
<sequence>
<receive name="recebeTemplate" joinCondition="False" partnerLink="client"
portType="ns4:CriarProjectoSA" operation="process"
variable="inputVariable" createInstance="yes">
<sapattern>

<guid>e728e550-f404-47bf-aa13-72429480cbc6</guid>
<guid>68e62379-55ac-48eb-b681-aee8f5a7696d</guid>
</sapattern>
</receive>
<scope variableAccessSerializable="no" name="ValidarExigências"
joinCondition="False">
<faultHandlers>
<catchAll>
<assign name="assignInvalid">
<bpelx:append>
<bpelx:from expression="concat(ns8:getVariableData('inputVariable','payload','/ns3:Template/ns3:Projecto/ns3:Observacoes'), string('Projecto inválido!!'))"/>
<bpelx:to variable="inputVariable" part="payload"
query="/ns3:Template/ns3:Projecto/ns3:Observacoes"/>
</bpelx:append>
</assign>
</catchAll>
</faultHandlers>
<sapattern>

<guid>2e56af66-6622-43e0-9adc-6d5f109cf374</guid>
</sapattern>
<sequence name="ValidarExigências" joinCondition="False">
<assign name="assignVPIn">
<copy>
<from variable="inputVariable" part="payload"/>
<to variable="invocaVP_initiate_InputVariable" part="payload"/>
</copy>
</assign>
<sapattern>

<guid>2e56af66-6622-43e0-9adc-6d5f109cf374</guid>
</sapattern>
<invoke name="invocaVP" joinCondition="False"
partnerLink="ValidacaoProjectos" portType="ns1:ValidacaoProjectos"
operation="initiate"
inputVariable="invocaVP_initiate_InputVariable">
<sapattern>

<guid>f3bc9c04-f4d2-4e96-acc8-7a6c88a8ced5</guid>
</sapattern>
</invoke>
<receive name="recebeVP" joinCondition="False"
partnerLink="ValidacaoProjectos"
portType="ns1:ValidacaoProjectosCallback" operation="onResult"
createInstance="no" variable="recebeVP_onResult_InputVariable">
<sapattern>

<guid>e9cdca59-888a-4e67-af54-a63ce2347ad3</guid>
<guid>1eba96a8-330a-4e4d-a14b-cdf6641fa614</guid>
</sapattern>
</receive>
<assign name="assignVPOut">
<copy>
<from variable="recebeVP_onResult_InputVariable" part="payload"/>
<to variable="inputVariable" part="payload"/>
</copy>
</assign>
</sequence>
</scope>
<scope variableAccessSerializable="no" name="AdicionarProjecto"
joinCondition="False">
<sapattern>

<guid>89c02eae-7788-4892-a616-e46b65ef1b50</guid>
</sapattern>
<sequence name="InvocarISAdicionarProjecto" joinCondition="False">
<assign name="assignIS">
<copy>
<from variable="inputVariable" part="payload"
query="/ns3:Template/ns3:Projecto/ns3:NomeProjecto"/>
<to variable="InvocaAdicionarProjecto_InputVariable" part="parameters"
query="/ns2:AdicionarProjecto/ns2:nome"/>
</copy>
<copy>
<from variable="inputVariable" part="payload"
query="/ns3:Template/ns3:Projecto/ns3:TipoProjecto"/>
<to variable="InvocaAdicionarProjecto_InputVariable" part="parameters"
query="/ns2:AdicionarProjecto/ns2:tipo"/>
</copy>
</assign>
<sapattern>

<guid>89c02eae-7788-4892-a616-e46b65ef1b50</guid>
</sapattern>
<invoke name="InvocaAdicionarProjecto" joinCondition="False"
partnerLink="NergaIS" portType="ns2:ServiceSoap"
operation="AdicionarProjecto"
inputVariable="InvocaAdicionarProjecto_InputVariable"
outputVariable="InvocaAdicionarProjecto_OutputVariable">
<sapattern>

<guid>76519bd3-c506-4c79-8190-8ff09abdd27d</guid>
</sapattern>
</invoke>
</sequence>
</scope>
<assign name="assignOutput">
<copy>
<from variable="inputVariable" part="payload"
query="/ns3:Template/ns3:Projecto"/>
<to variable="outputVariable" part="payload"/>
</copy>
</assign>
<reply name="devolveProjecto" joinCondition="False" partnerLink="client"
portType="ns4:CriarProjectoSA" operation="process"
variable="outputVariable">
<sapattern>

<guid>e728e550-f404-47bf-aa13-72429480cbc6</guid>
<guid>0dbefef0-3d04-4356-abbc-b291ea40d256</guid>
</sapattern>
</reply>
</sequence>
</process>

.v2.XMLParseException:Can not find definition for element 'descriptor'

I am getting the following error, while running 'empps.jsp' ...when executing the tutorial given at
ERROR Details:
500 Internal Server Error
javax.servlet.jsp.JspException: javax.faces.el.EvaluationException: Error getting property 'employees' from bean of type jsftoplink.model.EmployeesClient: Exception [TOPLINK-25004] (Oracle TopLink - 10g Release 3 (10.1.3.1.0) (Build 061004)): oracle.toplink.exceptions.XMLMarshalExceptionException Description: An error occurred unmarshalling the documentInternal Exception: Exception [TOPLINK-27101] (Oracle TopLink - 10g Release 3 (10.1.3.1.0) (Build 061004)): oracle.toplink.platform.xml.XMLPlatformExceptionException Description: An error occurred while parsing the document.Internal Exception: oracle.xml.parser.v2.XMLParseException: Can not find definition for element 'class-descriptor-type' at com.sun.faces.taglib.html_basic.DataTableTag.doEndTag(DataTableTag.java:501) at emps.jspService(_emps.java:629)
Pls help me in resolving this issue.

I am still gettng the same error. The xml file is now
<?xml version="1.0" encoding="UTF-8"?>
<CUSTOMER xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="" ID="568945">
<FIRSTNAME>Arnold</FIRSTNAME>
<LASTNAME>McEriccson</LASTNAME>
<ADDRESS>
<LINE1>31, Nomadic Avevnue</LINE1>
<LINE2>Pasadena Clove</LINE2>
<CITY>WoolTown, MT</CITY>
<ZIP>45263</ZIP>
</ADDRESS>
<BIRTHDATE>1967-08-13</BIRTHDATE>
</CUSTOMER>
The xsd file is:
<?xml version="1.0" encoding="UTF-8"?><xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="CUSTOMER">
<xs:complexType>
<xs:sequence>
<xs:element name="FIRSTNAME" type="xs:string"/> <xs:element name="LASTNAME" type="xs:string"/> <xs:element name="ADDRESS"> <xs:complexType>
<xs:sequence>
<xs:element name="LINE1" type="xs:string"/> <xs:element name="LINE2" type="xs:string"/> <xs:element name="CITY"/>
<xs:element name="ZIP" type="xs:int"/> </xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="BIRTHDATE" type="xs:date"/> </xs:sequence>
<xs:attribute name="ID" type="xs:double"/> </xs:complexType>
</xs:element>
</xs:schema>
There seems to be something fairly obvious that i am missing.

I am trying to download my paid for Elements 13 upgrade. When I click on the "download" button, I recieve this message: 413 Header Length too Large

I am trying to download my paid for Elements 13 upgrade. When I click on the "download" button, I receive this message: 413 Header Length too Large. Help?

You can download using direct download link , which I had provided.
Download Photoshop Elements products | 13, 12, 11, 10
During installation , when prompted enter serial number and proceed with the installation .
If you had purchased upgrade serial number.
First enter Photoshop Elements 13 serial number .
Then it will ask for previous qualifying version serial number.
From the drop down list , select Photoshop Elements 12 and then enter Photoshop Elements 12 serial number

When I bootup the icon for Elements shows up in orange. It changes to green only when I've gone to Finder and clicked on Elelments under the Devices list. This is a recent development. The icon used to be green upon bootup. Does anyone know why ?

When I bootup the icon for Elements shows up in orange. It changes to green only when I've gone to Finder and clicked on Elelments under the Devices list. This is a recent development. The icon used to be green upon bootup. Does anyone know why ?

I'm sorry to hear that.
I'm not affiliated w/ the developer, just a happy user that gave up fighting the apple podcast app a while ago. I used to have a bunch of smart playlists in itunes for my podcasts, and come home every day and pathologically synced my phone as soon as I walked in the door, and again before I walked out the door in the morning.
Since my wife was doing this too, we were fighting over who's turn it was to sync their phone.
Since I've switched to Downcast, I no longer worry about syncing my phone to itunes at all. I can go weeks between syncs.
Setup a "playlist" in downcast (ex., "Commute") and add podcasts to that playlist. Add another playlist ("walk" or "workout") and add different podcasts to that one.
Set podcast priorities on a per-feed basis (ex., high priority for some daily news feeds, medium priority for some favorite podcasts, lower priority for other stuff). Downcast will play the things in the priority you specify, and within that priority, it will play in date order (oldest to newest).
Allegedly, it will also sync your play status to other devices, although that is not a feature I currently use and can't vouch for. It uses apple's iCloud APIs, so to some extent may be limited by what Apple's APIs can do.

Manage multiple versions(ID CS,CS2,CS3,CS4) of INDD files Indesign proxy for PC

Dear scripters,
I have multiple version of ID installed in my system. I have ID CS,CS2,CS3 and CS4. While I am opening (double click) the ID CS file, automatically the file opening in CS4. For solving this problem I have searched in the forums I found there is a program called INDESIGN PROXY for MAC OSX. It manages the problems well.
Now I am in the process of developing the application same like that for windows using VB. Here is my observation about Indesign proxy.
1. While user double clicks the Indesign file the argument is not passing to the Indesign.exe, but the argument passes to the Indesign proxy. Something like this
"C:\Program Files\Adobe\Adobe InDesign CS4\InDesign.exe" "%1"
to this
"C:\Program Files\IDproxy\proxy.exe" "%1"
2. The proxy exe lists all the version of IDs in a dialog box. If user selects CS2, the proxy exe passes the command argument something like this
"C:\Program Files\Adobe\Adobe InDesign CS2\InDesign.exe" "%1"
3. Now the file will open in correct version.
I am comfort with VB forums and coding but I am struck getting the file path while user double click's the file. I short need to get the file path of "%1" argument.
I think I am detailed.
Kindly advice me how can I proceed more?
Thanks
regards
a r u l
vpublish.net

I don't think it's a mistake.
"InDesign CS4 (3.0)"
means: this is the OM for InDesign 3.0 (i.e., InDesign CS) that is contained in InDesign CS4.
Wait -- do you mean there might be a difference between "the OM for InDesign 4.0 (i.e., InDesign CS2) that is contained in InDesign CS4" and, say, "OM for InDesign 4.0 (i.e., InDesign CS2) that is contained in InDesign CS5" ?
Why on earth would anyone need that? I imagine it's not because even with versioning the 'older' scripts may not behave the same -- there must be dozens of mails about versioning not working ... I mean, if Adobe knows what causes older scripts to stop working (because, if I understand you correctly, they retroactively change it in the documentation for older versions), wouldn't it be yet easier to not cause those changes?

Reverse Proxy for SharePoint 2013

Hi,
I need to setup SharePoint 2013 environment which needs to be accessible from mobile devices e.g. iPAD/Android, for reverse proxy, I am looking at apache or IIS ARR since UAG is going to be deprecated. So far any one setup apache (on
RHEL 6.x)
or IIS ARR(on W2K8R2) successfully as reverse proxy for SharePoint 2013 access? Is there any issue? and which SharePoint authentication method should be configured?
Must is be Form based authentication? As I read some articles it seems ARR supports Windows authentication. Thanks in advance.

IIS ARR doesn't authenticate users, it is a pass-through (unlike UAG which can do auth or anon). Both IIS AAR and the new Web Proxy Role in Server 2012 R2 do not work with SharePoint 2013 Apps.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

How can I buy more storage for Elements?

Looking how to upgrade storage for my Photoshop Elements account. Every time I click on upgrade I'm taken to my products page and can't do anything from there as there are no active links to upgrade, buy more storage. I keep looping from the control panel for Elements to my account dashboard.

Your current Adobe® Photoshop® Elements or Adobe Premiere® Elements storage and sharing membership on Photoshop.com will move to a new service called Adobe Revel. More discussion around the same can be found here http://feedback.photoshop.com/photoshop_family/topics/other_adobe_photo_organizational_sof tware

Problem in creating a java proxy for PHP web service

This is a problem in generating a java proxy for a PHP webservice.
I have a PHP service running on Wamp Server and also a PHP client which is able to call the service.
The WSDL for the PHP web service is also generated .
I am trying to create a java proxy using the jdev (10.1.3.0.3) from the wsdl file.
The wsdl generated by the php program is
<?xml version="1.0" encoding="ISO-8859-1" ?>
<definitions xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:si="http://soapinterop.org/xsd" xmlns:tns="urn:hellowsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:hellowsdl">
<types>
<xsd:schema targetNamespace="urn:hellowsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="urn:hellowsdl#hello" style="rpc" />
<input>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>After making following changes to the wsdl program, I tried to generate java proxy.
<definitions name="hellowsdl"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:si="http://soapinterop.org/xsd" xmlns:tns="http://localhost/mywork/hellowsdl.wsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://localhost/mywork/myphpwsdl.wsdll">
<types>
<xsd:schema targetNamespace="http://localhost/mywork/hellowsdl.wsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="" style="rpc" />
<input>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>This is how the java stub file looks like:
public class HellowsdlBinding_Stub
    extends oracle.j2ee.ws.client.StubBase
    implements demo.mypackage.HellowsdlPortType {
     * public constructor
    public HellowsdlBinding_Stub(HandlerChain handlerChain) {
        super(handlerChain);
        _setProperty(ENDPOINT_ADDRESS_PROPERTY, "http://localhost/mywork/hellowsdl.php");
        setSoapVersion(SOAPVersion.SOAP_11);
        setServiceName( new QName("http://localhost/mywork/hellowsdl","hellowsdl"));
        setPortName( new QName("http://localhost/mywork/hellowsdl","hellowsdlPort"));
     * implementation of hello
    public java.lang.String hello(java.lang.String name)
        throws java.rmi.RemoteException {
        StreamingSenderState _state = null;
        try {
            _state = _start(_handlerChain);
            if (_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS) != null) {
                _state.getMessageContext().getMessage().setProperty("DimeEncode",_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS));
            InternalSOAPMessage _request = _state.getRequest();
            _request.setOperationCode(hello_OPCODE);
            _state.getMessageContext().setProperty("oracle.j2ee.ws.mgmt.interceptor.operation-qname",new QName("","hello"));
            demo.mypackage.runtime.HellowsdlBinding_hello_ReqS _myHellowsdlBinding_hello_ReqS = new demo.mypackage.runtime.HellowsdlBinding_hello_ReqS();
        _myHellowsdlBinding_hello_ReqS.setName(name);
        SOAPBlockInfo _bodyBlock = new SOAPBlockInfo(ns1_hello_hello_QNAME);
        _bodyBlock.setValue(_myHellowsdlBinding_hello_ReqS);
        _bodyBlock.setSerializer(myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer);
        _request.setBody(_bodyBlock);
        _state.getMessageContext().setProperty("http.soap.action", "http://localhost/mywork/hellowsdl");
        _send((String) _getProperty(ENDPOINT_ADDRESS_PROPERTY), _state);
        demo.mypackage.runtime.HellowsdlBinding_hello_RespS _myHellowsdlBinding_hello_RespS = null;
        Object _responseObj = _state.getResponse().getBody().getValue();
        if (_responseObj instanceof SOAPDeserializationState) {
            _myHellowsdlBinding_hello_RespS =
                (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)((SOAPDeserializationState)_responseObj).getInstance();
        } else {
            _myHellowsdlBinding_hello_RespS =
                (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)_responseObj;
        return _myHellowsdlBinding_hello_RespS.get_return();
    } catch (RemoteException e) {
        // let this one through unchanged
        throw e;
    } catch (JAXRPCException e) {
        throw new RemoteException(e.getMessage(), e);
    } catch (Exception e) {
        if (e instanceof RuntimeException) {
            throw (RuntimeException)e;
        } else {
            throw new RemoteException(e.getMessage(), e);
* this method deserializes the request/response structure in the body
protected void _readFirstBodyElement(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    int opcode = state.getRequest().getOperationCode();
    switch (opcode) {
        case hello_OPCODE:
            _deserialize_hello(bodyReader, deserializationContext, state);
            break;
        default:
            throw new SenderException("sender.response.unrecognizedOperation", Integer.toString(opcode));
* This method deserializes the body of the hello operation.
private void _deserialize_hello(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    try {
        Object myHellowsdlBinding_hello_RespSObj =
            myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer.deserialize(ns1_hello_helloResponse_QNAME,
                bodyReader, deserializationContext);
        SOAPBlockInfo bodyBlock = new SOAPBlockInfo(ns1_hello_helloResponse_QNAME);
        bodyBlock.setValue(myHellowsdlBinding_hello_RespSObj);
        state.getResponse().setBody(bodyBlock);
    } catch (DeserializationException e) {
        if (e.getSoapFaultSubCodeType() == JAXRPCExceptionBase.FAULT_CODE_NONE && e.getSoapFaultCodeType() != JAXRPCExceptionBase.FAULT_CODE_DATA_ENCODING_UNKNOWN) {
            e.setSoapFaultSubCodeType(JAXRPCExceptionBase.FAULT_CODE_BAD_ARGUMENTS);
        throw e;
public String _getEncodingStyle() {
    return SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding();
public void _setEncodingStyle(String encodingStyle) {
    throw new UnsupportedOperationException("cannot set encoding style");
public ClientTransport getClientTransport() {
    return super._getTransport();
* This method returns an array containing (prefix, nsURI) pairs.
protected String[] _getNamespaceDeclarations() {
    return myNamespace_declarations;
* This method returns an array containing the names of the headers we understand.
public QName[] _getUnderstoodHeaders() {
    return understoodHeaderNames;
* This method handles the case of an empty SOAP body.
protected void _handleEmptyBody(XMLReader reader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
public void _initialize(InternalTypeMappingRegistry registry) throws Exception {
    super._initialize(registry);
    myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_ReqS.class, ns1_hello_TYPE_QNAME);
    myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_RespS.class, ns1_helloResponse_TYPE_QNAME);
private static final QName _portName = new QName("http://localhost/mywork/hellowsdl", "hellowsdlPort");
private static final int hello_OPCODE = 0;
private static final QName ns1_hello_hello_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private static final QName ns1_hello_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private CombinedSerializer myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer;
private static final QName ns1_hello_helloResponse_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private static final QName ns1_helloResponse_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private CombinedSerializer myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer;
private static final String[] myNamespace_declarations =
                                    new String[] {
                                        "ns0", "http://localhost/mywork/hellowsdl"
private static final QName[] understoodHeaderNames = new QName[] { };
}The errors that are produced are-
java.rmi.RemoteException: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found; nested exception is:
     HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found
Kindly help to resolve this.
Thanks.

This is a problem in generating a java proxy for a PHP webservice.
I have a PHP service running on Wamp Server and also a PHP client which is able to call the service.
The WSDL for the PHP web service is also generated .
I am trying to create a java proxy using the jdev (10.1.3.0.3) from the wsdl file.
The wsdl generated by the php program is
<?xml version="1.0" encoding="ISO-8859-1" ?>
<definitions xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:si="http://soapinterop.org/xsd" xmlns:tns="urn:hellowsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:hellowsdl">
<types>
<xsd:schema targetNamespace="urn:hellowsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="urn:hellowsdl#hello" style="rpc" />
<input>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>After making following changes to the wsdl program, I tried to generate java proxy.
<definitions name="hellowsdl"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:si="http://soapinterop.org/xsd" xmlns:tns="http://localhost/mywork/hellowsdl.wsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://localhost/mywork/myphpwsdl.wsdll">
<types>
<xsd:schema targetNamespace="http://localhost/mywork/hellowsdl.wsdl">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
<xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
</xsd:schema>
</types>
<message name="helloRequest">
<part name="name" type="xsd:string" />
</message>
<message name="helloResponse">
<part name="return" type="xsd:string" />
</message>
<portType name="hellowsdlPortType">
<operation name="hello">
<documentation>Says hello to the caller</documentation>
<input message="tns:helloRequest" />
<output message="tns:helloResponse" />
</operation>
</portType>
<binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="hello">
<soap:operation soapAction="" style="rpc" />
<input>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</input>
<output>
<soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
</output>
</operation>
</binding>
<service name="hellowsdl">
<port name="hellowsdlPort" binding="tns:hellowsdlBinding">
<soap:address location="http://localhost/mywork/myphp.php" />
</port>
</service>
</definitions>This is how the java stub file looks like:
public class HellowsdlBinding_Stub
    extends oracle.j2ee.ws.client.StubBase
    implements demo.mypackage.HellowsdlPortType {
     * public constructor
    public HellowsdlBinding_Stub(HandlerChain handlerChain) {
        super(handlerChain);
        _setProperty(ENDPOINT_ADDRESS_PROPERTY, "http://localhost/mywork/hellowsdl.php");
        setSoapVersion(SOAPVersion.SOAP_11);
        setServiceName( new QName("http://localhost/mywork/hellowsdl","hellowsdl"));
        setPortName( new QName("http://localhost/mywork/hellowsdl","hellowsdlPort"));
     * implementation of hello
    public java.lang.String hello(java.lang.String name)
        throws java.rmi.RemoteException {
        StreamingSenderState _state = null;
        try {
            _state = _start(_handlerChain);
            if (_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS) != null) {
                _state.getMessageContext().getMessage().setProperty("DimeEncode",_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS));
            InternalSOAPMessage _request = _state.getRequest();
            _request.setOperationCode(hello_OPCODE);
            _state.getMessageContext().setProperty("oracle.j2ee.ws.mgmt.interceptor.operation-qname",new QName("","hello"));
            demo.mypackage.runtime.HellowsdlBinding_hello_ReqS _myHellowsdlBinding_hello_ReqS = new demo.mypackage.runtime.HellowsdlBinding_hello_ReqS();
        _myHellowsdlBinding_hello_ReqS.setName(name);
        SOAPBlockInfo _bodyBlock = new SOAPBlockInfo(ns1_hello_hello_QNAME);
        _bodyBlock.setValue(_myHellowsdlBinding_hello_ReqS);
        _bodyBlock.setSerializer(myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer);
        _request.setBody(_bodyBlock);
        _state.getMessageContext().setProperty("http.soap.action", "http://localhost/mywork/hellowsdl");
        _send((String) _getProperty(ENDPOINT_ADDRESS_PROPERTY), _state);
        demo.mypackage.runtime.HellowsdlBinding_hello_RespS _myHellowsdlBinding_hello_RespS = null;
        Object _responseObj = _state.getResponse().getBody().getValue();
        if (_responseObj instanceof SOAPDeserializationState) {
            _myHellowsdlBinding_hello_RespS =
                (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)((SOAPDeserializationState)_responseObj).getInstance();
        } else {
            _myHellowsdlBinding_hello_RespS =
                (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)_responseObj;
        return _myHellowsdlBinding_hello_RespS.get_return();
    } catch (RemoteException e) {
        // let this one through unchanged
        throw e;
    } catch (JAXRPCException e) {
        throw new RemoteException(e.getMessage(), e);
    } catch (Exception e) {
        if (e instanceof RuntimeException) {
            throw (RuntimeException)e;
        } else {
            throw new RemoteException(e.getMessage(), e);
* this method deserializes the request/response structure in the body
protected void _readFirstBodyElement(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    int opcode = state.getRequest().getOperationCode();
    switch (opcode) {
        case hello_OPCODE:
            _deserialize_hello(bodyReader, deserializationContext, state);
            break;
        default:
            throw new SenderException("sender.response.unrecognizedOperation", Integer.toString(opcode));
* This method deserializes the body of the hello operation.
private void _deserialize_hello(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    try {
        Object myHellowsdlBinding_hello_RespSObj =
            myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer.deserialize(ns1_hello_helloResponse_QNAME,
                bodyReader, deserializationContext);
        SOAPBlockInfo bodyBlock = new SOAPBlockInfo(ns1_hello_helloResponse_QNAME);
        bodyBlock.setValue(myHellowsdlBinding_hello_RespSObj);
        state.getResponse().setBody(bodyBlock);
    } catch (DeserializationException e) {
        if (e.getSoapFaultSubCodeType() == JAXRPCExceptionBase.FAULT_CODE_NONE && e.getSoapFaultCodeType() != JAXRPCExceptionBase.FAULT_CODE_DATA_ENCODING_UNKNOWN) {
            e.setSoapFaultSubCodeType(JAXRPCExceptionBase.FAULT_CODE_BAD_ARGUMENTS);
        throw e;
public String _getEncodingStyle() {
    return SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding();
public void _setEncodingStyle(String encodingStyle) {
    throw new UnsupportedOperationException("cannot set encoding style");
public ClientTransport getClientTransport() {
    return super._getTransport();
* This method returns an array containing (prefix, nsURI) pairs.
protected String[] _getNamespaceDeclarations() {
    return myNamespace_declarations;
* This method returns an array containing the names of the headers we understand.
public QName[] _getUnderstoodHeaders() {
    return understoodHeaderNames;
* This method handles the case of an empty SOAP body.
protected void _handleEmptyBody(XMLReader reader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
public void _initialize(InternalTypeMappingRegistry registry) throws Exception {
    super._initialize(registry);
    myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_ReqS.class, ns1_hello_TYPE_QNAME);
    myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_RespS.class, ns1_helloResponse_TYPE_QNAME);
private static final QName _portName = new QName("http://localhost/mywork/hellowsdl", "hellowsdlPort");
private static final int hello_OPCODE = 0;
private static final QName ns1_hello_hello_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private static final QName ns1_hello_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
private CombinedSerializer myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer;
private static final QName ns1_hello_helloResponse_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private static final QName ns1_helloResponse_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
private CombinedSerializer myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer;
private static final String[] myNamespace_declarations =
                                    new String[] {
                                        "ns0", "http://localhost/mywork/hellowsdl"
private static final QName[] understoodHeaderNames = new QName[] { };
}The errors that are produced are-
java.rmi.RemoteException: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found; nested exception is:
     HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found
Kindly help to resolve this.
Thanks.

Gold standard plug ins or collections for elements 9?

One more quick question, t feel like I've already posted too many questions until I know enough to start contributing back to the community...
Looking to get some plug ins for ps/premiere elements 9...
A) Photoshop elements 9:
1 Anyone know of any GREAT comparisons/ buyers guides pitting similar plug ins against each other (maybe even like collections with each title compared)
1b) Any opinions on Current/Latest 'Gold Standard' tools (head and shoulders above similar titles - kinda industry/user consensous choise of BEST, beyond individual preference even?)
2) Are they any HDR plug ins that work with photoshop elements 9 - if so, is there 1 or 2 'Gold Standard' titles that are heads and shoulders above the rest
if not for elements are there any standalone programs for HDR?
2b) Right now (till I build budget back after buying software and plug ins) my camera doesn't shoot RAW, does HDR even work with jpeg sources?
Or does HDR even work with elements? Have to go to ps cs5 for that?
B) Premiere Elements 9:
1) Same as photoshop elements above, are there any 'Gold Standard' Plug in or stock content, ect collections way better than the rest?
2) What type of and which titles would be great bets to add to a beginners set of video editing tools?
? Co pilot,(what/which) ect...?
Sorry if dragging on, I've been at this for almost 30 hours, trying to gey everything setup and learning how/what to use - Time for BED!
THANKS!

Take a look at elements+
http://elementsplus.net/
or
Elements XXL
http://thepluginsite.com/products/elementsxxl/

Namespace Error, while creating proxy for a WSRP producer(Created on Exo)

Hi ,
I have implemented and deployed WSRP producer on Exo portal container. When I was trying to create proxy for the same in weblogic portal 10.2 its giving me the following error. Upon submiting the WSDL URL
!ENTRY com.bea.wlp.eclipse.common 4 4 2008-12-08 13:46:27.540
!MESSAGE NAMESPACE_ERR
!STACK 0
org.w3c.dom.DOMException: NAMESPACE_ERR
     at weblogic.xml.domimpl.ElementNSImpl.<init>(ElementNSImpl.java:74)
     at weblogic.xml.saaj.SOAPElementImpl.<init>(SOAPElementImpl.java:40)
     at weblogic.xml.saaj.SaajDocument.createElementNS(SaajDocument.java:63)
     at com.bea.wsrp.util.DomUtils.createChildElement(DomUtils.java:386)
     at com.bea.wsrp.util.DomUtils.addChildElement(DomUtils.java:406)
     at com.bea.wsrp.util.DomUtils.addChildElement(DomUtils.java:371)
     at com.bea.wsrp.bind.serviceDescription.GetServiceDescriptionRequest.writeTo(GetServiceDescriptionRequest.java:40)
     at com.bea.wsrp.client.ProducerAgentImpl.getServiceDescription(ProducerAgentImpl.java:129)
     at com.bea.wsrp.client.ProducerAgentImpl.getServiceDescription(ProducerAgentImpl.java:80)
     at com.bea.wsrp.client.ProducerAgentImpl.getServiceDescription(ProducerAgentImpl.java:68)
     at com.bea.wsrp.client.ProducerAgentImpl.getServiceDescription(ProducerAgentImpl.java:57)
     at com.bea.wlp.eclipse.wsrp.portletbuilder.wsrp.ProducerAgent.getServiceDescription(ProducerAgent.java:99)
     at com.bea.wlp.eclipse.wsrp.portletbuilder.wsrp.ProducerAgent.<init>(ProducerAgent.java:57)
     at com.bea.wlp.eclipse.wsrp.portletbuilder.wsrp.ProducerAgent.<init>(ProducerAgent.java:45)
     at com.bea.wlp.eclipse.wsrp.portletbuilder.wizard.wsrp.SelectProducerPanel$ProducerInfoRunner.run(SelectProducerPanel.java:690)
Could any one help me to solve this problem.
Thanks & Regards,
Naresh

Hi Nate,
Please find the following wsdl.
<?xml version="1.0" encoding="UTF-8" ?>
<wsdl:definitions targetNamespace="http://localhost:8080/wsrp/services/Version" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://localhost:8080/wsrp/services/Version" xmlns:intf="http://localhost:8080/wsrp/services/Version" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<wsdl:message name="getVersionRequest" />
<wsdl:message name="getVersionResponse">
<wsdl:part name="getVersionReturn" type="soapenc:string" />
</wsdl:message>
<wsdl:portType name="Version">
<wsdl:operation name="getVersion">
<wsdl:input message="impl:getVersionRequest" name="getVersionRequest" />
<wsdl:output message="impl:getVersionResponse" name="getVersionResponse" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="VersionSoapBinding" type="impl:Version">
<wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
<wsdl:operation name="getVersion">
<wsdlsoap:operation soapAction="" />
<wsdl:input name="getVersionRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://axis.apache.org" use="encoded" />
</wsdl:input>
<wsdl:output name="getVersionResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/wsrp/services/Version" use="encoded" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="VersionService">
<wsdl:port binding="impl:VersionSoapBinding" name="Version">
<wsdlsoap:address location="http://localhost:8080/wsrp/services/Version" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Thanks & Regards,
Naresh

No proxy for elements in an FC Bundle

Similar Messages

Maybe you are looking for