Wsdl soap style get RPC need document/literal
Hi,
Using jdev10.1.3/jre1.3 to generate webservice wrappers
How do you change style which defaults to RPC and I need document/literal ?
Can't really find any properties in the IDE to do it, can anyone point me in to the relevant sections?
Thanks
Pete
Hello,
Which kind of Web Services are you building in JDeveloper?
- JAX-RPC (J2EE 1.4)
- Oracle Web Service stack (J2EE 1.3)
What is your targetted environment?
Oracle does not support Document style Web Services in Oracle Web Service stack (J2EE 1.3), it has to be done programmatically.
However the JAX-RPC stack does support, and it is the default, Document style Web Services and you can right click on the Web Service node to edit the service.
Regards
Tugdual Grall
Similar Messages
-
Hello,
i am looking for information regarding HTTP Get binding for SOAP. I have looked at the wsdl 1.1 specification which provides some information concerning that binding (http://www.w3.org/TR/wsdl#_http) and also in SOAP 1.2 (http://www.w3.org/TR/soap12-part0/#L26854). However all this is not precise enough.
In particular, i am wondering whether the serialization of SOAP request (from its definition in a wsdl) using http get is clearly formalized somewhere (in a specification). If any, what are the limitations and constraints, for instance, does it support complex types defined in the WSDL. Are there implementations currently available?
Thanks,
CyrilleHello,
Which kind of Web Services are you building in JDeveloper?
- JAX-RPC (J2EE 1.4)
- Oracle Web Service stack (J2EE 1.3)
What is your targetted environment?
Oracle does not support Document style Web Services in Oracle Web Service stack (J2EE 1.3), it has to be done programmatically.
However the JAX-RPC stack does support, and it is the default, Document style Web Services and you can right click on the Web Service node to edit the service.
Regards
Tugdual Grall -
Document/literal style wsdl with more than one port
Recently I have changed wsdl style from rpc/encoded to document/literal as BPEL does not handle soapenc:arrayType. The wsdl contains 2 operations and few complex type definitions.
In BPEL Designer I have created a process that invokes all operations defined in the wsdl, but only one of them will have some data in the response message and the other one will have an empty message. On the other hand, when I use stub generation to invoke Web Service everything is working fine.
If I provide separate wsdl for each operation (in BPEL process I would have two partnerLinks instead of one) than it works fine.
Does this mean that BPEL does not handle document/literal style endpoints with more than one port (operation)?
I have tested this with the orabpel_2.0_J1_win32.exe and orabpel_2.0rc9_win32.exe. Web Services, used for this test, are deployed in Jboss 3.2.3 and axis-1_2beta3.
WSDL used as partnerLink:
<?xml version="1.0" encoding="UTF-8" ?>
<wsdl:definitions targetNamespace="http://test" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://test" xmlns:intf="http://test" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<schema elementFormDefault="qualified" targetNamespace="http://test" xmlns="http://www.w3.org/2001/XMLSchema">
<complexType name="CardId">
<sequence>
<element name="cardType" nillable="true" type="xsd:string" />
<element name="number" nillable="true" type="xsd:string" />
</sequence>
</complexType>
<complexType name="CardIdArray">
<sequence>
<element maxOccurs="unbounded" name="item" nillable="true" type="impl:CardId" />
</sequence>
</complexType>
<element name="getCardsReturn" type="impl:CardIdArray" />
<complexType name="CardholderCards">
<sequence>
<element maxOccurs="unbounded" name="cards" nillable="true" type="impl:CardId" />
<element name="serialNumber" nillable="true" type="xsd:string" />
</sequence>
</complexType>
<element name="retrieveChReturn" type="impl:CardholderCards" />
</schema>
</wsdl:types>
<wsdl:message name="retrieveChRequest" />
<wsdl:message name="getCardsRequest" />
<wsdl:message name="retrieveChResponse">
<wsdl:part element="impl:retrieveChReturn" name="retrieveChReturn" />
</wsdl:message>
<wsdl:message name="getCardsResponse">
<wsdl:part element="impl:getCardsReturn" name="getCardsReturn" />
</wsdl:message>
<wsdl:portType name="TestService">
<wsdl:operation name="getCards">
<wsdl:input message="impl:getCardsRequest" name="getCardsRequest" />
<wsdl:output message="impl:getCardsResponse" name="getCardsResponse" />
</wsdl:operation>
<wsdl:operation name="retrieveCh">
<wsdl:input message="impl:retrieveChRequest" name="retrieveChRequest" />
<wsdl:output message="impl:retrieveChResponse" name="retrieveChResponse" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="TestServiceSoapBinding" type="impl:TestService">
<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
<wsdl:operation name="getCards">
<wsdlsoap:operation soapAction="" />
<wsdl:input name="getCardsRequest">
<wsdlsoap:body use="literal" />
</wsdl:input>
<wsdl:output name="getCardsResponse">
<wsdlsoap:body use="literal" />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="retrieveCh">
<wsdlsoap:operation soapAction="" />
<wsdl:input name="retrieveChRequest">
<wsdlsoap:body use="literal" />
</wsdl:input>
<wsdl:output name="retrieveChResponse">
<wsdlsoap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="TestServiceService">
<wsdl:port binding="impl:TestServiceSoapBinding" name="TestService">
<wsdlsoap:address location="http://localhost:8080/axis/services/TestService" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>Hi Dragana,
We definitely support the ability to call a web service that exposes two operations (document/literal or not).
Glancing through your WSDL, it looks good.
Could you please try to tunnel the second request and see 1) what data is sent to the service and 2) what data is returned by the service?
Can you please email us a reproduceable case so that we can help troubleshoot in parallel?
Thank you,
Edwin
[email protected]
please rename .zip to .zap -
Document/literal web service with WSDL
Hi
I is so hard to get an easily written example of how to do a Document/literal web service in java, to generate a WSDL descripbing it and then deploying it on Apache.
I first belived that I should use JAXM. But I think it is just SOAP and there is no way to generate a WSDL file for the JAXM service, or??
It seems that u can to document/literal style using JAX-RPC, but this is VERY strange since RPC style is the direct opposite of Document style.
well, well
I would be very greatful for information here.
regards
/RassolJWSDP 1.2 includes the WS-I sample application in JWSDP_HOME/wsi-sampleapp. Several components of
this application use document-literal operations. The architecture of the application is described
here http://ws-i.org/SampleApplications/SupplyChainManagement/2003-04/SCMArchitecture1.0-BdAD.pdf
The WSDL for the services is availabe from URLs in the document.
As you say, the trick is generating the WSDL for a new service. You have two options: 1. Modify
existing WSDL yourself. This might be fairly easy, since the only major changes will be in the
schema. Then use a tool to generate Java source code from the WSDL. 2. Use a tool to generate WSDL
from source files.
I prefer option 1 myself, since that gives me total control over the schema. It allows me to
serialize certain parts of the SOAP message as body elements, others as attributes, and others as
header elements. Then I use the Apache Axis tool WSDL2Java with the "-s" option to generate skeleton
service files. One big advantage to this approach is that WSDL2Java generates JavaBean class for the
types in the WSDL schema, so I don't need to build the SOAP message with SAAJ. A service client
generates stubs and calls the service exactly as it would for an rpc/encoded service.
wscompile also generates service files from WSDL if you give the "-gen:server" option, but I've only
used Axis for my services.
Here's a sample WSDL for a document/literal service you can modify as you need. I checked it with
the WS-I testing tools to be sure it conforms to the WS-I Basic Profile 1.0a (available at www.ws-
i.org). Notice that the processPo operation is a request-response type operation, even though it has
a document/literal style. This follows the recommendations in the Basic Profile.
Cheers,
Mike
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://www.ltree.com/wsdl/po" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:impl="http://www.ltree.com/wsdl/po" xmlns:intf="http://www.ltree.com/wsdl/po" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="http://www.ltree.com/types/po" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:tns1="http://www.ltree.com/types/po"
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
targetNamespace="http://www.ltree.com/types/po"
elementFormDefault="qualified">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/envelope/"
location="http://schemas.xmlsoap.org/soap/envelope/"/>
<xsd:complexType name="LineItem">
<xsd:sequence>
<xsd:element name="itemId" type="xsd:string"/>
<xsd:element name="quantity" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="PurchaseOrder">
<xsd:sequence>
<xsd:element name="customerName" type="xsd:string"/>
<xsd:element name="lineItem" type="tns1:LineItem"
minOccurs="1" maxOccurs="unbounded" />
</xsd:sequence>
<xsd:attribute name="purchaseOrderId" type="xsd:string" use="required"/>
</xsd:complexType>
<xsd:element name="purchaseOrder" nillable="true" type="tns1:PurchaseOrder"/>
<xsd:complexType name="CallbackEndpoint">
<xsd:attribute name="location" type="xsd:anyURI" use="required"/>
</xsd:complexType>
<xsd:element name="callbackEndpoint" nillable="false" type="tns1:CallbackEndpoint"/>
<xsd:complexType name="PurchaseOrderAck">
<xsd:sequence>
<xsd:element name="poId" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="purchaseOrderAck" nillable="true" type="tns1:PurchaseOrderAck"/>
<xsd:complexType name="InvalidCustomerNameException">
<xsd:sequence>
<xsd:element name="message" nillable="true" type="xsd:string"/>
<xsd:element name="customerName" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="invalidCustomerNameException" nillable="true"
type="tns1:InvalidCustomerNameException"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="processPoRequest">
<wsdl:part name="callbackEndpoint" element="tns1:callbackEndpoint"/>
<wsdl:part name="purchaseOrder" element="tns1:purchaseOrder"/>
</wsdl:message>
<wsdl:message name="processPoResponse">
<wsdl:part name="purchaseOrderAck" element="tns1:purchaseOrderAck"/>
</wsdl:message>
<wsdl:message name="invalidCustomerNameException">
<wsdl:part name="fault" element="tns1:invalidCustomerNameException"/>
</wsdl:message>
<wsdl:portType name="PurchaseOrderHandler">
<wsdl:operation name="processPo">
<wsdl:input message="impl:processPoRequest" name="processPoRequest"/>
<wsdl:output message="impl:processPoResponse" name="processPoResponse"/>
<wsdl:fault message="impl:invalidCustomerNameException" name="invalidCustomerNameException"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="PurchaseOrderHandlerPortSoapBinding" type="impl:PurchaseOrderHandler">
<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="processPo">
<wsdlsoap:operation soapAction="" style="document"/>
<wsdl:input name="processPoRequest">
<wsdlsoap:header message="impl:processPoRequest" part="callbackEndpoint" use="literal"/>
<wsdlsoap:body parts="purchaseOrder" use="literal"/>
</wsdl:input>
<wsdl:output name="processPoResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
<wsdl:fault name="invalidCustomerNameException">
<wsdlsoap:fault name="invalidCustomerNameException" use="literal"/>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="PurchaseOrderHandlerService">
<wsdl:port binding="impl:PurchaseOrderHandlerPortSoapBinding" name="PurchaseOrderHandlerPort">
<wsdlsoap:address location="http://localhost:8080/po/services/PurchaseOrderHandlerService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions> -
How to create Document / Literal WSDL with axis 1.3
Dear All,
1. How to create Document / Literal WSDL from java interface ?? or how to create Java 2 WSDL using Document/ Literal.
2. from document/literal WSDL to java classes(stub, skelton, serivces).
I am using Axis 1.3 , tomcat-5.5.20 and eclipse.
Please provide the command and arguments for java2wsdl and wsdl2java for doc/lit.
is there any tool that help to generate java2wsdl and wsdl2java for doc/lit.That would be the <web-service> element in the web-services.xml file, of course.
"Michael Wooten" <[email protected]> wrote:
>
Hi Rich,
Try adding a style="document" attribute to the starting <web-service>
element.
The might be a way to get <servicegen> to do this for you, but I haven't
found
it yet :-)
Regards,
Mike Wooten
"Rich Muth" <[email protected]> wrote:
How do you create document/literal web services with WLS7 ( not workshop)
- Is it possible with servicegen and stateless EJBs as the backend component?
The default is RPC/Soap-encoded is there anyway to craft the web-services.xml
to make it document/literal
- Is it possible with the JMS-implemented web services - have not tried
this yet
- Is there another mechanism? -
JAX RPC extension: Problem with document/literal and MyType[]
Hi,
I have installed the JAX RPC extension and want to generate a stub from my WSDL file. The WSDL describes a document/literal binding.
Problem:
A webservice server method like:
public wineshop.model.common.SimpleProducer[] getSimpleProducerList() throws RemoteException;
is translated into a stub method like:
public UnknownType getSimpleProducerList() throws Exception {..}
Is an array of own types with the binding style "document/literal" not supported in JAX RPC 1.4 or is it just a bug?
The WSDL file is generated by JAX RPC 1.4.
I have installed JWSDP-1.5 and generated a stub with wscompile from the WSDL file. The generated stub has the correct method return type:
public wineshop.ws.client.SimpleProducer[] getSimpleProducerList()
throws java.rmi.RemoteException
It there a workaround like replacing some JDev JARs with JWSDP-1.5 to solve the problem?
Any hints are welcome.
Thanks Markusrepost.....
-
Document-Literal and Arrays - WSDL seems incorrect ??
I have create a simple "document-literal" webservice that returns an object containing some simple fields and an array of another object.
Task.cfc
===============================
<cfcomponent>
<cfproperty name="Id" type="string">
<cfproperty name="Priority" type="numeric">
<cfproperty name="StartTime" type="date">
<cfproperty name="StopTime" type="date">
<cfproperty name="AOI" type="VertexPoint[]">
</cfcomponent>
VertexPoint.cfc
============================
<cfcomponent>
<cfproperty name="Latitude" type="numeric">
<cfproperty name="Longitude" type="numeric">
<cfproperty name="Altitude" type="numeric">
</cfcomponent>
My webservice returns a Task object
<cfcomponent style="document">
<cffunction name="getTask" returnType="Task" access="remote" output="false">
</cffunction>
</cfcomponent>
When I look at the generated WSDL is see the following complexTypes:
NOTICE THE name="item" IN THE COMPLEXTYPE ArrayOf_xsd_anyType.
<complexType name="VertexPoint">
<sequence>
<element name="Altitude" nillable="true" type="xsd:double"/>
<element name="Latitude" nillable="true" type="xsd:double"/>
<element name="Longitude" nillable="true" type="xsd:double"/>
</sequence>
</complexType>
<complexType name="Task">
<sequence>
<element name="AOI" nillable="true" type="tns1:ArrayOf_xsd_anyType"/>
<element name="Id" nillable="true" type="xsd:string"/>
<element name="Priority" nillable="true" type="xsd:double"/>
<element name="StartTime" nillable="true" type="xsd:dateTime"/>
<element name="StopTime" nillable="true" type="xsd:dateTime"/>
</sequence>
</complexType>
<complexType name="ArrayOf_xsd_anyType">
<sequence>
<element maxOccurs="unbounded" minOccurs="0" name="item" type="impl:VertexPoint"/>
</sequence>
</complexType>
When I look at the XML/data returned when I call the webservice it is:
<getTaskResponse xmlns="http://users">
<getTaskReturn>
<AOI>
<AOI xsi:type="ns1:VertexPoint" xmlns:ns1="http://users">
<Altitude>1.0</Altitude>
<Latitude>1.0</Latitude>
<Longitude>1.0</Longitude>
</AOI>
<AOI xsi:type="ns2:VertexPoint" xmlns:ns2="http://users">
<Altitude>2.0</Altitude>
<Latitude>2.0</Latitude>
<Longitude>2.0</Longitude>
</AOI>
</AOI>
<Id>1</Id>
<Priority>99.0</Priority>
<StartTime>2009-10-15T06:00:00.000Z</StartTime>
<StopTime>2009-10-17T05:59:59.000Z</StopTime>
</getTaskReturn>
</getTaskResponse>
Shouldn't the tags be
<AOI>
<item>
</item>
<item>
</item>
<AOI>
I am trying to access this WS from a java client and the AOI is always null
Any help would be greatly appreciated. (BTW - If I use "rpc" WS everything work fine)repost.....
-
Differences between Document Style vs RPC style WS.
Hello All,
Can some body explain me the differences between a document style and rpc style webservices. Apart from JAX-RPC next version is JAX-WS, which supports document style and rpc, I also studied that document style webservices are meant for Asynchronous style of communication, where client would not block until the response is received.
In either way of writing services using JAX-WS, I currently annotate the service with @Webservice, generage the WSDL and from that WSDL I generate the client side artifacts.
Once the artifacts are received, in both styles of communication, I invoke the method on the port. Now, this does not differ in rpc style and document style. So what is the difference and where is that difference visible.
Similarly, in what way SOAP over HTTP differ from XML over HTTP. After all SOAP is also XML document with SOAP namespace. So what is the differnce here.user13126996 wrote:
Can some body explain me the differences between a document style and rpc style webservices. Apart from JAX-RPC next version is JAX-WS, which supports document style and rpc, I also studied that document style webservices are meant for Asynchronous style of communication, where client would not block until the response is received. no, asynchronous vs. synchronous responses have nothing to do with rpc style vs. document style. they are two orthogonal concepts.
Once the artifacts are received, in both styles of communication, I invoke the method on the port. Now, this does not differ in rpc style and document style. So what is the difference and where is that difference visible.the difference is basically in how the data is encoded over the transport layer. in theory, you can encode some complex data structures more efficiently in the rpc style. in reality, no one ever uses these features. and since the document style is more strongly typed and much more "straightforward", most people tend to prefer the document style to the rpc style these days. (in fact, i don't think jaxws actually supports rpc style).
Similarly, in what way SOAP over HTTP differ from XML over HTTP. After all SOAP is also XML document with SOAP namespace. So what is the differnce here. none really. SOAP over HTTP is XML over HTTP. XML over HTTP has no strong specification, whereas SOAP puts lots of specs around what the XML should look like. also, obviously, SOAP can theoretically be sent over other transport layers besides HTTP (not that i've ever seen that). -
Issue with generation of document/literal type WSDL using Axis
Hi All,
I am trying to convert some Java code into WSDL using Axis 1.2 framework. I used Document/Literal style for binding.
One of the methods in my Java code returns an array. This array is described in Axis generated WSDL as follows:
<complexType name="ArrayOfThings">
<complexContent>
<restriction base="soapenc:Array">
<attribute ref="soapenc:arrayType" wsdl:arrayType="impl:Things[]"/>
</restriction>
</complexContent>
</complexType>
But the end user(client for the web service I am hosting) says " .NET won't allow him to consume my webservice (or generate the proper reference classes) for types that derive from encoded types".
So my question is "Would it be possible to change the webservice so that it doesn’t use that(soapenc) implementation of the array?"
The end user is expecting something more like this:
<s:complexType name="ArrayOfThings">
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="Things" nillable="true" type="tns:Things" />
</s:sequence>
</s:complexType>
I am new to Web Services. So any help or guidance would be greatly appreciated.
Thanks,
Scott.Hi Dragana,
We definitely support the ability to call a web service that exposes two operations (document/literal or not).
Glancing through your WSDL, it looks good.
Could you please try to tunnel the second request and see 1) what data is sent to the service and 2) what data is returned by the service?
Can you please email us a reproduceable case so that we can help troubleshoot in parallel?
Thank you,
Edwin
[email protected]
please rename .zip to .zap -
Document literal with JAX-RPC?
Hi folks,
I want to create a service that uses document literal. I'm at a loss as to how to specify this to wscompile or xrpcc.
Any help would be greatly appreciated.
Regards,
RajeshHi Rajesh,
I had the same problem last year when writing my master-degree paper. :>
My solution is to serialize/deserialize every XML files before and after the parameters sent and received.
However,this may be the most intuitive way to do it, but not the best way.
If you have enough time, you may try to register your own encoding style,
and assign the serialization job to your own serializer,
to make the follow-up jobs easier.
As I knew, some application servers would support literal-XML in their encoding style;One is MS-soap, and I forgot the other one.
You may also migrate your ap. to the MS-soap to use the literal-XML as the input/output paras.
Hope that would do help to your work.
Regards,
Jack -
Document/Literal SOAP format generation using jdeveloper 10.1.2.0.0
Hi,
Can anyone tell me please how to create Document/Literal SOAP format using jdeveloper 10.1.2.0.0 ??
Thanks in advance,
KhalilThe method that you call must take a org.w3c.dom.Element as an argument, and must also return an Element.
In the web.xml file, the servlet-class for your webservice must be changed to oracle.j2ee.ws.StatelessJavaDocWebService.
You can then either modify your WSDL by hand, or deploy your webservice to an OC4J container, which will then generate a Doc/Literal WSDL for you, and then use that.
When deploying, make sure that the JDeveloper-generated WSDL file is not included in the WAR file. -
Document/Rpc and Encoded/Literal
Hi,
I need a brief explanation about:
1. RPC/encoded
2. RPC/literal
3. Document/encoded
4. Document/literal
and their respective uses case, examples will be appreciated.Thanks but i have already read this article, what I want is a brief explanation or comparison
-
Ikeep getting "you need a newer version of Pages to open this document" but I have the newest version
You have 2 versions of Pages on your Mac.
Pages 5 is in your Applications folder.
Pages '09/'08 is in your Applications/iWork folder.
You are alternately opening the wrong versions.
Pages '09/'08 can not open Pages 5 files and you will get the warning that you need a newer version.
Pages 5.01 can not open Pages 5.1 files and you will get the warning that you need a newer version.
Pages 5 can open Pages '09 files but may damage/alter them. It can not open Pages '08 files at all.
Once opened and saved in Pages 5 the Pages '09 files can not be opened in Pages '09.
Once opened and saved in Pages 5.1 files can not be opened in Pages 5.
Anything that is saved to iCloud is also converted to Pages 5 files.
All Pages files no matter what version and incompatibility have the same extension .pages.
Pages 5 files are now only compatible with themselves on a very restricted set of hardware, software and Operating Systems and will not transfer correctly on any other server software than iCloud.
Apple has removed over 95 features from Pages 5 and added many bugs:
http://www.freeforum101.com/iworktipsntrick/viewforum.php?f=22&sid=3527487677f0c 6fa05b6297cd00f8eb9&mforum=iworktipsntrick
Archive/trash Pages 5, after exporting all Pages 5 files to Pages '09 or Word .docx, and rate/review it in the App Store, then get back to work.
Peter -
Unable to get Quick time movies to play on my imac. This is the error message I allways get.
"The document “4-20130701090400-7.mp4” could not be opened. The movie is not in a format that QuickTime Player understands.You may need to install additional software to open this type of file."Download and install VLC Player. It plays more formats and is free and highly regarded.
http://vlc-media-player.en.softonic.com/mac
Cheers
Pete -
The table of contents is empty because none of the paragraph styles selected in the Document Inspector are used in the document.
The above is what I get when I open a word document. Is there a way to solve this?Hmmm. Apply the styles?
Peter
Maybe you are looking for
-
My secondary monitor flashes and blacks out after the 10.7 install. Any ideas on how to fix this?
I have installed 10.7 and the secondary monitor flashes and blacks out. I downgraded back to 10.6 and the problem went away. I reinstalled 10.7 and the same problem happened again. The monitor blacks in and out especially when the pointer is place
-
Unable to read cdrom device in VirtualBox 3.2.10 on Solaris 5.10
Hello ... I'm trying to create an OpenSOLARIS guest in VirtualBox 3.2.10 on Solaris 5.10 and am getting the message when trying to start up and install OS in guest: Failed to open a session for the virtual machine OpenSOLARIS. Cannot open host device
-
We are trying to create a one-way, document type service based on types generated by autoType from a schema. We were successful with a simple schema, but when we substituted a more complex one we get: [servicegen] Generating service "CreditApp" ... [
-
Adobe Reader XI "not responding" Windows 7.
Everytime I try to open a document with Adobe it freezes and gives me the "not responding" message.
-
In applications such as snap chat where the modification of text and characters is permitted, the emojis take on a very unpleasant look to them becoming very pixelated and distorted. I'm not sure if this issue has been raised yet, but wouldn't a vect