September 2006 - jboss-dev-forums

by bogdan.sulima

Here you will find description of the elements which can be managed via xmlaccess. "http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/topic/com.ibm.wp.ent...." After a few days working with jboss portal i still missing xsd or dtd for confgiuration files. What the exported configuration going to look like - do we really want to export many different configuration files (object.xml, instances.xml, jboss-portlet.xml and so on)? I like "all-in-one-file" solution for export/import. When portlet is deployed, it can be still configured with multiple files. Admins also need some way to trace import/export failures or warnings. Separate responce file (can be configured with jboss app server logging) (might be olso one responce file per import/export activity) can be used to achieve this - i am not happy with the current console logging. It would be cool to perform import/export via the admin portlet. Each content node can get an "export" button that exports configuration of the selected portal node, child objects (pages, windows) and objects the node depends on (portlet instances, layout). As portal role-based administration evolves, kind of configuration changes log is required - we need to know "who-what-when" changes portal configuration. p.s.: lets define some sticky name for xml import interface. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973473#3973473 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973473

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by tom.elrod＠jboss.com

Ron, you can use one of the Client.addListener() methods that supports uni-directional callback polling (which will simulate push callbacks by using internal polling for uni-directional transports). Can use the same method when using bi-directional transport (for true push callbacks on same socket connection), so there is no code change needed when switching transports (i.e. from http to multiplex). The javadoc explains which addListener() methods would be best fit (see http://labs.jboss.com/portal/jbossremoting/docs/api/org/jboss/remoting/Cl...). These methods were added in May per request from the messaging team (http://jira.jboss.com/jira/browse/JBREM-363). Can also take a look at org.jboss.test.remoting.callback.push.unidirectional.CallbackPollTestClient to see it in use. For the uni-directional transports, probably the only config that you will want to consider is callbackPollPeriod (org.jboss.remoting.callback.CallbackPoller.CALLBACK_POLL_PERIOD), for setting how often client should poll for callback messages internally. As for type of streams being passed to marshalling layer, I would still be willing to change the remoting code (socket invoker in particular) so that marshalling layer is never passed an object stream but just the raw stream. However, this seems to be the opposite of what asked for in http://jira.jboss.com/jira/browse/JBREM-371. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973466#3973466 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973466

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-549 - Lease set to -1 causes exception

by tom.elrod＠jboss.com

To make things a little simplier, do you think it would be useful to add another method such as: void setLeaseEnabled(boolean) If call setLeaseEnabled(boolean) passed false and are current lease session, will clean them up. If passed true, will accept lease sessions even if no connection listeners (will just have no one to notify). Also, if try to call setLeasePeriod(long period) with number < 0, will throw an exception. Although a little more blunt in how things are handled, is much simplier from user API perspective. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973453#3973453 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973453

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - JBMESSAGING-545 - Leaks on XA transactions

by clebert.suconic＠jboss.com

as stated on http://jira.jboss.org/jira/browse/JBMESSAGING-545 two phase commit transactions are leaking once they are being stored on TransactionRepository and not being released. So, summarizing the changes I'm making to fix this: I - I'm creating a method deleteTransaction on TransactionRepository. II - I also changed Transaction to accept a reference to TransactionRepository, as TransactionRepository is not static. III - On commit/rollback transactionRepository.delete is being called IV - Changed JDBCPersistenceManagerTest to perform a test on this V - Added a property method getNumberOfRegisteredTransactions() on TransactionRepository what is meant to be used only by tests. (I could use reflection on a private field for this, but I thought it was much cleaner to just add the property field. I could change this if someone doesn't like the exposed property) Clebert Suconic View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973448#3973448 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973448

19 years, 6 months

1
0
0 / 0

[Design of Kosmos] - Re: Kosmos portlet page is empty

by joewilliams

I am new to Jboss portal system and I am trying to run KOSMOS. Looks like I have deployed kosmos successfully but I don?t see any pages, the same error as stated Cannot render , Object not found ,JBossSvnMonitoringPortletInstance and so on?. So as suggested I logged into admin page and added a page manually under Kosmos. but then I don?t know what to do next, how do I configure it.... when I clicked on the Preview link on my page it shows a new page but when I do that to the rest of the kosmos page I get a 404 error. Any help would be appreciated... Cheers Joe View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973436#3973436 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973436

19 years, 6 months

1
0
0 / 0

[Design of JBossCache] - Re: Designing Habanero - Configuration changes

by galder.zamarreno＠jboss.com

Maybe. I don't see an easy, not-complex solution here. The easiest would be to allow only adding at the beginning or the end. Trying to modify the stack itself without actually re-writting the way the customer wants would lead to errors, specially if they have to enter the position in the stack where to put the interceptor. So, in my opinion, either add at start or end, or if you want to modify the core stack, rewrite the way you want which would be the most flexible option giving full capacity to do any additions, removals or replacements in the core stack. What do the rest think? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973429#3973429 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973429

19 years, 6 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - java.lang.NoClassDefFoundError: com/inprise/vbroker/CORBA/Ob

by dalingxu

I am deploying a EJB/Web Service application on JBoss 4.0.4GA, using JVM 1.5.0_04, after the deploy finished, the system throws this exception: java.lang.NoClassDefFoundError: com/inprise/vbroker/CORBA/Object I attached the more detailed stack trace at end of this message. I looked for some solutions: (1) Some one suggested using JVM1.4, that's not an option for me because I am deploying an exsiting huge project, and the code source is conform with jdk1.5 (2) Weird thing is the app deploys and runs no problem on OC4J10.1.2 Any idea? Thanks! Error Stack trace: java.lang.NoClassDefFoundError: com/inprise/vbroker/CORBA/Object at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1812) at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:866) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1319) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1198) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2328) at java.lang.Class.getConstructor0(Class.java:2640) at java.lang.Class.newInstance0(Class.java:321) at java.lang.Class.newInstance(Class.java:303) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1055) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3917) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4201) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) 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:585) at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.apache.catalina.core.StandardContext.init(StandardContext.java:5116) 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:585) at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371) at org.jboss.web.WebModule.startModule(WebModule.java:83) at org.jboss.web.WebModule.startService(WebModule.java:61) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973413#3973413 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973413

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by ovidiu.feodorov＠jboss.com

OK, let's make this simple. Ron, these are the requirements: 1. The messaging client needs to connect to the server over HTTP 2. We need it implemented in such a way that there's no socket listening on the client, but the client can still receive messages asynchronously. 3. When the change is completed, all current Messaging functional tests, stress tests and smoke test must pass. We have: - Remoting - Current Messaging code base Do whatever you think it's necessary, in your work area, to make the above requirements a reality. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973405#3973405 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973405

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by ron_sigal

"timfox" wrote : What I was expecting is if I make an invocation from the server to the client as is currently the case for delivering messages to clients, then the http transport is clever enough to realise it is only allowed to make invocations from client to server, so uses some kind of polling mechanism to get messages from server to client. Here's the call on the server side that calls the callback server on the client side. It's in ServerConsumerEndpoint.Deliver.run(): anonymous wrote : | MessagingMarshallable resp = (MessagingMarshallable)connection.getCallbackClient().invoke(mm); | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973403#3973403 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973403

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by ron_sigal

"timfox" wrote : One of the selling points of remoting was that we could use the remoting API in a consistent way irrespective of the transport which was plugged in. | | This clearly appears not to be the case with the HTTP transport. As far as I can see, "push callbacks" are currently being done with the socket transport, but they're not Remoting "push callbacks". If I remember correctly, somewhere on the server side there is an explicit call to org.jboss.remoting.Client.invoker(). There shouldn't be any distinction in the way the socket and http transports handle this behavior. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973396#3973396 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973396

19 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums September 2006