Is MTOM/XOP supported?

We're interested in using MTOM/XOP for SOAP binary transfer. Does anyone know if this is supported in WebLogic 8.1SP4? If not, what version is?
Thanks in advance,
Kevin

According to [https://en.wikipedia.org/wiki/Snapdragon_%28system_on_chip%29 Wikipedia it is a Snapdragon 2]. Which would make it a compatible device.
If you search the Play Store for Firefox do you see a Firefox app to install?

Similar Messages

Oracle BPEL - MTOM/XOP support

I'm testing integration between a JBoss Web service and Oracle BPEL. I created a web service using a stateless EJB with MTOM turned on in JBoss 5.0.1 and tested it using the OSB which worked and returned the MTOM message, but the BPEL is getting confused with the MTOM XOP include element.
The error message from the BPEL is "exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PriviledgeActionException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: application/xop+xml; type="text/xml""
The OSB says the returned XML in the MIME's XOP include element looks like the following
"<xop:Include href="cid:[email protected]" xmlns:xop="http://www.w3.org/2004/08/xop/include"/>"
Something to note is that in java the datatype is defined as byte[] and that the WSDL generated with MTOM turned on is identical to the schema generated with MTOM turned off from JBoss.
Also does BPEL support the 2004 08 xop standard?
I have tried to find a example of MTOM/XOP being used on Oracles BPEL engine and I have been unable to find any useful information.
I appreciate any help. Thank you.
Shane

So,
11g BPEL / JDeveloper does not support MTOM?
If I want to call an external web service as a reference from BPEL and the external web service supports MTOM what are my choices for passing attachments to the external web service, am I limited to inline content?
Thanks,
Joe

MTOM/XOP behavior in WL 10

Hi!
I'm using BEA Workshop for WebLogic v. 10.1.
I want to use MTOM/XOP for sending and receiving binary data, but it doesn't seem to work as I expect.
I can only make it work if the binary data is at the top level in the request or response message.
If I'm using binary data at a lower level it doesn't become an attachment.
I haven't been able to find any documentation that can explain if is this is according to the standard,
if it's a limitation in the WebLogic implementation or if it's related to my use of XmlBeans for binding.
To clarify, I would like to define my types in e.g the following way:
<complexType name="PDFFile">
     <sequence>
          <element name="filename" type="string"/>
          <element name="printDate" type="date"/>
          <element name="contents" type="base64Binary"
               xmime:expectedContentTypes="application/pdf"/>
     </sequence>
</complexType>
<complexType name="BudgetPrint">
     <sequence>
          <element name="customerID" type="string"/>
          <element name="printID" type="string"/>
          <element name="print" type="tns:PDFFile"/>
     </sequence>
</complexType>
The in my JWS file I can have the following:
package com.my.service;
import ...
import weblogic.jws.Policy;
@WebService
@Policy(uri="policy:Mtom.xml", attachToWsdl=true)
public class BudgetService {
     @WebMethod
     public void saveBudgetPrint(BudgetPrint print) {
     @WebMethod
     public BudgetPrint getBudgetPrint(String customerID, String printID) {
This results in the following in the generated WSDL file (the above types have been removed to shorten it):
<?xml version='1.0' encoding='UTF-8'?>
<s2:definitions name="BudgetServiceServiceDefinitions" targetNamespace="http://com/my/service" xmlns="" xmlns:s0="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:s1="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:s2="http://schemas.xmlsoap.org/wsdl/" xmlns:s3="http://com/my/service" xmlns:s4="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">
<s0:Policy s1:Id="policy:Mtom">
<wsoma:OptimizedMimeSerialization xmlns:wsoma="http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization"/>
</s0:Policy>
<wsp:UsingPolicy s2:Required="true"/>
<s2:types>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://com/my/service" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://my.com/types"/>
<xs:element name="saveBudgetPrint">
<xs:complexType>
<xs:sequence>
<xs:element name="print" type="typ:BudgetPrint" xmlns:typ="http://my.com/types"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="saveBudgetPrintResponse">
<xs:complexType>
<xs:sequence/>
</xs:complexType>
</xs:element>
<xs:element name="getBudgetPrint">
<xs:complexType>
<xs:sequence>
<xs:element name="customerID" type="xs:string"/>
<xs:element name="printID" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="getBudgetPrintResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="BudgetPrint" type="typ:BudgetPrint" xmlns:typ="http://my.com/types"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</s2:types>
<s2:message name="saveBudgetPrint">
<s2:part element="s3:saveBudgetPrint" name="parameters"/>
</s2:message>
<s2:message name="saveBudgetPrintResponse">
<s2:part element="s3:saveBudgetPrintResponse" name="parameters"/>
</s2:message>
<s2:message name="getBudgetPrint">
<s2:part element="s3:getBudgetPrint" name="parameters"/>
</s2:message>
<s2:message name="getBudgetPrintResponse">
<s2:part element="s3:getBudgetPrintResponse" name="parameters"/>
</s2:message>
<s2:portType name="BudgetService">
<s2:operation name="saveBudgetPrint" parameterOrder="parameters">
<s2:input message="s3:saveBudgetPrint"/>
<s2:output message="s3:saveBudgetPrintResponse"/>
</s2:operation>
<s2:operation name="getBudgetPrint" parameterOrder="parameters">
<s2:input message="s3:getBudgetPrint"/>
<s2:output message="s3:getBudgetPrintResponse"/>
</s2:operation>
</s2:portType>
<s2:binding name="BudgetServiceServiceSoapBinding" type="s3:BudgetService">
<s4:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsp:Policy>
<wsp:PolicyReference URI="#policy:Mtom"/>
</wsp:Policy>
<s2:operation name="saveBudgetPrint">
<s4:operation soapAction="" style="document"/>
<s2:input>
<s4:body parts="parameters" use="literal"/>
</s2:input>
<s2:output>
<s4:body use="literal"/>
</s2:output>
</s2:operation>
<s2:operation name="getBudgetPrint">
<s4:operation soapAction="" style="document"/>
<s2:input>
<s4:body parts="parameters" use="literal"/>
</s2:input>
<s2:output>
<s4:body parts="parameters" use="literal"/>
</s2:output>
</s2:operation>
</s2:binding>
<s2:service name="BudgetServiceService">
<s2:port binding="s3:BudgetServiceServiceSoapBinding" name="BudgetServiceSoapPort">
<s4:address location="http://localhost:7001/MyService/BudgetService"/>
</s2:port>
</s2:service>
</s2:definitions>
When I monitor the HTTP requests I can observe that the binary data isn't attachments.
If I instead define my web methods as follows:
     @WebMethod
     public void saveBudgetPrintContents(String customerID, String printID, String filename, Calendar printDate, byte[] contents) {
     @WebMethod
     public byte[] getBudgetPrintContents(String customerID, String printID) {
it works as expected and the binary data is attachments.
The WSDL file is now:
<?xml version='1.0' encoding='UTF-8'?>
<s2:definitions name="BudgetServiceServiceDefinitions" targetNamespace="http://com/my/service" xmlns="" xmlns:s0="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:s1="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:s2="http://schemas.xmlsoap.org/wsdl/" xmlns:s3="http://com/my/service" xmlns:s4="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">
<s0:Policy s1:Id="policy:Mtom">
<wsoma:OptimizedMimeSerialization xmlns:wsoma="http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization"/>
</s0:Policy>
<wsp:UsingPolicy s2:Required="true"/>
<s2:types>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="java:com.my.service" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="base64Binary_literal" type="xs:base64Binary"/>
</xs:schema>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://com/my/service" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://my.com/types"/>
<xs:element name="saveBudgetPrintContents">
<xs:complexType>
<xs:sequence>
<xs:element name="customerID" type="xs:string"/>
<xs:element name="printID" type="xs:string"/>
<xs:element name="filename" type="xs:string"/>
<xs:element name="printDate" type="xs:dateTime"/>
<xs:element name="contents" type="xs:base64Binary"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="saveBudgetPrintContentsResponse">
<xs:complexType>
<xs:sequence/>
</xs:complexType>
</xs:element>
<xs:element name="getBudgetPrintContents">
<xs:complexType>
<xs:sequence>
<xs:element name="customerID" type="xs:string"/>
<xs:element name="printID" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="getBudgetPrintContentsResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="return" type="xs:base64Binary"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
</s2:types>
<s2:message name="saveBudgetPrintContents">
<s2:part element="s3:saveBudgetPrintContents" name="parameters"/>
</s2:message>
<s2:message name="saveBudgetPrintContentsResponse">
<s2:part element="s3:saveBudgetPrintContentsResponse" name="parameters"/>
</s2:message>
<s2:message name="getBudgetPrintContents">
<s2:part element="s3:getBudgetPrintContents" name="parameters"/>
</s2:message>
<s2:message name="getBudgetPrintContentsResponse">
<s2:part element="s3:getBudgetPrintContentsResponse" name="parameters"/>
</s2:message>
<s2:portType name="BudgetService">
<s2:operation name="saveBudgetPrintContents" parameterOrder="parameters">
<s2:input message="s3:saveBudgetPrintContents"/>
<s2:output message="s3:saveBudgetPrintContentsResponse"/>
</s2:operation>
<s2:operation name="getBudgetPrintContents" parameterOrder="parameters">
<s2:input message="s3:getBudgetPrintContents"/>
<s2:output message="s3:getBudgetPrintContentsResponse"/>
</s2:operation>
</s2:portType>
<s2:binding name="BudgetServiceServiceSoapBinding" type="s3:BudgetService">
<s4:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsp:Policy>
<wsp:PolicyReference URI="#policy:Mtom"/>
</wsp:Policy>
<s2:operation name="saveBudgetPrintContents">
<s4:operation soapAction="" style="document"/>
<s2:input>
<s4:body parts="parameters" use="literal"/>
</s2:input>
<s2:output>
<s4:body use="literal"/>
</s2:output>
</s2:operation>
<s2:operation name="getBudgetPrintContents">
<s4:operation soapAction="" style="document"/>
<s2:input>
<s4:body parts="parameters" use="literal"/>
</s2:input>
<s2:output>
<s4:body parts="parameters" use="literal"/>
</s2:output>
</s2:operation>
</s2:binding>
<s2:service name="BudgetServiceService">
<s2:port binding="s3:BudgetServiceServiceSoapBinding" name="BudgetServiceSoapPort">
<s4:address location="http://localhost:7001/MyService/BudgetService"/>
</s2:port>
</s2:service>
</s2:definitions>
As you can see the binary data is now at the top level.
Could somebody please enlighten me on this?
Is it by the standard, a limitation in WL or is there another explanation?
With the current behavior I'm tempted to just use good old attachments.
/John.
Edited by johnlindgreen at 10/24/2007 4:44 AM
Edited by johnlindgreen at 10/24/2007 4:45 AM
Edited by johnlindgreen at 10/24/2007 4:46 AM
Edited by johnlindgreen at 10/24/2007 4:46 AM

Sorry for the delay response. This is a known issue that MTOM is enabled only the binary data is at the top level in WLS 10.1.
But it has already support complex type MTOM encoded in WLS 10.3. Please download at [url http://commerce.bea.com/products/weblogicplatform/weblogic_prod_fam.jsp]here
Edited by jliao at 11/14/2007 5:46 AM

Force MTOM/XOP response on OSB

hello,
How can I force a MOTOM Response although it is not neccessary because I have no binary data in the response.
The reason is follow. I have a foreign test client that sends the request with MTOM enabled and expected that the response is also using MTOM (I think this is a little bit stupid). The client is using AXIS.
In the request the client sends binary data using MTOM but in my response no binary data is available and so OSB won't enable the Mtom Feature for the response. The result is that the client don't accept my response...
Is there a workaround to force that MTOM is being enabled?

Sorry for the delay response. This is a known issue that MTOM is enabled only the binary data is at the top level in WLS 10.1.
But it has already support complex type MTOM encoded in WLS 10.3. Please download at [url http://commerce.bea.com/products/weblogicplatform/weblogic_prod_fam.jsp]here
Edited by jliao at 11/14/2007 5:46 AM

Wants to send html as inline message instead of attachment(without MTOM)

Hi,
We have reuirement want send html as inile message instead of attachemnt in OSB 11g with out MTOM.
Any pointers on this regard will be of great help.
Regards
Venkata

For example use WSDL like this:
http://axis.apache.org/axis2/java/core/docs/mtom-guide.html#a251
and don't forget to disable MTOM/XOP support for proxy and business service.
You don't need anything but a base64binary element in your request or response message. That's all. When you turn MTOM/XOP support off, binary data will be inlined.
If you will still face an issue, try to send your WSDL, describe input, output and your proxy flow.

IPhone wants to send text as MMS

I want to simply send a text message to somebody, by creating a new message in Messages, and choosing the recipient from the contacts. However, when trying to send the message my phone says "MMS Messaging needs to be enabled to send to an email address." I never ever want to send an MMS (which is why MMS is disabled), and I do not want to send the message to an email address. When choosing the recipient from the contacts, the phone does not ask me whether I want to send it to the contact's phone number or email address. Why does it assume that I want to send it to an email address?
(On the flipside, if I access the contact through the Phone or Contacts app, and tap "Send Message," the phone provides me with a list of mobile numbers and email addresses, as it should.)
Here are my steps:
Open Messages.
Tap the new message button in the top-right corner.
Tap the Plus icon in the "To" field.
"Choose a contact to text message"
Compose message.
Tap "Send."
It's really inconvenient composing a text message and hitting Send, only to be reminded that the phone cannot send the text message this way.
Any ideas?

For example use WSDL like this:
http://axis.apache.org/axis2/java/core/docs/mtom-guide.html#a251
and don't forget to disable MTOM/XOP support for proxy and business service.
You don't need anything but a base64binary element in your request or response message. That's all. When you turn MTOM/XOP support off, binary data will be inlined.
If you will still face an issue, try to send your WSDL, describe input, output and your proxy flow.

MTOM support in the integration engine

Hi,
Short description of the process.
3rd party application -> PI WSDL -> SAP ERP
A 3rd party application sents a request to our WSDL on PI and the PI
starts a process (BPM). After the process is finished, PI sents the
result to SAP ERP over XI adapter.
Because the 3rd party application cannot add authentication parameters
for our Web Service we changed our URL to a service in SICF.
sap->xi->engine and added default authentication parameters. So that when the 3rd party application sents a request to PI, PI will not ask for
authentication.
(this
thread explains the problem with authentication and why we did used the
SICF solution. first entry by Michal Krawczyk)
Now, when the 3rd party sent a message (SOAP message with MTOM) with
attachment it is recognized by PI as a Multipart message.
The Service in SICF which gets executed when the message comes calls a
class inside. (cl_xms_http_handler) This class gets an exception while
parsing the MTOM enabled message. And it does not sent the message to the
PI engine.
Is the MTOM feature supported by this class? If yes, what may be the problem.
Thanks.
Sample MTOM Message:
--MIMEBoundaryurn_uuid_B7A0A8F29AF9AF0E5F1285180614419
content-type: application/xopxml; charset=UTF-8; type="application/soapxml"
content-transfer-encoding: binary
content-id: ïş
¢Sr ñ Fu02C6...
MIMEBoundaryurn_uuid_B7A0A8F29AF9AF0E5F1285180614419

Moved to Axis adapter which solved our problem

OSB MTOM HTTP Streaming

Hello everybody,
I have just started using Service Bus 11gR1 and I run into a problem. I need to define a proxy service (web service) which accepts large files (hundreds of MB).
I opted for using MTOM/XOP combined with HTTP streaming. To do this, I enabled in the "Message Handling Configuration" screen, the "XOP/MTOM Support" option and I set "Page Attachments to Disk" to true.
Actually, when I try to send large messages, the memory usage does not increase because the binary sent is buffered into the disk. Now I noticed that, before the proxy server is called, the binary sent is saved in a temporary file. I was wondering whether or not we can define a limit on the Message Size to be checked*before* the file is buffered on the disk. I want OSB to start reading the HTTP streaming and, when the max size is reached, to reset the http connection with the client. If this is not possible, I think that this is an issue from a security point of view.
Thank you in advance.
Edited by: 837199 on Feb 16, 2011 6:23 AM

I don't know the answer to your question. Sorry! But It sounds like you have more succes with mtom on OSB than me. So I have a question that I hope you can help me with. Is you service based on a WSDL? if it is, can I see how it looks because I have some problems, making a wsdlbased proxyservice with mtom and invoking it from soapui
BR,
Mads

OSB MTOM...

Hello everybody,
I am using Oracle Service Bus 10gR3. I need to define a proxy service (wsdl based web service) which accepts large files (attachments).
I am supposed to use MTOM/XOP combined with HTTP and I need to pass this request attachment to the backend using a Business Service. After googling I came to know that for this I need to enable the "XOP/MTOM Support" in the configuration settings for the proxy service. Still I am not sure about how to go for it.
Can anyone help me with a sample code for the same.
Thanks in advance.

I don't know the answer to your question. Sorry! But It sounds like you have more succes with mtom on OSB than me. So I have a question that I hope you can help me with. Is you service based on a WSDL? if it is, can I see how it looks because I have some problems, making a wsdlbased proxyservice with mtom and invoking it from soapui
BR,
Mads

Soap attachment mapping problem, xop:include

Hello experts,
I am using PI 7.3
I have a senario SOAP to IDOC which SOAP is a sender adapter.
My Web Service receives attachment which includes MTOM, xop:include
I read the attachment in the message mapping by User-Defined function.
But I have another problem while message mapping.
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>Unexpected value <null> for node /ns0:TrainingAttachment/ns1:binary</SAP:P1>
in attachment part of the web service is following,
<urn1:attachment>
<urn1:binary>
      <inc:Include href="cid:87732-65c0-665c" xmlns:inc"http://www.w3.org/2004/08/xop/include" />
</urn1:binary>
</urn1:attachment>
I think my message mapping doesnt resolve the binary part
I tried the Do Not Resolve XOP Includes checkbox, nothing changed
Thanx for your help
Hasan
Edited by: ordu_hasan on Feb 23, 2012 4:12 PM

Hi Hasan,
Please, try to implement next xslt mapping before message mapping.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:stylesheet version="1.0" xmlns:ns0="http://www.w3.org/1999/XSL/Transform" xmlns:xop="http://www.w3.org/2004/08/xop/include" xmlns:ns2="https://onlineservice.creditreform.de/webservice/0400-0005">
   <ns0:template match="node() | @*">
      <ns0:copy>
         <ns0:apply-templates select="node() | @*"/>
      </ns0:copy>
   </ns0:template>
   <ns0:template match="xop:Include"/>
</ns0:stylesheet>
Regards, Dzmitry

MTOM with XI

hello
does any one know what are the adjustments that the XI needs to do (if he needs) in order to recieve a WS that send message as/with MTOM?
does any one has an example of MTOM XOP message?
I know it looks like a soap message, I am just not familar exactly how, so if any one has an example it will be appreciate to look at it.
Thanks
Kfir

hi,
if you have 7.1 you can use XI with MTOM
but there are certain prerequisites:
http://help.sap.com/saphelp_nwpi71/helpdata/en/76/fc9c3d9a864aef8139d70759a499fc/content.htm
Regards,
Michal Krawczyk

ABAP SOAP Client with MTOM

Hi experts,
I need to create a SOAP client in ABAP for a web service that uses MTOM (xop:include) to transfer binary files.
I know how to create a client proxy in SE80 from WSDL, but I.have no idea how to send attachments with protocol MTOM.
Does anybody know how to do this in ABAP?
Thanks a lot!
LUIS B.

Hi there.
Well, I couldn't get the ABAP Proxy working so I build the SOAP client from scratch using class CL_HTTP_CLIENT. It was harder because I had to take care of every aspect in the HTTP communication but in the end it was more flexible.
I hope this helps.

Future direction of BEA Web Services? - binary / attachments

Hello,
I'm looking at needing to transfer binary data through a web service,
but can't handle the 4/3+ size increase that occurs when embedding the
data with base64 encoding.
I know that WL 8.1sp3 support SwA, but that standard is being deprecated
in favor of newer technologies like Fast Web Services (based on ASN.1
encoding rules), MTOM/XOP, Basic Attachments Profile.
We'd prefer to be able to rely on the support of the application server.
What is BEA's future direction in terms of this technology? Will they be
supporting one or all of these binary standards? When is the estimated
date for this technology to be implemented?
If these technologies won't be implemented for a while, is it possible
to plug in 3rd party web services solutions into BEA WL8.1 (e.g. Sun's
JWSDP, Axis, etc)? I believe it is, but am just asking for the sake of a
full answer.
Thanks

Steve,
Due to BEA's award winning support they offer, I had to figure this out on my own. After weeks of dealing with a support case they provided me with absolutely nothing. Just as they have done in this thread. I will share what I have done for the mean time to get around their limitations using attachments.
I used the Axis libraries to create a DIME attachment and call a BEA web service. Since BEA doesn't support Dime, a servlet filter had to be implemented and parse the DIME message prior to the web service received it. I'm sending 2GB files with transfer rates of 6MB/S.
This is a response from BEA's award winning support:
"We do not have good specification standard as yet as to how to best solve the issue. It appears like a pretty larger issue to solve because of the lack os standards and specification. Engineering is still researching on the issue and we don't know which version will have the fix."

JAXRPC 2.0 Improvements over 1.1

The JAX-RPC 2.0 SI has been re-architectured since 1.1. The new architecture will make it easier to add new capabilities in the future.
The new architecture allows for:
Multiple Transports
- EA currently supports HTTP
Multiple Encodings
- EA supports XML as text.
- The next EA will include MTOM/XOP and Fast Infoset
Multiple Protocols
- EA supports SOAP 1.1
- The next EA will include SOAP 1.2
The next EA due out before JavaOne will also have a dynamic runtime. This means no more stubs/ties,
serializers, deserializers etc. All artifacts generated
by the JAX-RPC SI will be 100% portable to other JAX-RPC
2.0 implementations.
Arun Gupta has blogged about how the current JAX-RPC 2.0
EA can be deployed ontop of JWSDP 1.5. You can read his blog at: http://weblogs.java.net/blog/arungupta/archive/2005/04/jaxrpc_20_ea_on_1.html
You can read my blog on JAXRPC 2.0 EA at: http://weblogs.java.net/blog/kohlert/archive/2005/04/jaxrpc_20_stand_1.html
You can dowload the current EA at: https://jax-rpc.dev.java.net/jaxrpc20-ea/.

Thanks,
This is what I thought would be the case but was holding out hope.
The downmix is fine but lacks the "pressence" we have set up in our Dolby studio.
I don't want to take away any space from my main asset as my menus are elaborate motion sets, so duplicating them will not work for most projects.
Just trying to add value to the experience, oh well.
Again, thanks
regbert

New OC4J 10g (10.1.3.1) Developer Preview now available for download!

A Developer Preview of the new OC4J 10g (10.1.3.1) release is now available for download.
This developer preview release is fully J2EE 1.4 compatible and offers numerous enhancments, including full support for the final EJB 3.0/JPA specifications and Common Annotations (JSR-250) support in the Web container. It also provides a complete Web Services stack with support of JAX-RPC, annotations based development using JSR-181, and attachment support including MIME, DIME and MTOM with support of streaming for large documents.
See http://www.oracle.com/technology/tech/java/oc4j/10131/index.html for details.

I've tried http://localhost:8888, but I get a "connection refused."
I have since found the answer. The site http://localhost:8888/ will indeed work. The problem was that the java_home for oc4j was pointing to a Java Runtime Edition of 1.5.0, and so oc4j was not starting, since oc4j only works with 1.4.x.
Still have the missing info from the readme, though.

Is MTOM/XOP supported?

Similar Messages

Maybe you are looking for