[JBoss Seam] - Re: Seam 1.1.5.GA released-problem with upload pictures
by JoviJojo
Hi,
i have posted a message few days back concerning upload pictures in seam space application. now i just tried again to load images and below is one of the exceptions i got: (the picture i tried to load is one of the png from seam 1.1.5, its not at all big)
can somebody from seam team please give me some tips why it is just NOT working...
-----------------------
javax.servlet.ServletException: /register2.xhtml @23,78 data="#{register.picture}": Exception setting property picture of base with class org.jboss.seam.intercept.Proxy$$EnhancerByCGLIB$$2fddc97e
org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:61)
org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:32)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
javax.servlet.ServletException: /register2.xhtml @23,78 data="#{register.picture}": Exception setting property picture of base with class org.jboss.seam.intercept.Proxy$$EnhancerByCGLIB$$2fddc97e
javax.faces.webapp.FacesServlet.service(FacesServlet.java:152)
org.jboss.seam.servlet.SeamMultipartFilter.doFilter(SeamMultipartFilter.java:31)
org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:46)
org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:32)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
javax.faces.el.EvaluationException: /register2.xhtml @23,78 data="#{register.picture}": Exception setting property picture of base with class org.jboss.seam.intercept.Proxy$$EnhancerByCGLIB$$2fddc97e
com.sun.facelets.el.LegacyValueBinding.setValue(LegacyValueBinding.java:74)
org.jboss.seam.ui.FileUpload.decode(FileUpload.java:51)
javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:606)
javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:602)
javax.faces.component.UIForm.processDecodes(UIForm.java:53)
javax.faces.component.UIComponentBase.processDecodes(UIComponentBase.java:602)
javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:135)
org.apache.myfaces.lifecycle.LifecycleImpl.applyRequestValues(LifecycleImpl.java:219)
org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:71)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:137)
org.jboss.seam.servlet.SeamMultipartFilter.doFilter(SeamMultipartFilter.java:31)
org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:46)
org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:32)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011868#4011868
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011868
19Â years, 2Â months
[JBossWS] - Problem with ws4ee stack and wsdl description using xsd:impo
by stone_42
Hello,
I have a very simple WCF web service and a ws4ee client running in Jboss 4.0.3sp1, but using the ws4ee stack delivered with JBoss 4.0.4.
The WSDL of the WCF service is separated into two documents. The main document contains the following wsdl:types definition
<wsdl:types>
| <xsd:schema targetNamespace="http://tempuri.org/Imports">
| <xsd:import schemaLocation="http://localhost/WsatTest1WebService/Service.svc?xsd=xsd0" namespace="http://tempuri.org/" />
| </xsd:schema>
| </wsdl:types>
And the second, imported document looks the following:
<?xml version="1.0" encoding="utf-8" ?>
| <xs:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://tempuri.org/">
| <xs:element name="SayHello">
| <xs:complexType>
| <xs:sequence>
| <xs:element minOccurs="0" maxOccurs="1" name="t1" type="xs:string" />
| </xs:sequence>
| </xs:complexType>
| </xs:element>
| <xs:element name="SayHelloResponse">
| <xs:complexType>
| <xs:sequence>
| <xs:element minOccurs="0" maxOccurs="1" name="SayHelloResult" type="xs:string" />
| </xs:sequence>
| </xs:complexType>
| </xs:element>
| </xs:schema>
When I call this web service from my ws4ee client, the wcf service does not deserialize the request correctly (it receives null instead of its input data) and the client is not able to deserialize the response, it throws a org.xml.sax.SAXException: Invalid element in de.itinformatik.mes.serviceproxies.services.test.SayHelloResponse - SayHelloResult
| at org.jboss.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:455)
| at org.jboss.axis.encoding.DeserializationContextImpl.startElement(DeserializationContextImpl.java:1173)
| [...]
Looking at the SOAP messages exchanged, i found the reason: The ws4ee stack does not use qualified xml names for the elements of complex types and does not allow them in the response.
Now the strange thing: If I resolve the xsd:import by hand, integrating the imported xsd document into the wsdl document, everything works fine.
Here the SOAP request messages my client sends to the WCF service,
1) using the original wsdl document:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
| <soapenv:Body>
| <ns1:SayHello xmlns:ns1="http://tempuri.org/">
| <t1>foo</t1>
| </ns1:SayHello>
| </soapenv:Body>
| </soapenv:Envelope>
2) using the modified wsdl document without xsd:import
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
| <soapenv:Body>
| <ns1:SayHello xmlns:ns1="http://tempuri.org/">
| <ns1:t1>foo</ns1:t1>
| </ns1:SayHello>
| </soapenv:Body>
| </soapenv:Envelope>
Could this be a bug in the ws4ee stack? Or are wsdl documents using xsd:import in their wsdl:types definition not supported by the ws4ee stack?
Regards,
Martin
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011863#4011863
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011863
19Â years, 2Â months
[Installation, Configuration & Deployment] - I deploy my old portlets - raise error
by VitalyV
Hello!
I deploy my old portlets (for release jboss-portal-2.4.1 - without error) - raise error on jboss-portal-2.6-ALPHA*.
My xml-file is very simple:
jboss-app.xml
<jboss-app>
<app-name>testHeaderApp</app-name>
</jboss-app>
jboss-portlet.xml
<portlet-app>
<portlet-name>testHeader</portlet-name>
</portlet-app>
portlet.xml
<portlet-app version="1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/portlet"
xmlns="http://java.sun.com/xml/ns/portlet">
<portlet-name>testHeader</portlet-name>
<portlet-class>ru.nvg.TestHeader</portlet-class>
<portlet-info>
test header
</portlet-info>
<mime-type>text/html</mime-type>
<portlet-mode>VIEW</portlet-mode>
</portlet-app>
testHeader-object.xml
<?xml version="1.0" encoding="UTF-8"?>
<parent-ref>default</parent-ref>
<if-exists>overwrite</if-exists>
<instance-name>testHeader</instance-name>
<component-ref>testHeaderApp.testHeader</component-ref>
<parent-ref>default</parent-ref>
<if-exists>overwrite</if-exists>
<page-name>testHeader</page-name>
<window-name>testheaderWindow</window-name>
<instance-ref>testHeader</instance-ref>
true
center
0
error:
15:01:20,119 INFO [TomcatDeployer] deploy, ctxPath=/testHeader, warUrl=.../tmp/
deploy/tmp54019testHeader-exp.war/
15:01:20,229 ERROR [PortletAppDeployment] Error when creating instances
java.lang.ClassCastException
at org.jboss.portal.core.deployment.jboss.PortletAppDeployment.buildInst
ances(PortletAppDeployment.java:244)
at org.jboss.portal.core.deployment.jboss.PortletAppDeployment.start(Por
tletAppDeployment.java:99)
at org.jboss.portal.server.deployment.jboss.DeploymentContext.start(Depl
oymentContext.java:99)
at org.jboss.portal.server.deployment.jboss.PortalDeploymentInfoContext.
start(PortalDeploymentInfoContext.java:210)
at org.jboss.portal.server.deployment.jboss.ServerDeployer.start(ServerD
eployer.java:217)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl...
My portlet:
package ru.nvg;
import java.io.PrintWriter;
import java.io.IOException;
import javax.portlet.GenericPortlet;
import javax.portlet.PortletConfig;
import javax.portlet.PortletSecurityException;
import javax.portlet.RenderRequest;
import javax.portlet.RenderResponse;
import javax.portlet.PortletException;
public class TestHeader extends GenericPortlet
{
public void init(PortletConfig config) throws PortletException
{
// TODO Auto-generated method stub
super.init(config);
}
protected void doView(RenderRequest request, RenderResponse response) throws PortletException, PortletSecurityException, IOException
{
// TODO Auto-generated method stub
response.setContentType("text/html");
PrintWriter writer = response.getWriter();
writer.print("Content goes here\n");
writer.close();
}
}
Where is my error?
thanks...
WBR
Vitaly
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011853#4011853
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011853
19Â years, 2Â months
[JBossCache] - Re: Configuration problems For PojoCache under JBoss AS
by Naxo
Thanks Ben for your replies,
The document written by Jamie Reifsnyder is just what i was looking for. I didn't know exactly how to use and installed JBoss Cache inside JBoss AS. And I think you should do something like that in the documentation, cause there are lots of examples about Standalone JBoss Cache but none about the use and instalation inside JBoss AS.
I did more o less what Jamie Reifsnyder suggest, but at least I have a confirmation that what I did is right. There a few things that I didn't do... Any way my actual problem doesn't have nothing to do with JBoss Cache. I am not using Ant to build my application, I am using Eclipse packaging tool. As I have told you several times I am kind of newbie in J2EE and JBossCache, so I will need to study how to "Include a call to aopc (precompiler) in my build.xml script to precompile the classes for caching" But this not a problem to solve in this forum so I really thank you for your help.
There is something confusing for me in the documentation. Here is the exact paragraph from chapter 2.2 "Features of POJOCache":
http://labs.jboss.com/file-access/default/members/jbosscache/freezone/doc...
anonymous wrote :
| Support annotation usage. Starting from release 1.2.3, PojoCache also supports declaration of POJO through annotation under JDK1.4. JBossAop provides an annotation precompiler that a user can use to pre-process the annotation. As a result, there will be no need for jboss-aop.xml file declaration for POJOs, if annotation is preferred. The JDK5.0 annotation will be supported in the next release.
|
The JDK5.0 annotation will be supported in the next release.
I understand by this line that there is not an actual support for JDK 5.0 in JBossCache 1.4.1. GA. But I understand that this is a mistake, right?
I want to use Annotation to get rid of any xml file, and more precisely JDK 5.0. (I hope so solve my problem soon with Ant, so I can try and test JBoss Cache, I think that it's I great product and very useful)
Thank you again,
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011842#4011842
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011842
19Â years, 2Â months