[JBossWS] - Stop Empty SOAP elements
by jizzoe
Hi All,
I'm using JBoss WebServices with JAX-WS to connect to a Web Service. I use wsconsume to generate Java Classes.
Here's my dliema. In some of my generated classes that I'm using as request objects, I instantiate the object, populate some fields and send it along. Problem is all of those fields are getting generated in the SOAP message, even if I left it as null. On the Web Service side, it's been interpreted as empty string instead of NULL, which causes problems.
Any idea why null values still get generated in SOAP? And any idea hot to stop this from happening? These fields are defined as nillable in the WSDL.
Any help is greatly appreciated.
Thanks,
Joe
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092784#4092784
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092784
18Â years, 7Â months
[Installation, Configuration & DEPLOYMENT] - Trying to get isapi_redirect to work
by mclagett
I've been trying to install jira on jboss 4.20GA, which I have actually managed to do and can now use it if I address http://localhost:8080/jira from my browser. I now need to expose it to the rest of the network via my Internet Information Services web server. I haven't really found any good instructions for jboss with Tomcat 6; directory structures seemed to have changed from the instructions being given for previous jboss versions, so I'm not quite sure what I might be doing wrong.
I did get the Isapi_redirect installed as a filter in IIS with the green all-systems-go arrow, but when I type in http://localhost/jira I get a 404 error message. I think that I'm supposed to be able to address it that way, but just in case I was supposed to type http://localhost/jakarta (jakarta is the name of the IIS virtual directory I was instructed to create), I tried that but get a 403 error message. What I was expecting was to be redirected to the Jira login screen the way it happens when I address port 8080 directly.
For informational purposes I have outlined the steps I took and the files I created below. One other step, however, that some of the older documentation talked about was modifying a "context" tag. I wasn't sure if that was necessary with this version and if it is, what file and directory to address. Perhaps this is why my install is failing. I would appreciate it greatly if someone with experience in this area could glance at the files below and see if he or she spots anything screwy and also advise me regarding the context tag and if and where I should be editing it.
Thank you very much for any assistance you can provide. I'm so close I can taste it and this is realy driving me up the wall.
Regards,
Mike
In the description below {ISAPI_REDIRECT_ROOT} is the root of the directory tree where I installed the Isapi_redirect.dll and {JBOSS_ROOT} is the root of my JBoss install.
Here are the steps I took to install:
1) downloaded latest version (August 7, 2007 timestamp) of isapi_redirect.dll from Apache and placed it in my {ISAPI_REDIRECT_ROOT}/bin
2) created the following workers.properties.minimal file and placed it into {ISAPI_REDIRECT_ROOT}/conf:
# workers.properties.minimal -
#
# This file provides minimal jk configuration properties needed to
# connect to Tomcat.
#
#
# Defining a worker named ajp13w and of type ajp13
# Note that the name and the type do not have to match.
#
worker.ajp13w.type=ajp13
worker.ajp13w.host=localhost
worker.ajp13w.port=8009
#
# The workers that jk should create and work with
#
worker.list=ajp13w
#
# Define status worker
#
worker.jkstatus.type=status
3) I created the following uriworkermap.properties and placed it also into {ISAPI_REDIRECT_ROOT}/conf:
# uriworkermap.properties - IIS
#
# This file provides sample mappings for example wlb
# worker defined in workermap.properties.minimal
# The general syntax for this file is:
# [URL]=[Worker name]
# Mount the Servlet context to the ajp13 worker
/jira=ajp13w
/jira/*=ajp13w
4) I created the following isapi_redirect.properties file which I placed into the {ISAPI_REDIRECT_ROOT}/bin directory alongside the isapi_redirect.dll:
# Configuration file for the Jakarta ISAPI Redirector
# The path to the ISAPI Redirector Extension, relative to the website
# This must be in a virtual directory with execute privileges
extension_uri=/jakarta/isapi_redirect.dll
# Full path to the log file for the ISAPI Redirector
log_file=C:\JBoss\jboss-4.2.0.GA\isapi_redirect-1.2.x\log\isapi_redirect.log
# Log level (debug, info, warn, error or trace)
log_level=info
# Full path to the workers.properties file
worker_file=C:\JBoss\jboss-4.2.0.GA\isapi_redirect-1.2.x\conf\workers.properties.minimal
# Full path to the uriworkermap.properties file
worker_mount_file=C:\JBoss\jboss-4.2.0.GA\isapi_redirect-1.2.x\conf\uriworkermap.properties
5) I added the isapi filter to the default web site, naming it Tomcat and providing the {ISAPI_REDIRECT_ROOT}/bin as its path.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092783#4092783
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092783
18Â years, 7Â months
[JBoss Tools (users)] - Ambiguous error with web.xml adding JSF
by GeoffHart
I'm wondering if there is some reason the error below is reported like this; or if I should file a feature request to get something more specific reported instead?
--
Wizard for adding JSF capabilities to a project can report a misleading error message for web.xml files that makes it hard for users to correct the issue. The error could be made much clearer (example follows). You get here by right-clicking on a project and selecting Red Hat Developer Studio -> Add JSF Capabilities....; it is the first window that appears.
Consider a project with an existing (and working) web-xml file which is considered INVALID by the JSF wizard:
<?xml version="1.0" encoding="UTF-8"?>
|
| <!DOCTYPE web-app
| PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
| "http://java.sun.com/dtd/web-app_2_2.dtd">
| <web-app>
| <servlet>
| <servlet-name>DummyServlet</servlet-name>
| <servlet-class>dummy.class</servlet-class>
| </servlet>
| <servlet-mapping>
| <servlet-name>DummyServlet</servlet-name>
| <url-pattern>myWebPage</url-pattern>
| </servlet-mapping>
| </web-app>
1.0.0 Beta2 reports the following error:
"Web descriptor file is corrupted : Element type "web-app" must be declared.:6:10."
The problem appears to be related to the doc-type/DTD field, and if I change the version to 2.3, it accepts the web.xml file:
<!DOCTYPE web-app
| PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
| "http://java.sun.com/dtd/web-app_2_3.dtd">
If the error said the DOCTYPE was invalid (and why) rather than web-app was missing, it would be a lot more helpful to track down errors.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092780#4092780
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092780
18Â years, 7Â months