Staff Styles or Score styles?

I apologise for having to post this but the manual hasn't gotten me where I need to go yet. If I create a new project with 7 staves and the delete 4 of them I am left with 3 staves. They are coupled together so clicking on one selects all 3. I have tried create Duplicate but the coupling remains in place. Any ideas on this? I will of course RTFM again but it is not Logics' easiest editor.

You might want to read throught that realated thread
http://www.logicprohelp.com/viewtopic.php?t=71888&highlight=
Make you are clear on the difference between Score Sets (Instrument related) and Staff Styles (Region related). And yes the Logic Manual is not really helpful to point that, rather confusing.
Edgar Rothermich
(DingDingMusic.com)

Similar Messages

Score Editor:Single-Staff Score Style With Optional Polyphony

Hi,
I need to do something i read in the manual:
"Sometimes you need to add a second Voice to a staff that usually only requires one Voice, in order to properly notate a short, rhythmically-independent passage...
One solution is to use a Score Style with a “Main Voice” and a “Secondary Voice”..."
O.K how do i create a Score Style with a “Main Voice” and a “Secondary Voice”?

- open the score style editor
- duplicate the score style you are using. name it.
- in the 'new' file menu, select 'insert voice'
- a new voice will be inserted into the score style.
- make the necessary adjusments such as hide rests, stems down, or make sure that the midi channel is set in the last box to be 2 or any number different from the your global midi channel.
- in your score select the stave you want to change (hint: why not cut it into the length you need the second voice to run for?) and choose your new score style.
- enter the notes you want to enter to be on the second voice.
- select them and change their midi channels to the number you assigned for them in your score style editor. so in this case; 2.

Score styles: spontaneously self-replicating

I duplicated the bass score style and edited it to accomodate independent MIDI voices. Now, every so often when I go to apply a style to a give MIDI region, multiple copies of the original "bass" style appear; later even more, and more, and so on. Why oh why? Ideas?

I'm not sure what you mean about a "default" style... AFAIK, there is no such thing in Logic. The closest thing to "default" that I can think of is something that's manipulated by the "style" setting of a instrument (MIDI or Audio). In case you're not familiar with this, do the following:
1. Go to the Arrange page and click on any instrument track
2. On the LH part of the screen is a dark gray box containing the name of the instrument. There's a little white triangle pointing to that name. If it's not already pointing downwards, click on the triangle and information about that instrument will appear. At the bottom of the list is a parameter called "style".
If "style" is set to Auto, what Logic does is it analyzes the note range of the region (right after it's recorded). If it determines that the part is mainly in the lower register, it applies a Bass score style to the score display for that part. A flute part, on the other hand, would result in a Logic applying a Treble score style. You get the idea...
You can override this and set up a "default" score style (of your choosing) for any particular instrument in your Environment.
Other than that, I don't know of any other Logic defaults for score styles.
Have you tried starting a new song (based on your Autoload), playing in a part or two, and seeing how that new song's score display reacts? Might be worth a shot to try to get to the bottom of this very strange problem.

SCORE: Polyphonic Score Style & Rests

Hello Score Gurus,
This horn part is written within a single MIDI region using a polyphonic score style with four parts (on 4 MIDI channels) to allocate the notes to the proper voice between the two staves.
In this example, only horns 1 and 3 are playing, so rests appear for horns 2 and 4 (and in the worst places -- and that's the problem).
I'm aware of several ways to overcome this problem (one of which is to duplicate the score style, hide rests for 2 and 4, and applying that style only to these measures, then enter user rests to show that 2 and 4 are not to play). Still, I'm wondering if there's some other kinds of tricks or workarounds to hide (or move) these rests so that I don't have to make these kinds of "specialty" score styles for individual measures.

yes there is.
insert a rest into the bar and change its midi
channel to match the non-playing instrument. then you
can drag the rest to where it won't clash with the
notes.
But remember to hold down the Option key while inserting the rest. This makes it a "user" rest.

Bad Score Style Deleted... error message?

I can't recall having this ever happen before...
I'm trying to open a song I was working on yesterday, but the latest version, as well as all back-ups, give me the message "Bad Score Style Deleted" when I try an open it, and even though there is an "OK" button to click, all that happens is I click the "OK" button repeatedly, and the error message remains, never goes away, and the song never opens.
This particular song was started from a SMF that the drummer had sent me along with his audio tracks, but I've done that many times before, without any problems.
Any ideas what this means, and how to get past it, before I start all over...
Thanks...

Adobe Digital Editions

Score editor: mapped score style

Hi,
I' m trying to write normal head notes in a mapped score style.
But i can only get an "X" instead of the normal head note.
I have: opened an environment window> double clicked on the icon> in Head i' ve change the "X", but it didn' t work.
Thanks.

it will provided you have chosen the correct instrumnet mapping and score style.

Creating a new img element and cannot change style.left or style.top to set placement as I can in other browsers

I create a new element of type img and am placing in a specific absolute position by setting style.position, style.left and style.top attributes. Works fine in IE and Opera but FF does not allow me to modify any of the style attributes either before or after the element is inserted into the document. I've tested this with 3.5.9 and 3.6.3 and both have the problem.
== This happened ==
Every time Firefox opened
== upon install of FF

I knew it was something incredibly obvious that I was missing.
by doing
himg.style.left = (Math.floor(coords[0]) + tweeks.x) + "px";
himg.style.top = (Math.floor(coords[1]) + tweeks.y) + "px";
instead of
himg.style.left = Math.floor(coords[0]) + tweeks.x;
himg.style.top = Math.floor(coords[1]) + tweeks.y;
it works. It seems Opera and IE assume px if nothing supplied while FF needs it explicitly specified.
Thanks!

FindChangeByList script to include Style Groups/sub Style Groups

I've been using this function happily (with varying degrees of success & lots of trial and error) for a while now. I'm not a script writer, understand very little but manage to copy and paste, and hope for the best.
This has served my wishes for the most part, but I have the need to apply a GREP search/replace to some text that needs to be styled with a paragraph style that lives inside a style group, inside another style group.
Style group called 'Headings', inside which is a style group called 'News from Areas heads' inside which is a paragraph style called 'b head_red (News from areas)'
I have picked up on helpful examples from others for applying a paragraph style that lives within one level of "Style Group", but don't know what the correct syntax to describe: a paragraph style within a folder, within a folder, within another folder might be?
I did wonder if the choice of underscores and brackets in the paragraph style may not help.
MTIA
Steve

Hi Jarek
Unfortunately I don't have much scripting knowledge, but to answer your questions
1. paraStyle real name is "b head_red (News from areas)"
    - "b head_red" is used elsewhere. Why didn't I keep it simple?
2. Do your findWhat string work in UI (run manually)?
    - yes, when I use normal GREP find/change it works okay.
3. Do your FindChangeByList.jsx work with some simplier example?
    - yes, I use it often. The .txt file I'm working on at the moment already contains about 10 text/glyph changes which work fine. I have had success in applying a 'paragraph style' that is within a 'style group'. But this is the first time I've tried to apply a 'paragraph style' that is in a 'style group', within a 'style group'.
Steve

How do you have the bottom stroke of a table show up using Table Styles and Cell Styles only?

I am using InDesign CS6, and I want to create a Table Style that has the bottom stroke show up, but does not have a table border, such as:
However, whenever I try to change the Table or Cell strokes so that the last stroke shows up, I get the entire table border, or some strange combination of borders:
Does anyone have any insight on how I can get the bottom stroke to show up while preserving my other stroke properties? Since I work with long documents, it's necessary to be able to control all of my tables through Table Styles and Cell Styles, and not by manually changing each and every table with the Stroke palette.
For reference, here are the my current Table Style properties and the resulting table:

Michael Murphy is the InDesign style-meister. He wrote "Adobe InDesign Styles" for Adobe Press, and did a great Lynda.com title on InDesign styling. Here's what he says in the book:
"As mentioned at the beginning of this chapter, with all the power of table and cell styles, it is important to understand not only how they work and what they can do for you, but also to understand their limitations.
"Two formatting features missing in table and cell styles have already been discussed: You will always have to set the column width and row height of cells when applying a table style for the first time, and you will always have to convert body rows to header and/or footer rows every time you apply a table style for first time or update the table's data....
"But there's another kind of limitation that's important to keep in mind as you are designing tables: It is very easy to design a table that cannot be completely defined by a table style. In many cases, you'll need to define an extra cell style or two that lets you complete for formatting. [my emphasis]."
So I think that's what you have to do: Apply another cell style on top of the cells at the bottom of the table after applying the table style.

Changes to [No Paragraph Style] causing unwanted style overrides

Hi fellow InDesigners
I'm using InDesign CS6. I'm working with long documents that were originally created in previous versions (CS4 and possibly earlier). My standard workflow for these jobs is to do the bulk of the text formatting in a newly created, bare-bones, single column document. First, I load the paragraph and character styles from the template, and when I'm done I copy and paste the formatted text back into the template for final layout and typesetting. This used to work fine in CS4, but in CS6, all my paragraphs show the plus sign in the Paragraph Styles panel, indicating that they have been overridden. They should be identical, since I imported the styles from one file to the other. The overrides include drop cap alignment, and even more obscure things like 'IdeoSpaceBehavior' and 'Diacritic Positioning'.
It seems likely to me that this problem is due to Adobe having changed the definition of the mysteriously ubiquitous '[No Paragraph Style]' style between versions. The template file has carried over the definition from CS4, but the newly created working files have the new definition, and since [No Paragraph Style] is not included when importing styles from one document to another, the inconsistency remains. Copying and pasting text with no overrides in one document, shows overrides in the other.
So the simplest solution I can think of, would be to change the [No Paragraph Style] in the template to match the definition of new CS6 documents. Is this even possible? My Googling thus far suggests that [No Paragraph Style] is pretty much untouchable.
Is there nothing for it but to create the template files again as new documents in CS6?

No worries Michael. Yes, I vaguely remember the change too.
My understanding is, [No Paragraph Style] is very much a style—a paradoxically named style to be sure, but a style nonetheless. Check out the [Basic Paragraph] style definition by double clicking on it in the Paragraph Styles panel. It's style definition is: '[No Paragraph Style] + next: [Same style]'. That's it. Minion Pro 12 point, with auto leading—and every other conceivable paragraph attribute—all handled by [No Paragraph Style]. Adobe needed some defaults, and that's what [No Paragraph Style] is—just a default style. You can never escape it either, since every style, no matter what it's based on, has [No Paragraph Style] as its most senior ancestor.
So that's essentially my problem. Adobe has, in their wisdom, changed the [No Paragraph Style] style between versions, so that a document originally created in an earlier version and a document created in CS6 have different [No Paragraph Style] settings. I'm pretty confident this is the cause of my problems.
Lots of my paragraph styles inherit from other styles. Why would I not want that? My custom 'Paragraph' style has lots of other styles based on it—from typesetting variations, to quotes, lists, etc. But the 'Paragraph' style itself is based on [No Paragraph Style]. As I said, you can't really escape [No Paragraph Style].

Styles and CSX styles

I imported a Word 2007 doc into a new RH 7 HTML project, and
I'm grappling with styles that aren't in RH 7 css or htts and
weren't in the Word template, either.
For example, when I highlight a paragraph that was a BulList
paragraph (in Word), the RH HTML Formatting ribbon displays the
style as BULLISTCXSPMIDDLE.
How do I fix this? If I try to edit the styles, there is no
BULLISTCXSPMIDDLE listed in the Styles dialog. Further, RH
instructions for deleting a style (from the Styles dialog) state:
Click "X". There is no "X". Rather, when I highlight a style I want
to delete, the Delete button becomes unavailable.The RH Styles
dialog has a neat list of Character and Paragraph formatting...and
then "Other"...how do I relate what's in this dialog to the "stuff"
that shwos up in the Formatting ribbon?
Further,

I can't speak specifically to Word-to-RH styles, but when you
see a style in RH all in caps, that means that RH can't find it in
the style sheet or in topic styles. That's why you can't find it in
the style sheet, either.
It should be sufficient to highlight the paragraphs in
question and select the Normal style (or whatever style you want it
to be).
As for getting that BULLISTCXSPMIDDLE style to never show up
at all, I don't know about that one.
Hope this helps,
Ben

Character styles & Body paragraph style not rendering as specified

Hi, I am creating my first epub, and am using InDesign CS 5 (no intention of upgrading). I've constructed it as a book, each chapter in its own file. I am encountering two problems I am unable to think my way out of:
1. None of the three character styles are rendering as they should.
-"Bold" text is rendering much larger than "Body" paragraph style, even though both are specified at 18 px.
-"Bullet" renders as UL, but at a much smaller point size than "Body" despite being specified as 18px.
-"Ital" is also rendering a much larger font size than is should.
2. I don't seem to be able to affect spacing between "Body" paragraphs, or below h1, etc.
Any insights? Any help?
Here is the CSS:
@font-face {
font-family: Times New Roman;
font-style: normal;
font-weight: bold;
src:url("../Fonts/timesbd.ttf");
@font-face {
font-family: Times New Roman;
font-style: normal;
font-weight: normal;
src:url("../Fonts/times.ttf");
@font-face {
font-family: Minion Pro;
font-style: normal;
font-weight: normal;
src:url("../Fonts/MinionPro-Regular.otf");
@font-face {
font-family: Helvetica;
font-style: normal;
font-weight: bold;
src:url("Fonts/hvb____.PFB");
@font-face {
font-family: Times New Roman;
font-style: italic;
font-weight: normal;
src:url("../Fonts/timesi.ttf");
div.generated-style {
div.generated-style-2 {
div.generated-style-3 {
p.h1 {
font-family: "Times New Roman";
font-weight: bold;
font-style: normal;
font-size: 2em;
line-height: 1.20em;
text-decoration: none;
font-variant: normal;
text-indent: 0em;
text-align: center;
color: #000000;
margin: 0em 0em 1em 0em;
p.author {
font-family: "Times New Roman";
font-weight: normal;
font-style: normal;
font-size: 2em;
line-height: 1.20em;
text-decoration: none;
font-variant: normal;
text-indent: 0em;
text-align: center;
color: #000000;
margin: 0em;
p.body {
font-family: "Times New Roman";
font-weight: normal;
font-style: normal;
font-size: 1.50em;
line-height: 1.20em;
text-decoration: none;
font-variant: normal;
text-indent: 0em;
text-align: left;
color: #000000;
margin: 0em;
p.basic-paragraph {
font-family: "Minion Pro";
font-weight: normal;
font-style: normal;
font-size: 1em;
line-height: 1.20em;
text-decoration: none;
font-variant: normal;
text-indent: 0em;
text-align: left;
color: #000000;
margin: 0em;
p.h2 {
font-family: "Times New Roman";
font-weight: bold;
font-style: normal;
font-size: 1.67em;
line-height: 1.20em;
text-decoration: none;
font-variant: normal;
text-indent: 0em;
text-align: left;
color: #000000;
margin: 1em 0em 0.50em 0em;
p.h3 {
font-family: "Times New Roman";
font-weight: bold;
font-style: normal;
font-size: 1.50em;
line-height: 1.20em;
text-decoration: none;
font-variant: normal;
text-indent: 0em;
text-align: left;
color: #000000;
margin: 0.78em 0em 0em 0em;
p.bullet {
font-family: "Times New Roman";
font-weight: normal;
font-style: normal;
font-size: 1.50em;
line-height: 1.20em;
text-decoration: none;
font-variant: normal;
text-indent: 0.06em;
text-align: left;
color: #000000;
margin: 0em 0em 0.56em 1.39em;
p.caption {
font-family: "Helvetica";
font-weight: bold;
font-style: normal;
font-size: 1.33em;
line-height: 1.20em;
text-decoration: none;
font-variant: normal;
text-indent: 0em;
text-align: center;
color: #000000;
margin: 0em;
p.pr-head {
font-family: "Times New Roman";
font-weight: normal;
font-style: normal;
font-size: 1.50em;
line-height: 1.20em;
text-decoration: none;
font-variant: normal;
text-indent: 0em;
text-align: center;
color: #000000;
margin: 0em;
span.bold1 {
font-family: "Helvetica";
font-weight: bold;
font-style: normal;
font-size: 1.50em;
span.ital {
font-family: "Times New Roman";
font-weight: normal;
font-style: italic;
font-size: 1.50em;
span.no-style-override {
span.h-link {
text-decoration: underline;
color: #0000ff;
span.no-style-override-1 {

Try watching this lynda course: Watch the Online Video Course InDesign CS5 to EPUB, Kindle, and iPad
If you don't have a subscription this link will get you a 10 day trial: lynda.com library | Trial Subscription
That said, I'd be remiss if I didn't tell you that you're in for a world of torture compared to InDesign CC2014. The advancements in EPUB export are amazing.

How do I (or can I) apply alternating para styles (using "next style") to existing text?

I am trying to apply background shading to alternate lines of text by creating two paragraph styles and naming each as the "next style".
This works when manually entering text - but I can't figure out if it is possible to apply it to existing copy with out applying the styles to each line individually.
Thanks for any help
d

Select multiple paragraphs of text, then right-click on the name of your first style in the Paragraph Styles panel. "Apply Style, Then Next Style" should be one of the options.

Updating style.css or style itself doesn't update topics

I am having an issue with the styles within RH. There is a defined style.css that was created, however, when the individual fonts or formats are changed within it, it doesn't change the topics. In addition, when I tried to just update a specific style on the style and formatting pod, I make the changes, it stores them, but when I select it to update selected paragraph of text, it changes the font to something totally different and the formatting as well. Am I missing some other area where possibly a default is taking over and I am not seeing it? It is becoming more and more frustrating, because I have had to go through topics over and over again, because it keeps re-formatting them on me. Any help would be greatly appreciated.

Yes, I believe the structure is correct, when I view the project manager, it lists the style.css as a top level item along with main folders, and the topics may be in some cases imbedded two or three levels deeper than that. Here is the text from the style.css as well as a picture showing the prj. mgr.
Thanks so much
Priscilla
text below the **** line is the css code:
/*Created with Adobe RoboHelp 9.*/
/* Document Defaults */
a:active {
color: #0000CC;
a:hover {
color: #CC0033;
a:link {
color: #3366CC;
a:visited {
color: #9999CC;
font-family: Verdana, Arial, Helvetica, sans-serif;
.GroupTitlesIX {
color: #003366;
font-size: 22px;
font-style: normal;
font-weight: bold;
margin-left: 0em;
margin-top: 0.5em;
margin-bottom: 0.5em;
text-align: left;
text-indent: 0em;
white-space: normal;
text-decoration: none;
.Preformatted {
color: #000000;
font-family: monospace;
font-size: 12px;
font-style: normal;
font-weight: normal;
margin-left: 0em;
margin-top: 0em;
margin-bottom: 0em;
text-align: left;
text-indent: 0em;
white-space: pre;
text-decoration: none;
.SmartList1 {
color: #000000;
font-style: normal;
font-weight: normal;
margin-left: 0em;
margin-top: 0.25em;
margin-bottom: 0.25em;
text-align: left;
text-indent: 0em;
white-space: normal;
font-size: 11pt;
font-family: "Times New Roman", serif;
text-decoration: none;
.SmartList1After {
margin-left: 0em;
.SmartList2 {
color: #000000;
font-style: normal;
font-weight: normal;
margin-left: 2.5em;
margin-top: 0.25em;
margin-bottom: 0.25em;
text-align: left;
text-indent: 0em;
white-space: normal;
font-size: 11pt;
font-family: "Times New Roman", serif;
line-height: 150%;
text-decoration: none;
.SmartList2After {
margin-left: 0em;
.SmartList3 {
color: #000000;
font-size: 12px;
font-style: normal;
font-weight: normal;
margin-left: 5em;
margin-top: 0.25em;
margin-bottom: 0.25em;
text-align: left;
text-indent: 0em;
white-space: normal;
text-decoration: none;
.SmartList3After {
margin-left: 0em;
.SmartList4 {
color: #000000;
font-size: 12px;
font-style: normal;
font-weight: normal;
margin-left: 7.5em;
margin-top: 0.25em;
margin-bottom: 0.25em;
text-align: left;
text-indent: 0em;
white-space: normal;
text-decoration: none;
.SmartList4After {
margin-left: 0em;
.SmartList5 {
color: #000000;
font-size: 12px;
font-style: normal;
font-weight: normal;
margin-left: 10em;
margin-top: 0.25em;
margin-bottom: 0.25em;
text-align: left;
text-indent: 0em;
white-space: normal;
text-decoration: none;
.SmartList5After {
margin-left: 0em;
.TableTitle {
color: #000000;
font-size: 12px;
font-style: italic;
font-weight: bold;
margin-left: 0em;
margin-top: 0.5em;
margin-bottom: 0.5em;
text-align: center;
text-indent: 0em;
white-space: normal;
text-decoration: none;
.Title {
color: #003366;
font-size: 24px;
font-style: normal;
font-weight: bold;
margin-left: 0em;
margin-top: 0.5em;
margin-bottom: 0.5em;
text-align: center;
text-indent: 0em;
white-space: normal;
text-decoration: none;
.TOC1 {
color: #000000;
font-size: 17px;
font-style: normal;
font-weight: bold;
margin-left: 0em;
margin-top: 0.25em;
margin-bottom: 0.25em;
text-align: left;
text-indent: 0em;
white-space: normal;
text-decoration: none;
.TOC2 {
color: #000000;
font-size: 15px;
font-style: normal;
font-weight: normal;
margin-left: 2.5em;
margin-top: 0em;
margin-bottom: 0em;
text-align: left;
text-indent: 0em;
white-space: normal;
text-decoration: none;
.TOC3 {
color: #000000;
font-size: 13px;
font-style: normal;
font-weight: normal;
margin-left: 5em;
margin-top: 0em;
margin-bottom: 0em;
text-align: left;
text-indent: 0em;
white-space: normal;
text-decoration: none;
.TOC4 {
color: #000000;
font-size: 11px;
font-style: normal;
font-weight: normal;
margin-left: 7.5em;
margin-top: 0em;
margin-bottom: 0em;
text-align: left;
text-indent: 0em;
white-space: normal;
text-decoration: none;
.TOC5 {
color: #000000;
font-size: 10px;
font-style: normal;
font-weight: normal;
margin-left: 10em;
margin-top: 0em;
margin-bottom: 0em;
text-align: left;
text-indent: 0em;
white-space: normal;
text-decoration: none;
rh-list.Style1 {
x-lvl-1-format: "<x>&c";
x-lvl-2-type: lower-alpha;
x-lvl-2-format: "<x>&c";
x-lvl-2-margin: 20px;
x-lvl-3-type: lower-roman;
x-lvl-3-format: "<x>&c";
x-lvl-3-margin: 40px;
x-lvl-4-type: decimal;
x-lvl-4-format: "&o<x>&c";
x-lvl-4-margin: 60px;
x-lvl-5-format: "&o<x>&c";
x-lvl-5-margin: 80px;
x-lvl-6-type: lower-roman;
x-lvl-6-format: "&o<x>&c";
x-lvl-6-margin: 100px;
x-lvl-8-type: lower-alpha;
x-lvl-8-margin: 140px;
x-lvl-7-format: "<x>.";
x-lvl-7-margin: 120px;
x-level-count: 9;
x-lvl-9-type: lower-roman;
x-lvl-9-margin: 160px;
h1 {
font-weight: bold;
margin-bottom: 14pt;
margin-left: 0pt;
page-break-after: avoid;
font-size: 14pt;
background-color: #7f7fff;
margin-top: 5pt;
margin-right: 256pt;
font-family: "Arial Black", sans-serif;
x-next-class: ;
x-next-type: p;
h2 {
font-weight: bold;
margin-bottom: 14pt;
margin-left: 0pt;
page-break-after: avoid;
font-size: 12pt;
font-style: italic;
background-color: #a3a5aa;
margin-top: 5pt;
margin-right: 256pt;
font-family: "Arial Black", sans-serif;
p {
font-size: 11pt;
margin-top: 0.5pt;
margin-left: 0px;
font-family: Arial, sans-serif;
text-align: justify;
margin-bottom: 5pt;
margin-right: 256pt;
table.TableTitle {
x-1st-row: 1;
x-1st-row-name: t1st;
font-size: 11pt;
font-weight: normal;
table.TableTitle tr.t1st td {
font-family: Verdana;
font-size: 11pt;
font-weight: bold;
background-color: #c0c0c0;
table.TableContent {
font-size: 10pt;
font-weight: bold;
background-color: #c4c4ff;
table.SimpleGridBlue {
padding: 0px;
x-border-spacing: 0px;
x-row-pat-1: 1;
x-row-pat-1-name: t1Row;
x-row-pat-count: 2;
x-row-pat-2: 1;
x-row-pat-2-name: t2Row;
border-left-style: Solid;
border-left-width: 1px;
border-left-color: #4F81BD;
border-top-style: Solid;
border-top-width: 1px;
border-top-color: #4F81BD;
table.SimpleGridBlue td {
padding-left: 10px;
padding-right: 10px;
padding-top: 0px;
padding-bottom: 0px;
table.SimpleGridBlue tr.t1Row td {
font-family: "Times New Roman";
font-size: 12pt;
border-right-style: Solid;
border-right-width: 1px;
border-right-color: #4F81BD;
border-bottom-style: Solid;
border-bottom-width: 1px;
border-bottom-color: #4F81BD;
table.SimpleGridBlue tr.t2Row td {
border-right-style: Solid;
border-right-width: 1px;
border-right-color: #4F81BD;
border-bottom-style: Solid;
border-bottom-width: 1px;
border-bottom-color: #4F81BD;
p.Style2 {
x-next-class: ;
x-next-type: p;
H4 {
font-weight: bold;
margin-bottom: 14pt;
margin-left: 0pt;
page-break-after: avoid;
font-size: 11pt;
margin-top: 0.5pt;
x-next-class: ;
x-next-type: P;
background-color: #c0c0c0;
margin-right: 256pt;
table.Style3 {
font-size: 11pt;
font-weight: bold;
.Style4 {
color: #000000;
margin-left: 0em;
margin-top: 0em;
margin-bottom: 0em;
text-align: left;
text-indent: 0em;
white-space: normal;
font-size: 11pt;
font-weight: bold;
font-style: normal;
text-decoration: none;
table.SimpleGridBlack {
padding: 0px;
border-top: Solid 1px #000000;
border-left: Solid 1px #000000;
x-border-spacing: 0px;
x-row-pat-1: 1;
x-row-pat-1-name: t1Row;
x-row-pat-count: 2;
x-row-pat-2: 1;
x-row-pat-2-name: t2Row;
table.SimpleGridBlack td {
padding-left: 10px;
padding-right: 10px;
padding-top: 0px;
padding-bottom: 0px;
table.SimpleGridBlack tr.t1Row td {
border-right-style: Solid;
border-right-width: 1px;
border-right-color: #000000;
border-bottom-style: Solid;
border-bottom-width: 1px;
border-bottom-color: #000000;
font-family: "Times New Roman";
font-size: 12pt;
table.SimpleGridBlack tr.t2Row td {
border-right-style: Solid;
border-right-width: 1px;
border-right-color: #000000;
border-bottom-style: Solid;
border-bottom-width: 1px;
border-bottom-color: #000000;
rh-list.Style5 {
x-lvl-1-format: "<x>&c";
x-lvl-2-type: lower-alpha;
x-lvl-2-format: "<x>&c";
x-lvl-2-margin: 20px;
x-lvl-3-type: lower-roman;
x-lvl-3-format: "<x>&c";
x-lvl-3-margin: 40px;
x-lvl-4-type: decimal;
x-lvl-4-format: "&o<x>&c";
x-lvl-4-margin: 60px;
x-lvl-5-format: "&o<x>&c";
x-lvl-5-margin: 80px;
x-lvl-6-type: lower-roman;
x-lvl-6-format: "&o<x>&c";
x-lvl-6-margin: 100px;
x-lvl-8-type: lower-alpha;
x-lvl-8-margin: 140px;
x-lvl-7-format: "<x>.";
x-lvl-7-margin: 120px;
x-level-count: 9;
x-lvl-9-type: lower-roman;
x-lvl-9-margin: 160px;

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).

Staff Styles or Score styles?

Similar Messages

Maybe you are looking for