[JBoss Portal] - New Theme - From web 2.0 template -> How to??
by soundspeace
i have a good question. I want to make a theme that look like web template that can download from example templateworld.com
this example web 2.0 template
http://www.templateworld.com/zero/in_action/jet_30/
to view look like these template in jboss portal. It easy for me. i just import css this template and part of css in portal_style.css i comment it.
because jboss portal have 3 layout -> i just take 1 column (index.jsp) for this template.
So i just copy paste some html content from this template put in to 1 column layout.
the problem is, when user change theme renewal use 1 column.. the theme will be look ugly, because have some content html that i put it for my new theme.
i need opinion, how i want to make new theme that look like i download from
[/url]www.templateworld.com[url]
what i need to do? how to? Did i need make all div (header,left,right,bottom, footer) as portlet??? because i want the data will be call from database..
i dun want static html..
can u giv me a link example website use jboss portal look like templateworld???
p/s -> i m new comer in java , new in jbossportal... im very interesting to learn java .. im php background.
tq[/url]
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221837#4221837
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221837
15 years, 3 months
[JBoss Portal] - org.apache.commons.discovery.DiscoveryException: Class org.a
by GajananM
when i am running webservice through axis client in potlet 2.7.1. I am getting following error.
stacktrace:
exception
javax.servlet.ServletException: Servlet execution threw an exception
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
java.lang.ExceptionInInitializerError
org.apache.axis.handlers.BasicHandler.(BasicHandler.java:81)
org.apache.axis.client.Service.getAxisClient(Service.java:140)
org.apache.axis.client.Service.(Service.java:149)
com.sun.j2ee.blueprints.opc.powebservice.PoEndpointBeanServiceLocator.(PoEndpointBeanServiceLocator.java:12)
com.sun.j2ee.blueprints.opc.powebservice.PoEndpointBeanProxy._initPoEndpointBeanProxy(PoEndpointBeanProxy.java:18)
com.sun.j2ee.blueprints.opc.powebservice.PoEndpointBeanProxy.(PoEndpointBeanProxy.java:8)
org.jboss.portal.portlet.samples.SampleClient.service(SampleClient.java:62)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
org.apache.commons.discovery.DiscoveryException: Class org.apache.commons.logging.impl.SLF4FLogFactory does not implement org.apache.commons.logging.LogFactory
org.apache.commons.discovery.tools.ClassUtils.verifyAncestory(ClassUtils.java:180)
org.apache.commons.discovery.tools.SPInterface.verifyAncestory(SPInterface.java:202)
org.apache.commons.discovery.tools.SPInterface.newInstance(SPInterface.java:196)
org.apache.commons.discovery.tools.DiscoverClass.newInstance(DiscoverClass.java:579)
org.apache.commons.discovery.tools.DiscoverSingleton.find(DiscoverSingleton.java:418)
org.apache.commons.discovery.tools.DiscoverSingleton.find(DiscoverSingleton.java:378)
org.apache.axis.components.logger.LogFactory$1.run(LogFactory.java:84)
java.security.AccessController.doPrivileged(Native Method)
org.apache.axis.components.logger.LogFactory.getLogFactory(LogFactory.java:80)
org.apache.axis.components.logger.LogFactory.(LogFactory.java:72)
org.apache.axis.handlers.BasicHandler.(BasicHandler.java:81)
org.apache.axis.client.Service.getAxisClient(Service.java:140)
org.apache.axis.client.Service.(Service.java:149)
com.sun.j2ee.blueprints.opc.powebservice.PoEndpointBeanServiceLocator.(PoEndpointBeanServiceLocator.java:12)
com.sun.j2ee.blueprints.opc.powebservice.PoEndpointBeanProxy._initPoEndpointBeanProxy(PoEndpointBeanProxy.java:18)
com.sun.j2ee.blueprints.opc.powebservice.PoEndpointBeanProxy.(PoEndpointBeanProxy.java:8)
org.jboss.portal.portlet.samples.SampleClient.service(SampleClient.java:62)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
thanks in advance
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221836#4221836
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221836
15 years, 3 months
[JNDI/Naming/Network] - sub-pool per user logged in
by manojpardeshi
Hi
We have an application which is deployed on jboss4 and maintaining a pool of connection with Inconcert database. PFB the ds.xml file:-
<no-tx-connection-factory>
<jndi-name>IcJava</jndi-name>
<adapter-display-name>Inconcert System Connection</adapter-display-name>
<rar-name>inconcert.rar</rar-name>
<connection-definition>com.wcg.framework.ra.InconcertConnectionFactory</connection-definition>
<config-property name="ServerName" type="java.lang.String">optxicp</config-property>
<config-property name="ServerHost" type="java.lang.String">icapp</config-property>
<config-property name="ServerPort" type="java.lang.String">61071</config-property>
<min-pool-size>0</min-pool-size>
<!-- A seperate sub-pool is created per username logged into inconcert, and the max pool size is per sub pool -->
<max-pool-size>40</max-pool-size>
<blocking-timeout-millis>5000</blocking-timeout-millis>
<idle-timeout-minutes>10</idle-timeout-minutes>
<application-managed-security/>
</no-tx-connection-factory>
I am not able to understand what is the meaning of sub pool per user. I think connection pool is maintained at application level and not at user level. Much appreciate if somebody clarify my doubt.
Thanks in advance,
Manoj
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221834#4221834
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221834
15 years, 3 months
[Management, JMX/JBoss] - Re: JBoss LoggingMonitor -
by vinothkumar
Hi All,
I have a webservice hosted on my machine and I had deployed the xml file(Deployment Descriptor File) for logging monitor with the name XXXXXX-monitor-service.xml
The attributes defined are :
| <attribute name="MonitoredObjects">
| <configuration>
| <monitoredmbean name="jboss.ws.XXXXXX"
| logger="com.sample">
| <attribute>RequestCount</attribute>
| <attribute>ResponseCount</attribute>
| <attribute>FaultCount</attribute>
| </monitoredmbean>
| </configuration>
| </attribute>
|
| <depends>jboss.ws.XXXXXX</depends>
| </mbean>
I got the following exception :
anonymous wrote : Problem configuring service jboss.monitor:type=LoggingMonitor,name=XXXMonitor
| org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@1eacdc4 on mbean jboss.monitor:type=LoggingMonitor,name=XXXMonitor; - nested throwable: (javax.management.MalformedObjectNameException: Key properties cannot be empty)
| at org.jboss.system.ServiceConfigurator.setAttribute(ServiceConfigurator.java:707)
| at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:332)
and
anonymous wrote : --- MBeans waiting for other MBeans ---
| ObjectName: jboss.monitor:type=LoggingMonitor,name=XXXMonitor
| State: FAILED
| Reason: org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@1eacdc4 on mbean jboss.monitor:type=LoggingMonitor,name=XXXMonitor; - nested throwable: (javax.management.MalformedObjectNameException: Key properties cannot be empty)
|
| --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
| ObjectName: jboss.monitor:type=LoggingMonitor,name=XXXMonitor
| State: FAILED
| Reason: org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@1eacdc4 on mbean jboss.monitor:type=LoggingMonitor,name=XXXMonitor; - nested throwable: (javax.management.MalformedObjectNameException: Key properties cannot be empty)
|
Pls help me to tackle the issue.
Regards,
Vinoth Kumar.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221833#4221833
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221833
15 years, 3 months
[JBossWS] - Re: No Content-type in the header
by gurkanerdogdu
Thanks for answer.
I have following jars in the endorsed library.
jbossws-native-jaxrpc.jar,-jaxws.jar, -jaxws-ext.jar, -saaj.jar,
Exception is : Exception in Thread main javax.xml.ws.WebServiceException :
No Content-type in the header
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java 163:)
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java
)
at com.sun.xml.ws.api.pipe.Fiber.__doRun
et.c....
I run the client in standalone mode in Eclipse. Actually, I am putting all the JBoss Client jars in to the class path.
Exactly, which jars that I have to setup in the client classpath to call webservice correctly?
Thanks a lot;
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221831#4221831
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221831
15 years, 3 months