[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [stp-dev] STP service creation
|
Antoine,
FYI, I deleted the ³-Dorg.osgi.framework.bootdelegation=*² from my
³~/tools/eclipse/eclipse.ini² file, leaving it only in
³~/tools/eclipse/Eclipse.app/Contents/MacOS/eclipse.ini². The
Eclipse->Preferences->Configuration display does indeed show the
³-Dorg.osgi.framework.bootdelegation=*² parameter correctly.
Thanks!
- Richard
From: Antoine Toulme <atoulme@xxxxxxxxxxx>
Reply-To: STP Dev list <stp-dev@xxxxxxxxxxx>
Date: Mon, 20 Aug 2007 05:22:11 +0200
To: STP Dev list <stp-dev@xxxxxxxxxxx>
Subject: Re: [stp-dev] STP service creation
Hi Adrian,
this is due to the JDK you use too I think. In the JDK6, Jsr-173
(javax.stream) is directly included in the standard libs, while you need to
add it explicitly in JDK5.
Richard, you may check that this parameter is set by opening
Help>About>Configuration. You should see a message dialog there, will all
the parameters. I think that with MacOS, eclipse.ini is also located in the
Eclipse.app folder, I don't know which one is picked up for sure though.
Hope this helps,
Antoine
On 8/20/07, Richard Mixon (CustCo) <rnmixon@xxxxxxxxxx> wrote:
> Adrian,
>
> I believe it is the exact same error.:
> !ENTRY org.eclipse.stp.common 4 0 2007-07-17 19:41:13.188
> !MESSAGE Celtix Java To Wsdl Generation failure
> !STACK 0 java.lang.LinkageError: loader constraints violated when linking
> javax/xml/namespace/QName class
>
> Here is the start of the thread I posted:
> http://www.eclipse.org/newsportal/article.php?id=194&group=eclipse.stp#194
> <http://www.eclipse.org/newsportal/article.php?id=194&group=eclipse.stp#19
> 4>
>
> I was quite embarrassed in the end. I switched to using a MacBook Pro last
> December after using Eclipse for 4 years on Windows and some Linux. For some
> reason I had never needed to set the eclipse.ini and just assumed that setting
> it in the main eclipse directory would work as before.
>
> Unfortunately I cannot see anywhere in the "eclipseWorkspace/.metadata/.log"
> that it shows if the org.osgi.framework.bootdelegation is set. Maybe someone
> else can say how to verify this other than the fact you are getting the
> LinkageError .
>
> Good luck - Richard
>
>
>
> From: Adrian Mos <adrian.mos@xxxxxxxx>
> Reply-To: STP Dev list <stp-dev@xxxxxxxxxxx>
> Date: Mon, 20 Aug 2007 01:48:32 +0200
>
> To: STP Dev list <stp-dev@xxxxxxxxxxx>
> Subject: Re: [stp-dev] STP service creation
>
> Hi Richard,
>
> Thanks for the idea, I have actually indeed include that line in the
> eclipse.ini fie. It's true it's a bit tricky on MacOS as you need to go into
> Eclipse.app using a shell, however I think I have correctly set it. To make
> sure it's not a MacOS issue, I have also tested this under Windows, had the
> same message so I must be doing something really wrong.
>
> Just to make sure I understood this, by correctly setting this line in
> eclipse.ini, have you corrected the exact same error that I reported (
> java.lang.LinkageError ), or was it another error related to JAX-WS? If it's
> the same error that you had and corrected, than perhaps you could send me your
> eclipse.ini file for comparison? This would still leave an open question as to
> why it doesn't work on Windows for me either...
>
> Cheers,
> Adrian.
>
>
>
>
> On Aug 20, 2007, at 12:11 AM, Richard Mixon (CustCo) wrote:
>
>> Adrian,
>>
>> Did you include
>> -Dorg.osgi.framework.bootdelegation=*
>> In your eclipse.ini file as documented in the getting started document?
>> http://wiki.eclipse.org/STP_Service_Creation_getting_started
>>
>> Its pretty easy in Windows and Linux, but on Mac OsX its done a bit
>> differently.
>>
>> Hope this helps, I thought I had it set for a couple of weeks and kept
>> getting this error. Works great now.
>>
>> - Richard
>>
>>
>>
>>
>> From: Adrian Mos <adrian.mos@xxxxxxxx>
>> Reply-To: STP Dev list <stp-dev@xxxxxxxxxxx>
>> Date: Sun, 19 Aug 2007 23:37:40 +0200
>> To: STP Dev list <stp-dev@xxxxxxxxxxx>
>> Subject: Re: [stp-dev] STP service creation
>>
>> Hi Guys,
>>
>> Just on the same topic, on running the service creation tutorial, I have
>> installed the same environment as Chadra (Eclipse 3.3 and the stp-all-in-one
>> bundle - the version that Chadra used as well as the most recent integration
>> build) and I could not get the plugin to generate the artefacts (WSDL and the
>> other classes). Looking into the Eclipse .log file, I found this error (see
>> below) occurred when the generation was attempted. I have correctly configure
>> the CXF path in the Eclipse preferences under the JAX-WS runtime path to the
>> root of the CXF binary distribution.
>>
>> Any help appreciated.
>>
>> Thank you,
>> Adrian.
>>
>>
>> !ENTRY org.eclipse.stp.common 4 0 2007-08-19 23:28:24.969
>> !MESSAGE Celtix Java To Wsdl Generation failure
>> !STACK 0
>> java.lang.LinkageError: loader constraints violated when linking
>> javax/xml/namespace/QName class
>> at
>> com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl.<clinit>(RuntimeBui
>> ltinLeafInfoImpl.java:186)
>> at
>> com.sun.xml.bind.v2.model.impl.RuntimeTypeInfoSetImpl.<init>(RuntimeTypeInfoS
>> etImpl.java:25)
>> at
>> com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeM
>> odelBuilder.java:84)
>> at
>> com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeM
>> odelBuilder.java:41)
>> at
>> com.sun.xml.bind.v2.model.impl.ModelBuilder.<init>(ModelBuilder.java:104)
>> at
>> com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.<init>(RuntimeModelBuilder
>> .java:49)
>> at
>> com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.ja
>> va:372)
>> at
>> com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:236)
>> at
>> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:76)
>> at
>> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:55)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.
>> java:25)
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:210)
>> at javax.xml.bind.ContextFinder.find(ContextFinder.java:366)
>> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
>> at
>> org.apache.cxf.jaxb.JAXBDataBinding.createJAXBContext(JAXBDataBinding.java:33
>> 2)
>> at
>> org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:172)
>> at
>> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServiceFromC
>> lass(ReflectionServiceFactoryBean.java:222)
>> at
>> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeService
>> Model(ReflectionServiceFactoryBean.java:250)
>> at
>> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(Reflection
>> ServiceFactoryBean.java:138)
>> at
>> org.apache.cxf.frontend.AbstractEndpointFactory.createEndpoint(AbstractEndpoi
>> ntFactory.java:81)
>> at
>> org.apache.cxf.frontend.AbstractServiceFactory.createService(AbstractServiceF
>> actory.java:29)
>> at
>> org.apache.cxf.tools.java2wsdl.processor.JavaToProcessor.process(JavaToProces
>> sor.java:87)
>> at
>> org.eclipse.stp.sc.cxf.generators.CeltixJavaToWsdlGenerator.run(CeltixJavaToW
>> sdlGenerator.java:102)
>> at
>> org.eclipse.stp.sc.jaxws.builders.ScJavaToWsdlBuilder.generate(ScJavaToWsdlBu
>> ilder.java:85)
>> at
>> org.eclipse.stp.sc.jaxws.builders.ScJavaToWsdlBuilder.buildOneJavaFile(ScJava
>> ToWsdlBuilder.java:57)
>> at
>> org.eclipse.stp.sc.common.builders.ScJavaBuilder.visitResourceFile(ScJavaBuil
>> der.java:127)
>> at
>> org.eclipse.stp.sc.common.builders.ScJavaBuilder.access$0(ScJavaBuilder.java:
>> 112)
>> at
>> org.eclipse.stp.sc.common.builders.ScJavaBuilder$ScBuildVisitor.visit(ScJavaB
>> uilder.java:174)
>> at
>> org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:105)
>> at
>> org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:57)
>> at
>> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeI
>> terator.java:81)
>> at
>> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeI
>> terator.java:85)
>> at
>> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeI
>> terator.java:85)
>> at
>> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeI
>> terator.java:85)
>> at
>> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeI
>> terator.java:85)
>> at
>> org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeI
>> terator.java:85)
>> at
>> org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeItera
>> tor.java:126)
>> at
>> org.eclipse.core.internal.resources.Resource.accept(Resource.java:67)
>> at
>> org.eclipse.core.internal.resources.Resource.accept(Resource.java:103)
>> at
>> org.eclipse.core.internal.resources.Resource.accept(Resource.java:87)
>> at
>> org.eclipse.stp.sc.common.builders.ScJavaBuilder.fullBuild(ScJavaBuilder.java
>> :75)
>> at
>> org.eclipse.stp.sc.common.builders.ScJavaBuilder.build(ScJavaBuilder.java:52)
>> at
>> org.eclipse.core.internal.events.BuildManager$2.run(BuildManager..java:624)
>> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
>> at
>> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:16
>> 6)
>> at
>> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:19
>> 7)
>> at
>> org.eclipse.core.internal.events.BuildManager$1.run(BuildManager..java:246)
>> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
>> at
>> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:24
>> 9)
>> at
>> org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.jav
>> a:302)
>> at
>> org.eclipse.core.internal.events.BuildManager.build(BuildManager..java:334)
>> at
>> org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:137)
>> at
>> org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>
>>
>>
>>
>> On Aug 13, 2007, at 5:22 PM, jain.chandra@xxxxxxxxx wrote:
>>
>>
>>> Hi Adrian, Denny,
>>>
>>> I was able to run through an end to end scenario. In the preferences
>>> for Apache CXF, I was incorrectly pointing to "Apache CXF plugin for JAX-WS
>>> development" rather than Apache CXF JAX-WS runtime.
>>>
>>> Thanks a lot for your inputs.
>>>
>>> regards,
>>> chandra
>>>
>>>
>>> <http://people.apache.org/repo/m2-snapshot-repository/org/apache/cxf/apache-
>>> cxf/2.1-incubator-SNAPSHOT/apache-cxf-2.1-incubator-20070729.204751-4.zip>
>>> ----- Original Message ----
>>> From: Adrian Skehill <adrian.skehill@xxxxxxxx>
>>> To: STP Dev list <stp-dev@xxxxxxxxxxx>
>>> Sent: Monday, August 13, 2007 3:47:10 PM
>>> Subject: Re: [stp-dev] STP service creation
>>>
>>> Hi,
>>>
>>>
>>>
>>> <snip>
>>>
>>>
>>>
>>>
>>>
>>>> > I noticed that when i create a new JAX-WS Web Service project it
>>>
>>>> > gives a warning dialog " You must specify a valid installation
>>>
>>>> > location for your selected runtime provider in JAX-WS preferences"
>>>
>>>> >
>>>
>>>> > I have specified 'org.apache.cxf_2.1-incubator-SNAPSHOT" in the
>>>
>>>> > preferences for Apache CXF. The resulting project shows Java
>>>
>>>> > Nature ( icon for project has a J) and not a SOA Tools Nature.
>>>
>>>> >
>>>
>>>> > Are there any known issues with this. I would like to debug
>>>
>>>> > this and understand the problem. What is the cvs repository
>>>
>>>> > location from which i can download the code and start debugging
>>>> this.
>>>
>>>
>>>
>>> In addition to having the plugin loaded into your eclipse environment, you
>>>
>>> will need an actual copy of the runtime you intend to deploy onto
>>> installed..
>>>
>>> IN this case you'll need to install CXF from [1]. Then set your preferences
>>> to
>>>
>>> point to the root of the install.
>>>
>>>
>>>
>>> The plugin that you install into eclipse provides the STP with access to
>>> the
>>>
>>> various generators that we need to execute during the process of creating
>>> SOA
>>>
>>> Services. The kit install is for the compilation and subsequent development
>>> of
>>>
>>> your SOA Services.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Adrian.
>>>
>>>
>>>
>>>
>>>
>>> [1] http://incubator.apache.org/cxf/download.html
>>>
>>> ----------------------------
>>> IONA Technologies PLC (registered in Ireland)
>>> Registered Number: 171387
>>> Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
>>>
>>>
>>>
>>>
>>>
>>> Park yourself in front of a world of choices in alternative vehicles.
>>> Visit the Yahoo! Auto Green Center.
>>> <http://us.rd.yahoo.com/evt=48246/*http://autos.yahoo.com/green_center/;_ylc
>>> =X3oDMTE5cDF2bXZzBF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDZ3JlZW4tY2VudGVy>
>>> _______________________________________________
>>> stp-dev mailing list
>>> stp-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/stp-dev
>>>
>>>
>>
>>
>>
>>
>> _______________________________________________
>> stp-dev mailing list
>> stp-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/stp-dev
>>
>> _______________________________________________
>> stp-dev mailing list
>> stp-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/stp-dev
>>
>
>
>
> _______________________________________________
> stp-dev mailing list
> stp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/stp-dev
>
> _______________________________________________
> stp-dev mailing list
> stp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/stp-dev
>
--
Intalio, the Open Source BPMS Company
<a href="http://www.intalio.com <http://www.intalio.com> ">
<http://www.intalio.com> ">http://www.intalio.com</a>
<http://www.intalio.com>
<a href="http://bpms.intalio.com";>Community website:
<http://bpms.intalio.com> ">http://bpms.intalio.com</a>
<http://bpms.intalio.com>
_______________________________________________
stp-dev mailing list
stp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/stp-dev
