EndpointURI property is not overriding WSDL address location

Hi all.
We're running into an issue regarding a reference component configured in a composite SOa app:
<reference name="AutenticarUsuarioExternoFSGuev1"
ui:wsdlLocation="AutenticarUsuarioExternoFSGuev1.wsdl">
<interface.wsdl
interface="http://www.claro.com.br/EBS/Claro/v1#wsdl.interface(AutenticarUsuarioExternoFSGuev1PortType)"/>
<binding.ws
port="http://www.claro.com.br/EBS/Claro/v1#wsdl.endpoint(AutenticarUsuarioExternoFSGuev1/AutenticarUsuarioExter
noFSGuev1PortSOA)"
location="AutenticarUsuarioExternoFSGuev1.wsdl"
soapVersion="1.1">
<property name="weblogic.wsee.wsat.transaction.flowOption"
type="xs:string" many="false">WSDLDriven</property>
<property
name="*endpointURI*">http://fachadasoague.claro.com.br/FachadaSoaGue/services/AutenticarUsuarioExternoFSGuev1</pr
operty>
</binding.ws>
</reference>
As we see above, we have an endpointURI property configured, which according to my experience in 10g version, I
assume it should override any endpoint configuration in the reference's WSDL.
The WSDL of the reference component mentioned above has an adress location property configured inside it:
     <wsdl:service name="AutenticarUsuarioExternoFSGuev1">
          <wsdl:port name="AutenticarUsuarioExternoFSGuev1PortSOA"
binding="tns:AutenticarUsuarioExternoFSGuev1PortTypeSOAP">
               <soap:*address*
location="http://fachadasoague.claro.com.br/FachadaSoaGue/services/AutenticarUsuarioExternoFSGuev1" />
          </wsdl:port>
     </wsdl:service>
The problem is: When service endpoint defined by the endpointURI property is called and it fails for some
reason, the WSDL address location is used as a second try (kind of failover mechanism).
What I expected: There should not be a failover process here, It´s not supposed to happen. Only the endpoint
defined by the endpointURI property should be used, that is, it should override any other endpoint.
I tried to work around the problem by removing the location property, according to the SOA Suite documentation,
but it continues to use both endpoints.
Any point on this will be appreciated.
Regards.
Denis

Hi all.
We're running into an issue regarding a reference component configured in a composite SOa app:
<reference name="AutenticarUsuarioExternoFSGuev1"
ui:wsdlLocation="AutenticarUsuarioExternoFSGuev1.wsdl">
<interface.wsdl
interface="http://www.claro.com.br/EBS/Claro/v1#wsdl.interface(AutenticarUsuarioExternoFSGuev1PortType)"/>
<binding.ws
port="http://www.claro.com.br/EBS/Claro/v1#wsdl.endpoint(AutenticarUsuarioExternoFSGuev1/AutenticarUsuarioExter
noFSGuev1PortSOA)"
location="AutenticarUsuarioExternoFSGuev1.wsdl"
soapVersion="1.1">
<property name="weblogic.wsee.wsat.transaction.flowOption"
type="xs:string" many="false">WSDLDriven</property>
<property
name="*endpointURI*">http://fachadasoague.claro.com.br/FachadaSoaGue/services/AutenticarUsuarioExternoFSGuev1</pr
operty>
</binding.ws>
</reference>
As we see above, we have an endpointURI property configured, which according to my experience in 10g version, I
assume it should override any endpoint configuration in the reference's WSDL.
The WSDL of the reference component mentioned above has an adress location property configured inside it:
     <wsdl:service name="AutenticarUsuarioExternoFSGuev1">
          <wsdl:port name="AutenticarUsuarioExternoFSGuev1PortSOA"
binding="tns:AutenticarUsuarioExternoFSGuev1PortTypeSOAP">
               <soap:*address*
location="http://fachadasoague.claro.com.br/FachadaSoaGue/services/AutenticarUsuarioExternoFSGuev1" />
          </wsdl:port>
     </wsdl:service>
The problem is: When service endpoint defined by the endpointURI property is called and it fails for some
reason, the WSDL address location is used as a second try (kind of failover mechanism).
What I expected: There should not be a failover process here, It´s not supposed to happen. Only the endpoint
defined by the endpointURI property should be used, that is, it should override any other endpoint.
I tried to work around the problem by removing the location property, according to the SOA Suite documentation,
but it continues to use both endpoints.
Any point on this will be appreciated.
Regards.
Denis

Similar Messages

  • Item property does not overrides block property ?

    I have CURRENT RECORD VISUAL ATTRIBUTE set to SOMETHING for block A. i also have CURRENT RECORD VISUAL ATTRIBUTE for item AA in block A ( A.AA) . but when i run form, it looks like item AA's CURRENT RECORD VISUAL ATTRIBUTE is not in effect ?
    usually item's property should override block property. but it'snot happening here.. can anyone figure out??

    Set_Item_Instance_Property is a more specific control, so Set_Item_Property logically should not change it.
    Create two package variables defined in a package specification in the form, trig_item and trig_record.
    Change your WBP trigger:
    Set_Item_Instance_Property(Pkg1.trig_item,Pkg1.trig_record, VISUAL_ATTRIBUTE,'');
    Pkg1.trig_item := :System.trigger_item;
    Pkg1.trig_record := :system.trigger_record;
    Set_Item_Instance_Property(Pkg1.trig_item,Pkg1.trig_record, VISUAL_ATTRIBUTE,'SET');
    Actually, a When-New-Item-Instance trigger might be better than the WBP trigger, so the same action would occur no matter how the cursor is moved around your form (Using Enter or Tab, or shift-Tab, or scrolling).

  • Virtual address location in process WSDL

    Hi,
    now we use following approach:
    We refer to default WSDL at http://<server>:<port>/orabpel/<domain>/<process name>/<process name>?wsdl
    Where address location is the default revision of the process: http://<server>:<port>/orabpel/<domain>/<process name>/<revision>
    Is there any possibility to refer to WSDL with 'virtual address location' that always refers to default revision?
    We want that our partner has one WSDL with address location
    and we can transparently change process revisions without notifying our partner to clear wsdl caches and refresh address location?
    Are there any possibilities?
    (we use BPEL 10.1.2.0.0 )
    Thank You and Reagrds
    Karel

    Hi,
    To always use the latest revision of a process you need to exclude the <revision> part of the Location url. To dynamically set the url's at runtime you can use the following in a assign activity:
    <copy>
    <from expression="string(bpws:getVariableData('urlVariable','/ns1:ParameterCollection/ns1:location'))"/>
    <to partnerLink="RunUcmJasperReport" bpelx:property="location"/>
    </copy>
    <copy>
    <from expression="string(bpws:getVariableData('urlVariable','/ns1:ParameterCollection/ns1:wsdlLocation'))"/>
    <to partnerLink="RunUcmJasperReport" bpelx:property="wsdlRuntimeLocation"/>
    </copy>
    Make sure you assign both wsdlLocation and Location and that the <from> part explicitly is a string. This works in 10.1.3 but i do not know if it also was available in 10.1.2
    Kind Regards,
    Andre

  • The AQ Service Bus showme a bad wsdl ( soap:address location )from internet

    Hi,
    first of all, excuse my bad english :-)
    I've a problem when I tray to get a wsdl file from Internet.
    In Aqualogic I've configured a wsdl file with the next content:
    <wsdl:service name="EmailValidation">
    <wsdl:port binding="tns:EmailValidationSoap" name="EmailValidation">
    <soap:address location="http://www.axonaxis.cl:7001/email"/>
    </wsdl:port>
    </wsdl:service>
    This file is reference from a proxy service.
    when I try to get the wsdl file from a browser, showme this:
    <service name="EmailValidation">
    <port binding="s0:EmailValidationSoap" name="EmailValidation">
    <s1:address location="http://server2005:7001/email"/>
    </port>
    </service>
    From a browser, put in "location" the server name (of course, if I try to execute the proxy service, the server not found).
    Why is doing this? How can I solve this problem?
    I don't have much experience in this so try to help me.
    Thank you very much (Muchas gracias!)

    ARCHIVO HOST!!!!

  • WSDL soap:address location

    Having developed/tested my soap services they are almost ready for shipping as a product.
    However, in the WSDL the <soap:address location=""> tag is set to my server - as used in development.
    So when I deploy this EAR file from JDev (9.0.5.2) this value is fixed, and will not work for customers.
    Is there anyway to make this value dynamic on deployment by customers or am I stuck with having to find out in advance customers server/port settings and then creating individual release per customer?
    I have tried using a relative url but this doesnt always work for clients trying to connect, e.g.:
    <soap:address location="/webservices/booking"/>
    Thanks in advance for any assistance.

    For now I have written a program, that is run after deployment. This program edits the web.xml and allows customers to specify the server name and port they are using.
    Anyone else have any solutions to this?

  • Using Firefox 4.0 Beta 4. When I open a link in a new window, the web address does not show in the location bar. Why?

    When I open a web page link in "a new window" the link opens, but the web page information does not appear in the location bar. It is blank. If I open the link in a new tab, there is ho problem.
    Further, if a open a link from the tab without a location in a new tab on the same window and then go back to the original tab, the location bar fills with the web address.
    Have done this starting in several locations, so it not location dependent.

    That behaviour is likely top be caused by an add-on, and in your case the likely culprit is IE Tab 2, the various versions of IE Tab have caused problems with Firefox 4 beta including issues with the location bar not being updated.
    You can test to see if IE Tab 2 is causing your problem by disabling it and then seeing if the location bar in a new window shows the address. If it is not that add-on causing the problem, see [[troubleshooting extensions and themes]].
    For info, the IE Tab Plus add-on has been updated recently to improve compatibility with Firefox 4 beta, you may want to try that one instead. The latest version is available from http://coralietab.mozdev.org/installation.html

  • Change SOAP Address Location in the WSDL

    When deploying a BPEL service the SOAP Address location is automatically generated to have the
    http://{SERVER}:{PORT} of the SOA server where you are deploying the service but i need to have a different address location.
    I basically needs this because we have a load balancer and firewall restrictions for any external third party that want to invoke our service.
    So the WSDL URL we give to the third party who want to invoke our service will be
    https://loadbalancer/orabpel/default/TestService/1.0/TestService?wsdl
    instead of
    http://soasever:soaserveport/orabpel/default/TestService/1.0/TestService?wsdl
    The loadbalancer will then strip of the https connection and send it as http request to the SOA server.
    So the third party is now able to access the WSDL but he is having issues while invoking the service as the SOAP address location is still having our SOA server name
    Any ideas?

    This can be achieved through dynamic partner linking.
    http://download.oracle.com/docs/cd/E19509-01/821-0017/cnfg_bpel-se-dynamic-ptnrlink_c/index.html
    HTH
    -ND

  • When I click on a link the address does not display in the location bar in the new tab. Which makes the back/forward button and refresh buttons unable to be used

    When opening a link any link from firefox address does not display in the location bar. Even when navigating forward from there the address does not show back/forward button and refresh all rendered unable to be used

    Do you have that problem when running in the Firefox SafeMode? <br />
    [http://support.mozilla.com/en-US/kb/Safe+Mode] <br />
    ''Don't select anything right now, just use "Continue in SafeMode."''
    If not, see this: <br />
    [http://support.mozilla.com/en-US/kb/troubleshooting+extensions+and+themes]

  • Address/Location bar, forward-back buttons are not shown

    Address/Location bar, forward-back buttons are not shown in my browser. How can I make them visible?

    If the menu bar is hidden then press F10 or hold down the Alt key, that should make the "Menu Bar" appear
    * Make sure that the "Navigation Toolbar" and the "Bookmarks Toolbar" are visible: "View > Toolbars"
    * If items are missing then open the Customize window via "View > Toolbars > Customize" or via "Firefox > Options > Toolbar Layout"
    * If a missing item is in the toolbar palette then drag it back from the Customize window on the toolbar
    * If you do not see an item on a toolbar and in the toolbar palette then click the "Restore Default Set" button to restore the default toolbar set up.
    See also:
    * http://kb.mozillazine.org/Toolbar_customization

  • How do I stop Calendar overriding my Event location

    Hi
    When creating an event in Calendar, the software is quite 'helpful' in offering suggestions for the event location as I type.
    However, if I don't like any of it's suggestions, or wish to override the suggested location, the software seems to stamp it's feet and insist on formatting the location data the way IT prefers.
    How do I stop it doing that?
    For instance, I am attending an event at the "Institute of Directors, 116 Pall Mall, London, SW1Y 5EA"
    Calendar finds a very close match for this and replaces my location with
    "116 Pall Mall
    London
    England
    SW1Y 5EA
    United Kingdom"
    Apart from the excessive screen real estate taken up by those superfluous new lines, it doesn't include the name of the location - "Institute of Directors" - and it includes 2 countries - England and United Kingdom - that I don't need to know because I live here.
    Can I not keep my own preferred format in the location field?

    I just fixed this issue by turning off the location support on iCal on my iPhone. If all your devices are synced up that may be causing the issue.
    After turning off location support I was able to enter the address I wanted. It gave me a choice to stick with my address or choose from the list of suggestions. After refreshing iCal on my computer it displayed the correct address.
    Hopefully your fix will be that easy!

  • JMS transport - weblogic changes soap:address location="jms:.. to http

    Hi,
    Please help me to configure web service to use only jms transport.
    I try to create web service that uses JMS transport.
    I started from WSDL where I placed two elements:
    <soap:binding style="document"
                   transport="http://www.openuri.org/2002/04/soap/jms" />
    and
    <soap:address location="jms://host:7041/contextPathName/serviceUriName?URI=queueName" />
    Then in web service implementation I placed following annotation:
    @WLJmsTransport(contextPath = "contextPathName", serviceUri = "serviceUriName", portName = "portName", queue = "queueName", connectionFactory = "connectionFactoryName")
    Deployment is successful but when I look at generated WSDL (Admin console) I see that weblogic has changed <soap:address location="jms:.. to <soap:address location="http....
    And when I look at monitoring I see that port is using JMS transport.
    When I try to test my service using Admin console Test client I see that the queue is not used (Admin console/monitoring/Messages total is still 0) and service uses (I suppose) http transport.

    Hi,
    Please change "http://www.openuri.org/2002/04/soap/jms" to http://www.openuri.org/2002/04/soap/jms/ for soap1.1 or http://www.openuri.org/2002/04/soap12/jms/ for soap1.2.
    There must be some mismatch between edoc and implementation.
    -LJ

  • Webservices soap address location url update

    Hi,
    Is there any way to change the soap address location in the wsdl?
    I tried by changing the frontendport and host,But I don't have any option for updating the protocol(http/https) option in weblogic.
    advance thanks

    Thank you very much,
    I followed the same document for updation of endpoint,these settings only updating the host and port ,not the frontend access protocol. End points are generated properly if both the proxy and internal app server mapping uses the same protocol.
    Weblogic always using the application server protocol instead of proxy protocol.
    Example:wsdl accessed from proxy with https and the internal mapping is http.
    https://proxy:443/xxx/xxx?wsdl--->http://appserver:7001/xxx/xxx?wsdl--->web servies end point is http://proxy:80/xxx/xxx?wsdl but the expected endpoint is
    https://proxy/xxx/xxx?wsdl.
    thanks for providing any other advices

  • SOAP Address Location

    Is there any way to tell what the SOAP Address Location on our Netweaver is? 
    I'm being told by the queryview web service WSDL call that it is
    http://<server>:<port>/sap/bw/xml/soap/queryview?sap-client=100
    I'm not sure if this is correct, because I can't get the queryview webservice to work correctly with adobe flex and that is the URL string it is balking at.
    Any help is greatly appreciated!

    when you simply call this url from browser you would get the following messages
    - <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
    - <soap-env:Body>
    - <soap-env:Fault>
      <faultcode>soap-env:Server</faultcode>
      <faultstring xml:lang="en">SOAP processing failure, error id = 112</faultstring>
      </soap-env:Fault>
      </soap-env:Body>
      </soap-env:Envelope>
    Regards
    Raja
    Consider rewarding points to helpful answers and mark it answered once you question is answered.

  • Disable the soap address location

    Hi,
    I wonder if it’s possible to disable the soap:address location in the WSDL?
    My problem is that I use a proxy (SOAP) between my WebService Client and the WebLogic
    WebService.
    When I ask the WSDL through my proxy, it’s work well. But the next call, the client
    goes directly to the WebLogic and does not use anymore the proxy. I think the
    problem comes from the soap:address location.
    Thanks for your help.
    Charles

    Hi Charles,
    You could post your own WSDL, see the docs [1] for details, or you could
    use a dynamic client without the WSDL; there are a number of examples of
    how to do this such as Manoj's [2].
    Regards,
    Bruce
    [1]
    http://edocs.bea.com/wls/docs81/webserv/webxml.html#1007638
    [2]
    http://manojc.com/?sample25
    Charles Desmoulins wrote:
    >
    Hi,
    I wonder if it’s possible to disable the soap:address location in the WSDL?
    My problem is that I use a proxy (SOAP) between my WebService Client and the WebLogic
    WebService.
    When I ask the WSDL through my proxy, it’s work well. But the next call, the client
    goes directly to the WebLogic and does not use anymore the proxy. I think the
    problem comes from the soap:address location.
    Thanks for your help.
    Charles

  • WSDL address - dev, qat, prd - upd

    Hi,
    in my WSDL file I can see section:
    <soap:address xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" location="the URL of the server"
    the URL of the server - is the <b>dev</b> server URL
    when I create a web dynpro app it uses this URL
    but what if I'd like to test my web dynpro
    app with QAT server with new URL ?
    do I need to have/import a new WSDL ?
    are there any procedures on how to handle this?
    - if there are no official procedures maybe
    you can tell how you handle it from your own exprience ?
    Thanks for your help,
    Regards,
    michal
    Message was edited by: Michal Krawczyk

    hi
    You can create the alias for the wsdl file and get it from your application.
    Create the alias name in the server for the WSLD file that should be point outin the server location .Create the alias in Visual Admin -> Destinations->Http
    try this to call the webservice by generic
    final InitialContext ctx = new InitialContext();
    final DestinationService dstService = (DestinationService)ctx.lookup(DestinationService.JNDI_KEY);
    if (dstService== null)
    throw new NamingException ("Destination service not available");
    final Destination destination = dstService.getDestination("HTTP","WEBSERVICE NAME");
    final HTTPDestination httpDestination = (HTTPDestination) destination;
    HttpURLConnection httpConnection = httpDestination.getURLConnection();
    String xyz = String.valueOf(httpConnection.getURL());
    Request_AdvLocationVer1ViDocument_getLocation obj=wdContext.currentRequest_AdvLocationVer1ViDocument_getLocationElement().modelObject();
    obj._setHTTPDestinationName("WEBSERVICE NAME");
    obj._setEndPoint(xyz);
    obj.execute();
    Pls see the thread
    Re: Web Services :HTTP Destination not getting resloved.
    Kind Regards,
    Mukesh.

Maybe you are looking for