I've crawled through the logs, and all the build/test runs are successful.
This appears to be an issue with TCH. Both
http://beehive01.bea.com/downloads/20050606221541/general/build.out and
http://beehive01.bea.com/downloads/20050606221541/general/test.dist.out
show the following error in
[
http://issues.apache.org/jira/browse/BEEHIVE-794?page=comments#action_12312849
]
V.Gnanasegaran commented on BEEHIVE-794:
I am very sorry to say that it is my fault in setting up tomcat to encode jsp
pages using utf-8. Could you pleace remove
[ http://issues.apache.org/jira/browse/BEEHIVE-794?page=all ]
Eddie O'Neil closed BEEHIVE-794:
Closing as per last comment.
Character encoding in jsps
--
Key: BEEHIVE-794
URL:
[ http://issues.apache.org/jira/browse/BEEHIVE-794?page=all ]
Eddie O'Neil resolved BEEHIVE-794:
--
Resolution: Invalid
No problem at all -- glad everything worked! And, thanks for letting us know.
Character encoding in jsps
I'm guessing that this happened because of the website update
yesterday. It appears that the controls test infrastructure is
relying on the presence of a DTD here:
http://incubator.apache.org/beehive/dtd/gtlf/gtlf-config-2.0.dtd
and that this file no longer exists at this URL. I've put it
I think this is a sound plan. It allows us to keep momentum and gets
good bits to people early and often.
+1
Steve
-Original Message-
From: Eddie ONeil [mailto:[EMAIL PROTECTED]
Sent: Monday, June 06, 2005 5:30 PM
To: Beehive Developers
Subject: planning for future beehive releases
The new website just went live, so we'll see if CC passes next time.
On 6/7/05, Eddie ONeil [EMAIL PROTECTED] wrote:
I'm guessing that this happened because of the website update
yesterday. It appears that the controls test infrastructure is
relying on the presence of a DTD here:
[ http://issues.apache.org/jira/browse/BEEHIVE-774?page=all ]
Krista Baker closed BEEHIVE-774:
Verified in v1m1 that the sample instructions for petstore, netui-samples,
netui-jsf, wsm-address books all include Steve's notes about needing to change
All--
I've been taking a look through the WSM code in the last few days
and suggest that we fix a few issues that exist in the code base which
are listed below.
If anyone disagrees with any of this work / wants to help (which
would be great!), let me know and we'll address / coordinate.
View results here -
http://beehive01.bea.com/cruisecontrol/buildresults?log=log20050607091329LBUILD.574
I'll give the base plan a +1...
I think we should continue to produce a WSM/Service control
distribution, that will roll into a real release of Beehive once the
TCK is final...
On 6/7/05, Steven Tocco [EMAIL PROTECTED] wrote:
I think this is a sound plan. It allows us to keep momentum and gets
[ http://issues.apache.org/jira/browse/BEEHIVE-615?page=all ]
Krista Baker closed BEEHIVE-615:
Verified in v1m1 that a ConfigUtil.isInit method and checking have been added.
Also verified that the bvt/attached example is passing.
Static _config
[ http://issues.apache.org/jira/browse/BEEHIVE-797?page=all ]
Rich Feit updated BEEHIVE-797:
--
Summary: query strings not being restored when injecting nested page flows
using action interceptors (was: query strings not being restored when using
nested
[ http://issues.apache.org/jira/browse/BEEHIVE-739?page=all ]
Rich Feit resolved BEEHIVE-739:
---
Resolution: Fixed
Assign To: Alejandro Ramirez (was: Rich Feit)
Applied the patch with revision 188831. Thanks Carlin!
A url template ref without
I was looking at the webservice system-control's suite of tests and
noticed that there is only minimal code/feature coverage. I thought
I'd spend some time adding additional tests to try to get more
complete code/feature coverage for this control.
I was thinking of adding a bunch of new
[ http://issues.apache.org/jira/browse/BEEHIVE-797?page=all ]
Rich Feit resolved BEEHIVE-797:
---
Resolution: Fixed
Assign To: Alejandro Ramirez (was: Rich Feit)
Fixed with revision 188830.
Info for verifying this fix: There's an
[ http://issues.apache.org/jira/browse/BEEHIVE-265?page=all ]
Krista Baker closed BEEHIVE-265:
Unable to reproduce the IllegalStateException while using custom module config
locators. The associated bvt is also passing. Verified on v1m1rc2.
[ http://issues.apache.org/jira/browse/BEEHIVE-779?page=all ]
Rich Feit resolved BEEHIVE-779:
---
Resolution: Fixed
Applied the patch with revision 188851. Thanks!
ScopedRequestImpl.restoreAttributes() should not point the
ScopedAttributeContainer
[
http://issues.apache.org/jira/browse/BEEHIVE-717?page=comments#action_12312937
]
daryoush mehrtash commented on BEEHIVE-717:
---
Daryoush -- Hey; thanks for the patch! A couple of comments:
- the AxisFaultAdaptor seems to be missing the ASF
It looks to me like Struts is using the default rules for Checkstyle.
Here is the Struts Checkstyle task in build.xml:
target name=checkstyle if=checkstyle.jar
description=Checks source code against Sun coding
guidelines
depends=init
taskdef name=checkstyle
[
http://issues.apache.org/jira/browse/BEEHIVE-717?page=comments#action_12312940
]
Eddie O'Neil commented on BEEHIVE-717:
--
Daryoush--
Gotcha -- one question I have is about whether the ControlProvider would ever
throw an AxisFault and if it did why
[ http://issues.apache.org/jira/browse/BEEHIVE-597?page=all ]
Nathan Jantz closed BEEHIVE-597:
Assign To: Nathan Jantz (was: daryoush mehrtash)
Verified in 1.0m1 distribution that the build.properties file has been moved
from wsm-blank/WEB-INF to
Daryoush--
Another thought occurred to me regarding the AxisFault fix in JIRA
717 -- for the beginning of the discussion, see here:
http://issues.apache.org/jira/browse/BEEHIVE-717
Instead of creating a new AxisFaultAdapter, could we just call the
AxisFault.makeFault(Exception) method which
[ http://issues.apache.org/jira/browse/BEEHIVE-717?page=all ]
daryoush mehrtash updated BEEHIVE-717:
--
Attachment: faultpatch.txt
updated patch for the fixed to this bug.
minor non-conformance of exceptions to JSR-181 / JAX-RPC 1.1
No. If the default AxisFault would have worked we would not have had
the serialization issue. Please read my comments in JIRA/code.
Daryoush
-Original Message-
From: Eddie ONeil [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 07, 2005 3:39 PM
To: Beehive Developers
Subject:
Right, so, just to be clear then, AxisFaultAdapter is intended to
work around the serialization problem with faults in Axis.
Correct?
Daryoush Mehrtash wrote:
No. If the default AxisFault would have worked we would not have had
the serialization issue. Please read my comments in
The bug in the JIRA is for Axis to properly serialized AxisFaults, that
is the AxisFualts that Axis would generate if you do wsdl2Java or if you
write your own AxisFaults.
Until AxisFault serialization is fixed, you would not be able to throw
an AxisFault subclass from your JWS and except a
OK, are we ready to delve into this? I'm all for it, and I'm hoping we
can come to agreement. I propose that we take the Sun conventions as a
starting point, with the mods Jeremiah suggested. This isn't an
official vote... just wondering how people feel about the following:
1) Do we
Hi all,
Q: Now that our first (milestone) release is out, what should future
Release Notes contain?
- high-level description of new features
- bugs/issues addressed in the release
- known issues
?
If by this you mean to deal with a user defined exception, I attached
the AxisFaultAdaptor for you to look at.
The AxisFaultAdaptor expects the Exception to have been registered with
type mapping; which we do in the WSM and it uses that and the correct
(based on the WSDL definition) element to
Great!Would the AxisFaultAdaptor code that I attached be enough or
do you need more from us in terms of a patch?
daryoush
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 07, 2005 7:14 PM
To: Daryoush Mehrtash
Cc: Beehive Developers
Patch please.
On 6/7/05, Daryoush Mehrtash [EMAIL PROTECTED] wrote:
Great!Would the AxisFaultAdaptor code that I attached be enough or
do you need more from us in terms of a patch?
daryoush
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent:
I'm not voting for this, but there is a few additions:
[4] I think we tend to have line lengths of greater than 80, I think
something like 100 or 120 is reasonable.
[6.3] I agree that we should allow declaration before use and not
require them to be defined at the top of blocks.
[9] We name
We needed this yesterday :)
Service control performs two main functions. Generates JCX based on
WSDL, and use the WSDL and JCX interface to communicate with the
service.
I think the first test in service control should cover the JCX
generation.The idea is that if the JCX that the service
I wouldn't mind checkstyle and coding conventions.
#1 - I'm not exactly sure what you me by 'enforce' - if a class comes
up with checkstyle errors could you still commit it or would the
commit be blocked until the errors were resolved?
I'm not sure if blocking would be possible with checkstyle
Seems that it should contain all of these. At the very least, bugs
/ issues addressed in the release and known issues should go into some
sort of release note (IMHO). Not sure how new features should be
described -- I'd be fine with those being addressed in the same
location under some sort of
One thing I would add, is a release description. This would describe
the overall goals of the release (feature work, bug fix work, etc).
In addition, it would be nice if each release had a bit of a road map
for the expectations and time frame is for the next release in the
line. In addition, if
I can mostly live with what has been proposed so far and agree with
Daryl about curly braces / line breaks and such. The one thing I
can't do is this:
if ( i == 4 ) {
...
}
All the extraneous spaces just drive me nuts. :)
We also need to allow for the use of _ as a prefix to
Yeah, definitely agree with that. Something like this:
http://incubator.apache.org/derby/releases/release-10.0.2.1.html
On 6/7/05, Daryl Olander [EMAIL PROTECTED] wrote:
One thing I would add, is a release description. This would describe
the overall goals of the release (feature
All--
After having worked on the Beehive website some in the last couple
of days, I've got a couple of suggestions for how we can make this
process significantly easier. The approach has two parts... The
first is the most (immediately) important.
1) check the generated website into
Totally. That's a great template for us. Should we just add this stuff
to the known issues (#3.2) of our release criteria
(http://wiki.apache.org/beehive/V1ReleaseCriteria )?
Eddie ONeil wrote:
Yeah, definitely agree with that. Something like this:
(I've pasted in Daryl's reply below, just so we're all in the same thread.)
For full disclosure, I really dislike braces on the same line (as
opposed to braces on newlines). But unless there's a groundswell in
favor of changing it, we have Sun, Daryl and Eddie all arguing for it.
So I'll
Sure, that seems like a good starting point. We'll also need to put
together something that will help automate the generation of this
report; I'd rather not do it by hand.
:)
On 6/7/05, Richard Feit [EMAIL PROTECTED] wrote:
Totally. That's a great template for us. Should we just add
On naming interfaces with I -- I'd like to see us adopt this as a
convention going forward -- we definitely have an issue on older
interfaces.
Would also like to see us standardize on some naming conventions for
things Adapter vs. Adaptor so that we're not divergent across
Beehive
OK, *finally* I get to use the Sun guidelines on my side! :) I'm
really not in favor of using the I prefix -- I don't think it's
necessary or particularly helpful. But I'd even go with that if others
-- committers and other community members -- feel strongly about it.
Can others chime in?
+1 to both -- I totally agree with this.
Rich
Eddie ONeil wrote:
All--
After having worked on the Beehive website some in the last couple
of days, I've got a couple of suggestions for how we can make this
process significantly easier. The approach has two parts... The
first is the most
In addition to the extra info, I changed the Release Criteria page to
say that the release notes are gating, and that they should be included
in the dist (not just on the website). If anyone disagrees, shout.
Rich
Richard Feit wrote:
Definitely. I'll add the item to the release criteria,
47 matches
Mail list logo
