The message:
Trying to install an already registered mbean:
jboss.ws:service=WebServiceClientDeployer
indicates that you have managed to get two instances of the
webserviceclientdeployer bean in your deployment directory.
you should ensure that when you deploy the new sar that it is going over
Heitor,
The message "Trying to install an already registered mbean" is telling me
that you managed to get two copies of one of the jars in your lib directory.
Double check that all of the files you installed when over the top of the
files they should have.
Steve
View the original post
"tobinibot" wrote : Couple more details. I'm working with 2 other guys on a
project. I wrote a basic web service and deploying on my machine. All 3 of us
can successfully hit my web service.
|
| I then checked the web service into source control, and had the other 2
guys check it out. O
"sklerche" wrote : Hi Steve
|
| I've just started Jboss with jdk 5.0, recompiled my bean accordingly and
guess what, everything worked fine!
|
| I thought jboss should work with all jdk's >= 5.0.
|
| Anyhow thanks a million!
| Stephan
It probably should work on 1.6, but then agai
Hi Craig,
Your web services are failing because collections are not supported by
jax-rpc. (if you search on this forum you can find out more details).
The short of it is you will have to change your collections to arrays.
Steve.
View the original post :
http://www.jboss.com/index.html?m
Hi sklerche,
Not sure exactly whats going on but are you able to try it with jdk 1.5?
Steve
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990831#3990831
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990831
actually you wont be able to move the soap messages to the info level as such.
You will need to set the level on your appender to debug and use categories to
filter out what you dont want.
http://docs.jboss.org/process-guide/en/html/logging.html
Also do you really want your soap messages goi
This is a known issue although looking at the job it is yet to be fixed.
http://jira.jboss.org/jira/browse/JBWS-800
The work around is to pass a java.util.date ( not any of the sub classes).
Steve.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989073#398
ummm the connection timed out exeception usually means you are trying to
connect a port on a machine that is not open...
For example if your server is running on port 80 and your web service is trying
to connect to port 8080. you will get this error.
There are so many different reasons that
you might have grabbed some old documentation. the actual port configurations
for the new ones are in the jbossws.sar\jbossws.beans. you will need to unzip
and rezip
see.
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=84965
Steve.
View the original post :
http://www.jboss.com/i
It looks like you managed to miss when you did the 1.0.3 install.
From the error trace you have deployed the jbossws component to the deploy
directory rather than the deploy/jbossws.sar directory.
Ie the error you have is caused by the app server loading the
deploy/jbossws.sar/META-INF/jboss-
Hi ncapito,
It is not clear what was processing at 250,000/second. but i would assume
that there shouldn't be any changes in the response time of the jboss server
because of the type of client, or at least nothing of any significance (maybe
slight differences in the structure of the soap mes
Actually it looks more like a mapping problem.. the soap message has a request
for the getKey operation, and the container doesnt know which method on which
class to invoke.
Steve
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971149#3971149
Reply to the p
Hi Thomas,
I can accept that wsdl generation only works for trivial use cases. The actual
problem is how unpredictable the existing code generation is.
My 3rd post in this thread show how changing a method name by one character can
cause different wsdls. I would not have expected any changes
"jpremji" wrote : I am having the same issue. It would seem that even after
specifying the target namespace, the wsdl that is generated contains 2 complex
elements of the same java type. This then causes confusion to the client when
calling the method that would return or accept this type.
I h
"jiwils" wrote :
|
| I have no problem writing test cases, etc. I would even look into
submitting a patch of some sort, but building the source has too many
dependancies (having to pull JBossAS and build it for example) for this to seem
feasible. If we had a source zip/release, that woul
not sure about 1) probably go back over
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=89058
and make sure you havnt missed something.
as for 2) these are server configurations see
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=89058
View the original post :
http://www.jb
Hi Eric,
see
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=89277
the jboss-bean.xml also contains a webservicehost param.
Steve.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968822#3968822
Reply to the post :
http://www.jboss.com/index.ht
Yep it usually is as simple as copying your war to a spot on the file system,
if you are using the default server the path is
%jboss_home%\server\default\deploy and if everything is sweet it should just
deploy.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewt
Zohar,
I set up an instance of the ejb you posted, a few minor tweaks with target
namespace and operation name so the generated wsdl would match the one you
posted, and sent the request you posted to my web service using xmlspy and it
worked fine.
I am running jbossws 1.0.2GA, but i wouldn
Hi Zohar,
You have posted the reply from the server, but do you have the original soap
message from teh client to the server.
I have a feeling that the server is not understanding the request that your
client is providing, ie potentially the wrong name spaces etc. I had a similar
probl
Hi Zohar,
Did you have copies of the generated wsdl and the soap message being sent to
the server.
Steve.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967715#3967715
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply
There is already plans to have the file unziped to make it easier to update.
http://jira.jboss.com/jira/browse/JBWS-1007
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967379#3967379
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting
The listening port is controled in the deploy/jbossweb-tomcat55.sar\server.xml.
the ports in the wsdl are controlled by the deploy/jbossws.sar/jbossws.beans
which you will have to unzip.
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=84965
View the original post :
http://www.jboss.
I remember reading somewhere that .net likes methods that start with
capitals... it might be a convention or otherwise. Try setting the operation
name on you webmethod annotation to include operationName="Test1".
No claims that this will work but give it a try.
Steve.
View the original post
Sorry i forgot to mention i am running 4.0.4GA with jbossws 1.0.2GA.
Steve
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967146#3967146
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967146
__
Alright i have been having a bit of a play with my classes as one of my web
services was behaving in what can only be described as an interesting maner.
I am looking at the generated wsdl from my soap class and it works fine as per
the listing below. but if i change the method name of getResult
"stevenh" wrote :
|
| As for your web service the controls for changinging ports in your wsdl is
done in two parts. the uriScheme (the https bit) is controlled from the wsdl,
ie if the url in the wsdl starts with "https" it will update the wsdl with a
url including
Heiko,
It sounds like you are talking about the ssl connector rather than the web
service port, so ill float what i know and you can pick and choose.
The actual ssl connector is controlled by jbossweb-tomcat55.sar\server.xml. you
will have to enable ssl here before you can use the https.
Hi Ravi,
Its not really a limitation on the soap message rather than the limitations
on jax-rpc. The topic has been covered quite extensivly, see:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=84998
Which is where i probably should have pointed you in the first place, rather
th
Hi Ravi,
What heiko is trying to say is to use and array rather than the array list..
ie you will have to invoke the toArray method on your array list.
ie
public result[] getResults()
rather than
public Collection getResults()
Steve.
View the original post :
http://www.jboss.com/
I have been messing round with the wsdlLocation attribute on the WebService
annotation and this looks like it will give me the consistency that i was
after.
Steve.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3965607#3965607
Reply to the post :
http://w
I was just curious about the state of the "Start with WSDL and Java" (2.2.3)
for mapping the WSDL Directory to the Java class.
I have been having a few issues with the Start with Java and it generating
inconsistent WSDL's, (which ill post when i manage to pin down). And thought
that i do pref
Let me know if anyone has any luck doing this.
i have trawled the jsr181 and found nothing on attachments and i think jsr67 is
a little early for annotations, quick browse of the jcp web site and found
nothing newer than saaj-1.3.
View the original post :
http://www.jboss.com/index.html?modul
I had a similar issue, it probably is a bug, but the work around is to use an
interface on your user object and return the interface rather than the user
itself.
This hides the super class from the processes building the jaxrpc-mapping
allowing it to generate correctly...
View the original p
Try creating a interface for your Cabin object to implement.
public interface ICabin {
public int getId();
public void setId(int id);
public String getName();
public void setName();
}
Then have your travel agent return the ICabin rather than the Cabin. I had a
similar probl
36 matches
Mail list logo
