Re: (JBWS-1617) JAXRPC doc/literal trims empty string
by Thomas Diesler
We have code freeze on Mon,20-Aug-2007
So now would be good ;-)
-thomas
On Tue, 2007-08-14 at 08:59 +0200, Alexey Loubyansky wrote:
> Let me know when you start preparing for a release and I'll release the
> XB for you.
>
> Alexey
>
> Thomas Diesler wrote:
> > Hi Alex,
> >
> > this is resolved using
> >
> > http://snapshots.jboss.org/maven2/org/jboss/jbossxb/1.0.0-SNAPSHOT/jbossx...
> >
> > what are your release plans? I would not like to ship an arbitrary
> > snapshot with jbossws-2.0.1.GA
> >
> > cheers
> > -thomas
> >
> > On Tue, 2007-06-26 at 16:47 +0200, Alexey Loubyansky wrote:
> >> Hi Thomas,
> >>
> >> you are right, I missed the marshalling part. Could you please try
> >> again? I've updated the snapshots.
> >>
> >> https://snapshots.jboss.org/maven2/org/jboss/jbossxb/1.0.0-SNAPSHOT/jboss...
> >> 0626.144333-2-sources.jar
> >>
> >> And th trunk the 2.0.0 too.
> >>
> >> I don't have the WS checked out and would really like to avoid checking
> >> it out if possible and keeping it simple: schema, xml, configuration.
> >>
> >> Let me know.
> >>
> >> Alexey
> >>
> >>
> >> Thomas Diesler wrote:
> >>> How to build and install the latest is covered in detail here
> >>>
> >>> http://jbws.dyndns.org/mediawiki/index.php/JBossWS_FAQs#How_can_I_build_a...
> >>>
> >>>
> >>>
> >>> On Mon, 2007-06-25 at 11:50 +0200, Thomas Diesler wrote:
> >>>> Hi Alex,
> >>>>
> >>>> on AS42 its not working for us
> >>>>
> >>>> http://jira.jboss.org/jira/browse/JBWS-1617#action_12366623
> >>>>
> >>>> you can easily run the test your self. It pulls its dependencies from
> >>>> AS. Hence you simple copy your snapshot to the AS client/lib and
> >>>> uncomment the FIXME
> >>>>
> >>>> cheers
> >>>> -thomas
> >>>>
> >>>>
> >>>> On Fri, 2007-06-22 at 23:44 +0200, Alexey Loubyansky wrote:
> >>>>> I read somewhere on the wiki that snapshots should go to the
> >>>>> snapshots.jboss.org. That's why...
> >>>>> And I'd like to make sure the issue is fixed before releasing something.
> >>>>>
> >>>>> Alexey
> >>>>>
> >>>>> Thomas Diesler wrote:
> >>>>>> Hi Alex,
> >>>>>>
> >>>>>> our QA depends on thirdparty artifacts from http://repository.jboss.com/
> >>>>>> Could you please release these jars there?
> >>>>>>
> >>>>>> cheers
> >>>>>> -thomas
> >>>>>>
> >>>>>> On Wed, 2007-06-20 at 12:09 +0200, Alexey Loubyansky wrote:
> >>>>>>> can try these snapshots?
> >>>>>>>
> >>>>>>> https://snapshots.jboss.org/maven2/org/jboss/jbossxb/2.0.0-SNAPSHOT/jboss...
> >>>>>>> https://snapshots.jboss.org/maven2/jboss/jbossxb/jbossxb/1.0.0-SNAPSHOT/j...
> >>>>>>>
> >>>>>>> 2.0.0 is for JBoss 5, 1.0.0 is for the Branch_4_2 and 4_0.
> >>>>>>>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
19 years, 1 month
Re: (JBWS-1617) JAXRPC doc/literal trims empty string
by Thomas Diesler
Hi Alex,
this is resolved using
http://snapshots.jboss.org/maven2/org/jboss/jbossxb/1.0.0-SNAPSHOT/jbossx...
what are your release plans? I would not like to ship an arbitrary
snapshot with jbossws-2.0.1.GA
cheers
-thomas
On Tue, 2007-06-26 at 16:47 +0200, Alexey Loubyansky wrote:
> Hi Thomas,
>
> you are right, I missed the marshalling part. Could you please try
> again? I've updated the snapshots.
>
> https://snapshots.jboss.org/maven2/org/jboss/jbossxb/1.0.0-SNAPSHOT/jboss...
> 0626.144333-2-sources.jar
>
> And th trunk the 2.0.0 too.
>
> I don't have the WS checked out and would really like to avoid checking
> it out if possible and keeping it simple: schema, xml, configuration.
>
> Let me know.
>
> Alexey
>
>
> Thomas Diesler wrote:
> > How to build and install the latest is covered in detail here
> >
> > http://jbws.dyndns.org/mediawiki/index.php/JBossWS_FAQs#How_can_I_build_a...
> >
> >
> >
> > On Mon, 2007-06-25 at 11:50 +0200, Thomas Diesler wrote:
> >> Hi Alex,
> >>
> >> on AS42 its not working for us
> >>
> >> http://jira.jboss.org/jira/browse/JBWS-1617#action_12366623
> >>
> >> you can easily run the test your self. It pulls its dependencies from
> >> AS. Hence you simple copy your snapshot to the AS client/lib and
> >> uncomment the FIXME
> >>
> >> cheers
> >> -thomas
> >>
> >>
> >> On Fri, 2007-06-22 at 23:44 +0200, Alexey Loubyansky wrote:
> >>> I read somewhere on the wiki that snapshots should go to the
> >>> snapshots.jboss.org. That's why...
> >>> And I'd like to make sure the issue is fixed before releasing something.
> >>>
> >>> Alexey
> >>>
> >>> Thomas Diesler wrote:
> >>>> Hi Alex,
> >>>>
> >>>> our QA depends on thirdparty artifacts from http://repository.jboss.com/
> >>>> Could you please release these jars there?
> >>>>
> >>>> cheers
> >>>> -thomas
> >>>>
> >>>> On Wed, 2007-06-20 at 12:09 +0200, Alexey Loubyansky wrote:
> >>>>> can try these snapshots?
> >>>>>
> >>>>> https://snapshots.jboss.org/maven2/org/jboss/jbossxb/2.0.0-SNAPSHOT/jboss...
> >>>>> https://snapshots.jboss.org/maven2/jboss/jbossxb/jbossxb/1.0.0-SNAPSHOT/j...
> >>>>>
> >>>>> 2.0.0 is for JBoss 5, 1.0.0 is for the Branch_4_2 and 4_0.
> >>>>>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
19 years, 1 month
[Design of JBoss Web Services] - Invocation exception handling
by palin
Hi all,
on jira we currently have an issue about invocation exception handling with the metro stack http://jira.jboss.com/jira/browse/JBWS-1670.
Basically the problem is caused by the handleInvocationException method of the abstract class org.jboss.wsf.spi.invocation.InvocationHandler that unwraps the throwable raised by the service endpoint implementation:
if (th instanceof InvocationTargetException)
| {
| // Unwrap the throwable raised by the service endpoint implementation
| Throwable targetEx = ((InvocationTargetException)th).getTargetException();
| handleInvocationException(targetEx);
| }
|
This is correct for the native stack, but causes the Metro stack integration to fail whenever a custom user exception is thrown, since the unwrapping process is perfomed twice (both by metro and jbossws code above).
This drove me to think that the InvocationHandler might delegate the exception handling process to an InvocationExceptionHandler which is going to be different for each stack (for now, the native one would unwrap InvocationExceptions, the metro one would not).
The EndpointHandlerDeploymentAspect could set the right InvocationExceptionHandler (according to the jbossws-xxx-config.xml) into every InvocationHandler (regardless of its type, the container we are running on, etc).
Any opinion about this?
Bye
Alessio Soldano
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073647#4073647
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073647
19 years, 1 month
Hudson for the 2.0 branch?
by Darran Lofthouse
Is there a Hudson build for the JBossWS 2.0 branch?
I am getting a lot of failures locally and want to see if this is
something specific to my machine or of it is a general issue but I can
only find Hudson for trunk.
--
Regards,
Darran Lofthouse.
Senior Software Maintenance Engineer
JBoss, a division of Red Hat
19 years, 1 month
