Hi Dims,
I've been working on the Beehive WSM components that integrate with
AXIS. While I may have been a bit too quiet while working on this, I
did submit a patch in late August so the JavaCompiler could compile
annotated .jws files which was important to have in place before the
release.
I ha
Hi all:
Now that we have a distribution, we need some way to get docs into it.
The easiest way to do this before ApacheCon, is to inject the HTML web site
(trunk\site\build\site\index.html) into the dist. Any objections, concerns
about this? Or better ideas?
-Steve Hanson
Hi dims,
Can you elaborate more on your concerns -- I'm not sure I understand
your email. We've been talking about problems/work-arounds we had with
Axis (on both the axis and the beehive mailing lists) as far as I
remember and I had the impression that the cooperation was quite good.
Cheers,
-m
Kyle,
Am sure Ias is NOT complaining about that specific article not talking
about Axis. He is wondering IF a similar effort needs to be done for
Axis and how useful it could be for both WSM and Axis.
Am personally SPECIFICALLY bothered that there is no emails on either
Axis dev or users from any
Glad the idea appeals to you. There is much work yet to be done in this
area. We're having some difficulty working out an ontology for
representing metadata. To date, OWL is presenting the most likely path
(OWL-DL in particular). For now, the metadata would represent specific
characteristics of the
This is an interesting idea. Currently, there's never a control that's
wholly responsible for rendering a piece of UI (at least that's not the
typical pattern). Often there's a control involved upstream in
providing data to back the UI, but in the end the NetUI tags in a JSP
are the final wor
+1
Daryl Olander wrote:
+1
On Tue, 19 Oct 2004 18:54:36 -0600, Richard Feit <[EMAIL PROTECTED]> wrote:
+1 on the branch. Same issue -- I'll want to start working on
(potentially destabilizing) features before ApacheCon.
Rich
Kyle Marvin wrote:
+1 to doing a branch, and I'd vote for early next
+1
On Tue, 19 Oct 2004 18:54:36 -0600, Richard Feit <[EMAIL PROTECTED]> wrote:
> +1 on the branch. Same issue -- I'll want to start working on
> (potentially destabilizing) features before ApacheCon.
> Rich
>
>
>
> Kyle Marvin wrote:
>
> >+1 to doing a branch, and I'd vote for early next wee
The following issue has been updated:
Updater: Eddie O'Neil (mailto:[EMAIL PROTECTED])
Date: Wed, 20 Oct 2004 7:59 AM
Comment:
Fixing the affected version to be TBD.
Changes:
Version changed to TBD
Version changed from Version 1
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/BEEHIVE-22
Here is an overview of the issue:
-
Hi Ias,
I understand what you are saying, but just as we should really avoid discussing
BEA-specific technologies or downstream use cases of Beehive here, you also
have to expect that this is exactly the type of content that is going to be
found on a BEA developer's web site. I'd be equally in
I've read "Introduction to Web Services Metadata" at
http://dev2dev.bea.com/technologies/webservices/articles/Anil_WServices.jsp?
PC=04-AA19-GEN99 and found that it would be (more) practical if it
demonstrated how to use WSM with Beehive WSM and Axis.
Regards,
Ias
Hi Mridul,
This work was done fairly recently, and hasn't been reflected in any of the
programming model docs. The answer is sort of "it depends".
For the set of control containers bundled within Beehive, the generated client
initializer class is automatically invoked to initialize nested con
Hi,
Is there any documentation on how to use declarative programming while
using controls ?
In the tests , I see that they invoke
'class'ClientInitializer.initialize() while using declarative mode - is
there any documentation on this ?
Thanks and Regards
Mridul
--
Java Navigator will have a lo
All--
Below is the change log for the initial checkin of a Beehive
petstore-style application.
Tomorrow, I'll add a TODO list and additional comments on building /
deploying / running.
In the meantime, here's a primer. It's currently set-up to run
against a dev build; to do this, start
That's an excellent improvement -- thanks!
Eddie O'Neil wrote:
All--
In an effort to simplify the way the NetUI build infrastructure
works, I'm going to reorganize the files under
$BEEHIVE_HOME/netui/src/webapp-template. These files are the ones
that makeup the non-runtime bits of the NetUI w
+1 on the branch. Same issue -- I'll want to start working on
(potentially destabilizing) features before ApacheCon.
Rich
Kyle Marvin wrote:
+1 to doing a branch, and I'd vote for early next week.
I'm working some proposals for a Controls roadmap and other planning-related
activities this week
17 matches
Mail list logo
