Too much faith in received materials. Schema and wsdl had different contents.
Once corrected, it ran perfectly
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4153231#4153231
Reply to the post :
I forgot to mention, that I also received a WSDL for the service, and this was
the one I used with wsconsume
Lasse Petersen
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4153153#4153153
Reply to the post :
I am working on a webservice for a customer that will deliver
patient data to a government office. I have received a complete set of schema
files (lots of 'include schemaLocation') and a test xml.I have used Altova to
verify that the text xml file indeed conforms to the schema files.
My plan
The service deploy-hasingleton.service does exactly what we want, and since
your first proposal does not offer this, we decided to try out your second
proposal: removing avalon from jboss/lib and remove iiop_service.xml from
deploy directory.
This has so far been working. Jboss as well as the
and the message in the log about 'Only the root deployment..,' that can be
ignored is invalid in this situation
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4134755#4134755
Reply to the post :
The application is a war file and reads EDI files and applies these as updates
to the database. There are few html pages where you can 'take the temperature'
of the application, and it is on these pages that the error occurrs.
One difference between Jboss 3.2.2 and jboss 4.2.1 is the use of
Thanks for the suggestion
I have done as you and the doc described and the application starts nicely up
and no error occurred. But the real test comes when I deploy it into the
cluster next week. I will get back with the result
Lasse Petersen
View the original post :
I am currently involved in a migration of web applications from single Jboss
3.2.2 to Jboss 4.2.1 cluster version. I need to deploy an application as a
singleton, so I want to deploy it to deploy-hasingleton directory in the all
configuration. When the application is deployed in deploy
