I see -- yes, I'd be shocked if v1.0 wasn't out by then. :) Kyle
basically kicked off the process a few weeks ago (see his "Heading
towards a Beehive 1.0 release" email to this list), and it feels like
everyone's cranking hard enough on bugs to get this out well before that.
Rich
[EMAIL PROTECTED] wrote:
The book is scheduled for August. Do you think 1.0 will be out by then? I
would love to chat more about the book if/when u have time.
Give me a holler..(310) 562-5050
Kunal Mittal
IT - Television
Sony Pictures Entertainment
Cell: (310) 562-5050
Richard Feit <[EMAIL PROTECTED]>
04/24/2005 03:09 PM
Please respond to
"Beehive Developers" <[email protected]>
To
Beehive Developers <[email protected]>
cc
Subject
Re: Beehive in Portal Environment.
Hi Kunal,
I'd actually recommend getting in touch with someone who works on
WebLogic Portal -- I've talked to people from that group who are
testing/integrating Beehive, but since the product hasn't been released
yet, this sort of testing is not really something any Beehive developer
can do.
Out of curiosity, when's the planned release date for your book?
Thanks,
Rich
[EMAIL PROTECTED] wrote:
Hi Rich -
Has anyone tested Beehive on BEA Portal? If not, I would be happy to try
this out for you guys. Srini and me are writing a book on Apache Beehive
and want to include a chapter on how Beehive works in a Portal
environment.
Any help from you or anyone on this group would be very much appreciated,
and credited appropriately in the book.
Thanks
Regards,
Kunal Mittal
IT - Television
Sony Pictures Entertainment
Cell: (310) 562-5050
Richard Feit <[EMAIL PROTECTED]>
04/24/2005 12:32 PM
Please respond to
"Beehive Developers" <[email protected]>
To
Beehive Developers <[email protected]>
cc
Subject
Re: Beehive in Portal Environment.
Hi Srini and Kunal,
I'm assuming this question is about Page Flow working in a JSR168
environment (with its Portlet Request, etc.). Unfortunately, direct
support for running in a JSR168 portlet didn't make it into v1.0, but it
really should be in 1.1 (any comments you have would be great to add to
the recently-created Beehive Wishlist at
http://wiki.apache.org/beehive/WishList ). NetUI/Page Flow *is* set up
internally to work in a portal/portlet environment, since its previous
incarnation as part of the WebLogic Workshop server runtime was
integrated into WebLogic Portal (and I know from the WebLogic Portal
people that Beehive is being integrated/tested in the next version of
that product). Given that appropriate abstractions/hooks are there, it
*may* be possible to write an adapter that would make all this work
without changing any Beehive code... but I'm not sure about this and
haven't looked into it yet. Doing this right may require deeper changes
to the Page Flow APIs.
Just so we're all on the same page, by "working" inside a portlet, I
mean that an entire page flow, including all the parameters/attributes
in its requests and all its internally-stored session state, is scoped
so it is independent of all other Page Flow portlets, and all its
rendered URLs are automatically rewritten to take advantage of this
scoping behavior and to re-post to Portal URLs rather than straight
action/page URLs.
If I've missed any piece of your question, let me know.
Thanks,
Rich
[EMAIL PROTECTED] wrote:
Just to add to Srini's question - has Beehive been tested on any
specific
Portal - BEA, IBM, JBoss etc?
Thanks
Regards,
Kunal Mittal
IT - Television
Sony Pictures Entertainment
Cell: (310) 562-5050
Srini <[EMAIL PROTECTED]>
04/23/2005 07:00 PM
Please respond to
"Beehive Developers" <[email protected]>
To
[email protected]
cc
Subject
Beehive in Portal Environment.
Hello every one,
I have a question regarding usage of Beehive .
I am curious to know whether Apache Beehive be used in portal
environment.
Can we develop/deploy portlets using Apache Beehive. Is there any
document
or example which shows examples of Using Apache Beehive in a Portal
Environment.
Thanks
Srini
****************************************************************
* Srinivas Kanchanavally *
* E-mail : [EMAIL PROTECTED] *
* *
* *
* *
* *
* *
**************************************************************
