My war is working on Tomcat6, but got error on Weblogic10.3:
The tag handler class was not found "jsp_servlet.tags.__tag"
Here is the situation:
I have developed 5 tag files, and define these 5 tag file in one tld,
and package them into nnn.jar with tld.
My first JSP is using 2 of 5 tag files, when I click this page,
in tomcat, it's working well,but in Weblogic10.3, got error above,
I found the key factor of this error is "using 2 of 5 tag",because that when I'm using all 5 tag files in one JSP, the Weblogic103 is working well!
So I think maybe this's a weblogic bug or I need do some configuration to avoid this.
Any idea about this situation? thans a lot!
Related
I am experiencing a problem with the Productcomments module which I am using in a custom module and I cannot figure out how to fix it. The problem is with the star rating in the Productcomments form itself. This form works perfectly in a localhost environment - see images 1 and 2, but not on a live server - see images 3 and 4. On the live server it is showing no stars, just radio buttons, and no delete button for removing the stars.
Form as it looks on WAMP
Code from Chromes Inspect for WAMP
Form as it looks on Live Server
Code from Chromes Inspect for Live Server
Disabling the link to the following 2 js files recreates the problem on the local server which would suggest that the problem lies in the links to these two files on the live server, however I have checked all links to these files and they are correct, as are the permissions for these files.
jquery.rating.pack.js and productcomments.js
Occasionally when I clear cache under Advanced Parameters > Performance I get the following error message:
Fatal error: Uncaught --> Smarty: unable to write file /home/productm/public_html/cache/smarty/compile/10/e2/20/wrt5cbbb0747109d3_91450142
<-- thrown in /home/productm/public_html/tools/smarty/sysplugins/smarty_internal_write_file.php on line 46
This problem applies to all 1.6 versions of Prestashop tested.
Any suggestions on how to fix this problem would be appreciated.
Thanks
Kathleen
The error code you've got from clearing cache is linked to permission problems.
Here's probably a duplicate of your issue: How to fix erorr "Fatal error: Uncaught --> Smarty: unable to write file"?
Check that your prestashop files are set to 644 and folders 755 permission. (not just the js files you've mentioned).
Also if you manually moved the module to your live server(ftp), check the ownership of those files.
Edit:
I'll add this to the answer since the permissions didn't fix your problem.
looks like you have a prestashop bug going on with the JS (Synchronous loaded scripts)
here's a patch to fix that, maybe it fixes your original problem.
https://github.com/PrestaShop/PrestaShop/pull/6749/commits/73fd8dbed9f413a70f7d04fc4badd48f00ca501a
I have a project deployed on the appstore(everything ok),which after 2 months on running source code gives me crazy errors.
what i tried
Build settings-> set YES to Always search user paths
Not working
Please provide some suggestions.I think i need to chang some thing in build settings.Do anyone know why this is happening?
I was able to solve it in 2 ways
1.I removed the framework and added it back again
2.In framework search paths i removed everything and added $(SRCROOT) there.
I am trying to integrate axis2 -1.6.2 and Websphere7 .
I followed the links provided by Andreas such as: http://axis.apache.org/axis2/java/core/docs/app_server.html
and I also excluded axis1.4 which was getting downloaded transitively.
The module is 'parent-last' class loading and whole EAR , I tried both parent-first and last but I still get
java.lang.InstantiationError: org.apache.axis2.databinding.ADBDataSource.....and
java.lang.NoClassDefFoundError: org/apache/commons/fileupload/FileUploadException
though I have commons-fileupload jar and axis2-1.6.2 and axis2-adb jar.
Please post any suggestions.
FYI: I also followed this procedure :
http://www-01.ibm.com/support/docview.wss?rs=0&q1=axis2&q2=technote&uid=swg21315686&loc=en_US&cs=utf-8&cc=us&lang=en
Thanks.
I am new to BlackBerry Web Works.I am following the instruction for development given on development site.While packaging the Application I am getting this error in command prompt : "[ERROR] feature cannot be found in any extension(blackberry. pin .memo)".
Before going to this step I have already created project folder with config.xml and index.html and also zip file of application components properly.And now trying to package the application.But I am getting error like:
Please help me to figure out this error.
Thanks
Finally I got the solution after a lot of searching and analogy.
This error occurs when either we have added some feature in config.xml which we are not using in our application or when we are using same feature but not defined in "feature" tag in config.xml. It is the same case with "spinner" ,"sms" etc.
In my case it was because of "memo" ,which I was defining in config.xml but didn't use any Contact feature in my Application.So it producing error like "feature cannot be found in any extension(blackberry. pin .memo)".
I have created a new project of SharePoint 2010 --> Visual Web part,
seleted it as form solution. and it created the web part.
I just edited it with Hello World! for confirmation and deployed it using VS, and successfully added to page.
problem, arrises when i activated the same package after uploaded it from site actions--> site settings --> galleries --> Solutions
-- > upload new solution --> activate it.
error came:
This solution contains invalid markup or elements that cannot be deployed as part of a sandboxed solution. Solution manifest for solution 'GUID' failed validation, file manifest.xml, line 14, character 4: The element 'Solution' in namespace 'http://schemas.microsoft.com/sharepoint/' has invalid child element 'TemplateFiles' in namespace 'http://schemas.microsoft.com/sharepoint/'. List of possible elements expected: 'FeatureManifests, ActivationDependencies' in namespace 'http://schemas.microsoft.com/sharepoint/'
I don't know why VS didn't get this error while its deployment or i am missing some thing while my deployment.
any idea?
Try to make your visual web part as sand boxed solution your problem will be resolved