Jetspeed+Soap

[Werner Punz <we...@gmx.at>]

Hi since nobody answered to my last post regarding this.
I sucessfully merged Jetspeed and Soap on a binary level (see my last 
post) using Axis. I also developed a sample application accessing a soap 
service on the net (I found) via Axis and WSDL in a portlet.

(I also have a soap service serviced from my local database layer
which also is accessed by jetspeed in the same webapp)

So far it seems to work quite well. If anyone is interested I will write 
everything down and post the info. Just leave a comment in this thread 
if you are interested and I will write everything down the next few days.

But what I acutally need is some info from the developers. I got a 
little bit butterflies in my stomach, by merging both systems within the 
same webapp on a binary level. The problem might be that, I had to 
remove the apache soap jar file and the old xalan file from the Jetspeed 
lib dir. (Xalan was replaced with the newer build in JDK 1.4.1 and Soap 
by the stuff which Axis delivers). So far the system runs really well, 
but does anyone of the developers have a clue what sideefects this might 
cause in the long term? I assume Xalan shouldn´t pose too much of a 
problem since it seems backward compatible, but the problem might be 
Soap/Axis. Since they might be used somewhere in the jetspeed 
sourcetree. Can anyone of the developers comment on this?



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Portlet linking problem

[Łukasz Olek <ol...@hoga.pl>]

Hello!
As I understood a portlet entry must exist in user's psml file to make
linking possible using $jslink.
I do as follows:

        <entry id="P-f0e7834ba4-10001" parent="Meeting">
            <parameter name="_display" value="closed"/>
        </entry>
This entry is added in psml file.

Next in velocity template I put link:
<a href='$jslink.getPortletByName("Meeting")'>Kako</A>

But it doesn't work.
I have a single column controller. The only thing that I managed to do
is linking between items in menu controller with parameter
"_menustate=closed", but it's not enough for me.
Any help appreciated
Thanks
Lukasz Olek


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: Jetspeed+Soap

[David Sean Taylor <da...@bluesunrise.com>]

> -----Original Message-----
> From: Glen Carl [mailto:carl@csc-monterey.com]
> Sent: Monday, October 14, 2002 3:37 PM
> To: Jetspeed Users List
> Subject: Re: Jetspeed+Soap
>
>
> Remember to modify the Stock Quote portlet example to work with Axis.
>

Well, its actually not necessary. It currently does not use Axis or Apache
Soap.
Just plain Java.

I bet we could cut out 100 lines of code if we did convert it!
The original intention was to show how easy (and tedious) SOAP is without a
toolkit.



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Jetspeed+Soap

[Glen Carl <ca...@csc-monterey.com>]

Remember to modify the Stock Quote portlet example to work with Axis.

David Sean Taylor wrote:
> 
>>-----Original Message-----
>>From: Werner Punz [mailto:werpu@gmx.at]
>>Sent: Monday, October 14, 2002 3:22 PM
>>To: Jetspeed Users List
>>Subject: Re: Jetspeed+Soap
>>
>>
>>On Monday 14 October 2002 19:53, David Sean Taylor wrote:
>>
>>>Im in the process of upgrading Jars in Jetspeed, Turbine and Torque
>>>specifically, think Im getting pretty close now.
>>>
>>>I think we should drop soap.jar, and include the latest version of Axis.
>>
>>Btw... Axis is version 1.0 finally :-)
>>
>>
>>>I don't think that soap.jar is used in any portlets, since the
>>>StockQuotePortlet does its own Soap.
>>>
>>>Im at xerces-2.0.2.jar and xalan-2.3.1.jar
>>>
>>>If you could document how to include Axis in the Jetspeed distributable,
>>>I'd be glad to commit the changes
>>
>>Thanks for the fast reply.  I 'm still on jetspeed 1.4b1 running
>>on Tomcat 4.1
>>with JDK1.4.1
>>
>>Basically the merge is very easy. There are only 3 files which collide
>>with jetspeed, one is the obligatory web.xml file
>>the other one the soap.jar which axis replaces packagewise and
>>the third one
>>seems to be the xalan file which has to be replaced/removed.
>>
>>What I did was following:
>>I merged both web.xml files into a working file (I will post it tomorrow)
>>I removed the soap.jar and xalan.jar (the JDK1.4.1 has a xalan
>>which works
>>with Axis the Xalan from 1.4b1 didn work). I'm still not sure where
>>the problem was, but the wsdl compiler threw me errors with the old Xalan
>>Jetspeed had. I personally
>>think that Axis needed a newer version of Xalan than Jetspeed did
>>and the JDK
>>after a small check had the Xalan libs in its rt.jar, so
>>basically they must
>>be newer.
>>
>>And then I basically merged both directory structures into one. Thats
>>basically it. As I said it works so far on my 1.4b1 based install, but I
>>still have butterflies in my stomach due to the "dirty" merge I did.
>>
>>I dont have access now to the altered web.xml, but I will post it
>>tomorrow,
>>this should give a headstart to merge the systems. The build
>>however should
>>be done in the long run on a source level, I guess.
>>
>>But believe me merging jetspeed and Axis results in a killer app...
> 
> 
> I agree
> 
> 
>>I will post a small example tomorrow evening as well in this thread.
>>
> 
> 
> I'd like to take Axis as a jar file, and have an ant deploy task
> automatically merge it into the Jetspeed war.
> (Or if someone has a better solution...)
> We shouldn't be duplicating any Axis files in Jetspeed.
> Look forward to your posting
> 
> 
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
> 


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Jetspeed+Soap

[Werner Punz <we...@gmx.at>]

On Monday 14 October 2002 20:49, David Sean Taylor wrote:
> I agree
>
> > I will post a small example tomorrow evening as well in this thread.
>
> I'd like to take Axis as a jar file, and have an ant deploy task
> automatically merge it into the Jetspeed war.
> (Or if someone has a better solution...)
> We shouldn't be duplicating any Axis files in Jetspeed.
> Look forward to your posting

I'm not sure if that really is a good solution. The problem I saw
was that Axis relies on a load of other Apache libraries. I'm not sure how 
problematic the compatiblity of various library versions is. 

But doing that might work for certain Jetspeed/Axis combinations
(like it seems to work with 1.4b1/Axis 1.0) but as soon as there is another
major inclusion of a library in Turbine, the whole merge might be problematic 
again. 

Since I'm not involved in Jakarta projects I'm not really sure how
the project synchronisation is handled, all I could see was that most projects
try to keep downward compatiblity tests by extensive unit testing.

But I think the best thing would be if
axis would be merged in some way into Turbine (where it actually would fit 
perfectly into) or at least there should be some kind of coordination between 
both projects so that a merge is possible. I don't really like the idea of 
having Axis running as a separate webapp only. 


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: Jetspeed+Soap

[David Sean Taylor <da...@bluesunrise.com>]

> -----Original Message-----
> From: Werner Punz [mailto:werpu@gmx.at]
> Sent: Monday, October 14, 2002 3:22 PM
> To: Jetspeed Users List
> Subject: Re: Jetspeed+Soap
>
>
> On Monday 14 October 2002 19:53, David Sean Taylor wrote:
> > Im in the process of upgrading Jars in Jetspeed, Turbine and Torque
> > specifically, think Im getting pretty close now.
> >
> > I think we should drop soap.jar, and include the latest version of Axis.
>
> Btw... Axis is version 1.0 finally :-)
>
> > I don't think that soap.jar is used in any portlets, since the
> > StockQuotePortlet does its own Soap.
> >
> > Im at xerces-2.0.2.jar and xalan-2.3.1.jar
> >
> > If you could document how to include Axis in the Jetspeed distributable,
> > I'd be glad to commit the changes
>
> Thanks for the fast reply.  I 'm still on jetspeed 1.4b1 running
> on Tomcat 4.1
> with JDK1.4.1
>
> Basically the merge is very easy. There are only 3 files which collide
> with jetspeed, one is the obligatory web.xml file
> the other one the soap.jar which axis replaces packagewise and
> the third one
> seems to be the xalan file which has to be replaced/removed.
>
> What I did was following:
> I merged both web.xml files into a working file (I will post it tomorrow)
> I removed the soap.jar and xalan.jar (the JDK1.4.1 has a xalan
> which works
> with Axis the Xalan from 1.4b1 didn work). I'm still not sure where
> the problem was, but the wsdl compiler threw me errors with the old Xalan
> Jetspeed had. I personally
> think that Axis needed a newer version of Xalan than Jetspeed did
> and the JDK
> after a small check had the Xalan libs in its rt.jar, so
> basically they must
> be newer.
>
> And then I basically merged both directory structures into one. Thats
> basically it. As I said it works so far on my 1.4b1 based install, but I
> still have butterflies in my stomach due to the "dirty" merge I did.
>
> I dont have access now to the altered web.xml, but I will post it
> tomorrow,
> this should give a headstart to merge the systems. The build
> however should
> be done in the long run on a source level, I guess.
>
> But believe me merging jetspeed and Axis results in a killer app...

I agree

> I will post a small example tomorrow evening as well in this thread.
>

I'd like to take Axis as a jar file, and have an ant deploy task
automatically merge it into the Jetspeed war.
(Or if someone has a better solution...)
We shouldn't be duplicating any Axis files in Jetspeed.
Look forward to your posting



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Jetspeed+Soap

[Werner Punz <we...@gmx.at>]

On Monday 14 October 2002 19:53, David Sean Taylor wrote:
> Im in the process of upgrading Jars in Jetspeed, Turbine and Torque
> specifically, think Im getting pretty close now.
>
> I think we should drop soap.jar, and include the latest version of Axis.

Btw... Axis is version 1.0 finally :-)

> I don't think that soap.jar is used in any portlets, since the
> StockQuotePortlet does its own Soap.
>
> Im at xerces-2.0.2.jar and xalan-2.3.1.jar
>
> If you could document how to include Axis in the Jetspeed distributable,
> I'd be glad to commit the changes

Thanks for the fast reply.  I 'm still on jetspeed 1.4b1 running on Tomcat 4.1
with JDK1.4.1

Basically the merge is very easy. There are only 3 files which collide
with jetspeed, one is the obligatory web.xml file
the other one the soap.jar which axis replaces packagewise and the third one
seems to be the xalan file which has to be replaced/removed.

What I did was following:
I merged both web.xml files into a working file (I will post it tomorrow)
I removed the soap.jar and xalan.jar (the JDK1.4.1 has a xalan which works 
with Axis the Xalan from 1.4b1 didn work). I'm still not sure where
the problem was, but the wsdl compiler threw me errors with the old Xalan 
Jetspeed had. I personally 
think that Axis needed a newer version of Xalan than Jetspeed did and the JDK 
after a small check had the Xalan libs in its rt.jar, so basically they must 
be newer.

And then I basically merged both directory structures into one. Thats 
basically it. As I said it works so far on my 1.4b1 based install, but I 
still have butterflies in my stomach due to the "dirty" merge I did.

I dont have access now to the altered web.xml, but I will post it tomorrow, 
this should give a headstart to merge the systems. The build however should 
be done in the long run on a source level, I guess.

But believe me merging jetspeed and Axis results in a killer app...
I will post a small example tomorrow evening as well in this thread.





--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: Jetspeed+Soap

[David Sean Taylor <da...@bluesunrise.com>]

Im in the process of upgrading Jars in Jetspeed, Turbine and Torque
specifically, think Im getting pretty close now.

I think we should drop soap.jar, and include the latest version of Axis.
I don't think that soap.jar is used in any portlets, since the
StockQuotePortlet does its own Soap.

Im at xerces-2.0.2.jar and xalan-2.3.1.jar

If you could document how to include Axis in the Jetspeed distributable, I'd
be glad to commit the changes

> -----Original Message-----
> From: Werner Punz [mailto:werpu@gmx.at]
> Sent: Monday, October 14, 2002 12:39 PM
> To: jetspeed-user@jakarta.apache.org
> Subject: Jetspeed+Soap
>
>
> Hi since nobody answered to my last post regarding this.
> I sucessfully merged Jetspeed and Soap on a binary level (see my last
> post) using Axis. I also developed a sample application accessing a soap
> service on the net (I found) via Axis and WSDL in a portlet.
>
> (I also have a soap service serviced from my local database layer
> which also is accessed by jetspeed in the same webapp)
>
> So far it seems to work quite well. If anyone is interested I will write
> everything down and post the info. Just leave a comment in this thread
> if you are interested and I will write everything down the next few days.
>
> But what I acutally need is some info from the developers. I got a
> little bit butterflies in my stomach, by merging both systems within the
> same webapp on a binary level. The problem might be that, I had to
> remove the apache soap jar file and the old xalan file from the Jetspeed
> lib dir. (Xalan was replaced with the newer build in JDK 1.4.1 and Soap
> by the stuff which Axis delivers). So far the system runs really well,
> but does anyone of the developers have a clue what sideefects this might
> cause in the long term? I assume Xalan shouldn´t pose too much of a
> problem since it seems backward compatible, but the problem might be
> Soap/Axis. Since they might be used somewhere in the jetspeed
> sourcetree. Can anyone of the developers comment on this?
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
>



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>