[Smartfrog-checkins] core/extras/alpine/doc/jaxrpc alpine.tex,1.17,1.18 bibliography.bib,1.19,1.20 i

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Update of /cvsroot/smartfrog/core/extras/alpine/doc/jaxrpc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv20413/alpine/doc/jaxrpc

Modified Files:
	alpine.tex bibliography.bib implications.tex introduction.tex 
	jaxrpc.tex wsdl.tex 
Log Message:
some typos, some layout.

Index: introduction.tex
===================================================================
RCS file: /cvsroot/smartfrog/core/extras/alpine/doc/jaxrpc/introduction.tex,v
retrieving revision 1.19
retrieving revision 1.20
diff -C2 -d -r1.19 -r1.20
*** introduction.tex	26 Apr 2005 13:52:53 -0000	1.19
--- introduction.tex	28 Apr 2005 16:13:40 -0000	1.20
***************
*** 2,6 ****
  \label{introduction}

! In beginning any discussion of SOAP-based technologies, it is 
  valuable to review the core features which made adopting SOAP
  attractive initially. We briefly characterise these as follows:
--- 2,8 ----
  \label{introduction}

! %\PARstart{I}{n}
! In
! beginning any discussion of SOAP-based technologies, it is 
  valuable to review the core features which made adopting SOAP
  attractive initially. We briefly characterise these as follows:

Index: implications.tex
===================================================================
RCS file: /cvsroot/smartfrog/core/extras/alpine/doc/jaxrpc/implications.tex,v
retrieving revision 1.9
retrieving revision 1.10
diff -C2 -d -r1.9 -r1.10
*** implications.tex	26 Apr 2005 13:52:53 -0000	1.9
--- implications.tex	28 Apr 2005 16:13:40 -0000	1.10
***************
*** 46,50 ****
  The 2.0 revision of the JAX-RPC specification promises to correct some of these
  flaws, but not, we fear, enough. It uses a new O/X mapping, the Java
! Architecture for XML Binding 2.0 9 (JAXB 2.0)\cite{spec:JAX-B-20}. This is possibly the most
  sophisticated XML to Java mapping framework yet designed, with broad support
  for generating classes from XML Schema, and XML Schema from annotated classes.
--- 46,50 ----
  The 2.0 revision of the JAX-RPC specification promises to correct some of these
  flaws, but not, we fear, enough. It uses a new O/X mapping, the Java
! Architecture for XML Binding 2.0 (JAXB 2.0)\cite{spec:JAX-B-20}. This is possibly the most
  sophisticated XML to Java mapping framework yet designed, with broad support
  for generating classes from XML Schema, and XML Schema from annotated classes.

Index: wsdl.tex
===================================================================
RCS file: /cvsroot/smartfrog/core/extras/alpine/doc/jaxrpc/wsdl.tex,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -d -r1.14 -r1.15
*** wsdl.tex	26 Apr 2005 13:52:53 -0000	1.14
--- wsdl.tex	28 Apr 2005 16:13:40 -0000	1.15
***************
*** 44,57 ****
  \item

! Some aspects of the service are not extracted from the raw signatures
! of the classes and methods. For example, if a method chooses to
! extract attachments from a message, that information can be hidden in
! the contents of the message, instead of in the signature of the
! call. The generated WSDL will hence omit any information about the
! attachment needs of the service.

  \item

! There is no warning of portability issues before integration time.
  When defining a service using an IDL, the author typically knows when
  there are problems as the IDL will not compile. Yet with contract-last
--- 44,63 ----
  \item

! Some aspects of the service are not extracted from the raw signatures of the
! classes and methods. For example, A method may extract attachments from a
! message programmatically, rather than declaring the attachment in the signature.
! This can be done for two reasons. It may be that the attachment is optional; the
! programmatic extraction can handle a missing attachment more gracefully. The
! other reason is to deliberately avoid including attachment information in the
! WSDL, in the knowledge that some clients cannot handle attachments in WSDL
! properly. The developers are reduced to moving part of the service contract out
! of band, to avoid portability problems. As a consequence, those clients that can
! process attachment declarations in WSDL correctly are being deprived of the
! opportunity to use it. With handwritten WSDL, one could have two WSDL service
! descriptions, one containing the attachment information, and one omitting it.

  \item

! There is no pre-deployment warning of portability issues.
  When defining a service using an IDL, the author typically knows when
  there are problems as the IDL will not compile. Yet with contract-last

Index: bibliography.bib
===================================================================
RCS file: /cvsroot/smartfrog/core/extras/alpine/doc/jaxrpc/bibliography.bib,v
retrieving revision 1.19
retrieving revision 1.20
diff -C2 -d -r1.19 -r1.20
*** bibliography.bib	26 Apr 2005 13:52:52 -0000	1.19
--- bibliography.bib	28 Apr 2005 16:13:40 -0000	1.20
***************
*** 176,180 ****
      title="{Basic Profile}",
      edition="1.1",
!     year="2004"
      note="http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html"
      }
--- 176,180 ----
      title="{Basic Profile}",
      edition="1.1",
!     year="2004",
      note="http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html"
      }
***************
*** 261,264 ****
--- 261,272 ----
      }

+ @misc{pjr:NKonXml,
+     title="{Introducing NetKernel}",
+     author="Peter Rodgers",
+     year="2005",
+     howpublished="online",
+     note="http://www.xml.com/pub/a/2005/04/27/netkernel.html",
+     }
+     
  @misc{MSFT:TransitionsInProgrammingModels,
      title="{Transitions in Programming Models}",

Index: jaxrpc.tex
===================================================================
RCS file: /cvsroot/smartfrog/core/extras/alpine/doc/jaxrpc/jaxrpc.tex,v
retrieving revision 1.17
retrieving revision 1.18
diff -C2 -d -r1.17 -r1.18
*** jaxrpc.tex	28 Jan 2005 20:32:43 -0000	1.17
--- jaxrpc.tex	28 Apr 2005 16:13:40 -0000	1.18
***************
*** 37,42 ****
  %\onecolumn

! %bibliographystyle{alpha}
! %\bibliography{bibliography}
  \bibliographystyle{IEEEtran}
  \bibliography{IEEEabrv,bibliography}
--- 37,42 ----
  %\onecolumn

! %trigger new page at reference 10
! \IEEEtriggeratref{9}
  \bibliographystyle{IEEEtran}
  \bibliography{IEEEabrv,bibliography}

Index: alpine.tex
===================================================================
RCS file: /cvsroot/smartfrog/core/extras/alpine/doc/jaxrpc/alpine.tex,v
retrieving revision 1.17
retrieving revision 1.18
diff -C2 -d -r1.17 -r1.18
*** alpine.tex	26 Apr 2005 13:52:52 -0000	1.17
--- alpine.tex	28 Apr 2005 16:13:40 -0000	1.18
***************
*** 165,167 ****
  extensions of existing languages, such as C$\omega$, or XML runtimes such as
  Apache Cocoon and NetKernel by 1060 Research
! \cite{MSFT:TransitionsInProgrammingModels,pjr:NKonTSS}.
--- 165,167 ----
  extensions of existing languages, such as C$\omega$, or XML runtimes such as
  Apache Cocoon and NetKernel by 1060 Research
! \cite{MSFT:TransitionsInProgrammingModels,pjr:NKonXml}.

[Smartfrog-checkins] core/extras/alpine/doc/jaxrpc alpine.tex,1.17,1.18 bibliography.bib,1.19,1.20 i

[Smartfrog-checkins] core/extras/alpine/doc/jaxrpc alpine.tex,1.17,1.18 bibliography.bib,1.19,1.20 implications.tex,1.9,1.10 introduction.tex,1.19,1.20 jaxrpc.tex,1.17,1.18 wsdl.tex,1.14,1.15