Page rebuilding and caching
Hi all, I'm trying to add to J2 some kind of security constraints at the level of a single portlet. It's supposed to be as simple as possible. To achive this goal I'm using portlet enitity's preferences. I modified a little bit PageAggregatorImpl and according to these preferences above I can decide about page structure (which portlets should be hidden to logged user). The problem is that every time I rebuild the page: 1. I get this message [org.apache.ojb.broker.core.PersistenceBrokerImpl] WARN: No running tx found, please only store in context of an PB-transaction, to avoid side-effects - e.g. when rollback of complex objects but, the portlet that I don't want to be shown, disappers. So far, so good. 2. Even after I had changed preferences in database back to their previous values (before page rebulding) the portlets that disappeared don't appear again. I belive this is somehow connected with J2 caching system. Is there any way to avoid it? Or even better, to use it the way I would like to? By 'my way' I mean situation when I have one psml file common for couple of users. Let's say it has 3 portlets in it (A,B,C). According to the user logged in page appearance is diffrent. User 1 sees only portlet A on the page, and user 2 sees A and B... I know that this problem can be solved by using different psml files for different users, but this is not the way I would like to have it. It's far more easy for my to configure to portald doing it the way I described. I belive I described my problem and what I would like to achive quite clearly. If not feel free to ask for more detailed information. I am aware that my English can be understoodble only for me ;) Sorry for pretty long post. Any help will be appreciate. Thanks! Tomasz - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
jetspeed 2 in jboss4.0.1
hi, While i was deploying jetspeed 2 in jboss 4.0.1 I encounter an exception which says as problem with xsl transformation. Whoever has successfully deployed j2 in jboss4.0.1 please help me out. regards, giri 2005-02-10 10:35:31,566 ERROR [org.jboss.deployment.MainDeployer] Could not initialise deployment: file:/D:/jboss-4.0.1/server/default/deploy/jetspeed-ds.xml org.jboss.deployment.DeploymentException: Problem with xsl transformation; - nested throwable: (javax.xml.transform.TransformerException: java.util.EmptyStackException) at org.jboss.deployment.XSLSubDeployer.init(XSLSubDeployer.java:215) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:828) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:765) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:305) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:481) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:416) at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at
Re: Access your own psml file
Hi David, Thanks for your answer. I tried that, but I still get the default-page.psml file. Actually I can type anything after http://localhost:8789/jetspeed/portal/ and it still gives me the same jetspeed default page Please help :( Amit Original Message Follows From: David Sean Taylor [EMAIL PROTECTED] Reply-To: Jetspeed Users List jetspeed-user@jakarta.apache.org To: Jetspeed Users List jetspeed-user@jakarta.apache.org Subject: Re: Access your own psml file Date: Wed, 09 Feb 2005 09:37:49 -0800 Shah Amit wrote: I have my own portlet web application. Now it logically makes sense that to deploy this this applicaiton, I should just throw it under jetspeed/web-inf/deploy, and should be able to access my webapplication from the browser. Till now I used to edit the default-page.psml in jetspeed/web-inf/pages directory and enter my portlet in there. But suppose I want to have my own psml file. (I guess I should put it under my-webapp/web-inf/pages/myPage.psml ??) Now even if I do this, how should I access this page from the browser ? http://localhost:8080/jetspeed/myapp/myPage.psml ?? http://localhost:8080/jetspeed/portal/myapp/myPage.psml Also look at the _user directory, as it holds folders and pages specific to a user. Also regarding decorators. I have read all the documentation on the website and I understand how it should be done. But again similar question. I should be able to put my decorators under my-webapp/web-inf/decorations etc. ?? Decorations can be packaged into a jar and dropped in the WEB-INF/deploy directory My only concern is that I dont want to change anything in jetspeed. This way I can easily keep updating jetspeed with new releases. Otherwise I would have to put my changes in jetspeed everytime I upgrade my jetspeed. I do exactly that on my projects here. For development, I have maven goals to drop in decorators, PSML and portlet apps With PSML, I have one PSML directory per project (I don't use the demo PSML directory from the Jetspeed cvs) Please help/advise/comment Thanks, Amit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194 - 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]
Jetspeed 2 Login Issue
Hello I am using jboss 3.2.6 and jetspeed 2, I am able to login from the index page using the admin/admin, but I am facing small problem, as soon as I login, it will ask to change password, if I change also , it is asking repeatedly many times and I am not able to go to administrative portlets. Kindly provide me some solution to view the administrative portlets. Thank You giri Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments.
RE: Jetspeed 2 Login Issue
giri, I'm not sure what's going on with your particular issue ... but you can take a look at the database table named SECURITY_CREDENTIAL and you'll see a field named AUTH_FAILURES ... you can reset that field back to 0 in order to keep trying your password. You can also set the IS_ENCODED field to 0 and manually type in your password if you want. Additionally, you can also set the UPDATE_REQUIRED field to 0 so that J2 doesn't ask you to enter a new password. - Frank -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, February 10, 2005 12:11 AM To: jetspeed-user@jakarta.apache.org Subject: Jetspeed 2 Login Issue Hello I am using jboss 3.2.6 and jetspeed 2, I am able to login from the index page using the admin/admin, but I am facing small problem, as soon as I login, it will ask to change password, if I change also , it is asking repeatedly many times and I am not able to go to administrative portlets. Kindly provide me some solution to view the administrative portlets. Thank You giri Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Changing the webapp context on J2
Thanks for the info Chris. This is a real bummer, kinda need this soon ...
like I said, I'm real close to making it work. I'm able to page through the
site in my new context and see all my portlet placeholders, but their
content all comes up Reason: null. I'll keep trying and post to this list
if I figure out how to get it done ... this is definately some type of
initialization issue.
- Frank
-Original Message-
From: Chris Custine [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 09, 2005 09:17 PM
To: Jetspeed Users List
Subject: Re: Changing the webapp context on J2
You aren't the only one looking forward to this ;-) This has come up
several times on the list in the past few months, but apparently this
is not a trivial task, and I believe it currently requires some
re-work to the core JS2 codebase. Unless I am mistaken, I don't think
this has been fully implemented yet.
Chris
On Wed, 9 Feb 2005 15:05:31 -0600, Frank Villarreal
[EMAIL PROTECTED] wrote:
Hello all,
I feel silly having to ask this, but this simple task hasn't been as
straight-forward as I would like
How do you give Jetspeed2 a new webapp context (instead of the default
/jetspeed).
Here is what I've already tried ...
1) renamed ${tomcat_home}/webapps/jetspeed to
${tomcat_home}/webapps/mysite
2) renamed path docBase attributes in
${tomcat_home}\conf\Catalina\localhost\jetspeed.xml to /mysite and
mysite respectively ...
3) renamed the value of the CONTEXT_ROOT field in the WEB_APPLICATION
table to /mysite for the record previously named /jetspeed
4) renamed the mapping for the jetspeed servlet in
${tomcat_home}\webapps\mysite\WEB-INF\web.xml as follows ...
servlet-mapping
servlet-namejetspeed/servlet-name
url-pattern/mysite/*/url-pattern
/servlet-mapping
Only after performing all 4 steps above was I able to view the portal in
the
/mysite context (at least the decorators and layouts) BU ...
one
thing is still vomiting on me ... my portlets all render as Portlet is
not
available: null Reason: null without providing meaningful clues as to why
in the logs (seems my portletDefinition objects are all null) ... hence my
email, does anyone know why??? (Seems like I must be missing a setting
somewhere).
I'm so close, yet s far away :-(
- Frank
-
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]
Re: PAM protlet not foud
I solved this problem while deploying manually the application portal - Original Message - From: jean charles jabouille [EMAIL PROTECTED] To: Jetspeed Users List jetspeed-user@jakarta.apache.org Sent: Thursday, February 10, 2005 11:31 AM Subject: PAM protlet not foud Hi, when I deploying Jetspeed I can see that the pam application (pam.war) is deploying. So The PAM portlet definition loaded for Jetspeed. But when I try to access to the http://localhost:8080/jetspeed it means that Jetspeed can't find the PAM portlet definition and do an error. How can I define the PAM portlet without deploying pam.war ? thanks for answers Jabouille Jean Charles - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Changing the webapp context on J2
OK ... got it!
In order to change the default context in Jetspeed2 ... I still had to take
all the steps I outlined in my previous email (see below), but I had to
perform them immediately after running Maven's quickStart task.
Apparently, J2 does some type of initialization that hard-codes the
context into the database in a place/manner I haven't yet identified for the
portlets. This happens the very first time you start-up J2. So, the moral
of the story ... make your context change before you start J2 for the very
first time ... or else, you're up the proverbial creek! ;-)
- Frank
-Original Message-
From: Frank Villarreal [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 10, 2005 09:14 AM
To: Jetspeed Users List
Subject: RE: Changing the webapp context on J2
Thanks for the info Chris. This is a real bummer, kinda need this soon ...
like I said, I'm real close to making it work. I'm able to page through the
site in my new context and see all my portlet placeholders, but their
content all comes up Reason: null. I'll keep trying and post to this list
if I figure out how to get it done ... this is definately some type of
initialization issue.
- Frank
-Original Message-
From: Chris Custine [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 09, 2005 09:17 PM
To: Jetspeed Users List
Subject: Re: Changing the webapp context on J2
You aren't the only one looking forward to this ;-) This has come up
several times on the list in the past few months, but apparently this
is not a trivial task, and I believe it currently requires some
re-work to the core JS2 codebase. Unless I am mistaken, I don't think
this has been fully implemented yet.
Chris
On Wed, 9 Feb 2005 15:05:31 -0600, Frank Villarreal
[EMAIL PROTECTED] wrote:
Hello all,
I feel silly having to ask this, but this simple task hasn't been as
straight-forward as I would like
How do you give Jetspeed2 a new webapp context (instead of the default
/jetspeed).
Here is what I've already tried ...
1) renamed ${tomcat_home}/webapps/jetspeed to
${tomcat_home}/webapps/mysite
2) renamed path docBase attributes in
${tomcat_home}\conf\Catalina\localhost\jetspeed.xml to /mysite and
mysite respectively ...
3) renamed the value of the CONTEXT_ROOT field in the WEB_APPLICATION
table to /mysite for the record previously named /jetspeed
4) renamed the mapping for the jetspeed servlet in
${tomcat_home}\webapps\mysite\WEB-INF\web.xml as follows ...
servlet-mapping
servlet-namejetspeed/servlet-name
url-pattern/mysite/*/url-pattern
/servlet-mapping
Only after performing all 4 steps above was I able to view the portal in
the
/mysite context (at least the decorators and layouts) BU ...
one
thing is still vomiting on me ... my portlets all render as Portlet is
not
available: null Reason: null without providing meaningful clues as to why
in the logs (seems my portletDefinition objects are all null) ... hence my
email, does anyone know why??? (Seems like I must be missing a setting
somewhere).
I'm so close, yet s far away :-(
- Frank
-
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]
RE: Jetspeed 2 Login Issue
I had the same problem - in my case, iirc I got around by modifying the isUpdateRequired method to simply return false, but that's obviously just a temporary hack (my goal was to get it to work with an existing LDAP directory, so I didn't mind that), Regards, Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, 10 February 2005 7:11 PM To: jetspeed-user@jakarta.apache.org Subject: Jetspeed 2 Login Issue Hello I am using jboss 3.2.6 and jetspeed 2, I am able to login from the index page using the admin/admin, but I am facing small problem, as soon as I login, it will ask to change password, if I change also , it is asking repeatedly many times and I am not able to go to administrative portlets. Kindly provide me some solution to view the administrative portlets. Thank You giri Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE : jetspeed 2 in jboss4.0.1
I think your jetspeed-ds.xml is not well formated. Compare with hsql-ds.xml. Cedric -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Envoyé : jeudi 10 février 2005 13:59 À : jetspeed-user@jakarta.apache.org Objet : jetspeed 2 in jboss4.0.1 hi, While i was deploying jetspeed 2 in jboss 4.0.1 I encounter an exception which says as problem with xsl transformation. Whoever has successfully deployed j2 in jboss4.0.1 please help me out. regards, giri 2005-02-10 10:35:31,566 ERROR [org.jboss.deployment.MainDeployer] Could not initialise deployment: file:/D:/jboss-4.0.1/server/default/deploy/jetspeed-ds.xml org.jboss.deployment.DeploymentException: Problem with xsl transformation; - nested throwable: (javax.xml.transform.TransformerException: java.util.EmptyStackException) at org.jboss.deployment.XSLSubDeployer.init(XSLSubDeployer.java:215) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:828) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:765) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher. java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor. java:122) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBea nOperationInterceptor.java:131) at org.jboss.mx.server.Invocation.invoke(Invocation.java:74) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav a:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentSc anner.java:305) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScan ner.java:481) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doS can(AbstractDeploymentScanner.java:204) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(Abst ractDeploymentScanner.java:277) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupp ort.java:272) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBean Support.java:222) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher. java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav a:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController .java:891) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:416) at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher. java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.jav a:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher. java:144) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor. java:122) at
JFreeChart and JetSpeed2
Hi, I am trying to use CeWolf and JFreeChart packages within JetSpeed2 Portlets. The image never gets rendered and I get The Chart has expired and please reload error. When I debugged this error message, I found that somehow the session object used by renderer is different. So the image is never found in session object in the renderer code. Has anyone else ever run into similar issues? Regards -Satya - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Changing the webapp context on J2
OK ... got it! In order to change the default context in Jetspeed2 ... I still had to take all the steps I outlined in my previous email (see below), but I had to perform them immediately after running Maven's quickStart task. Apparently, J2 does some type of initialization that hard-codes the context into the database ... Indeed J2 does this! I had the problem that my own, Struts-based portlet simply did not show any contents when I deployed it the first time. (I only could see the Portlet title and the maximize/minimize etc. icons). The JPetstore portlet (Struts-based, too), however showed content and I could not see any differences between both of them, until ... I looked at the database! J2 stores a lot of portlet and other information here, so initialization, once done for a Portlet is only done in a reduced manner on each following startup. That at least is my impression so far. It helps, to run the Maven quickStart task, which - besides other tasks - clears the database and refills the initial values. You may as well extract the appropriate SQL scripts for your database and run them manually. in a place/manner I haven't yet identified for the portlets. This happens the very first time you start-up J2. So, the moral of the story ... make your context change before you start J2 for the very first time ... or else, you're up the proverbial creek! ;-) Apparently my own Portlet was not made up correctly in the first place, when J2 registered it in the database and after correcting the mistakes it wasn't re-initialized correctly, 'cause J2 finds some information in the database and skips initial deployment (- this you see in the Logs). Cleaning and reinitializing the database could solve you're webapp context problem, too. Though it is a rather bad solution. Maybe one can find the tables and fields that need to be cleared, to make J2 startup the next time from scratch. Sven. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
