Hi Philip,

Just double-checked that I didn't have the portlet-api-1.0.jar in my WAR
file.

It's a bit strange.

The only idea I can think of going forward is to pull down the Jetspeed 2
source from the repository and maybe debug my way through it myself.

Possible for a sanity check, could you send me your WAR file that is working
without problem and I will test it in my Jetspeed instance?

That will at least eliminate my Jetspeed instance as an issue area.

Thanks

Matthew



-----Original Message-----
From: Philip Mark Donaghy [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 31 January 2006 12:08
To: Jetspeed Users List; [EMAIL PROTECTED]
Subject: Re: Problem deploying Simplest Portlet


The war should not contain the portlet-api-1.0.jar, if this is the
case please remove it. In the 2.0 and the latest source there is no
deploy time error. 'Cannot create Portlet instance Simplest for
Portlet Application simplest' is displayed at runtime. Otherwise, I
can't reproduce your error.

On 1/30/06, Matthew Ryan <[EMAIL PROTECTED]> wrote:
> Hi Frank,
>
> I just tried that as well and still no luck. I have the exact same error.
>
> I didn't want to but I guess I will pull down the Jetspeed 2 source,
> build and debug. Maybe then I will track it down.
>
> Cheers
>
> Matt
>
>
> Frank Villarreal wrote:
> > Ryan,
> >
> > If you haven't done so already, make sure you rip the carriage returns
from
> > your PSML files too ... I just remembered that was another issue I had
as
> > well.
> >
> > - Frank
> >
> >
> >> -----Original Message-----
> >> From: Matthew Ryan [mailto:[EMAIL PROTECTED]
> >> Sent: Monday, January 30, 2006 03:17 AM
> >> To: Jetspeed Users List
> >> Subject: Re: Problem deploying Simplest Portlet
> >>
> >>
> >> Hi Philip,
> >>
> >> Thank you for your email. I am using the same JDK as you.
> >>
> >> Thanks again for your help.
> >>
> >> Matthew
> >>
> >>
> >> Philip Mark Donaghy wrote:
> >>
> >>> Hi Matthew,
> >>>
> >>> I tried this tutorial with the Jetspeed2.0-derby-install.jar using
> >>> jdk-1.5.0_06. All went well. There was a change to the documentation
> >>> where the psml was missing the xml header. I have to admit that I was
> >>> having difficulties with this because I am running two different
> >>> jdk's. Which jdk are you using? I'll try later on windows.
> >>>
> >>> Philip
> >>>
> >>> On 1/29/06, Matthew Ryan <[EMAIL PROTECTED]> wrote:
> >>>
> >>>
> >>>> Hi Frank,
> >>>>
> >>>> I ripped out all the carriage returns and the same problem
> >>>>
> >> remained......
> >>
> >>>> Now I'm not sure.
> >>>>
> >>>> Matt
> >>>>
> >>>>
> >>>> Frank Villarreal wrote:
> >>>>
> >>>>
> >>>>> Hi Ryan,
> >>>>>
> >>>>> Not sure if this is your problem, but when I first attempted
> >>>>>
> >> to deploy a new
> >>
> >>>>> portlet war file into the jetspeed2-final portal on Windows,
> >>>>>
> >> I ran into
> >>
> >>>>> problems with "illegal" characters in my "portlet.xml" file.
> >>>>>
> >> This turned
> >>
> >>>>> out to be the age old problem where some piece of code deep
> >>>>>
> >> down (in this
> >>
> >>>>> case the xml parser) doesn't process Windows OS carriage
> >>>>>
> >> returns correctly.
> >>
> >>>>> I'm guessing the strictness of the xml parsing/parser in the JDK1.5
is
> >>>>> different. Anyway, I didn't have this problem with the
> >>>>>
> >> previous milestone
> >>
> >>>>> releases on JDK1.4x. I solved this by downloading some
> >>>>>
> >> obscure text editor
> >>
> >>>>> that was capable of viewing these invisible characters so
> >>>>>
> >> that I coud remove
> >>
> >>>>> them.  After that, I was able to deploy my portlet application into
> >>>>> jetspeed.
> >>>>>
> >>>>> - Frank
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: Matthew Ryan [mailto:[EMAIL PROTECTED]
> >>>>>> Sent: Saturday, January 28, 2006 05:14 PM
> >>>>>> To: [email protected]
> >>>>>> Subject: Problem deploying Simplest Portlet
> >>>>>>
> >>>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>> I just gave this tutorial a go and found trouble deploying
> >>>>>>
> >> the Portlet.
> >>
> >>>>>> Any ideas? Maybe someone else has had this problem.
> >>>>>>
> >>>>>>
> >>>>>>
http://portals.apache.org/jetspeed-2/guides/guide-simple-portlet.html
> >>>>>>
> >>>>>>
> >>>>>> Found web.xml
> >>>>>> ERROR: java.lang.IllegalArgumentException: WEB-INF/portlet.xml
> >>>>>> org.apache.jetspeed.deployment.DeploymentException:
> >>>>>> java.lang.IllegalArgumentException: WEB-INF/portlet.xml
> >>>>>>         at
> >>>>>> org.apache.jetspeed.deployment.impl.DeployPortletAppEventListener.
> >>>>>> deployPortletApplication(DeployPortletAppEventListener.java:173)
> >>>>>>         at
> >>>>>> org.apache.jetspeed.deployment.impl.DeployPortletAppEventListener.
> >>>>>> invokeDeploy(DeployPortletAppEventListener.java:158)
> >>>>>>         at
> >>>>>> org.apache.jetspeed.deployment.impl.StandardDeploymentManager.disp
> >>>>>> atch(StandardDeploymentManager.java:257)
> >>>>>>         at
> >>>>>> org.apache.jetspeed.deployment.impl.StandardDeploymentManager.depl
> >>>>>> oy(StandardDeploymentManager.java:168)
> >>>>>>         at
> >>>>>> org.apache.jetspeed.deployment.impl.StandardDeploymentManager.fire
> >>>>>> DeploymentEvent(StandardDeploymentManager.java:202)
> >>>>>>         at
> >>>>>> org.apache.jetspeed.deployment.impl.StandardDeploymentManager$File
> >>>>>> SystemScanner.run(StandardDeploymentManager.java:342)
> >>>>>> Caused by: java.lang.IllegalArgumentException: WEB-INF/portlet.xml
> >>>>>>         at
> >>>>>> org.apache.jetspeed.tools.deploy.JetspeedDeploy.<init>(JetspeedDep
> >>>>>> loy.java:142)
> >>>>>>         at
> >>>>>> org.apache.jetspeed.deployment.impl.DeployPortletAppEventListener.
> >>>>>> deployPortletApplication(DeployPortletAppEventListener.java:168)
> >>>>>>         ... 5 more
> >>>>>> ERROR: Failure deploying
> >>>>>>
> >>>>>>
> >> E:\dev\servers\jetspeed2.0\webapps\jetspeed\WEB-INF\deploy\simplest.war
> >>
> >>>>>> The portal.xml is straight from the tutorial on the above link.
> >>>>>>
> >>>>>> I have JDK 1.5 and Jetspeed 2 off the download link on the
> >>>>>>
> >> project main
> >>
> >>>>>> page.
> >>>>>>
> >>>>>> Thanks
> >>>>>>
> >>>>>> Matthew
> >>>>>>
> >>>>>>
---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail:
[EMAIL PROTECTED]
> >>>>>> For additional commands, e-mail:
> >>>>>>
> >> [EMAIL PROTECTED]
> >>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>>>> For additional commands, e-mail:
[EMAIL PROTECTED]
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>>> For additional commands, e-mail:
[EMAIL PROTECTED]
> >>>>
> >>>>
> >>>>
> >>>>
> >>> --
> >>> Philip Donaghy
> >>> donaghy.blogspot.com del.icio.us/donaghy/philip
> >>> Skype: philipmarkdonaghy
> >>> Office: +33 5 56 60 88 02
> >>> Mobile: +33 6 20 83 22 62
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>> For additional commands, e-mail: [EMAIL PROTECTED]
> >>>
> >>>
> >>>
> >>>
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Philip Donaghy
donaghy.blogspot.com del.icio.us/donaghy/philip
Skype: philipmarkdonaghy
Office: +33 5 56 60 88 02
Mobile: +33 6 20 83 22 62

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


*~~~****DISCLAIMER****~~~*
This e-mail may contain confidential information. If you are not the intended 
recipient, please notify the sender immediately and delete this e-mail from 
your system. You must not disclose this email to anyone without express 
permission from the sender. The contents of all emails sent to, and received 
from, Optus may be scanned, stored, or disclosed to others by Optus at Optus' 
discretion. Optus has exercised care to avoid errors in the information 
contained in this e-mail but does not warrant that the information is error or 
omission free. 

Reply via email to