[Design of POJO Server] - Re: Getting runtime component name from attachment
by alesj
This would/does produce a CCE with the current code:
In AbstractManagedObjectFactory.getValue
Property is not managed, so we resolve to a simple metattype
| if (managed)
| {
| TypeInfo typeInfo = propertyInfo.getType();
| if( typeInfo.isArray() || typeInfo.isCollection() )
| metaType = new ArrayMetaType(1, MANAGED_OBJECT_META_TYPE);
| else
| metaType = MANAGED_OBJECT_META_TYPE;
| }
| else
| {
| metaType = metaTypeFactory.resolve(propertyInfo.getType());
| }
|
And since metatype is not managed we push in simple value
| return metaValueFactory.create(value, propertyInfo.getType());
|
But on the ManagementViewImpl.processManagedObject
// See if this is a ManagementObjectRef
| ManagementObjectRef ref = (ManagementObjectRef) pannotations.get(ManagementObjectRef.class.getName());
| if ( ref != null )
| {
| // The reference key is the prop value + ref.type()
| log.debug("Property("+prop.getName()+") references: "+ref);
| SimpleValue refValue = (SimpleValue) prop.getValue();
| String refName = (String) refValue.getValue();
| if (refName == null)
| refName = ref.name();
| String targetKey = refName + "/" + ref.type();
|
refValue.getValue() is an Integer, since our property returned max-pool-size. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092882#4092882
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092882
18 years, 6 months
[Design of JBoss jBPM] - Re: [sim] language features
by kukeltje
1) Agreed, but having realistic scenario's is great.... something that often lacks so called 'load tests' And yes, more needs to be done, but I'd hate to have to do duplicate work... :-)
2) less readable... to a certain extend... yes.... but we have a lot more complex xml documents than a fairly decent jpdl process and imo not a real big problem
Regarding the proxy stuff, that can be easily handled when people configure their resolvers correctly (for JBoss it is even nothing more than dropping an xsd in a certain directory). But extending the jbpm resolver to allow custom schema's to be included (there is no need to always resolve this from the net) is fairly easy....
I even (in a local branch) extended jbpm in a way that people can add custom tags WITH a prefix in the jpdl and reference these via method calls in actions, the webpage or whatever. So a really generic extension.... including validation, completion etc... in the source of jpdl
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092870#4092870
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092870
18 years, 6 months
[Design of JBoss jBPM] - Re: [sim] language features
by camunda
1.) Use Simulation engine for load testing: Hmm, I am not really sure about this usage. Load testing normally involves some more sophisticated load generating strategy, for example with more than one computer. This is not addressed by the simulation engine at the moment, even if it could be, if simulation runs are too slow. But this would be stuff for the very far future ;-)
And you don't get real information about calculation time, because simulation time has nothing to do with real time. And all figures and logs refer only to the model time.
2.) The Namespaces: The old discussion :-) I can tell you, Ronald, why I don't like them: Because it gets less readable for the human. But I agree with you, that it is nice for validation and that stuff.
But to be honest: The most bigger jbpm projects I know remove the jpdl schema (because the add stuff themselves and don't use namespaces or, most faimous, they have a proxy in the company an eclipse can not access the http:... schema, which leads to waiting times while saveing the process. And the configuration property in eclipse is not well knwon. Or for completly other reasons).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092850#4092850
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092850
18 years, 6 months
[Design of JBoss Portal] - jboss-portal-2.6.2.GA run on Eclipse
by xjwqs2000
I want use MyEclipse run JBoss Portal + JBoss AS 4.2.1
when runtime error in MyEclipse
But I use run.bat is success
10:36:24,375 INFO [RepositoryImpl] initializing workspace 'default'...
10:36:26,546 INFO [RepositoryImpl] workspace 'default' initialized
10:37:23,593 ERROR [Scheduler$Listener] Invoke of the Schedulable MBean failed
javax.management.RuntimeErrorException
at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:178)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.varia.scheduler.Scheduler$MBeanListener.handleNotification(Scheduler.java:1346)
at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:153)
at $Proxy11.handleNotification(Unknown Source)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: java.lang.OutOfMemoryError: Java heap space
10:42:16,312 INFO [SettingsFactory] Generate SQL with comments: disabled
10:42:16,312 INFO [SettingsFactory] Order SQL updates by primary key: disabled
10:42:16,312 INFO [SettingsFactory] Order SQL inserts for batching: disabled
10:42:16,312 INFO [SettingsFactory] Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory
10:42:16,312 INFO [ASTQueryTranslatorFactory] Using ASTQueryTranslatorFactory
10:42:16,312 INFO [SettingsFactory] Query language substitutions: {}
10:42:16,312 INFO [SettingsFactory] JPA-QL strict compliance: disabled
10:42:19,437 ERROR [Scheduler$Listener] Invoke of the Schedulable MBean failed
javax.management.RuntimeErrorException
at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:178)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:163)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.varia.scheduler.Scheduler$MBeanListener.handleNotification(Scheduler.java:1346)
at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:153)
at $Proxy11.handleNotification(Unknown Source)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: java.lang.OutOfMemoryError: Java heap space
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092821#4092821
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092821
18 years, 6 months