[JBoss Portal] - WSRP: problem with portal url rewriting in WSRP wsdls
by jeremie.petit
Hello,
I'm trying to provide a JBoss Portal portlet as an external remote portal. I'm using JBoss Portal 2.6DR1 (the bundle found on the jboss download section, incl. the AS), but the problem is similar (and even worse because the port itself is lost, it's 8080 whichever the request URL port) on 2.4 & 2.4.1CR2:
On Portal 2.6.DR1 I added the latest JBossWS stack (jbossws-1.0.4.GA), as found in the download sections (and I followed the installation instructions).
when I request the WSRP wsld, using the URL http://jpetit2.emea.hpqcorp.net:8082/portal-wsrp/MarkupService?wsdl, I obtain the following:
| - <wsdl:definitions targetNamespace="urn:oasis:names:tc:wsrp:v1:wsdl"
| xmlns="http://schemas.xmlsoap.org/wsdl/"
| xmlns:bind="urn:oasis:names:tc:wsrp:v1:bind"
| xmlns:intf="urn:oasis:names:tc:wsrp:v1:intf"
| xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
| xmlns:tns="urn:oasis:names:tc:wsrp:v1:wsdl"
| xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
| <wsdl:import
| location="http://jpetit2:8082/portal-wsrp/MarkupService?wsdl&resource=wsrp_v1_bindi..."
| namespace="urn:oasis:names:tc:wsrp:v1:bind" />
| - <wsdl:service name="WSRPService">
| - <wsdl:port binding="bind:WSRP_v1_PortletManagement_Binding_SOAP" name="WSRPPortletManagementService">
| <soap:address location="http://jpetit2:8082/portal-wsrp/PortletManagementService" />
| </wsdl:port>
| - <wsdl:port binding="bind:WSRP_v1_Registration_Binding_SOAP" name="WSRPRegistrationService">
| <soap:address location="http://jpetit2:8082/portal-wsrp/RegistrationService" />
| </wsdl:port>
| - <wsdl:port binding="bind:WSRP_v1_Markup_Binding_SOAP" name="WSRPBaseService">
| <soap:address location="http://jpetit2:8082/portal-wsrp/MarkupService" />
| </wsdl:port>
| - <wsdl:port binding="bind:WSRP_v1_ServiceDescription_Binding_SOAP" name="WSRPServiceDescriptionService">
| <soap:address location="http://jpetit2:8082/portal-wsrp/ServiceDescriptionService" />
| </wsdl:port>
| </wsdl:service>
| </wsdl:definitions
|
Remark as the domain name is missing from the 'location' URL: anonymous wrote : location="http://jpetit2:8082/portal-wsrp/MarkupService?wsdl&resource=wsrp_v1_bindi..." . This is an issue because the consumer and the provider are not in the same domain so the hostname only is not enough for the consumer.
As I stated previously, the 2.4 (and 2.4.1RC2) are even worse in that the location strings start with anonymous wrote : http://jpetit2:8080/ whichever the port configured in tomcat's server.xml.
I'm looking for some help regarding this issue, because it currently prevents me from showcasing the WSRP capabilities of JBoss Portal in our environment.
For the record, I'm working on Windows XP SP2, DB is the DB setup in the 2.6 bundle.
Thank you
Jeremie Petit
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995093#3995093
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995093
19 years, 4 months
[JBoss Seam] - Re: integration with Trinidad (ADF)
by lle
here is my faces-config.xml:
<?xml version="1.0" encoding="UTF-8"?>
| <!DOCTYPE faces-config PUBLIC "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.0//EN"
| "http://java.sun.com/dtd/web-facesconfig_1_0.dtd">
| <faces-config>
| <!-- Navigation rules for the risk app -->
| <navigation-rule>
| <navigation-case>
| <from-outcome>login</from-outcome>
| <to-view-id>/home.xhtml</to-view-id>
| <redirect/>
| </navigation-case>
| <navigation-case>
| <from-outcome>main</from-outcome>
| <to-view-id>/main.xhtml</to-view-id>
| </navigation-case>
| <navigation-case>
| <from-outcome>error</from-outcome>
| <to-view-id>/error.xhtml</to-view-id>
| <redirect/>
| </navigation-case>
| </navigation-rule>
|
| <application>
| <!-- Use the Trinidad RenderKit -->
| <default-render-kit-id>
| org.apache.myfaces.trinidad.core
| </default-render-kit-id>
| </application>
|
| <!-- Select one of the two standard persistence lifecycle models for the Seam application -->
| <lifecycle>
| <phase-listener>org.jboss.seam.jsf.TransactionalSeamPhaseListener</phase-listener>
| </lifecycle>
| </faces-config>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995092#3995092
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995092
19 years, 4 months
[JBoss Seam] - Re: integration with Trinidad (ADF)
by lle
Hi,
Yes, I followed the example on wiki and still got the exception. I checked my faces-config.xml many times and very sure there's no configuration of the view handler there, only in web.xml. Still got the exception...
Here is my web.xml:
<?xml version="1.0" encoding="UTF-8"?>
| <web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
| <display-name>Risk Application</display-name>
|
| <context-param>
| <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
| <param-value>org.jboss.seam.ui.facelet.SeamFaceletViewHandler</param-value>
| </context-param>
|
| <!-- Facelets with Trinidad configuration-->
| <context-param>
| <param-name>org.apache.myfaces.trinidad.ALTERNATE_VIEW_HANDLER</param-name>
| <param-value>com.sun.facelets.FaceletViewHandler</param-value>
| </context-param>
| <!-- Use documents saved as *.xhtml -->
| <context-param>
| <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
| <param-value>.xhtml</param-value>
| </context-param>
|
| <!-- Use client-side state saving. In Trinidad, it is an
| optimized, token-based mechanism that is almost always a
| better choice than the standard JSF server-side state saving. -->
| <context-param>
| <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
| <param-value>client</param-value>
| <!--param-value>server</param-value-->
| </context-param>
|
| <!-- Trinidad by default uses an optimized client-side state saving
| mechanism. To disable that, uncomment the following -->
| <!--context-param>
| <param-name>org.apache.myfaces.trinidad.CLIENT_STATE_METHOD</param-name>
| <param-value>all</param-value>
| </context-param-->
|
| <context-param>
| <param-name>org.apache.myfaces.trinidad.USE_APPLICATION_VIEW_CACHE</param-name>
| <param-value>false</param-value>
| </context-param>
|
| <context-param>
| <param-name>org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION</param-name>
| <param-value>true</param-value>
| </context-param>
|
| <!-- <context-param>
| <param-name>org.apache.myfaces.trinidad.CHANGE_PERSISTENCE</param-name>
| <param-value>session</param-value>
| </context-param> -->
|
| <!-- Special Debug Output for Development -->
| <context-param>
| <param-name>facelets.DEVELOPMENT</param-name>
| <param-value>true</param-value>
| </context-param>
|
| <context-param>
| <description>If true, rendered HTML code will be formatted, so that it is "human readable".
| i.e. additional line separators and whitespace will be written, that do not
| influence the HTML code.
| Default: "true"</description>
| <param-name>org.apache.myfaces.PRETTY_HTML</param-name>
| <param-value>true</param-value>
| </context-param>
| <context-param>
| <description>If true, a javascript function will be rendered that is able to restore the
| former vertical scroll on every request. Convenient feature if you have pages
| with long lists and you do not want the browser page to always jump to the top
| if you trigger a link or button action that stays on the same page.
| Default: "false"</description>
| <param-name>org.apache.myfaces.AUTO_SCROLL</param-name>
| <param-value>true</param-value>
| </context-param>
|
| <!-- ajax4jsf filter - must be before any other filter -->
| <filter>
| <display-name>Ajax4jsf Filter</display-name>
| <filter-name>ajax4jsf</filter-name>
| <filter-class>org.ajax4jsf.Filter</filter-class>
| </filter>
| <!-- trinidad -->
| <filter>
| <filter-name>trinidad</filter-name>
| <filter-class>org.apache.myfaces.trinidad.webapp.TrinidadFilter</filter-class>
| </filter>
| <!-- Propagate conversations across redirects -->
| <filter>
| <filter-name>Seam Redirect Filter</filter-name>
| <filter-class>org.jboss.seam.servlet.SeamRedirectFilter</filter-class>
| </filter>
| <!-- Needed to ensure safe tx cleanup when using Seam-managed sessions/persistence contexts -->
| <filter>
| <filter-name>Seam Exception Filter</filter-name>
| <filter-class>org.jboss.seam.servlet.SeamExceptionFilter</filter-class>
| </filter>
| <filter-mapping>
| <filter-name>trinidad</filter-name>
| <servlet-name>Faces Servlet</servlet-name>
| </filter-mapping>
| <filter-mapping>
| <filter-name>ajax4jsf</filter-name>
| <url-pattern>*.jsf</url-pattern>
| </filter-mapping>
| <filter-mapping>
| <filter-name>Seam Redirect Filter</filter-name>
| <url-pattern>*.jsf</url-pattern>
| </filter-mapping>
| <filter-mapping>
| <filter-name>Seam Exception Filter</filter-name>
| <url-pattern>*.jsf</url-pattern>
| </filter-mapping>
| <!-- Seam -->
| <listener>
| <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>
| </listener>
| <!-- MyFaces -->
| <listener>
| <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
| </listener>
| <servlet>
| <servlet-name>Faces Servlet</servlet-name>
| <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
| <load-on-startup>1</load-on-startup>
| </servlet>
| <servlet-mapping>
| <servlet-name>Faces Servlet</servlet-name>
| <url-pattern>*.jsf</url-pattern>
| </servlet-mapping>
|
| <!-- trinidad resources servlet -->
| <servlet>
| <servlet-name>resources</servlet-name>
| <servlet-class>org.apache.myfaces.trinidad.webapp.ResourceServlet</servlet-class>
| </servlet>
|
| <!-- This cannot be configured currently -->
| <servlet-mapping>
| <servlet-name>resources</servlet-name>
| <url-pattern>/adf/*</url-pattern>
| </servlet-mapping>
|
| <!-- only allow developers to have access to the xhtml files -->
| <security-constraint>
| <display-name>Restrict XHTML Documents</display-name>
| <web-resource-collection>
| <web-resource-name>XHTML</web-resource-name>
| <url-pattern>*.xhtml</url-pattern>
| </web-resource-collection>
| <auth-constraint>
| <description>Only Let 'developer's access XHTML pages</description>
| <role-name>developer</role-name>
| </auth-constraint>
| </security-constraint>
| <login-config>
| <auth-method>BASIC</auth-method>
| </login-config>
| </web-app>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995090#3995090
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995090
19 years, 4 months
[JBoss Seam] - Problem in writing own annotation in seam
by waheed.murad
I want to have my own Hibernate annotaion validator...... named NotEmpty a problem is that when after form submition the only initialize() method is called. isValid() method does not executes......
below is the code and Thanks in advance for help......
------------- Annotation descriptor -------------------
import java.lang.annotation.Documented;
import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;
import org.hibernate.validator.ValidatorClass;
@ValidatorClass(value=NotEmptyValidator.class)
@Target(value={ElementType.METHOD,ElementType.FIELD})
@Retention(value=RetentionPolicy.RUNTIME)
@Documented
public @interface NotEmpty {
String message() default "Field cannot be empty";
}
------------- Annotation validator -------------------
import org.hibernate.validator.PropertyConstraint;
import org.hibernate.validator.Validator;
import java.io.Serializable;
public class NotEmptyValidator implements Validator, PropertyConstraint, Serializable {
public boolean isValid(Object value) {
System.out.println(" is Valid method called...");
..............
..............
return false;
}
public void initialize(NotEmpty parameters) {
System.out.println(" Initialize method called...");
}
public void apply(org.hibernate.mapping.Property property){
System.out.println(" Apply method called...");
}
}
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995089#3995089
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995089
19 years, 4 months
[JBoss jBPM] - Re: create task instance without saving it
by falazar
I concur, this shoudl be fixed, because we noticed real quick that we would go to the page, not really want to start the task leave, and we would have a started, empty task, that was just taking aspot for no reason.
It doesnt look like it was that hard to fix, there is a function in ParticipantBean that starts it, and then a function in TaskBean that saves/ends it.
If we can move most of the logic from the first to the second it should work.
You dont have to worry about the variables, cause you only need them when you save, and when you save, teh first thing you can do is create the task instance.
So the only real thing to do, is make sure you can get access to the initial form.
This may have changed in in the newest version, that David is working on though.
James Ratcliff
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995088#3995088
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995088
19 years, 4 months
[EJB 3.0] - Help With EJB 3 & JBoss 4.0.5
by abhinav19
Hi All
I am using Jboss 4.0.5, EJB3.0 RC 9, downloaded the JEMs
but when i try to deploy the projct i get the error that I am not complying to EJB 2.1 specifications. I am pasting the contents of the server log for reference. Please let me know where I am wrong.
an
12:06:34,093 WARN [verifier] EJB spec violation:
Bean : User
Section: 10.6.2
Warning: The entity bean's class must implement, directly or indirectly, the javax.ejb.EntityBean interface.
12:06:34,093 WARN [verifier] EJB spec violation:
Bean : User
Section: 10.6.2
Warning: The entity bean class must be defined as public and abstract.
12:06:34,109 WARN [verifier] EJB spec violation:
Bean : User
Section: 10.6.1
Warning: The Bean Provider must provide a remote interface and a remote home interface or a local interface and a local home interface for the bean.
12:06:34,109 WARN [verifier] EJB spec violation:
Bean : UserManager
Section: 7.10.2
Warning: A Session bean must implement, directly or indirectly, the javax.ejb.SessionBean interface.
12:06:34,109 WARN [verifier] EJB spec violation:
Bean : UserManager
Section: 7.10.3
Warning: A Session bean must define at least one ejbCreate method.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995084#3995084
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995084
19 years, 4 months