You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Al Le <Al...@gmx.de> on 2013/08/21 08:40:35 UTC
Build error: Where is http_jetty.configuration?
Hello.
I'm trying to build CXF. At home this goes well, the build is successful. But at work, where we have a firewall and a web proxy, the build fails.
I check out the code via git (no problems with this) and then use the command "mvn -e -X -Pfastinstall". I've configured maven to correctly work with the proxy. All the needed libraries get downloaded from the internet.
The error occurs when building the module "cxf-rt-transports-http-jetty". Below are the first error messages.
My question is: where do the missing entities (e.g. the type ThreadingParametersIdentifiedType) live? Are they in an external library (then it's a problem with downloading libs from the internet)? Or are they part of CXF itself (then it's probably a problem with checking out code)?
Thanks for any suggestion!
AL
[ERROR] /C:/Users/x/AppData/Local/work/cxf/rt/transports/http-jetty/src/main/java/org/apache/cxf/transport/http_jetty/spring/JettySpringTypesFactory.java:[42,58] C:\Users\x\AppData\Local\work\cxf\rt\transports\http-jetty\src\main\java\org\apache\cxf\transport\http_jetty\spring\JettySpringTypesFactory.java:42: package org.apache.cxf.transports.http_jetty.configuration does not exist
[ERROR] /C:/Users/x/AppData/Local/work/cxf/rt/transports/http-jetty/src/main/java/org/apache/cxf/transport/http_jetty/spring/JettySpringTypesFactory.java:[43,58] C:\Users\x\AppData\Local\work\cxf\rt\transports\http-jetty\src\main\java\org\apache\cxf\transport\http_jetty\spring\JettySpringTypesFactory.java:43: package org.apache.cxf.transports.http_jetty.configuration does not exist
[ERROR] /C:/Users/x/AppData/Local/work/cxf/rt/transports/http-jetty/src/main/java/org/apache/cxf/transport/http_jetty/spring/JettySpringTypesFactory.java:[44,58] C:\Users\x\AppData\Local\work\cxf\rt\transports\http-jetty\src\main\java\org\apache\cxf\transport\http_jetty\spring\JettySpringTypesFactory.java:44: package org.apache.cxf.transports.http_jetty.configuration does not exist
[ERROR] /C:/Users/x/AppData/Local/work/cxf/rt/transports/http-jetty/src/main/java/org/apache/cxf/transport/http_jetty/spring/JettySpringTypesFactory.java:[52,15] C:\Users\x\AppData\Local\work\cxf\rt\transports\http-jetty\src\main\java\org\apache\cxf\transport\http_jetty\spring\JettySpringTypesFactory.java:52: cannot find symbol
symbol : class ThreadingParametersIdentifiedType
location: class org.apache.cxf.transport.http_jetty.spring.JettySpringTypesFactory
[ERROR] /C:/Users/x/AppData/Local/work/cxf/rt/transports/http-jetty/src/main/java/org/apache/cxf/transport/http_jetty/spring/JettySpringTypesFactory.java:[61,62] C:\Users\x\AppData\Local\work\cxf\rt\transports\http-jetty\src\main\java\org\apache\cxf\transport\http_jetty\spring\JettySpringTypesFactory.java:61: cannot find symbol
symbol : class ThreadingParametersType
Re: Build error: Where is http_jetty.configuration?
Posted by Daniel Kulp <dk...@apache.org>.
Thanks Aki!
Dan
On Aug 22, 2013, at 9:48 AM, Aki Yoshida <el...@gmail.com> wrote:
> i can see the trunk having this issue.
> i'll submit the fix after running the test for the whole project.
> regards, aki
>
> 2013/8/22 Aki Yoshida <el...@gmail.com>:
>> is this about the trunk code?
>> in that case, i think the recent api refactoring might have changed
>> the local schema locations and that could be causing this issue.
>> i'll take a look at it.
>>
>>
>> 2013/8/22 Al Le <Al...@gmx.de>:
>>>> You can add -Dhttp.proxyHost=… -Dhttp.proxyPort=… with mvn clean install, this should help.
>>>
>>> Yes, this did help a bit indeed, but I still get build errors -- now because of (I think) saml.jar has a wrong checksum (there were warnings about wrong checksum when maven downloaded the JAR). I'll look into it.
>>>
>>>> Btw, which cxf version you are using?
>>>
>>> I check out the trunk.
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: Re: Build error: Where is http_jetty.configuration?
Posted by Aki Yoshida <el...@gmail.com>.
i can see the trunk having this issue.
i'll submit the fix after running the test for the whole project.
regards, aki
2013/8/22 Aki Yoshida <el...@gmail.com>:
> is this about the trunk code?
> in that case, i think the recent api refactoring might have changed
> the local schema locations and that could be causing this issue.
> i'll take a look at it.
>
>
> 2013/8/22 Al Le <Al...@gmx.de>:
>>> You can add -Dhttp.proxyHost=… -Dhttp.proxyPort=… with mvn clean install, this should help.
>>
>> Yes, this did help a bit indeed, but I still get build errors -- now because of (I think) saml.jar has a wrong checksum (there were warnings about wrong checksum when maven downloaded the JAR). I'll look into it.
>>
>>> Btw, which cxf version you are using?
>>
>> I check out the trunk.
Re: Re: Build error: Where is http_jetty.configuration?
Posted by Aki Yoshida <el...@gmail.com>.
is this about the trunk code?
in that case, i think the recent api refactoring might have changed
the local schema locations and that could be causing this issue.
i'll take a look at it.
2013/8/22 Al Le <Al...@gmx.de>:
>> You can add -Dhttp.proxyHost=… -Dhttp.proxyPort=… with mvn clean install, this should help.
>
> Yes, this did help a bit indeed, but I still get build errors -- now because of (I think) saml.jar has a wrong checksum (there were warnings about wrong checksum when maven downloaded the JAR). I'll look into it.
>
>> Btw, which cxf version you are using?
>
> I check out the trunk.
Aw: Re: Build error: Where is http_jetty.configuration?
Posted by Al Le <Al...@gmx.de>.
> You can add -Dhttp.proxyHost=… -Dhttp.proxyPort=… with mvn clean install, this should help.
Yes, this did help a bit indeed, but I still get build errors -- now because of (I think) saml.jar has a wrong checksum (there were warnings about wrong checksum when maven downloaded the JAR). I'll look into it.
> Btw, which cxf version you are using?
I check out the trunk.
Re: Build error: Where is http_jetty.configuration?
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
You can add -Dhttp.proxyHost=… -Dhttp.proxyPort=… with mvn clean install, this should help.
Btw, which cxf version you are using?
－－－－－－－－－－－－－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: @Freeman小屋
On 2013-8-21, at 下午9:58, Al Le wrote:
>> It looks like build need the internet access.
>> Maybe you need to setup the proxy on the maven option.
>
> Yes, looks like this. I think I've correctly set up the proxy for maven itself (since it can download artifacts), and that the problem is in the maven module (IIUC everything in maven is done by modules) which presumably does not respect/use maven proxy settings.
Aw: Re: Build error: Where is http_jetty.configuration?
Posted by Al Le <Al...@gmx.de>.
> It looks like build need the internet access.
> Maybe you need to setup the proxy on the maven option.
Yes, looks like this. I think I've correctly set up the proxy for maven itself (since it can download artifacts), and that the problem is in the maven module (IIUC everything in maven is done by modules) which presumably does not respect/use maven proxy settings.
Re: Build error: Where is http_jetty.configuration?
Posted by Willem jiang <wi...@gmail.com>.
It looks like build need the internet access.
Maybe you need to setup the proxy on the maven option.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Wednesday, August 21, 2013 at 7:56 PM, Al Le wrote:
> Thank you for the quick reply!
>
> > ThreadingParametersType is auto-generated during build, try with "mvn clean install"
>
> I did it but I still get error messages. But I must correct myself: the first "suspicious" messages are the following (see below). So I assume this might be some problem with the XML parser or with the proxy (the latter is more likely).
>
> [WARNING] C:\Users\x\AppData\Local\work\cxf\rt\transports\http-jetty\src\main\resources\schemas\configuration\http-jetty.xsd [39:91]: schema_reference.4: Failed to read schema document 'http://cxf.apache.org/schemas/configuration/security.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
> org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://cxf.apache.org/schemas/configuration/security.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
>
> [ERROR] C:\Users\x\AppData\Local\work\cxf\rt\transports\http-jetty\src\main\resources\schemas\configuration\http-jetty.xsd [74:85]: src-resolve: Cannot resolve the name 'sec:TLSServerParametersType' to a(n) 'type definition' component.
> org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'sec:TLSServerParametersType' to a(n) 'type definition' component.
>
> AL
Aw: Re: Build error: Where is http_jetty.configuration?
Posted by Al Le <Al...@gmx.de>.
Thank you for the quick reply!
> ThreadingParametersType is auto-generated during build, try with "mvn clean install"
I did it but I still get error messages. But I must correct myself: the first "suspicious" messages are the following (see below). So I assume this might be some problem with the XML parser or with the proxy (the latter is more likely).
[WARNING] C:\Users\x\AppData\Local\work\cxf\rt\transports\http-jetty\src\main\resources\schemas\configuration\http-jetty.xsd [39:91]: schema_reference.4: Failed to read schema document 'http://cxf.apache.org/schemas/configuration/security.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://cxf.apache.org/schemas/configuration/security.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
[ERROR] C:\Users\x\AppData\Local\work\cxf\rt\transports\http-jetty\src\main\resources\schemas\configuration\http-jetty.xsd [74:85]: src-resolve: Cannot resolve the name 'sec:TLSServerParametersType' to a(n) 'type definition' component.
org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'sec:TLSServerParametersType' to a(n) 'type definition' component.
AL
Re: Build error: Where is http_jetty.configuration?
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
ThreadingParametersType is auto-generated during build, try with "mvn clean install"
－－－－－－－－－－－－－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: @Freeman小屋
On 2013-8-21, at 下午2:40, Al Le wrote:
> Hello.
>
> I'm trying to build CXF. At home this goes well, the build is successful. But at work, where we have a firewall and a web proxy, the build fails.
>
> I check out the code via git (no problems with this) and then use the command "mvn -e -X -Pfastinstall". I've configured maven to correctly work with the proxy. All the needed libraries get downloaded from the internet.
>
> The error occurs when building the module "cxf-rt-transports-http-jetty". Below are the first error messages.
>
> My question is: where do the missing entities (e.g. the type ThreadingParametersIdentifiedType) live? Are they in an external library (then it's a problem with downloading libs from the internet)? Or are they part of CXF itself (then it's probably a problem with checking out code)?
>
> Thanks for any suggestion!
>
> AL
>
>
>
> [ERROR] /C:/Users/x/AppData/Local/work/cxf/rt/transports/http-jetty/src/main/java/org/apache/cxf/transport/http_jetty/spring/JettySpringTypesFactory.java:[42,58] C:\Users\x\AppData\Local\work\cxf\rt\transports\http-jetty\src\main\java\org\apache\cxf\transport\http_jetty\spring\JettySpringTypesFactory.java:42: package org.apache.cxf.transports.http_jetty.configuration does not exist
>
> [ERROR] /C:/Users/x/AppData/Local/work/cxf/rt/transports/http-jetty/src/main/java/org/apache/cxf/transport/http_jetty/spring/JettySpringTypesFactory.java:[43,58] C:\Users\x\AppData\Local\work\cxf\rt\transports\http-jetty\src\main\java\org\apache\cxf\transport\http_jetty\spring\JettySpringTypesFactory.java:43: package org.apache.cxf.transports.http_jetty.configuration does not exist
>
> [ERROR] /C:/Users/x/AppData/Local/work/cxf/rt/transports/http-jetty/src/main/java/org/apache/cxf/transport/http_jetty/spring/JettySpringTypesFactory.java:[44,58] C:\Users\x\AppData\Local\work\cxf\rt\transports\http-jetty\src\main\java\org\apache\cxf\transport\http_jetty\spring\JettySpringTypesFactory.java:44: package org.apache.cxf.transports.http_jetty.configuration does not exist
>
> [ERROR] /C:/Users/x/AppData/Local/work/cxf/rt/transports/http-jetty/src/main/java/org/apache/cxf/transport/http_jetty/spring/JettySpringTypesFactory.java:[52,15] C:\Users\x\AppData\Local\work\cxf\rt\transports\http-jetty\src\main\java\org\apache\cxf\transport\http_jetty\spring\JettySpringTypesFactory.java:52: cannot find symbol
> symbol : class ThreadingParametersIdentifiedType
> location: class org.apache.cxf.transport.http_jetty.spring.JettySpringTypesFactory
>
> [ERROR] /C:/Users/x/AppData/Local/work/cxf/rt/transports/http-jetty/src/main/java/org/apache/cxf/transport/http_jetty/spring/JettySpringTypesFactory.java:[61,62] C:\Users\x\AppData\Local\work\cxf\rt\transports\http-jetty\src\main\java\org\apache\cxf\transport\http_jetty\spring\JettySpringTypesFactory.java:61: cannot find symbol
> symbol : class ThreadingParametersType