Hi Sebastien,
I can confirm that you are right, that was the problem. I would swear
I saw many examples that had the implementation element as last one in
the composite file ;-).
Thanks again,
Radim
On 9/20/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
> Simon Laws wrote:
> > On 9/20/07, Radim Kolarik <[EMAIL PROTECTED]> wrote:
> >
> >> Hi Sebastien,
> >>
> >> thanks for your help! It was the the custom Web container property as
> >> described in the WebSphere fixpack.
> >>
> >> I can also confirm now that it works with 6.1.0.11 fixpack as well, if
> >> the property is set.
> >>
> >> In the log file, however, we are getting something I am not sure we
> >> were getting before:
> >>
> >> [20/09/07 10:47:17:187 BST] 00000036 ValidatingXML W XMLSchema
> >> validation problem in:
> >>
> >> file:/c:/Program%20Files/IBM/WebSphere/AppServer/profiles/vws/installedApps/vws/example-sc-0_0_1_war.ear/example-
> >> sc-0.0.1.war/WEB-INF/classes/example-sc.composite,
> >> line: 12, column: 7
> >> cvc-complex-type.2.4.a: Invalid content was found starting with
> >> element 'implementation.java'. One of
> >> '{"http://www.osoa.org/xmlns/sca/1.0":service,
> >> "http://www.osoa.org/xmlns/sca/1.0":reference,
> >> "http://www.osoa.org/xmlns/sca/1.0":property}' is expected.
> >>
> >> Do you have an idea what could be wrong?
> >>
> >> It looks to me that in http://www.osoa.org/xmlns/sca/1.0/sca-core.xsd
> >> the following code suggests that only service, reference or property
> >> elements are possible within the component:
> >>
> >> - <sequence>
> >> <element ref="sca:implementation" minOccurs="0" maxOccurs="1" />
> >> - <choice minOccurs="0" maxOccurs="unbounded">
> >> <element name="service" type="sca:ComponentService" />
> >> <element name="reference" type="sca:ComponentReference" />
> >> <element name="property" type="sca:Property" />
> >> </choice>
> >> <any namespace="##other" processContents="lax" minOccurs="0"
> >> maxOccurs="unbounded" />
> >> </sequence>
> >>
> >> We also have implementation.java there and it seems to be a valid
> >> option based on several examples, including examples in the spec.
> >>
> >> Thanks,
> >> Radim
> >>
> >>
> >> On 9/19/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
> >>
> >>> Radim Kolarik wrote:
> >>>
> >>>> Hi Simon,
> >>>>
> >>>> unfortunatelly I am seeing the same problem on WAS 6.1.0.9.
> >>>>
> >>>> Sebastien, do you still have the WAS environment? Could you try to
> >>>> deploy RC3 based example web service on it?
> >>>>
> >>>> Thanks a lot,
> >>>> Radim
> >>>>
> >>>>
> >>>>
> >>> It works for me.
> >>>
> >>> I need more precise information to be able to help.
> >>>
> >>> - which web service based sample? helloworld? calculator? built
> >>> yourself? using mvn or ant?
> >>> - the steps you are following to install and run the sample and the
> >>> exact output you are getting when you run it
> >>> - whether or not you have configured the WAR classloader "parent last"
> >>> and "single classloader"
> >>> - whether or not you have configured the custom Web container property
> >>> as described in the WebSphere fixpack at [1]
> >>> - the time of the error
> >>> - your SystemOut.log and SystemError.log files
> >>> - the FFDC files created in yout logs directory at the time of the error
> >>>
> >>> Could you please put that information in a JIRA. I'm watching the JIRA
> >>> notifications so I'll get notified when you do so, and will investigate
> >>> quickly. Thanks.
> >>>
> >>> [1] http://www-1.ibm.com/support/docview.wss?uid=swg24014758
> >>>
> >>> Thanks.
> >>>
> >>> --
> >>> Jean-Sebastien
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>> For additional commands, e-mail: [EMAIL PROTECTED]
> >>>
> >>>
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >> Hi Radim
> >>
> >
> > You're seeing this output now because Sebastien recently implemented schema
> > validation against the SCA files.
> >
> > What the schema is saying is that you can have an <implementation.?> element
> > (implementation.java in your case) which can then be followed by a choice of
> > any number of service, reference or property elements.
> >
> > Can you check in your .composite file that you have the default namespace
> > xmlns="http://www.osoa.org/xmlns/sca/1.0"; and that the <implementation.java>
> > element appears as the first child element in your component definition.
> >
> > Regards
> >
> > Simon
> >
> >
>
> A common bug I've seen in many composites is that the <implementation>
> element must appear first under <component>.
>
> Hope you find the validation useful :)
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
