Wednesday Apr 01, 2009
Wednesday Jan 28, 2009
By Jeffrey Rubinoff on Jan 28, 2009
http://wiki.netbeans.org/attach/RestJMakiComponents/CustomerJMakiApp.zip EDIT: As soon as I write this post, Patch 2 is released! So the problem is over.
Tuesday Dec 02, 2008
By Jeffrey Rubinoff on Dec 02, 2008
Wednesday Oct 01, 2008
By Jeffrey Rubinoff on Oct 01, 2008
Saturday Aug 30, 2008
By Jeffrey Rubinoff on Aug 30, 2008
Monday Aug 25, 2008
By Jeffrey Rubinoff on Aug 25, 2008
Because I am not a Mediawiki developer, I left the username and password fields blank. If I had developer privileges, I would have entered my authorization credentials so I could later commit changes back to the Mediawiki repository. In the next panel of the checkout wizard, the IDE automatically filled out the Repository Folder field with the path to the phase3 folder. I accepted this default. Then in the local folder field, I specified the path to the web folder for my Xampp installation. This meant that the Apache server in my Xampp could immediately expose my checked out Mediawiki repository. I left all other fields and check boxes blank, which is the default setting.
When I clicked Finish, the IDE checked out the Mediawiki phase3 SVN repository correctly to my Xampp web folder, with the path G:/xampp/htdocs/phase3.Next I completed the Mediawiki installation procedure as described in the Mediawiki installation guide:
- Prepare the directories.
- Create a database.
- Run the installation script.
In the Name and Location panel, I browsed to the G:/xampp/htdocs/phase3 folder. I then selected "Put NetBeans metadata into a separate directory" This is so that no NetBeans metadata would be committed back to the Subversion repository. (I had no check in privileges in any case but wanted to test the feature.) I created a "mediawiki" folder in my NetBeansProjects directory for this purpose. I left all other fields at their default settings.
In the Run Configuration panel, I chose to run the project as a local web site, on my Xampp Apache server. I could instead have chosen to run the project on a remote FTP server or as a command-line script, as described in the Setting Up a PHP Project tutorial. Because I had already checked out the Mediawiki repository to my web folder, I did not need to copy source files to that location. So I left all fields at their default settings.
That was it! When I clicked Finish, the IDE created a PHP project out of the checked out Mediawiki repository. It took about 30 seconds to index all the files. From then on, I could use the IDE's PHP editing features to work on the project and its versioning features to update and commit my changes.
Thursday Jul 31, 2008
By Jeffrey Rubinoff on Jul 31, 2008
Friday Jul 11, 2008
By Jeffrey Rubinoff on Jul 11, 2008
The problem appears to be that Patch 2 replaced the JSP parser with a new version, and the nbm files are set up to use the old version. Until a new version of the nbm is created, I'm afraid you need to have an installation of NetBeans IDE 6.1 without updates in order to use Facelets support.
Thursday Jun 26, 2008
By Jeffrey Rubinoff on Jun 26, 2008
I've just been reading this rather interesting post on WSDL and WADL via DZone. When I got to the all-too-brief discussion of WADL at the end, I realized something: after 6 years documenting web service related stuff, I still don't really know what's going on in a WSDL document. But when I look at WADL, it seems clear as day. Is this just my naive social-science-major tech writer POV, or do WS developers feel the same way?
Wednesday Jun 25, 2008
By Jeffrey Rubinoff on Jun 25, 2008
Thursday Jun 05, 2008
By Jeffrey Rubinoff on Jun 05, 2008
Tuesday May 27, 2008
By Jeffrey Rubinoff on May 27, 2008
Sunday May 18, 2008
By Jeffrey Rubinoff on May 18, 2008
Sunday Apr 13, 2008
By Jeffrey Rubinoff on Apr 13, 2008
- Download the Java version of the Interoperability Testing Tool from the WS-I.org Deliverables page.
- Unzip the tool into the location of your choice.
- Create a WSI_HOME environment variable set to the location of the unzipped Interoperability Testing Tool.
- Open the IDE and navigate to Tools > soapUI > Preferences. Open the WS-I Settings tab and, in the Tool Location field, enter the location of the downloaded and unzipped wsi-test-tools folder. Select other options according to your preferences and click OK.
To validate SOAP messages, first monitor a SOAP request and response, as follows:
- Find the binding node in the Web Service Tests node and expand it to show the requests.
- Right-click a request and open the Request Editor, described in soapUI documentation.
- In the Request Editor, send a request and wait for the response.
- Right-click in the response window and select Check WS-I Compliance.
You can see the test configuration used to generate the test report in the Config tab. SOAP message test reports also have a Log tab, which is an XML log of the request and response SOAP exchange.
Friday Mar 14, 2008
By Jeffrey Rubinoff on Mar 14, 2008
I'm a technical writer for NetBeans, covering web service support.
- WSDL Customization Issues and Workarounds in Java EE 6 Applications in NetBeans
- RESTful Web Services and EJB 3.1
- Portability and Performance in JAX-WS Clients built in NB 6.7
- Question of the day
- Still alive
- NEW temporary problem with RESTful client stubs created in jMaki or Spring framework
- Temporary problem with RESTful client stubs created in JMaki framework
- @ProduceMime, @ConsumeMime > @Produces, @Consumes
- Facelets support on the trunk for NetBeans 6.5
- Creating a PHP Project from a Subversion repository