Trinidad at Websphere 5.1.2 how to?

We are having a problem when we try to implement apache trinidad jsf in our Websphere platform.
We are using Suns jsf 1.1 library, but we want to use trinidad jsf? What ever we tried to instal we all failed,
Any idea how to install Trinidad Jsf on to Websphere 5.1.2 step by step ?

Completely off the cuff, my experience with introducing non-IBM libraries meant to replace IBM libraries has been negative. One thing IBM recommends doing for other libraries (e.g., myfaces) is to have the jars as shared libraries in the server instead of application-local WEB-INF/lib. Have you tried including the libraries that way? We have a mix of 5.1.2 and 6.1 apps, and both of them are highly optimized for IBM's implementations, even to the point of ignoring basic specification requirements (for example, until 6.1.0003 or so they would not allow servlet filters, making Struts 2 apps impossible).
Also, it sounds like you are using WSAD (or RAD) for development. Be sure to remove all the facets except the base JSF libraries, including the extended JSF stuff. IBM tries to do a lot of work for you and is automated almost to a fault. I use RAD 7 for 3/4 of my stuff, and whenever I use non-IBM I usually try to just get rid of a lot of their automation, just to be safe. Of course, the templating and automatic managed bean generation is pretty cool, but sometimes it gets in the way if you are trying to do something outside IBM's original intention.
BTW, in your prefs you can change the "pagecode" default package name to be created in your own "com.mycompany.app.web.pagecode". Took me a year to figure that one out :)

Similar Messages

  • Send message to WebSphere MQ resource adapter - how?

    Hi,
    has anybody a working sample how an Weblogic EJB can write to an MQ queue via the WebSphere MQ resource adapter?
    http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.csqzaw.doc/uj40010_.htm
    I took Adrian Cole's sample from
    WebSphere MQ resource adapter  and Weblogic - how?
    the message driven bean works, but for outbound I couldn't get it to work.
    I used
         @Resource(name = "wmq/ConnectionFactory")
         private javax.jms.ConnectionFactory queueConnectionFactory;
         Connection connection = null;
         connection = queueConnectionFactory.createConnection();
         Session sess = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
         MessageProducer messageProducer = sess.createProducer(queue);
         messageProducer.send(msg);
         connection.close();
    But then I get
    javax.jms.JMSException: [JMSPool:169819]There was an error with a resource pool used to pool JMS sessions: weblogic.common.ResourceException: 0:javax.jms.JMSException: MQJCA1018:Only one session per connection allowed.
    Can't I use the Resource Adapter to trigger an MDB and write in the same application to the same Resource Adapter?
    Thanks,
    Juergen

    By using @Resource you activate Session pooling [http://download.oracle.com/docs/cd/E12840_01/wls/docs103/jms/j2ee.htm]. Although you constantly create and close the connection, you end up with one connection and multiple Sessions created out of it when there is sufficient concurrency. In JCA, ManagedConnection represents a single Resource (because it also deals with JDBC). In JMS, a Session is a resource. Session pooling violates the requirement "one resource per managed connection" which is what MQ Resource Adapter is telling [http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.csqzaw.doc/uj40030_.htm].
    Some possible solutions:
    * Set max-beans-in-free-pool 1 in weblogic-ejb-jar.xml
    * disable wls Session pooling by simply looking up using InitialContext.lookup. WLS session pool is redundant because resource adapters usually pool connections [http://download.oracle.com/docs/cd/E12840_01/wls/docs103/resadapter/connect.html]. Define outbound resource adapter use its connection factory.

  • MOD_PLSQL on Websphere

    I have a question:
    Can we config mod_plsql on Websphere? If can, how to do?
    Has anyone can answer it? Please help me.
    Thanks a lot.
    Phong

    Scott,
    Everything is working fine! Thanks a lot.
    I have a question regarding Edit Security Attributes. How come the public user value is APEX_PUBLIC_USER and not PUBLIC_USER?
    Thx,
    Louis-Guillaume
    Homepage : http://www.insum.ca
    Blog : http://insum-apex.blogspot.com

  • Hi All ,need ideas on using oracle apex maps...

    Hi All,
    I need a map on country like trinidad and Tobago and jamaica together how do I accomplish that...using the current oracle apex..
    I couldnt find country tobaga and Trinidad listed there
    Thanks any guidance shall be appreciated..
    Paul j

    Hi Paul,
    There actually isn't a country map for Jamaica or Trinidad and Tobago in the suite of AnyChart maps that we integrate into Application Express. Your easiest option is to use either the World, Americas or North America map - either of these will allow you to represent Jamaica and Trinidad & Tobago on a map, and associate data with it. I've used the Americas map as an example here: http://apex.oracle.com/pls/apex/f?p=36648:89.
    I appreciate that this isn't ideal if you wish to represent these locations on their respective country maps, but it might be a possible workaround for you. Alternatively, you would need to source your own Shapefiles for these countries, and use the AnyChart Flash Map Converter utility - http://anychart.com/products/anymap/converter/ - to convert your Shapefile into a .amap file. That .amap file would then need to be incorporated in your APEX /images directory, and its information would then need to be referenced in your map SQL query in order to associate data with the new maps. For further information on the Converter utility, or indeed on the AnyChart maps, please refer to the AnyChart site: http://anychart.com/products/anymap/docs/.
    Regards,
    Hilary

  • JWSDP1.5: wscompile error: "(should not happen): tie.generator.002

    Hi all,
    I'm working with a doc/lit webservice; I have a WSDL and I'm attempting to generate Java artefacts with wscompile. I'm using JWSDP1.5. I've had a range of errors (I'm updating an old WSDL for the Tentative Hold Protocol, see http://www.w3.org/TR/tenthold-2/). The latest, though, is problematic. The final error message is:
    error: generator error: internal error (should not happen): tie.generator.002I have included the full output from wscompile at the end of this posting; I'll post the full WSDL in a reply. Any advice would be much appreciated!
    Cheers,
    --Tim West
    Full output (from wscompile Ant task) - added linebreaks for readability
    Buildfile: C:\common\eclipse-projects\thp\build.xml
    wscompile-init:
    ANEW-generate-server-binding:
    [wscompile] command line: wscompile -d C:\common\eclipse-projects\thp\zant-build \
    -features:documentliteral,wsi -g -gen:server -keep -verbose \
    C:\common\eclipse-projects\thp\server-wscompile-config.xml -classpath (path omitted for readability)
    [wscompile] [CustomClassGenerator: generating JavaClass for: userDefinedBody]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdRequestHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdHeader]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdRequestAckHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyRequestHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyResponseChoiceHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyGrantHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdGrantHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdModifyDenialHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdDenialHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdCancellationRequestHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdCancellationResponseHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusQueryHdr]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusResponseBody]
    [wscompile] [CustomClassGenerator: generating JavaClass for: statusStructure]
    [wscompile] [CustomClassGenerator: generating JavaClass for: holdStatusResponseHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: userDefinedBody]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdHeader]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdRequestHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdRequestAckHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdModifyRequestHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdGrantHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdModifyGrantHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdDenialHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdModifyDenialHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdModifyResponseChoiceHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdCancellationRequestHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdCancellationResponseHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdStatusQueryHdr]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: statusStructure]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdStatusResponseBody]
    [wscompile] [LiteralObjectSerializerGenerator: writing  serializer/deserializer for: holdStatusResponseHdr]
    [wscompile] error: generator error: internal error (should not happen): tie.generator.002
    BUILD FAILED: C:\common\eclipse-projects\thp\build.xml:342: wscompile failed
    Total time: 2 seconds

    Hi again,
    The offending WSDL is below. I should add that I Googled this and couldn't find anything useful. Axis is happy with the WSDL, as is the validator at http://www.soapclient.com/SoapTools.html (though I'm not sure of its quality). I'm now downloading IBM Websphere 6 to see how that goes.
    Thanks again,
    -Tim West
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions
        name="TentativeHold"
        targetNamespace="http://www.w3.org/2001/08/thp/definitions"
        xmlns:tns="http://www.w3.org/2001/08/thp/definitions"
        xmlns:holdSchema="http://www.w3.org/2001/08/thp/schemas"
        xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
        xmlns="http://schemas.xmlsoap.org/wsdl/">
      <types>
        <schema xmlns="http://www.w3.org/2001/XMLSchema"
            xmlns:holdSchema="http://www.w3.org/2001/08/thp/schemas"
            targetNamespace="http://www.w3.org/2001/08/thp/schemas">
          <!-- =================================================================== -->
          <!-- Item - holdHeader -->
          <!-- Note - This information is required in all the Tentative Hold Protocol
                      communications. -->
          <!-- Fields- holdID - UUID. -->
          <!--             customerID - account number or other identifier -->
          <!--             replyTo - could be a unique locator such as a URI or an
                              email address depending on the communication protocol
                              to be used. -->
          <!-- comment - space for trading partner defined info. -->
          <!-- =================================================================== -->
          <complexType name="holdHeader">
            <sequence>
              <element name="holdID" type="int"/>
              <element name="customerID" type="string"/>
              <element name="replyTo" type="string"/>
              <element name="comment" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - userDefinedBody -->
          <!-- Note - This will carry any domain-specific information  (e.g., product
                ID and quantity). An implementation shall probably have many
                different userDefinedBody's (one for holdRequest, holdRequestAck,
                ...). This body is used in all messages. -->
          <!-- Fields - Trading partner to trading partner specific or an agreed
             - standard (e.g., RosettaNet PIP). -->
          <!-- =================================================================== -->
            <!-- TIM: Just junk here for now, must fix later -->
          <complexType name="userDefinedBody">
            <sequence>
              <element name="someRequestField" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdRequestHdr -->
          <!-- Note - Specifies the Tentative Hold Protocol header for messages
             - requesting a tentative hold. -->
          <!-- Fields - Same as holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdRequestHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdRequestAckHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + timeUntilResponse - a indication of the time it
             - will take the resource provider to process the request. -->
          <!-- =================================================================== -->
          <complexType name="holdRequestAckHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
              <element name="timeUntilResponse" type="duration"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdGrantHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + holdDuration - the agreed to length of the hold
             - on the resource requested. -->
          <!-- =================================================================== -->
          <complexType name="holdGrantHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
              <element name="holdDuration" type="duration"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdDenialHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + reason - a description of the reason for the
             - denial. The implementation may choose to use reason codes or just
             - textual descriptions. -->
          <!-- =================================================================== -->
          <complexType name="holdDenialHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
              <element name="reason" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdModifyRequestHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdModifyRequestHdr">
            <sequence>
              <element name="modifiedHoldRequest" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdModifyGrantHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + holdDuration - the agreed to length of the hold
             - on the resource requested. -->
          <!-- =================================================================== -->
          <complexType name="holdModifyGrantHdr">
            <sequence>
              <element name="modifiedHoldRequest" type="holdSchema:holdGrantHdr"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdModifyDenialHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + reason - a description of the reason for the denial.
             - The implementation may choose to use reason codes or just textual
             - descriptions.-->
          <!-- =================================================================== -->
          <complexType name="holdModifyDenialHdr">
            <sequence>
              <element name="modifiedHoldRequest" type="holdSchema:holdDenialHdr"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdModifyResponseChoiceHdr -->
          <!-- Note - The use of a single type for this response was to facilitate a
             - synchronous request/response for the modify request without preventing
             - asynchronous.-->
          <!-- Fields - Either holdModifyGrantHdr or holdModifyDenialHdr -->
          <!-- =================================================================== -->
          <!-- TIM: JWSDP does not support xsd:choice, so I'm turning this into a sequence.
             -      The implementor is now responsible for ensuring exactly one of these
                    is present.
            -->
          <complexType name="holdModifyResponseChoiceHdr">
            <sequence>
              <element name="grant" type="holdSchema:holdModifyGrantHdr"/>
              <element name="deny" type="holdSchema:holdModifyDenialHdr"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdCancellationRequestHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + customerReason - a description of or a code for
             - the reason why the hold is being cancelled. -->
          <!-- =================================================================== -->
          <complexType name="holdCancellationRequestHdr">
            <sequence>
              <element name="customerHold" type="holdSchema:holdHeader"/>
              <element name="customerReason" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdCancellationResponseHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdCancellationResponseHdr">
            <sequence>
              <element name="customerHold" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdCancellationNotificationHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader + cancellationReason - a description of or a code
             -for the reason the vendor is cancelling the hold. -->
          <!-- =================================================================== -->
          <complexType name="holdCancellationNotificationHdr">
            <sequence>
              <element name="customerHold" type="holdSchema:holdHeader"/>
              <element name="cancellationReason" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdStatusQueryHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdStatusQueryHdr">
            <sequence>
              <element name="customerHold" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdStatusResponseHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <complexType name="holdStatusResponseHdr">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - statusStructure -->
          <!-- Note - -->
          <!-- Fields - holdHeader + holdState - a description of the state of the hold.
             - Possible values currently defined are: responding, in process, active,
             - and inactive. The definition is left open (not restricted) for future or
             - user refinement of the useful values. -->
          <!-- =================================================================== -->
          <complexType name="statusStructure">
            <sequence>
              <element name="itemHeader" type="holdSchema:holdHeader"/>
              <element name="holdState" type="string"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdStatusResponseBody -->
          <!-- Note - -->
          <!-- Fields - holdItemsCount - the number of holds matching the holdStatusQuery. -->
          <!--             itemList - The header and state of the holds that match the query. -->
          <!-- =================================================================== -->
          <complexType name="holdStatusResponseBody">
            <sequence>
              <element name="holdItemsCount" type="int"/>
              <element name="itemList" type="holdSchema:statusStructure" minOccurs="0" maxOccurs="unbounded"/>
            </sequence>
          </complexType>
          <!-- =================================================================== -->
          <!-- Item - holdErrorHdr -->
          <!-- Note - -->
          <!-- Fields - holdHeader -->
          <!-- =================================================================== -->
          <!-- TIM: Combined old "holdErrorHdr" and "holdErrorBody" as a fault must
             - have only a single part (see WSDL sec 3.6).
            -->
          <complexType name="holdError">
            <sequence>
              <element name="baseHeader" type="holdSchema:holdHeader"/>
              <element name="holdErrorType" type="int"/>
              <element name="holdErrorDesc" type="string"/>
            </sequence>
          </complexType>
          <!-- TIM: To use doc/lit, we need <element> tags here to reference from WSDL -->
          <element name="userDefinedBody" type="holdSchema:userDefinedBody"/>
          <element name="holdRequestHdr" type="holdSchema:holdRequestHdr"/>
          <element name="holdRequestAckHdr" type="holdSchema:holdRequestAckHdr"/>
          <element name="holdGrantHdr" type="holdSchema:holdGrantHdr"/>
          <element name="holdDenialHdr" type="holdSchema:holdDenialHdr"/>
          <element name="holdModifyRequestHdr" type="holdSchema:holdModifyRequestHdr"/>
          <element name="holdModifyGrantHdr" type="holdSchema:holdModifyGrantHdr"/>
          <element name="holdModifyDenialHdr" type="holdSchema:holdModifyDenialHdr"/>
          <element name="holdModifyResponseChoiceHdr" type="holdSchema:holdModifyResponseChoiceHdr"/>
          <element name="holdCancellationRequestHdr" type="holdSchema:holdCancellationRequestHdr"/>
          <element name="holdCancellationResponseHdr" type="holdSchema:holdCancellationResponseHdr"/>
          <element name="holdCancellationNotificationHdr" type="holdSchema:holdCancellationNotificationHdr"/>
          <element name="holdStatusQueryHdr" type="holdSchema:holdStatusQueryHdr"/>
          <element name="holdStatusResponseHdr" type="holdSchema:holdStatusResponseHdr"/>
          <element name="holdStatusResponseBody" type="holdSchema:holdStatusResponseBody"/>
          <element name="holdError" type="holdSchema:holdError"/>
        </schema>
      </types>
      <message name="HoldRequest">
        <part name="headerHoldRequest" element="holdSchema:holdRequestHdr"/>
        <part name="bodyHoldRequest" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldRequestAck">
        <part name="headerHoldRequestAck" element="holdSchema:holdRequestAckHdr"/>
        <part name="bodyHoldRequestAck" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldGrantResponse">
        <part name="headerHoldGrantResponse" element="holdSchema:holdGrantHdr"/>
        <part name="bodyHoldGrantResponse" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldDenialResponse">
        <part name="headerHoldDenialResponse" element="holdSchema:holdDenialHdr"/>
        <part name="bodyHoldDenialResponse" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldModifyRequest">
        <part name="headerHoldModifyRequest" element="holdSchema:holdModifyRequestHdr"/>
        <part name="bodyHoldModifyRequest" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldModifyResponse">
        <part name="headerHoldModifyResponse" element="holdSchema:holdModifyResponseChoiceHdr"/>
        <part name="bodyHoldModifyResponse" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldCancellationRequest">
        <part name="headerHoldCancellationRequest" element="holdSchema:holdCancellationRequestHdr"/>
        <part name="bodyHoldCancellationRequest" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldCancellationResponse">
        <part name="headerHoldCancellationResponse" element="holdSchema:holdCancellationResponseHdr"/>
        <part name="bodyHoldCancellationResponse" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldCancellationNotification">
        <part name="header" element="holdSchema:holdCancellationNotificationHdr"/>
        <part name="body" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldStatusQueryRequest">
        <part name="headerHoldStatusQueryRequest" element="holdSchema:holdStatusQueryHdr"/>
        <part name="bodyHoldStatusQueryRequest" element="holdSchema:userDefinedBody"/>
      </message>
      <message name="HoldStatusResponse">
        <part name="headerHoldStatusResponse" element="holdSchema:holdStatusResponseHdr"/>
        <part name="bodyHoldStatusResponse" element="holdSchema:holdStatusResponseBody"/>
      </message>
      <message name="HoldErrorResponse">
        <!-- TIM: altered to be consistent with updated schema - the
           - fault body must have only one part
          -->
        <part name="bodyHoldErrorResponse" element="holdSchema:holdError"/>
      </message>
      <portType name="TentativeHoldServicePortType">
        <operation name="InitiateHold">
          <input message="tns:HoldRequest"/>
          <output message="tns:HoldRequestAck"/>
          <!--
          <fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
          -->
        </operation>
        <operation name="InitiateHoldModify">
          <input message="tns:HoldModifyRequest"/>
          <output message="tns:HoldModifyResponse"/>
          <!--
          <fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
          -->
        </operation>
        <operation name="InitiateHoldCancellation">
          <input message="tns:HoldCancellationRequest"/>
          <output message="tns:HoldCancellationResponse"/>
          <!--
          <fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
          -->
        </operation>
        <operation name="InitiateStatusQuery">
          <input message="tns:HoldStatusQueryRequest"/>
          <output message="tns:HoldStatusResponse"/>
          <!--
          <fault name="HoldErrorResponse" message="tns:HoldErrorResponse"/>
          -->
        </operation>
      </portType>
      <portType name="TentativeHoldNotificationServicePortType">
        <operation name="NotifyHoldGranted">
          <output message="tns:HoldGrantResponse"/>
        </operation>
        <operation name="NotifyHoldDenied">
          <output message="tns:HoldDenialResponse"/>
        </operation>
        <operation name="NotifyServerHoldCancellation">
          <output message="tns:HoldCancellationNotification"/>
        </operation>
      </portType>
      <binding name="TentativeHoldSoapBinding" type="tns:TentativeHoldServicePortType">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
          <operation name="InitiateHold">
            <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHold"/>
            <input>
              <soap:body use="literal"/>
            </input>
            <output>
              <soap:body use="literal"/>
            </output>
            <!--
            <fault name="HoldErrorResponse">
              <soap:fault name="HoldErrorResponse" use="literal"/>
            </fault>
            -->
          </operation>
          <operation name="InitiateHoldModify">
            <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHoldModify"/>
            <input>
              <soap:body use="literal"/>
            </input>
            <output>
              <soap:body use="literal"/>
            </output>
            <!--
            <fault name="HoldErrorResponse">
              <soap:fault name="HoldErrorResponse" use="literal"/>
            </fault>
            -->
          </operation>
          <operation name="InitiateHoldCancellation">
            <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateHoldCancellation"/>
            <input>
              <soap:body use="literal"/>
            </input>
            <output>
              <soap:body use="literal"/>
            </output>
            <!--
            <fault name="HoldErrorResponse">
              <soap:fault name="HoldErrorResponse" use="literal"/>
            </fault>
            -->
          </operation>
          <operation name="InitiateStatusQuery">
            <soap:operation soapAction="http://www.w3.org/2001/08/thp/InitiateStatusQuery"/>
            <input>
              <soap:body use="literal"/>
            </input>
            <output>
              <soap:body use="literal"/>
            </output>
            <!--
            <fault name="HoldErrorResponse">
              <soap:fault name="HoldErrorResponse" use="literal"/>
            </fault>
            -->
          </operation>
      </binding>
      <service name="TentativeHoldService">
        <documentation> Mythical Tentative Hold Web service</documentation>
        <port name="TentativeHoldPort" binding="tns:TentativeHoldSoapBinding">
          <soap:address location="http://xyz.com/tentativeHold/"/>
        </port>
      </service>
      <service name="TentativeHoldNotificationService">
        <port name="NotificationPort" binding="tns:TentativeHoldSoapBinding">
          <soap:address location="http://xyz.com/tentativeHoldNotification"/>
        </port>
      </service>
    </definitions>

  • JNDI returns a different class for different applications

    Hello,
    I have a WebSphere server that runs a JNDI service, in which I defined an entry for a ConnectionFactory declared on a remote server. On the server I run an EJB application which connects the JNDI and gets the ConnectionFactory. I also have a stand-alone Java application which gets the ConnectionFactory from the JNDI on the server.
    The problem is that the implementation class for the ConnectionFactory I get is different between the EJB and the stand-alone applications. The stand-alone application recieves a MQXAQueueConnectionFactory, which is just fine because I want to use XA transactions, but the EJB application receives a JMSQueueConnectionFactoryHandle!
    What can be the reason for that? How does the JNDI service determine which implementation class to return?
    (I suppose that is a specific behavior for Websphere...) How can I control that, if at all?
    Thanks!

    I have a similar situation occurring. Was therre any resolution found?

  • Can I  use JMS?

    I write a trigger to detect the updated record in my oracle db table(once trigger detects the change it sends out the information). I also want to write a servlet on websphere app server. How can I make the servlet as a listener in order to get the information sent from oracle? Can I use JMS?

    Yes, you do indeed get the point :-)
    For your other questions -
    1) Oracle AQ does not use JNDI to connect - you get the connection with...
    TopicConnectionFactory tc_factory = AQjmsFactory.getTopicConnectionFactory(serverAddr,"ORCL",1521,"thin");2)Yep - Queues are one-to-one, Topics are one-to-many. You will need to be careful with the client id when you create the subscriptions. Each applets client ID will need to be different or only one will consume the message.
    R.
    KMS

  • Creating a separate transaction in both JTA and nonJTA environment

    I want to record some performance information for each call to my application and I want to write it to the database even if the transaction rolls back. The code needs to run both in a Websphere JTA context and a non-JTA context. The code I wrote works in non-JTA, but doesn't work in Websphere JTA context. How do I create an independent transaction when running in JTA context ? Would starting a new thread work, assuming that started a new JTA transaction ? Is there any other way that would have less overhead ?

    One way would be to use non-JTA data source. I am not sure that WebSphere allows that in JTA case, but you still may be able to create it and put into jndi "by hand".
    Alternatively you may try to use suspend / resume apis defined in jta spec.:
    Transaction tobj = TransactionManager.suspend();
    TransactionManager.resume(tobj);
    For more please see
    Java Transaction API (JTA)
    3.2.3 Suspending and Resuming a Transaction

  • 10.1.3 ADF migration & regions

    Hi,
    I've noticed that the ADF regions taglibs are not migrated to Trinidad. My applications make an extensive use of regions. Is there any future support planned for migrating adf regions ?
    Thanks,
    Seb.

    Hello Sebastien,
    Sorry for the late answer, I was actually browsing about regions because I failed to have Facelets work easily with data bindings and found this thread. Actually, Trinidad does support regions (not sure how functional it is either), but it's a secret feature that's flagged experimental, undomcumented and deprecated. Actually it's more than deprecated, it's not officially supported at all and, because of that, might get dumped at any time without any notice. It's so mainly because Trinidad has native Facelets support, which is superior and has community acknowledgment, whereas regions remains marginal. You can use the equivalent of region using the following (can be found in Trinidad demo code):
    In your page
    <tr:componentRef id="reg1" componentType="org.apache.myfaces.trinidaddemo.region.stock"
                  value="Watch this stock">
      <f:attribute name="symbol" value="XYZ"/>
      <f:attribute name="company" value="XYZ Incorp"/>
      <f:attribute name="amount" value="13.66"/>
      <f:facet name="action">
        <tr:commandButton text="Buy" disabled="true"/>
      </f:facet>
    </tr:componentRef>In WEB-INF/region-metadata.xml:
    <faces-config>
      <component>
        <component-type>org.apache.myfaces.trinidaddemo.region.stock</component-type>
        <component-class>
          org.apache.myfaces.trinidad.component.UIXRegion
        </component-class>
        <component-extension>
          <region-jsp-ui-def>/components/regions/stock.jspx</region-jsp-ui-def>
        </component-extension>
        <attribute>
          <attribute-name>symbol</attribute-name>
          <attribute-class>java.lang.String</attribute-class>
          <attribute-extension>
            <required>true</required>
          </attribute-extension>
        </attribute>
        <attribute>
          <attribute-name>amount</attribute-name>
          <attribute-class>float</attribute-class>
          <default-value>0</default-value>
        </attribute>
        <attribute>
          <attribute-name>company</attribute-name>
          <attribute-class>java.lang.String</attribute-class>
          <default-value>Default Company</default-value>
        </attribute>
        <attribute>
          <attribute-name>description</attribute-name>
          <attribute-class>java.lang.String</attribute-class>
          <default-value>Default Description</default-value>
        </attribute>
      </component>
    </faces-config>In the region page (here /components/regions/stock.jspx):
    <tr:componentDef var="stuff">
      <tr:panelBox text="Symbol:#{stuff.symbol} Company:#{stuff.company}">
        <tr:outputText value="#{stuff.description}"/>
        <tr:outputFormatted
          value="<br>Current Value:<b>$#{stuff.amount}</b>"/>
        <tr:outputFormatted rendered="#{not empty bindings}"
          value="<br>Value attribute is:#{bindings}"/>
        <tr:facetRef facetName="action"/>
      </tr:panelBox>
    </tr:componentDef>For now it's part of the JAR, so it's available. It's far from the best solution, but it'll most likely provide what you need for a first migration phase. Moving to either Facelets or 11g templates is probably going to be mandatory in the future but, who knows, if you're lucky enough, that future could be far enough for some templating standard to emerge, possibly with JSF 2.0, see https://javaserverfaces-spec-public.dev.java.net/proposals/JSF-2_0-draft.html.
    Regards,
    ~ Simon

  • The html images have broken in Struts. Why?

    I'm developing a web application using JSP and Struts.
    The Context Root of my app is : mm
    1- The image tag: img src="../_images/logo.gif"
    Requested URL: http://localhost:8090/mm/jsp/addCompany.jsp
    Rendered Image URL: http:// localhost:8090/mm/_images/logo.gif
    Websphere: OK JBoss: OK
    Requested URL: http://localhost:8090/mm/addCompany.do (Struts Action)
    Rendered Image URL: http:// localhost:8090/_images/logo.gif
    Websphere: Broken JBoss: Broken
    2- The image tag: img src="<%= request.getContextPath() %>/_images/logo.gif"
    Requested URL: http://localhost:8090/mm/jsp/addCompany.jsp
    Rendered Image URL: http:// localhost:8090/mm/_images/logo.gif
    Websphere: Broken JBoss: OK
    Requested URL: http://localhost:8090/mm/addCompany.do (Struts Action)
    Rendered Image URL: http:// localhost:8090/mm/_images/logo.gif
    Websphere: OK JBoss: Broken
    How to solve this problem!
    thanks in advance

    Struts has an <html:base> tag that should solve your problems
    http://struts.apache.org/struts-action/struts-taglib/tlddoc/

  • Help! Got ipod nano 2gb for christmas,

    can't find device on itunes to disconnect, and I disconnected before I knew I had to eject before diconnecting

    my 1st nano ipod jus stopped working, these things are so **** fragile n its so expensive i think i need to take it back. i bought it in canada and im in trinidad now, god alone know s how long itll take to b repaired!

  • JNDI service returns a different ConnectionFactory implementation

    Hello,
    I have a WebSphere server that runs a JNDI service, in which I defined an entry for a ConnectionFactory declared on a remote server. On the server I run an EJB application which connects the JNDI and gets the ConnectionFactory. I also have a stand-alone Java application which gets the ConnectionFactory from the JNDI on the server.
    The problem is that the implementation class for the ConnectionFactory I get is different between the EJB and the stand-alone applications. The stand-alone application recieves a MQXAQueueConnectionFactory, which is just fine because I want to use XA transactions, but the EJB application receives a JMSQueueConnectionFactoryHandle!
    What can be the reason for that? How does the JNDI service determine which implementation class to return?
    (I suppose that is a specific behavior for Websphere...) How can I control that, if at all?
    Thanks!

    I have a similar situation occurring. Was therre any resolution found?

  • Facing challenges in CCSID

    My OSB proxy service is reading UTF-8 encoding XML messages from an IBM WebSphere MQ and the XML has the following elements with special chars:
    <value>10% ֠15%</value>
    <value>This corrected report is issued to correct the Interpretation from Ӳ5 Ԡto Ԡ250 Ԯ There are no other changes to the original report.</value>
    When I opened my XML with N++ edition with UTF-8 encoding format it’s showing the following special chars: x96, x93, x94.
    Now the problem is OSB is replacing all these special chars with question mark symbol (?) while reading from IBM WebSphere MQ queue. How to avoid this behavior? Please advise.
    Thanks in advance

    Thanks.
    I assigned CCSID value to 1208 in MQ Connection resource still I am getting the following exception:
    Caused By: com.bea.wli.sb.sources.TransformException: Failed to parse XML text
         at com.bea.wli.sb.sources.XmlObjectSource.getInstance(XmlObjectSource.java:206)
         at com.bea.wli.sb.sources.XmlObjectTransformer.getXmlObjectSource(XmlObjectTransformer.java:199)
         at com.bea.wli.sb.sources.XmlObjectTransformer.transform(XmlObjectTransformer.java:111)
         at com.bea.wli.sb.sources.MetaTransformer.doTransform(MetaTransformer.java:138)
         at com.bea.wli.sb.sources.MetaTransformer.transform(MetaTransformer.java:89)
         at com.bea.wli.sb.pipeline.PipelineContextImpl$LazyInitTransformer.transform(PipelineContextImpl.java:1640)
         at com.bea.wli.sb.context.SOAPMessageImpl.parseCheckPayload(SOAPMessageImpl.java:1212)
         at com.bea.wli.sb.context.SOAPMessageImpl.generateBody(SOAPMessageImpl.java:1040)
         at com.bea.wli.sb.context.SOAPMessageImpl.getBody(SOAPMessageImpl.java:260)
         at com.bea.wli.sb.context.BodyVariable.getTypedValue(BodyVariable.java:106)
         at com.bea.wli.sb.context.BodyVariable.getTypedValue(BodyVariable.java:25)
         at com.bea.wli.sb.context.SystemVariable.getValue(SystemVariable.java:49)
         at com.bea.wli.sb.context.MessageContextImpl.getVariableValue(MessageContextImpl.java:202)
         at com.bea.wli.sb.stages.expressions.xquery.XQueryExprExecutor.getVariables(XQueryExprExecutor.java:182)
         at com.bea.wli.sb.stages.expressions.xquery.XQueryExprExecutor.executeJavaObject(XQueryExprExecutor.java:129)
         at stages.logging.runtime.LogRuntimeStep.processMessage(LogRuntimeStep.java:109)
         at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
         at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
         at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
         at com.bea.wli.sb.pipeline.PipelineStage.processMessage(PipelineStage.java:84)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
         at com.bea.wli.sb.pipeline.Pipeline.processMessage(Pipeline.java:141)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
         at com.bea.wli.sb.pipeline.PipelineNode.doRequest(PipelineNode.java:55)
         at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
         at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
         at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:96)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
         at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:375)
         at com.bea.wli.sb.transports.mq.InboundRequestWorkerThread.run(InboundRequestWorkerThread.java:141)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: org.apache.xmlbeans.XmlException: error: Illegal XML character: 0x1a
    org.apache.xmlbeans.impl.piccolo.io.IllegalCharException: Illegal XML character: 0x1a
         at org.apache.xmlbeans.impl.piccolo.xml.XMLReaderReader.read(XMLReaderReader.java:169)
         at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.yy_refill(PiccoloLexer.java:3477)
         at org.apache.xmlbeans.impl.piccolo.xml.PiccoloLexer.yylex(PiccoloLexer.java:3962)
         at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.yylex(Piccolo.java:1290)
         at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.yyparse(Piccolo.java:1400)
         at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:714)
         at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3456)
         at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1331)
         at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1305)
         at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:360)
         at org.apache.xmlbeans.XmlObject$Factory.parse(XmlObject.java:765)
         at com.bea.wli.sb.sources.XmlObjectSource.getInstance(XmlObjectSource.java:197)
         at com.bea.wli.sb.sources.XmlObjectTransformer.getXmlObjectSource(XmlObjectTransformer.java:199)
         at com.bea.wli.sb.sources.XmlObjectTransformer.transform(XmlObjectTransformer.java:111)
         at com.bea.wli.sb.sources.MetaTransformer.doTransform(MetaTransformer.java:138)
         at com.bea.wli.sb.sources.MetaTransformer.transform(MetaTransformer.java:89)
         at com.bea.wli.sb.pipeline.PipelineContextImpl$LazyInitTransformer.transform(PipelineContextImpl.java:1640)
         at com.bea.wli.sb.context.SOAPMessageImpl.parseCheckPayload(SOAPMessageImpl.java:1212)
         at com.bea.wli.sb.context.SOAPMessageImpl.generateBody(SOAPMessageImpl.java:1040)
         at com.bea.wli.sb.context.SOAPMessageImpl.getBody(SOAPMessageImpl.java:260)
         at com.bea.wli.sb.context.BodyVariable.getTypedValue(BodyVariable.java:106)
         at com.bea.wli.sb.context.BodyVariable.getTypedValue(BodyVariable.java:25)
         at com.bea.wli.sb.context.SystemVariable.getValue(SystemVariable.java:49)
         at com.bea.wli.sb.context.MessageContextImpl.getVariableValue(MessageContextImpl.java:202)
         at com.bea.wli.sb.stages.expressions.xquery.XQueryExprExecutor.getVariables(XQueryExprExecutor.java:182)
         at com.bea.wli.sb.stages.expressions.xquery.XQueryExprExecutor.executeJavaObject(XQueryExprExecutor.java:129)
         at stages.logging.runtime.LogRuntimeStep.processMessage(LogRuntimeStep.java:109)
         at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
         at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
         at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
         at com.bea.wli.sb.pipeline.PipelineStage.processMessage(PipelineStage.java:84)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
         at com.bea.wli.sb.pipeline.Pipeline.processMessage(Pipeline.java:141)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
         at com.bea.wli.sb.pipeline.PipelineNode.doRequest(PipelineNode.java:55)
         at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
         at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
         at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:96)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
         at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:375)
         at com.bea.wli.sb.transports.mq.InboundRequestWorkerThread.run(InboundRequestWorkerThread.java:141)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
         at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3488)
         at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1331)
         at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1305)
         at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:360)
         at org.apache.xmlbeans.XmlObject$Factory.parse(XmlObject.java:765)
         at com.bea.wli.sb.sources.XmlObjectSource.getInstance(XmlObjectSource.java:197)
         at com.bea.wli.sb.sources.XmlObjectTransformer.getXmlObjectSource(XmlObjectTransformer.java:199)
         at com.bea.wli.sb.sources.XmlObjectTransformer.transform(XmlObjectTransformer.java:111)
         at com.bea.wli.sb.sources.MetaTransformer.doTransform(MetaTransformer.java:138)
         at com.bea.wli.sb.sources.MetaTransformer.transform(MetaTransformer.java:89)
         at com.bea.wli.sb.pipeline.PipelineContextImpl$LazyInitTransformer.transform(PipelineContextImpl.java:1640)
         at com.bea.wli.sb.context.SOAPMessageImpl.parseCheckPayload(SOAPMessageImpl.java:1212)
         at com.bea.wli.sb.context.SOAPMessageImpl.generateBody(SOAPMessageImpl.java:1040)
         at com.bea.wli.sb.context.SOAPMessageImpl.getBody(SOAPMessageImpl.java:260)
         at com.bea.wli.sb.context.BodyVariable.getTypedValue(BodyVariable.java:106)
         at com.bea.wli.sb.context.BodyVariable.getTypedValue(BodyVariable.java:25)
         at com.bea.wli.sb.context.SystemVariable.getValue(SystemVariable.java:49)
         at com.bea.wli.sb.context.MessageContextImpl.getVariableValue(MessageContextImpl.java:202)
         at com.bea.wli.sb.stages.expressions.xquery.XQueryExprExecutor.getVariables(XQueryExprExecutor.java:182)
         at com.bea.wli.sb.stages.expressions.xquery.XQueryExprExecutor.executeJavaObject(XQueryExprExecutor.java:129)
         at stages.logging.runtime.LogRuntimeStep.processMessage(LogRuntimeStep.java:109)
         at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
         at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
         at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
         at com.bea.wli.sb.pipeline.PipelineStage.processMessage(PipelineStage.java:84)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
         at com.bea.wli.sb.pipeline.Pipeline.processMessage(Pipeline.java:141)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
         at com.bea.wli.sb.pipeline.PipelineNode.doRequest(PipelineNode.java:55)
         at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:1055)
         at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
         at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:96)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
         at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:375)
         at com.bea.wli.sb.transports.mq.InboundRequestWorkerThread.run(InboundRequestWorkerThread.java:141)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

  • How to Set Up SSO Between IBM WebSphere and SAP EP Using JAAS

    Hi
    I have read the article on SDN called "How to Set Up SSO Between IBM WebSphere and SAP EP Using JAAS", which is also the name of my posting.
    The reason why I post this is that I've tried to follow the links in the PDF to get the file WebsphereEpSsoLib.zip but I get an error 403, which tells me that the file is not there.
    Does anybody know where this file went or can somebody tell me an alternative place to get this file?
    Jacob

    Please open the associated whitepaper, and you can find the download link to the .ZIP file on page 4.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/ibm/how to set up single sign-on between an ibm websphere portal and the sap enterprise portal using jaas.pdf
    Hope that works!
    Elise

  • How can I link to a jsp page from another jsp page within websphere portal?

    Afternoon all,
    I have a websphere portlet which displays a jsp page. I want to put a hyperlink on the jsp page which when clicked will open another jsp page.
    Does anyone know how to do this?
    Thanks,
    Alex

    The anchor tag is the correct one for generating clickable links.
    <jsp:forward> is for transferring control at the server end. Its when you decide to change which page you want to show the user. ie check user is logged in. If not then forward them to login page, else display current page.
    I tried that. It does open the jsp page
    but the place and page links in the portal theme get screwed up.Whats mucked up about them? Do they point where they shouldn't?
    You might try using a <base> tag to set where relative links are resolved from.
    Cheers,
    evnafets

Maybe you are looking for