This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Product Version = NetBeans IDE 8.0 (Build 201403101706) Operating System = Linux version 3.2.0-4-amd64 running on amd64 Java; VM; Vendor = 1.8.0_11 Runtime = Java HotSpot(TM) 64-Bit Server VM 25.11-b03 when i try to edit my jsf files (*.xhtml) the IDE html checker say that cannot "find preset schema for namespace http //java.sun.com/jsf/facelets" and disable the autocomplete for my jsf tags..
Created attachment 148446 [details] Log do IDE
Please could you attach sample .xhtml page where it doesn't work to you?
Created attachment 148447 [details] page this is the page from the printscreen, but in thw whole project JSF autocomplete is disabled... i only see completion for angular and knockout
Created attachment 148448 [details] the message the image of the page in my IDE with the message
one more tip, when i close and reopen IDE many times, the problem seems to stop but when i close the xhtml and reopen, or open another xhtml, the problem is back... i develop in JSF 2.1 in the same IDE, same machine, this problem does not happen... its only in JSF 2.2 and HTML5 doctype page
Sorry, I'm not able to reproduce your problem in any way. There will be problem with the project setup: "INFO [JsfSupportImpl]: project 'Maven[/home/arthur/Documentos/workspaces/fpti/turismo/portal-reservas/trunk/PortalReservas/pom.xml]' does not have source classpath; documentBase=/home/arthur/Documentos/workspaces/fpti/turismo/portal-reservas/trunk/PortalReservas/src@1660650e:55dc7614" Please could you attach your pom.xml file (or at least important parts of it)? It looks that your document root is set to the src folder where I would expect rather source root. Which project type do you use? Is it Maven Web project? Thanks.
Created attachment 148521 [details] my pom Yes, i have some particularities in my pom, one is the automatic generation of my SOAP webservice client classes... i using the netbeans options to generate client ws from WSDL and and the code is automatically placed on my pom
(In reply to arthurgregorio from comment #7) > Created attachment 148521 [details] > my pom > > Yes, i have some particularities in my pom, one is the automatic generation > of my SOAP webservice client classes... > > i using the netbeans options to generate client ws from WSDL and and the > code is automatically placed on my pom And in which folder are you facelets placed? Is it <..>/PortalReservas/src?
(In reply to Martin Fousek from comment #8) > (In reply to arthurgregorio from comment #7) > > Created attachment 148521 [details] > > my pom > > > > Yes, i have some particularities in my pom, one is the automatic generation > > of my SOAP webservice client classes... > > > > i using the netbeans options to generate client ws from WSDL and and the > > code is automatically placed on my pom > > And in which folder are you facelets placed? Is it <..>/PortalReservas/src? in PortalReservas/src/main/webapp i solved the problem changing the auto-generated code in my pom by some other configs diferent of the netbeans code. it seems he mess entire folder source folder.
(In reply to arthurgregorio from comment #9) > i solved the problem changing the auto-generated code in my pom by some > other configs diferent of the netbeans code. > > it seems he mess entire folder source folder. Please could you send us diff you did into the pom.xml and exactly which feature mess that up? We can try to fix that (i.e. the WS generator). Thanks a lot!
Created attachment 148606 [details] the diff from old pom basically what I did was remove the folders and files that the IDE generates and make the maven plugin generate classes in every build based on the URL of the service, without the need to have the WSDL in the project.
would be interesting if there was the possibility of allowing the user to select how want to generate the client classes, maybe this way I'm doing without having the WSDL in the project could be one, without the need to create a subdirectory of codes and avoiding these problems about reference ...
Your JSF issues are cause by the generated "webResources" section. I'm going to take a look what feature wrongly generated that. If you would be facing the same issue, remove that section from the pom.xml. But I believe that we will be able to fix that in the daily builds - you are not the only one who hit such a trouble.
Reassigning to the webservices - more information will follow.
Created attachment 148714 [details] screenshot from the project view The cause of the JSF malfunction seems to be broken project setup by "WebService from WSDL file" generation action. Once I tried that feature it includes into pom.xml file following part: <webResources> <resource> <directory>src</directory> <targetPath>WEB-INF</targetPath> <includes> <include>jax-ws-catalog.xml</include> <include>wsdl/**</include> </includes> </resource> </webResources> That marks whole 'src' folder as a web root which doesn't look to be correct. At least tow users were already complaining about that and in both cases they didn't need to have such a piece of code in their pom.xml - is it necessary from point of view of WebServices?
CCing pggeldenhuys who was facing the same troubles.
Also solved the issue by removing: <webResources> <resource> <directory>src</directory> <targetPath>WEB-INF</targetPath> </resource> </webResources> from my pom, but yes the ws gen code needs to have a re-look.
From the screenshot you attached, problem seems to be in jaxws-maven-plugin:2.3 execution. This is likely the problem of parsing schema in jdk1.8. Access to XML schema (WSDL) is restricted by default in jdk1.8. The solution is either to start netbeans with: -J-Djavax.xml.accessExternalSchema=all or (better), include the following JVM option into pom.xml: ... <plugin> <groupId>org.jvnet.jax-ws-commons</groupId> <artifactId>jaxws-maven-plugin</artifactId> <version>2.3</version> <executions> <execution> <goals> <goal>wsimport</goal> </goals> <configuration> <wsdlFiles> <wsdlFile>ws/WSTUR004.apw.wsdl</wsdlFile> </wsdlFiles> <vmArgs> <vmArg>-Djavax.xml.accessExternalSchema=all</vmArg> </vmArgs> <packageName>ws.wstur004</packageName> </configuration> See also the issue 241570. See also: http://wiki.netbeans.org/FaqWSDLExternalSchema We may add this JVM option automatically for jaxws-maven-plugin. Please, confirm if this is the issue.
i can't test if its solve the problem because i already solved with another approach. I changed the generated configuration by generating the ws client dynamically by the wsdl URL See: <plugin> <groupId>org.jvnet.jax-ws-commons</groupId> <artifactId>jaxws-maven-plugin</artifactId> <version>2.1</version> <executions> <execution> <id>wsimport-generate-wstur004</id> <phase>generate-sources</phase> <goals> <goal>wsimport</goal> </goals> <configuration> <wsdlUrls> <wsdlUrl>${ws.base}WSTUR004.apw?WSDL</wsdlUrl> </wsdlUrls> <packageName>ws.wstur004</packageName> </configuration> </execution> </executions> </plugin> As I suggested earlier, if the customer uses the url of the wsdl to generate the client would be interesting not having to bring it to the project (since ws can still change) and use this setting, where each build the wsdl is accessed and client files will always be updated. If the user has the wsdl in the project, put it directly in web-inf is also something better than having separate folders and in the end it all goes in there.
Keeping wsdl locally is useful when working offline. You may also make jaxb customization on that local wsdl, without changing the contract (original wsdl) between the server and the client. Don't remember cases when wsdl file was also needed in runtime. Will consult that with JAX-WS team whether this is needed anymore.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss