Web Services Jira Notifications
by Darran Lofthouse
Are there any known issues with the 'jbossws-issues' mailing list? It
looks like the last Jira notification to be sent to the list was the 8th
February.
Regards,
Darran Lofthouse.
17 years, 1 month
Re: WS 1.2.1DEV -> 1.2.1GA
by Thomas Diesler
Patrick,
no, the set of libraries is stable. 1.2.1.GA is waiting for Alejandr to
provide a compatible wsbpel release.
Alejandro, when do you think this will be done?
http://jira.jboss.org/jira/browse/JBWS-1602
cheers
-thomas
On Thu, 2007-04-05 at 16:20 -0400, Patrick Macdonald wrote:
> Thomas,
>
> We're in the home stretch of getting Application Platform to Beta.
> To that end, can you please inform me if any new libraries will be
> added or updated [revision wise] in the update from 1.2.1DEV to
> 1.2.1GA?
>
> Cheers,
> Patrick
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 1 month
wsbpel not compatible with wsdl4j-1.6.2
by Thomas Diesler
Hi Alejandro,
http://jira.jboss.org/jira/browse/JBWS-1602
we finally had to update wsdl4j. That causes issues with all (old)
implementors of WSDLLocator such that the
public void close()
is required to be implemented. The method does not actually have to do
anything yet.
Could you please release an updated version that supports the new API?
Branching from you last stable release would be possible for this
trivial change.
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 2 months
Re: JBWS-1515 and information
by Thomas Diesler
Ok, this reading. How is the cookie supposed to get set on the server
side?
Our test case shows that a client handler can read the cookie when a
server handler actually sets one.
We did an optimization where the server component does not create a new
HttpSession for every request, because this is an expensive operation.
Hence, when the server component does not access the HttpSession and no
other component expicitly sets a cookie there will be no cookie for the
client to read.
cheers
-thomas
On Wed, 2007-04-04 at 09:23 -0400, Chris Laprun wrote:
> On Apr 4, 2007, at 3:28 AM, Thomas Diesler wrote:
>
> > please study the testcase associated with the the jira issue. It shows
> > how to work with cookies.
>
> I did. Here's a code sample that I use in my handler:
>
> public boolean handleResponse(MessageContext msgContext)
> {
> SOAPMessageContext smc = (SOAPMessageContext)msgContext;
> SOAPMessage message = smc.getMessage();
> MimeHeaders mimeHeaders = message.getMimeHeaders();
> String[] cookieValues = mimeHeaders.getHeader("Set-Cookie");
>
> if (cookieValues != null)
> {
> // deal with cookies...
> }
>
> return super.handleResponse(msgContext);
> }
>
> The problem is that with 1.0.4.GA and up, the Set-Cookie header is
> not present anymore. My code works fine with 1.0.3.sp1 and below and
> when I step debug it, I can see the Set-Cookie header present in the
> MimeHeaders. With 1.0.4.GA and above (that includes 1.2.1 that I
> compiled yesterday), the Set-Cookie header is not present anymore
> when I step debug the code. I looked at the test case configuration
> to see if I was missing anything but it doesn't look like it
> either... so I'm not quite sure what's going on.
>
> Best,
> Chris
>
> ==
> JBoss Portal Developer / WSRP Lead
> JBoss, a division of Red Hat
>
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 2 months
Status & Direction
by Thomas Diesler
Folks,
looking at the remaining issues in jbossws.jtx we only have very few
areas left to work on.
Here is my suggestion of how we split up the work, such that we don't
step on eachothers feet
#1 jaxrpc: xsd:Date interop (Alexey)
#2 jaxws: HttpBinding (Thomas)
#3 saaj: AttachmentPart (Heiko)
#4 saaj: RestrictionsAllowable (Alejandro)
#5 webservices: HandlerSec + various (Jason)
#6 webservices12: various (Heiko)
I will be branching the codebase for the http binding work since I
expect this to affect many areas over the next few days.
Our QA environment is setup such that every moring at 6am CET a clean
version of JBossAS is build, which triggers the AS webservice testsuite
http://jbws.dyndns.org:8180/hudson/job/AS-5.0/
http://jbws.dyndns.org:8180/hudson/job/JBAS-Tests-AS-5.0/
Every 10min we poll the SVN repository for changes in jbossws/trunk
This is then run against the latest AS build
http://jbws.dyndns.org:8180/hudson/view/JBossWS%
20Testsuite/job/JBWS-Tests-AS-5.0/
You should expect to receive email notifications for unstable builds.
Heiko, will provide us with daily results from CTS runs. This should
allow us to detect/address regression quickly.
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
17 years, 2 months
