RE: Branch Code Freeze
by Magesh Kumar Bojan
Oops sorry. This task has already been done!
Thanks & Regards,
Magesh Kumar B
-----Original Message-----
From: Magesh Kumar Bojan
Sent: Wednesday, December 13, 2006 8:26 AM
To: Jason T. Greene; 'jbossws-dev(a)lists.jboss.org'
Cc: Darran Lofthouse; David Boeren
Subject: RE: Branch Code Freeze
I have a slightly different issue. I have a change present in
jbossws-1.0 related to jbossws-1.0.4.GA-JBWS-1379 that has not been
merged to trunk yet. I wanted to rewrite the solution before I update
into trunk. I will update it to trunk today if you have no issues.
Thanks & Regards,
Magesh Kumar B
-----Original Message-----
From: Jason T. Greene
Sent: Wednesday, December 13, 2006 7:02 AM
To: Jason T. Greene; 'jbossws-dev(a)lists.jboss.org'
Cc: Darran Lofthouse; Magesh Kumar Bojan; David Boeren
Subject: RE: Branch Code Freeze
Just in case someone misses this email, I have locked everyone out of
this branch. Contact me if something comes up.
> -----Original Message-----
> From: Jason T. Greene
> Sent: Tuesday, December 12, 2006 4:25 PM
> To: jbossws-dev(a)lists.jboss.org
> Cc: Darran Lofthouse; Magesh Kumar Bojan; David Boeren
> Subject: Branch Code Freeze
>
> This week I am merging trunk to the jbossws-1.0 branch, please avoid
> making changes to jbossws-1.0 if at all possible. If you need to make
> changes, please apply them to trunk.
>
> Otherwise, please contact me about your change first, so I can keep
from
> overwriting it.
>
> Thanks,
> -Jason
>
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Jason T. Greene
> Senior Software Engineer
> JBoss, a division of Red Hat
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 5 months
RE: Branch Code Freeze
by Magesh Kumar Bojan
I have a slightly different issue. I have a change present in
jbossws-1.0 related to jbossws-1.0.4.GA-JBWS-1379 that has not been
merged to trunk yet. I wanted to rewrite the solution before I update
into trunk. I will update it to trunk today if you have no issues.
Thanks & Regards,
Magesh Kumar B
-----Original Message-----
From: Jason T. Greene
Sent: Wednesday, December 13, 2006 7:02 AM
To: Jason T. Greene; 'jbossws-dev(a)lists.jboss.org'
Cc: Darran Lofthouse; Magesh Kumar Bojan; David Boeren
Subject: RE: Branch Code Freeze
Just in case someone misses this email, I have locked everyone out of
this branch. Contact me if something comes up.
> -----Original Message-----
> From: Jason T. Greene
> Sent: Tuesday, December 12, 2006 4:25 PM
> To: jbossws-dev(a)lists.jboss.org
> Cc: Darran Lofthouse; Magesh Kumar Bojan; David Boeren
> Subject: Branch Code Freeze
>
> This week I am merging trunk to the jbossws-1.0 branch, please avoid
> making changes to jbossws-1.0 if at all possible. If you need to make
> changes, please apply them to trunk.
>
> Otherwise, please contact me about your change first, so I can keep
from
> overwriting it.
>
> Thanks,
> -Jason
>
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Jason T. Greene
> Senior Software Engineer
> JBoss, a division of Red Hat
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 5 months
Branch Code Freeze
by Jason T. Greene
This week I am merging trunk to the jbossws-1.0 branch, please avoid
making changes to jbossws-1.0 if at all possible. If you need to make
changes, please apply them to trunk.
Otherwise, please contact me about your change first, so I can keep from
overwriting it.
Thanks,
-Jason
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Jason T. Greene
Senior Software Engineer
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 5 months
[Design of JBoss Web Services] - jbossWs document/literal
by tobake
Hi!
I trying to get this dummyMethod to work with document/literal
public class Test {
|
| @WebService(name="testWS", serviceName="TestService")
| @SOAPBinding(style=SOAPBinding.Style.DOCUMENT,
| use=SOAPBinding.Use.LITERAL,
| parameterStyle = SOAPBinding.ParameterStyle.BARE)
|
| @WebMethod
| public String dummyService(String input, String input2) {
| log.debug("dummyService was called");
| return "Okey I am here";
| }
| }
This did work when I only had one input parameter. But when testing with multiple inputs I get the following error when trying to deploy to jboss.
12:17:44,644 ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.0.5.GA/server/default/tmp/deploy/tmp14496icr3.ear-contents/icr3.war
org.jboss.ws.WSException: Attempt to map multiple operation inputs to: {http://webservice.icr3.com/jaws}dummyService
I have tried parameterStyle.WRAPPED and then it deploys but in that case it is giving me strange result when I try to consume the service with my .NET consumer application. I simply dont get the right input parameters in my proxy.
instead of looking like this :
proxy.dummyService(String input1, String input2)
it shows this :
proxy.dummyService(tester.jbossws.dummyService dummyService1)
Help is appriciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992730#3992730
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992730
17 years, 5 months
RE: Sam stuck again
by Thomas Diesler
Sam,
09:45:18,706 ERROR [JAXWSDeployerJSE] Cannot process web
deployment
java.lang.ClassNotFoundException: No ClassLoaders found for:
org.jboss.samples.HelloWorldWS
at
org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:306)
at
org.jboss.mx.loading.UnifiedClassLoader.loadClassImpl(UnifiedClassLoader.java:275)
at
org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:406)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
you war does not contain any classes. Honestly Sam, is this the level of
support you need?
Hot deployment in jboss-5.0 is not yet implemented, you need to deploy
through JMX (i.e. from a test) or restart the server.
Please keep the dev list in the loop. You'll get quicker responses that
way.
cheers
-thomas
On Sun, 2006-12-10 at 09:39 -0600, Sam Grifffith wrote:
> Thomas,
>
> I've enclosed my project again. It's just a simple hello-world but I
> can't figure out why it won't show up in the http://localhost:8080/
> jbossws view of the server.
>
> You'll need to change the extension to .zip from .zipper.
>
>
> Please take a look if you could.
>
> Thanks,
>
> Sam
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 5 months
Re: Reporting Training Hours
by Thomas Diesler
ok, done.
Could you plesae all verify that the spreadsheet shows correct
information for your training engagements?
cheers
-thomas
Darran Lofthouse wrote:
> Thomas,
>
> We have not had any solution for reporting the training hours. I would
> like to add another column to the spreadsheet so you can all enter your
> own hours for training.
>
> This will just be a temporary solution, about March next year we are
> going to be moving off Salesforce anyway so will have to revisit what
> data we can get from the new system.
>
> Regards,
> Darran Lofthouse.
>
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 6 months
RE: [jbossws-dev] Document/Wrapped can not be a message type
by Jason T. Greene
I take that back, they added support for mixing @SOAPBinding in
maintenance release of JSR-181. In this case, we need to move parameter
style to the operation level.
http://jira.jboss.com/jira/browse/JBWS-1416
Also, this is tested by the CTS:
http://jira.jboss.com/jira/browse/JBCTS-425
The message level test will still need to be removed though, because the
user is required to actually specify the binding type properly.
-Jason
________________________________
From: jbossws-dev-bounces(a)lists.jboss.org
[mailto:jbossws-dev-bounces@lists.jboss.org] On Behalf Of Jason T.
Greene
Sent: Thursday, December 07, 2006 7:03 PM
To: Thomas Diesler
Cc: jbossws-dev(a)lists.jboss.org
Subject: RE: [jbossws-dev] Document/Wrapped can not be a message type
You can't mix parameter styles in the same endpoint
________________________________
From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Thursday, December 07, 2006 4:49 PM
To: Jason T. Greene
Cc: jbossws-dev(a)lists.jboss.org
Subject: Re: [jbossws-dev] Document/Wrapped can not be a message type
http://jira.jboss.com/jira/browse/JBWS-1414
What about a SEI like this
MyService
{
public void foo(String one, String two);
public void bar(SOAPElement elmt);
}
Jason T. Greene wrote:
-----Original Message-----
From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Thursday, December 07, 2006 12:42 PM
To: Jason T. Greene
Cc: jbossws-dev(a)lists.jboss.org
Subject: Re: [jbossws-dev] Document/Wrapped can not be a message
type
This is saying:
if document/wrapped and the endpoint is not a SOAPElement
endpoint do
the wrapping.
There are occasions where a message type endpoint registers as
document/wrapped
We should fix this then. As I was saying, it's illegal for a wrapped
type to be a message style service. A message style service is simply a
bare service with a SOAPElement or DOM Element for a parameter.
I have created a jira issue for this:
http://jira.jboss.com/jira/browse/JBWS-1414
-Jason
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 6 months
RE: [jbossws-dev] Document/Wrapped can not be a message type
by Jason T. Greene
You can't mix parameter styles in the same endpoint
________________________________
From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Thursday, December 07, 2006 4:49 PM
To: Jason T. Greene
Cc: jbossws-dev(a)lists.jboss.org
Subject: Re: [jbossws-dev] Document/Wrapped can not be a message type
http://jira.jboss.com/jira/browse/JBWS-1414
What about a SEI like this
MyService
{
public void foo(String one, String two);
public void bar(SOAPElement elmt);
}
Jason T. Greene wrote:
-----Original Message-----
From: Thomas Diesler [mailto:thomas.diesler@redhat.com]
Sent: Thursday, December 07, 2006 12:42 PM
To: Jason T. Greene
Cc: jbossws-dev(a)lists.jboss.org
Subject: Re: [jbossws-dev] Document/Wrapped can not be a message
type
This is saying:
if document/wrapped and the endpoint is not a SOAPElement
endpoint do
the wrapping.
There are occasions where a message type endpoint registers as
document/wrapped
We should fix this then. As I was saying, it's illegal for a wrapped
type to be a message style service. A message style service is simply a
bare service with a SOAPElement or DOM Element for a parameter.
I have created a jira issue for this:
http://jira.jboss.com/jira/browse/JBWS-1414
-Jason
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 6 months
