[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1255) memory leak after 7 hours
[ http://jira.jboss.com/jira/browse/JBAS-1255?page=comments#action_12314523 ] Alex Loubyansky commented on JBAS-1255: --- What does the following mean? In stable JBoss 4.0.1, there is no 3.5 (or 7) hours long constant-memory-use period. If it's really CMP related, I assume I should see the leak if I remove all the MDB stuff and just create and delete entity instances. Is there a chance you can confirm this? Thanks. memory leak after 7 hours - Key: JBAS-1255 URL: http://jira.jboss.com/jira/browse/JBAS-1255 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.0 Final Reporter: SourceForge User Assignee: Alex Loubyansky SourceForge Submitter: atomrom . Hi, I have experienced strange memory leaks under JBoss 4.0.0 after 7 hours, and under JBoss 4.0.1RC2 after 3.5 hours running my application. (In the first 7 hours my application consumes 100M of memory under 4.0.0, however after 7 hours the memory consumption raises lineraly). I used YourKit to detect the memory leak and I found that the memory is chiefly occupied by HashMap and entity bean proxies. Unfortunately I cannot provide source code, but I can give a short description of the component architecture and functioning: (a) objects are inserted into a messaging topic (b) an MDB receives the objects and: (b.i) dispaches them to a resource adapter (the RA sends the object over the network) (b.ii) creates a database entry using the String(s) returned by the RA (a tuple looks like this: [String: id, Date: date, String: st]; I'm using a CMP entity bean) (c) a timer periodically removes the overaged database entries (see date). ejbTimeout is implemented by a stateless session bean, database entries are removed by the corresponding CMP entity bean (d) whenever the RA receives an object over the network, it dispatches it to a stateless session bean, which is registered as an endpoint at the RA (e) the stateless session bean (e.i) updates the database entry (using the ), or more precisely, its st field (e.ii) inserts a new database entry (e.iii) if the st field statisfies certain conditions, removes both the inserted and updated entries Additional infos: * OS: RedHat AS (running on various hardware, e.g. simple PC and a 4 processor Xeon server) * JDK: jdk1.4.5 * I see lot of log messages regarding rolled back transactions (because of timeouts); these exceptions are thrown in the CMP entity bean in that method, which removes the overaged entries. After a findByDate I iterate over the resulting collection and when I want to access id, an exception is thrown. Not always, but strangely often. * the memory leak emerges after 7 (or 3.5) hours regardless the load, and configuration. The load influences only the gradient of the lineraly increasing (and therefore deadly) period. Merry Christmas, Mormota -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBXB-3) Refactoring of public API
[ http://jira.jboss.com/jira/browse/JBXB-3?page=history ]
Alex Loubyansky updated JBXB-3:
---
Attachment: JBossXB_API_Refactoring.txt
JBossXB_API_Refactoring.xls
Most of it is done. Attached are modules and files affected with comments.
Refactoring of public API
-
Key: JBXB-3
URL: http://jira.jboss.com/jira/browse/JBXB-3
Project: JBoss XML Binding (JBossXB)
Type: Task
Reporter: Alex Loubyansky
Assignee: Alex Loubyansky
Attachments: JBossXB_API_Refactoring.txt, JBossXB_API_Refactoring.xls
Sorry, I think I should do it earlier than later. I will search for the
usages and fix them in jboss-head and microkernel.
This is a preliminary plan. If you have any suggestions, please, add a
comment. Thanks.
* add interface NamespaceResolver { String resolveNamespace(String prefix); }
* interface ContentNavigator
- rename to UnmarshallingContext or something like this
- remove resolveQName method (this is TypeBinding.unmarshalQName() which is
more general)
- add method 'NamespaceResolver getNamespaceResolver()'
- add methods to get annotations for the current element
* add interface MarshallingContext (equivalent to UnmarshallingContext) to
ObjectModelProvider methods to get access to contextual info such as
element/attribute's type, annotations, etc
* interface GenericObjectModelFactory
- move completedRoot method to ObjectModelFactory and rename it to
completeRoot
* interface TypeConverter
- rename to TypeBinding (?)
* class TypeBinding
- rename to SimpleTypeBindings
- change unmarshal(String xsdType, String value) to unmarshal(String
xsdType, String value, NamespaceResolver nsResolver)
- change marshal(String xsdType, Object value) to marshal(String xsdType,
Object value, NamespaceResolver nsResolver)
* class Unmarshaller
- rename to UnmarshallerImpl (or something) and expose Unmarshaller
interface (Marshaller is already an interface)
- add a factory for Unmarshaller instances, e.g.
UnmarshallerFactory.getUnmarshaller(/*Properties props*/);
- remove explicit JBossXBParser creation and configuration. Instead add
get/setParser methods, if not set use parser factory to get default instance
with default properties.
- remove Object unmarshal(InputSource is, ObjectModelFactory factory,
Object root)
* add a factory for Marshaller instances, e.g.
MarshallerFactory.getMarshaller(/*Properties props*/);
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBXB-3) Refactoring of public API
Refactoring of public API
-
Key: JBXB-3
URL: http://jira.jboss.com/jira/browse/JBXB-3
Project: JBoss XML Binding (JBossXB)
Type: Task
Reporter: Alex Loubyansky
Assigned to: Alex Loubyansky
Sorry, I think I should do it earlier than later. I will search for the usages
and fix them in jboss-head and microkernel.
This is a preliminary plan. If you have any suggestions, please, add a comment.
Thanks.
* add interface NamespaceResolver { String resolveNamespace(String prefix); }
* interface ContentNavigator
- rename to UnmarshallingContext or something like this
- remove resolveQName method (this is TypeBinding.unmarshalQName() which is
more general)
- add method 'NamespaceResolver getNamespaceResolver()'
- add methods to get annotations for the current element
* add interface MarshallingContext (equivalent to UnmarshallingContext) to
ObjectModelProvider methods to get access to contextual info such as
element/attribute's type, annotations, etc
* interface GenericObjectModelFactory
- move completedRoot method to ObjectModelFactory and rename it to
completeRoot
* interface TypeConverter
- rename to TypeBinding (?)
* class TypeBinding
- rename to SimpleTypeBindings
- change unmarshal(String xsdType, String value) to unmarshal(String xsdType,
String value, NamespaceResolver nsResolver)
- change marshal(String xsdType, Object value) to marshal(String xsdType,
Object value, NamespaceResolver nsResolver)
* class Unmarshaller
- rename to UnmarshallerImpl (or something) and expose Unmarshaller interface
(Marshaller is already an interface)
- add a factory for Unmarshaller instances, e.g.
UnmarshallerFactory.getUnmarshaller(/*Properties props*/);
- remove explicit JBossXBParser creation and configuration. Instead add
get/setParser methods, if not set use parser factory to get default instance
with default properties.
- remove Object unmarshal(InputSource is, ObjectModelFactory factory, Object
root)
* add a factory for Marshaller instances, e.g.
MarshallerFactory.getMarshaller(/*Properties props*/);
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-14) CompleteUnitTestCase fails under java5
[ http://jira.jboss.com/jira/browse/JBAS-14?page=comments#action_12310868 ] Alex Loubyansky commented on JBAS-14: - These tests are bad as they report failures when generated queries are in fact correct from the data fetching point of view. The problem is that you can't predict the exact order of a sequence of conjunctions/disjunctions in the WHERE clause, tables in the FROM clause, etc. So, in general, if these tests pass it's a luck. CompleteUnitTestCase fails under java5 -- Key: JBAS-14 URL: http://jira.jboss.com/jira/browse/JBAS-14 Project: JBoss Application Server Type: Bug Versions: JBossAS-4.0.1 Final Environment: 13:35:08,406 INFO [Server] Starting JBoss (MX MicroKernel)... 13:35:08,406 INFO [Server] Release ID: JBoss [Zion] 4.0.1RC2 (build: CVSTag=Branch_4_0 date=200411271821) 13:35:08,406 INFO [Server] Home Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2 13:35:08,406 INFO [Server] Home URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/ 13:35:08,406 INFO [Server] Library URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/lib/ 13:35:08,406 INFO [Server] Patch URL: null 13:35:08,406 INFO [Server] Server Name: all 13:35:08,406 INFO [Server] Server Home Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2\server\all 13:35:08,421 INFO [Server] Server Home URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/server/all/ 13:35:08,421 INFO [Server] Server Data Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2\server\all\data 13:35:08,421 INFO [Server] Server Temp Dir: C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.0.1RC2\server\all\tmp 13:35:08,421 INFO [Server] Server Config URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/server/all/conf/ 13:35:08,421 INFO [Server] Server Library URL: file:/C:/cvs/JBoss4.0/jboss-4.0/build/output/jboss-4.0.1RC2/server/all/lib/ 13:35:08,421 INFO [Server] Root Deployment Filename: jboss-service.xml 13:35:08,421 INFO [Server] Starting General Purpose Architecture (GPA)... 13:35:08,937 INFO [ServerInfo] Java version: 1.5.0,Sun Microsystems Inc. 13:35:08,937 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0-b64,Sun Microsystems Inc. 13:35:08,937 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 Reporter: Scott M Stark Assignee: Alex Loubyansky When running the org.jboss.test.cmp2.commerce.CompleteUnitTestCase test under java5 there are two failures related to query expecation failures: Suite: org.jboss.test.cmp2.commerce.CompleteUnitTestCase Test:testJBossQL Type:failure Exception: net.sourceforge.junitejb.RemoteAssertionFailedError Message: Expected: SELECT t0_o1.ORDER_NUMBER FROM ORDER_DATA t0_o1, ORDER_DATA t3_o2, CUSTOMEREJB t1_o1_customer, CUSTOMEREJB t2_o2_customer WHERE (( NOT (t1_o1_customer.id=t2_o2_customer.id)) AND (t0_o1.CC_TYPE=t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME=t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI=t3_o2.CC_MI AND t0_o1.CC_LAST_NAME=t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP=t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER=t3_o2.CC_CARD_NUMBER) AND t0_o1.customer=t1_o1_customer.id AND t3_o2.customer=t2_o2_customer.id) but got: SELECT t0_o1.ORDER_NUMBER FROM ORDER_DATA t0_o1, ORDER_DATA t3_o2, CUSTOMEREJB t2_o2_customer, CUSTOMEREJB t1_o1_customer WHERE (( NOT (t1_o1_customer.id=t2_o2_customer.id)) AND (t0_o1.CC_TYPE=t3_o2.CC_TYPE AND t0_o1.CC_FIRST_NAME=t3_o2.CC_FIRST_NAME AND t0_o1.CC_MI=t3_o2.CC_MI AND t0_o1.CC_LAST_NAME=t3_o2.CC_LAST_NAME AND t0_o1.CC_BILLING_ZIP=t3_o2.CC_BILLING_ZIP AND t0_o1.CC_CARD_NUMBER=t3_o2.CC_CARD_NUMBER) AND t3_o2.customer=t2_o2_customer.id AND t0_o1.customer=t1_o1_customer.id) - Suite: org.jboss.test.cmp2.commerce.CompleteUnitTestCase Test:testEJBQL Type:failure Exception: net.sourceforge.junitejb.RemoteAssertionFailedError Message: expected:...0_o.ORDER_NUMBER=t4_l.ORDER_NUMBER AND t6_l_product.id=t5_l_product_productCategories_R.PRODUCT_ID AND t1_pc.id=t5_l_product_productCategories_R.PRODUCT_CATEGORY_ID AND t1_pc.subId=t5_l_product_productCategories_R.PRODUCT_CATEGORY_SUBID AND t4_l.product=t6_l_product.id but was:...6_l_product.id=t5_l_product_productCategories_R.PRODUCT_ID AND t1_pc.id=t5_l_product_productCategories_R.PRODUCT_CATEGORY_ID AND t1_pc.subId=t5_l_product_productCategories_R.PRODUCT_CATEGORY_SUBID AND t4_l.product=t6_l_product.id AND t0_o.ORDER_NUMBER=t4_l.ORDER_NUMBER - -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-277) datetime as PK doesn't work in 3.0.3
[ http://jira.jboss.com/jira/browse/JBAS-277?page=comments#action_12311336 ] Alex Loubyansky commented on JBAS-277: -- Logged In: YES user_id=543482 I coudn't reproduce it. - Composite pk with VARCHAR and TIMESTAMP; - create 10 records; - findAll records and remove each one iterating through all. - Branch_3_0. Could you provide a test-case or more details? datetime as PK doesn't work in 3.0.3 Key: JBAS-277 URL: http://jira.jboss.com/jira/browse/JBAS-277 Project: JBoss Application Server Type: Bug Components: CMP service Reporter: SourceForge User Assignee: Alex Loubyansky Priority: Critical SourceForge Submitter: softwaremasters . OS: Win2K JDK: 1.4 DBMS: MS SQL Server 7.0 JBoss version: 3.0.3 I have a table with a composite primary key consisting of a varchar column and a datetime column. I tried to remove all rows in the table by doing a findAll() and then iterate through the list and remove each bean. JBoss complained that these beans cannot be found. Tried changing the JDBC type for java.util.Date in standardjaws.xml and standardjbosscmp-jdbc.xml from DATE to TIMESTAMP but got the same results. This is the exception generated on the server side: 06:32:36,564 ERROR [LogInterceptor] TransactionRolledbackLocalException, causedBy: javax.ejb.NoSuchObjectLocalException: Entity not found: primaryKey=[.my.machine. Fri Oct 04 10:32:32 EDT 2002.] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext (AbstractTxInterceptor.java:181) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti ons(TxInterceptorCMT.java:178) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke (TxInterceptorCMT.java:60) at org.jboss.ejb.plugins.SecurityInterceptor.invoke (SecurityInterceptor.java:130) at org.jboss.ejb.plugins.LogInterceptor.invoke (LogInterceptor.java:203) at org.jboss.ejb.EntityContainer.invoke (EntityContainer.java:493) at org.jboss.ejb.plugins.local.BaseLocalContainerInvoker.inv oke(BaseLocalContainerInvoker.java:301) at org.jboss.ejb.plugins.local.EntityProxy.invoke (EntityProxy.java:38) at $Proxy54.getStateMachine(Unknown Source) at com.macronetics.wf.ejb.StateMachineManagerBean.get ActiveVersion(StateMachineManagerBean.java:110) 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:324) at org.jboss.ejb.StatelessSessionContainer$ContainerInterc eptor.invoke(StatelessSessionContainer.java:660) at org.jboss.resource.connectionmanager.CachedConnectio nInterceptor.invoke (CachedConnectionInterceptor.java:186) at org.jboss.ejb.plugins.StatelessSessionInstanceIntercept or.invoke(StatelessSessionInstanceInterceptor.java:77) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext (AbstractTxInterceptor.java:107) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti ons(TxInterceptorCMT.java:178) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke (TxInterceptorCMT.java:60) at org.jboss.ejb.plugins.SecurityInterceptor.invoke (SecurityInterceptor.java:130) at org.jboss.ejb.plugins.LogInterceptor.invoke (LogInterceptor.java:203) at org.jboss.ejb.StatelessSessionContainer.invoke (StatelessSessionContainer.java:313) at org.jboss.ejb.Container.invoke (Container.java:712) at org.jboss.mx.server.MBeanServerImpl.invoke (MBeanServerImpl.java:517) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke (JRMPInvoker.java:381) at sun.reflect.GeneratedMethodAccessor29.invoke (Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at sun.rmi.server.UnicastServerRef.dispatch (UnicastServerRef.java:261) at sun.rmi.transport.Transport$1.run (Transport.java:148) at java.security.AccessController.doPrivileged (Native Method) at sun.rmi.transport.Transport.serviceCall (Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages (TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.r un(TCPTransport.java:701) at java.lang.Thread.run(Thread.java:536) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-32) Exception is thrown when removing entity with null/invalid CMR value
[ http://jira.jboss.com/jira/browse/JBAS-32?page=comments#action_12310751 ] Alex Loubyansky commented on JBAS-32: - If this is the case, how do I make CMR work for child 4? Either set the foreign key to null or create a parent with pk 3. I was thinking the fk-constraint tag in the DD tells the container to check data integrity for all operations (i.e. insert, update and delete). fk-constraint tag is used only for database schema generation, i.e. it indicates whether the foreign key constraint should be created when JBossCMP creates tables. Why not the container just removes child 4 when there is no cascade-delete requirement? Because before removal, the instance should be removed from all the container managed relationships it participates in. The indicator of existing relationship is non-null foreign key value. Exception is thrown when removing entity with null/invalid CMR value Key: JBAS-32 URL: http://jira.jboss.com/jira/browse/JBAS-32 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.0 Final, JBossAS-3.2.6 Final Reporter: Sonnel Pun Assignee: Scott M Stark Let's look at the following example. T_Parent == (pk) -- 1 2 T_Child == (pk) (fk) -- 1 1 2 1 3 null 4 3 Let say, table T_Child and T_Parent have a 1-M relationship. This relationship is modelled using CMR such that, no fk constraint and cascade delete is required. It is fine when removing the record 1 and 2 from T_Child but when removing records 3 and 4, exception is thrown. Here is the stack trace -- 16:00:37,108 ERROR [LogInterceptor] TransactionRolledbackLocalException in method: null, causedBy: javax.ejb.NoSuchObjectLocalException: Entity not found: primaryKey=[.0.] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:182) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:342) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:149) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:128) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122) at org.jboss.ejb.EntityContainer.internalInvoke(EntityContainer.java:514) at org.jboss.ejb.Container.invoke(Container.java:854) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.invokeRemoveRelation(JDBCCMRFieldBridge.java:1211) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.destroyRelationLinks(JDBCCMRFieldBridge.java:1026) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.destroyRelationLinks(JDBCCMRFieldBridge.java:1012) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.destroyRelationLinks(JDBCCMRFieldBridge.java:996) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.setInstanceValue(JDBCCMRFieldBridge.java:890) at org.jboss.ejb.plugins.cmp.jdbc.CascadeDeleteStrategy$NoneCascadeDeleteStrategy.removedIds(CascadeDeleteStrategy.java:52) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.removeFromRelations(JDBCCMRFieldBridge.java:393) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.removeFromRelations(JDBCEntityBridge.java:308) at org.jboss.ejb.plugins.cmp.jdbc.JDBCRemoveEntityCommand.execute(JDBCRemoveEntityCommand.java:91) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.removeEntity(JDBCStoreManager.java:682) at org.jboss.ejb.plugins.CMPPersistenceManager.removeEntity(CMPPersistenceManager.java:506) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.removeEntity(CachedConnectionInterceptor.java:454) at org.jboss.ejb.EntityContainer.remove(EntityContainer.java:530) 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:324) at org.jboss.invocation.Invocation.performCall(Invocation.java:345) at org.jboss.ejb.EntityContainer$ContainerInterceptor.invoke(EntityContainer.java:1159) at org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor.invoke(JDBCRelationInterceptor.java:72) at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynchronizationInterceptor.java:273) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-32) Exception is thrown when removing entity with null/invalid CMR value
[ http://jira.jboss.com/jira/browse/JBAS-32?page=history ] Alex Loubyansky closed JBAS-32: --- Assign To: Alex Loubyansky (was: Scott M Stark) Resolution: Rejected Not a JBoss issue. Exception is thrown when removing entity with null/invalid CMR value Key: JBAS-32 URL: http://jira.jboss.com/jira/browse/JBAS-32 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-4.0.0 Final, JBossAS-3.2.6 Final Reporter: Sonnel Pun Assignee: Alex Loubyansky Let's look at the following example. T_Parent == (pk) -- 1 2 T_Child == (pk) (fk) -- 1 1 2 1 3 null 4 3 Let say, table T_Child and T_Parent have a 1-M relationship. This relationship is modelled using CMR such that, no fk constraint and cascade delete is required. It is fine when removing the record 1 and 2 from T_Child but when removing records 3 and 4, exception is thrown. Here is the stack trace -- 16:00:37,108 ERROR [LogInterceptor] TransactionRolledbackLocalException in method: null, causedBy: javax.ejb.NoSuchObjectLocalException: Entity not found: primaryKey=[.0.] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:182) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:342) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:149) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:128) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122) at org.jboss.ejb.EntityContainer.internalInvoke(EntityContainer.java:514) at org.jboss.ejb.Container.invoke(Container.java:854) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.invokeRemoveRelation(JDBCCMRFieldBridge.java:1211) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.destroyRelationLinks(JDBCCMRFieldBridge.java:1026) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.destroyRelationLinks(JDBCCMRFieldBridge.java:1012) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.destroyRelationLinks(JDBCCMRFieldBridge.java:996) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.setInstanceValue(JDBCCMRFieldBridge.java:890) at org.jboss.ejb.plugins.cmp.jdbc.CascadeDeleteStrategy$NoneCascadeDeleteStrategy.removedIds(CascadeDeleteStrategy.java:52) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.removeFromRelations(JDBCCMRFieldBridge.java:393) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.removeFromRelations(JDBCEntityBridge.java:308) at org.jboss.ejb.plugins.cmp.jdbc.JDBCRemoveEntityCommand.execute(JDBCRemoveEntityCommand.java:91) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.removeEntity(JDBCStoreManager.java:682) at org.jboss.ejb.plugins.CMPPersistenceManager.removeEntity(CMPPersistenceManager.java:506) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.removeEntity(CachedConnectionInterceptor.java:454) at org.jboss.ejb.EntityContainer.remove(EntityContainer.java:530) 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:324) at org.jboss.invocation.Invocation.performCall(Invocation.java:345) at org.jboss.ejb.EntityContainer$ContainerInterceptor.invoke(EntityContainer.java:1159) at org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor.invoke(JDBCRelationInterceptor.java:72) at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynchronizationInterceptor.java:273) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:185) at org.jboss.ejb.plugins.EntityReentranceInterceptor.invoke(EntityReentranceInterceptor.java:111) at org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:211) at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:89) at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInterceptor.java:53) at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:48) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:105
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-32) Exception is thrown when removing entity with null/invalid CMR value
[ http://jira.jboss.com/jira/browse/JBAS-32?page=comments#action_12310736 ] Alex Loubyansky commented on JBAS-32: - Child 4 references non-existing parent 3. So it is expected to fail. Child 3 should be removed successfully. What is the code and deployment descriptors for Child and Parent? Thanks. Exception is thrown when removing entity with null/invalid CMR value Key: JBAS-32 URL: http://jira.jboss.com/jira/browse/JBAS-32 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-3.2.6 Final, JBossAS-4.0.0 Final Reporter: Sonnel Pun Assignee: Scott M Stark Let's look at the following example. T_Parent == (pk) -- 1 2 T_Child == (pk) (fk) -- 1 1 2 1 3 null 4 3 Let say, table T_Child and T_Parent have a 1-M relationship. This relationship is modelled using CMR such that, no fk constraint and cascade delete is required. It is fine when removing the record 1 and 2 from T_Child but when removing records 3 and 4, exception is thrown. Here is the stack trace -- 16:00:37,108 ERROR [LogInterceptor] TransactionRolledbackLocalException in method: null, causedBy: javax.ejb.NoSuchObjectLocalException: Entity not found: primaryKey=[.0.] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:182) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:342) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:149) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:128) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122) at org.jboss.ejb.EntityContainer.internalInvoke(EntityContainer.java:514) at org.jboss.ejb.Container.invoke(Container.java:854) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.invokeRemoveRelation(JDBCCMRFieldBridge.java:1211) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.destroyRelationLinks(JDBCCMRFieldBridge.java:1026) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.destroyRelationLinks(JDBCCMRFieldBridge.java:1012) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.destroyRelationLinks(JDBCCMRFieldBridge.java:996) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.setInstanceValue(JDBCCMRFieldBridge.java:890) at org.jboss.ejb.plugins.cmp.jdbc.CascadeDeleteStrategy$NoneCascadeDeleteStrategy.removedIds(CascadeDeleteStrategy.java:52) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.removeFromRelations(JDBCCMRFieldBridge.java:393) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.removeFromRelations(JDBCEntityBridge.java:308) at org.jboss.ejb.plugins.cmp.jdbc.JDBCRemoveEntityCommand.execute(JDBCRemoveEntityCommand.java:91) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.removeEntity(JDBCStoreManager.java:682) at org.jboss.ejb.plugins.CMPPersistenceManager.removeEntity(CMPPersistenceManager.java:506) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.removeEntity(CachedConnectionInterceptor.java:454) at org.jboss.ejb.EntityContainer.remove(EntityContainer.java:530) 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:324) at org.jboss.invocation.Invocation.performCall(Invocation.java:345) at org.jboss.ejb.EntityContainer$ContainerInterceptor.invoke(EntityContainer.java:1159) at org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor.invoke(JDBCRelationInterceptor.java:72) at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntitySynchronizationInterceptor.java:273) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:185) at org.jboss.ejb.plugins.EntityReentranceInterceptor.invoke(EntityReentranceInterceptor.java:111) at org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:211) at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockInterceptor.java:89) at org.jboss.ejb.plugins.EntityCreationInterceptor.invoke(EntityCreationInterceptor.java:53) at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-28) CacheInvalidator(3.2.7RC1 jdbc2) complains alot, why?
[ http://jira.jboss.com/jira/browse/JBAS-28?page=comments#action_12310701 ] Alex Loubyansky commented on JBAS-28: - The warning means that the entry is not in the cache. For the 'idle' machine it's ok since it might not have the entry in the cache. In this case, it's safe to ignore this message and the log level should be DEBUG or TRACE. For the machine doing the work, it seems like it tried to remove the entry from the cache more than once. First of all, a question for you whether it makes sense for your application? (if no, just don't make the cache invalidable) Second, there was an issue, i.e. an entry was invalidated as many times as the number of invocations on the instance was done in the tx. But I thought I fixed it with 'use transaction local instead of custom impl of the concept; also each key is invalidated now only once at commit, not as many times as the instance was invoked (missed call to synchronizations.put() in previous implementation)' http://cvs.sourceforge.net/viewcvs.py/jboss/jboss/src/main/org/jboss/cache/invalidation/InvalidationsTxGrouper.java?r1=1.1.2.5r2=1.1.2.6 If you can debug it, please, do. CacheInvalidator(3.2.7RC1 jdbc2) complains alot, why? - Key: JBAS-28 URL: http://jira.jboss.com/jira/browse/JBAS-28 Project: JBoss Application Server Type: Bug Components: CMP service Versions: JBossAS-3.2.7 Environment: 3.2.7 jdbc2 with Cache Invalidation(JMS) Oracle 9i SonicMQ Win 2000 Pro JDK1.4 2 Jboss instances(1 doing work, 1 sitting idle recieving cache invalidation messages) Reporter: Ivan O. Parra Assignee: Scott M Stark We keep seeing these warning in our log files. Quote: jvm 1 | 11:19:31,671 WARN [CacheInvalidator] removal of 466 rejected for null: the entry could not be found and Quote: jvm 1 | 11:17:13,859 WARN [CacheInvalidator] removal of 1 rejected for TransactionImpl:XidImpl [FormatId=257, GlobalId=scale-server2//10163, BranchQual=]: the entry could not be found So what is this and how do I get rid of it? Other things I notice: 1) The invalidator with the null transaction is not referenceing this data. IE. This particular machine has not accessed that table/row (yet). This is the idle machine. 2) The invalidator with the defined transaction is shown more than once(some times once, sometimes 3-4 times). What I think may be happening. 1) The cache is being invalidation by the InvalidationManager on the global cache that has not been set. 2) On commit of a modified row, multiple removes aer being called on the same transaction. If only one call is done, it works. But if multiple removes for the same transaction is done, this warning appears. I can throw into debugger to confirm both scenarios. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBXB-2) Xni parser has problems with short form tags
[ http://jira.jboss.com/jira/browse/JBXB-2?page=history ] Alex Loubyansky resolved JBXB-2: Resolution: Done This should be fixed now. XNI includes also emptyElement callback (which was misused) in addition to start/endElement. SAX-based parser should be avoided as it does not provide contextual information about the element being parsed other than uri, local name, qname. Which was the reason to implement parser based on XNI. Please, check that your code runs w/o issues now. Are there tests I could run to make sure I don't break anything next time? Xni parser has problems with short form tags Key: JBXB-2 URL: http://jira.jboss.com/jira/browse/JBXB-2 Project: JBoss XML Binding (JBossXB) Type: Bug Environment: jboss-head Reporter: Adrian Brock Assignee: Alex Loubyansky The new Xni parser does not emit endElement() notifications for tags of the form mytag/ rather than mytag/mytag where it does. This means the stack of accepted elements gets out of step with the end element notifications. I've switched back to the Sax parser in the Unmarshaller as the default in jboss-head to avoid this problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBXB-2) Xni parser has problems with short form tags
[ http://jira.jboss.com/jira/browse/JBXB-2?page=history ] Alex Loubyansky closed JBXB-2: -- closed Xni parser has problems with short form tags Key: JBXB-2 URL: http://jira.jboss.com/jira/browse/JBXB-2 Project: JBoss XML Binding (JBossXB) Type: Bug Environment: jboss-head Reporter: Adrian Brock Assignee: Alex Loubyansky The new Xni parser does not emit endElement() notifications for tags of the form mytag/ rather than mytag/mytag where it does. This means the stack of accepted elements gets out of step with the end element notifications. I've switched back to the Sax parser in the Unmarshaller as the default in jboss-head to avoid this problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] HEAD: Instance Per Transaction container
Something went wrong with Instance Per Transaction CMP2.x EntityBean conatiner configuration in HEAD. I found that at least one-to-many relationships are not working currently. Attempt to set relationship results in an exception (snippet below). I haven't looked at it yet. Did anyone do something related to it recently? alex java.lang.IllegalStateException: A CMR field cannot be set or added to a relatio nship in ejbCreate; this should be done in the ejbPostCreate method instead [EJB 2.0 Spec. 10.5.2]. at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMRFieldBridge.addRelation( JDBCCMRFieldBridge.java:892) at org.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor.invoke(JDBCRel ationInterceptor.java:74) at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntityS ynchronizationInterceptor.java:248) at org.jboss.ejb.plugins.EntityReentranceInterceptor.invoke(EntityReentr anceInterceptor.java:54) at org.jboss.ejb.plugins.EntityMultiInstanceInterceptor.invoke(EntityMul tiInstanceInterceptor.java:65) at org.jboss.ejb.plugins.EntityLockInterceptor.invoke(EntityLockIntercep tor.java:57) at org.jboss.ejb.entity.EntityInterceptor.invoke(EntityInterceptor.java: 268) --- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBoss-3.2 build issues
I did a clean check out of jboss-3.2 and can't build it on Win2000
with Sun's jdk1.3.1.
I have no idea what's wrong. Whether it's something wrong with my
environment or it is check out incorrectly, though I re-checked out it
again. Any hints are welcome.
The problem is with classpath.
I had to correct local.properties
#xdoclet.xdoclet.root=${project.root}/thirdparty/xdoclet-xdoclet
xdoclet.xdoclet.root=${project.root}/thirdparty/xdoclet/xdoclet
and other paths from vendor-jarname to vendor/jarname as it appears in
checked out dir structure.
I didn't fix all the problems yet. Any hints?
Thank you,
alex
---
This SF.net email is sponsored by: Does your code think in ink?
You could win a Tablet PC. Get a free Tablet PC hat just for playing.
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] JBoss-3.2 build issues
Amazing... I wonder how it got mixed.
I should have used
cvs -z3 -d:ext:[EMAIL PROTECTED]:/cvsroot/jboss co jboss-3.2
Is it correct? Should I specify branch version in addition? I never did
it and had no problems.
Thank you,
alex
Tuesday, March 18, 2003, 4:59:17 PM, Scott Stark wrote:
SMS There is no xdoclet.xdoclet.root in the 3.2
build/etc/local.properties-production. This
SMS was only added in head and the correct path for xdoclet root is
SMS thirdparty/xdoclet/xdoclet for 3.2.
SMS
SMS Scott Stark
SMS Chief Technology Officer
SMS JBoss Group, LLC
SMS
SMS - Original Message -
SMS From: Alex Loubyansky [EMAIL PROTECTED]
SMS To: jboss-development [EMAIL PROTECTED]
SMS Sent: Tuesday, March 18, 2003 6:40 AM
SMS Subject: [JBoss-dev] JBoss-3.2 build issues
I did a clean check out of jboss-3.2 and can't build it on Win2000
with Sun's jdk1.3.1.
I have no idea what's wrong. Whether it's something wrong with my
environment or it is check out incorrectly, though I re-checked out it
again. Any hints are welcome.
The problem is with classpath.
I had to correct local.properties
#xdoclet.xdoclet.root=${project.root}/thirdparty/xdoclet-xdoclet
xdoclet.xdoclet.root=${project.root}/thirdparty/xdoclet/xdoclet
and other paths from vendor-jarname to vendor/jarname as it appears in
checked out dir structure.
I didn't fix all the problems yet. Any hints?
Thank you,
alex
---
This SF.net email is sponsored by: Does your code think in ink?
You could win a Tablet PC. Get a free Tablet PC hat just for playing.
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] JBoss-3.2 build issues
Yes, branch is required. Thank you very much.
alex
Tuesday, March 18, 2003, 5:10:52 PM, David Jencks wrote:
DJ did you check out -r Branch_3_2 jboss-3.2
DJ david jencks
DJ On 2003.03.18 09:40 Alex Loubyansky wrote:
I did a clean check out of jboss-3.2 and can't build it on Win2000
with Sun's jdk1.3.1.
I have no idea what's wrong. Whether it's something wrong with my
environment or it is check out incorrectly, though I re-checked out it
again. Any hints are welcome.
The problem is with classpath.
I had to correct local.properties
#xdoclet.xdoclet.root=${project.root}/thirdparty/xdoclet-xdoclet
xdoclet.xdoclet.root=${project.root}/thirdparty/xdoclet/xdoclet
and other paths from vendor-jarname to vendor/jarname as it appears in
checked out dir structure.
I didn't fix all the problems yet. Any hints?
Thank you,
alex
---
This SF.net email is sponsored by: Does your code think in ink?
You could win a Tablet PC. Get a free Tablet PC hat just for playing.
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] MarshalledValue
MarshalledValue's constructor is
public MarshalledValue(Object obj) throws IOException
{
baos = new ByteArrayOutputStream();
MarshalledValueOutputStream mvos = new MarshalledValueOutputStream(baos);
mvos.writeObject(obj);
mvos.flush();
isHashComputed = false;
}
Here is get():
public Object get() throws IOException, ClassNotFoundException
{
if (serializedForm == null)
return null;
ByteArrayInputStream bais = new ByteArrayInputStream(serializedForm);
MarshalledValueInputStream mvis = new MarshalledValueInputStream(bais);
return mvis.readObject();
}
Should the constructor include the line
serializedForm = baos.toByteArray(); ?
searializedForm is initialized only in readExternal(). Thus, for
instances constructed with 'new MarshalledValue(obj)' all the methods
except for readExternal/writeExternal are broken.
Or am I missing something?
PS: this is for all MarshalledValue's in invocation.*, aop.* and
interception.*.
Thanks,
alex
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed
This morning I had problems with this error and clean build. The error was out of memory. JDK 1.3.1_05 Windows2000 alex Monday, March 03, 2003, 5:06:03 PM, David Jencks wrote: DJ I don't think so, the error is not shown. DJ I built fresh from a clean checkout last night with no problems. The DJ problem may be that Chris is not doing a clean checkout every day. DJ david jencks DJ On 2003.03.03 09:41 Bill Burke wrote: Is this an XDoclet thing again? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Sunday, March 02, 2003 8:41 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [JBoss-dev] [AUTOMATED] (HEAD) JBoss compilation failed = ==THIS IS AN AUTOMATED EMAIL - SEE http://jboss.kimptoc.net FOR DETAILS= = JAVA VERSION DETAILS java version 1.3.1_06 Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_06-b01) Java HotSpot(TM) Server VM (build 1.3.1_06-b01, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE org.jboss.ejb.EJBDeployer -- EJBDeployerMBean qualified to EJBDeployerMBean org.jboss.ejb.ContainerPlugin -- Service qualified to Service org.jboss.ejb.InstanceCache -- StatisticsProvider qualified to StatisticsProvider org.jboss.ejb.EntityEnterpriseContext -- EJBContextImpl qualified to EJBContextImpl org.jboss.invocation.Invoker -- Remote qualified to Remote org.jboss.ejb.StatefulSessionContainer -- AbstractContainerInterceptor qualified to AbstractContainerInterceptor org.jboss.ejb.EjbModule -- EjbModuleMBean qualified to EjbModuleMBean org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager -- StatefulSessionFilePersistenceManagerMBean qualified to StatefulSessionFilePersistenceManagerMBean org.jboss.ejb.timer.AbstractTimerSource -- AbstractTimerSourceMBean qualified to AbstractTimerSourceMBean org.jboss.ejb.timer.FilePersistenceManager -- FilePersistenceManagerMBean qualified to FilePersistenceManagerMBean org.jboss.ejb.timer.SchedulerTimerSource -- SchedulerTimerSourceMBean qualified to SchedulerTimerSourceMBean org.jboss.invocation.InvokerXAResource -- InvokerXAResourceMBean qualified to InvokerXAResourceMBean org.jboss.invocation.XATerminatorContainer -- XATerminatorContainerMBean qualified to XATerminatorContainerMBean org.jboss.invocation.http.server.HttpInvokerMBean -- ServiceMBean qualified to ServiceMBean org.jboss.invocation.local.LocalInvoker -- LocalInvokerMBean qualified to LocalInvokerMBean org.jboss.invocation.jrmp.server.JRMPInvoker -- JRMPInvokerMBean qualified to JRMPInvokerMBean org.jboss.invocation.pooled.server.PooledInvoker -- PooledInvokerMBean qualified to PooledInvokerMBean org.jboss.invocation.trunk.client.ConnectionManager -- ConnectionManagerMBean qualified to ConnectionManagerMBean org.jboss.invocation.trunk.client.TrunkInvokerProxy -- TrunkInvokerProxyMBean qualified to TrunkInvokerProxyMBean org.jboss.invocation.trunk.server.TrunkInvoker -- TrunkInvokerMBean qualified to TrunkInvokerMBean org.jboss.jms.asf.ServerSessionPoolLoader -- ServerSessionPoolLoaderMBean qualified to ServerSessionPoolLoaderMBean org.jboss.jms.jndi.JMSProviderLoader -- JMSProviderLoaderMBean qualified to JMSProviderLoaderMBean org.jboss.jmx.connector.RemoteMBeanServer -- MBeanServer qualified to MBeanServer org.jboss.jmx.connector.notification.JMSNotificationListener -- JMSNotificationListenerMBean qualified to JMSNotificationListenerMBean org.jboss.jmx.connector.notification.RMINotificationListener -- RMINotificationListenerMBean qualified to RMINotificationListenerMBean org.jboss.jmx.adaptor.rmi.RMIAdaptorService -- RMIAdaptorServiceMBean qualified to RMIAdaptorServiceMBean org.jboss.jmx.adaptor.xml.XMLAdaptorService -- XMLAdaptorServiceMBean qualified to XMLAdaptorServiceMBean org.jboss.jmx.adaptor.xml.XMLTestService -- XMLTestServiceMBean qualified to XMLTestServiceMBean org.jboss.jmx.connector.rmi.RMIConnectorImpl -- RMIConnectorImplMBean qualified to RMIConnectorImplMBean org.jboss.jmx.connector.ejb.EJBConnector -- EJBConnectorMBean qualified to EJBConnectorMBean org.jboss.jmx.connector.ConnectorFactoryService -- ConnectorFactoryServiceMBean qualified to ConnectorFactoryServiceMBean org.jboss.jmx.connector.notification.PollingNotificationListener -- PollingNotificationListenerMBean qualified to PollingNotificationListenerMBean org.jboss.logging.Log4jService -- Log4jServiceMBean qualified to Log4jServiceMBean org.jboss.logging.Log4jSocketServer -- Log4jSocketServerMBean qualified to Log4jSocketServerMBean org.jboss.naming.ExternalContext -- ExternalContextMBean qualified to ExternalContextMBean
Re[2]: [JBoss-dev] New module for cmp? What about the ejb module?
Sunday, March 02, 2003, 9:15:33 PM, Jason Dillon wrote: JD I think it might be better to use a different name non-ejb related... JD but whatever... what about just persistence? I like just persistence too. alex JD --jason JD On Monday, March 3, 2003, at 01:45 AM, Jeremy Boynes wrote: I think so. Is 'cmp' OK for the new module name, or is that too strongly associated with EJBs? Maybe 'persistence'? Jeremy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Jencks Sent: Sunday, March 02, 2003 10:10 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] New module for cmp? What about the ejb module? Would it be appropriate to put the new cmp framework in its own module since it is not particularly dependent on ejbs? Are we going to move the ejb support into the currently empty ejb module? david jencks --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] tx propagation in 3.2 and HEAD
This came from XPetstore-2.2.
First, tx propagation in 3.2 and HEAD differs.
Consider the following situation:
- CMP CategoryEJB with default tx attr Required;
- CategoryEJB has business method getCategoryValue with tx attr
Supports (this is not spec compliant but anyway);
- session bean PetstoreEJB with the following method:
/**
* @ejb.interface-method
* @ejb.transaction
* type=NotSupported
*/
public CategoryValue getCategory( String categoryId )
throws FinderException
{
return getCategoryLocalHome().findByPrimaryKey(categoryId).getCategoryValue();
}
In HEAD this throws the exception saying there is no tx associated
with the current thread.
But in 3.2 it passes. I think it's a bug in 3.2, as the tx context should
be associated only with the finder (Required) but not with
getCategoryValue (Supports).
alex
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] Finders, Selectors and ... deleters?
Jeremy, as I remember, once we already considered delete and update operations in JBossQL. This is great because we don't depend on the specific database. I thought this was planned for 4.0. alex Friday, January 17, 2003, 7:08:43 PM, you wrote: I was thinking about something while looking at my application's database behaviour... in many cases it is very inefficient to use a finder method together with remove() for large collections. It would be so much more efficient to have something like public int deleteByCode(int code); deleter method-namedeleteByCode/method-name method-params method-paramint/method-param method-params delete-method ejb-qldelete from Transactions t where t.code = ?1/ejb-ql /delete-method /deleter This all of course integrated with the cache so that it invalidates objects that are already loaded, etc. JB This is the same semantic (i.e. remove a load of stuff :-) that we need to JB improve to make cascade-delete efficient. I would be fairly easy to extend JB that to user-defined operations. JB I'm against adding delete (or insert and update) semantics to JBoss-QL JB though - that changes the nature of the language from read-only to JB read-write. JB Instead you could define a DeleteMethod as: JB deleter JB method-namedeleteByCode/method-name JB method-params JB method-paramint/method-param JB method-params JB jboss-qlwhere code = ?1/jboss-ql JB /deleter JB or, using values from the another entity via a subquery JB deleter JB method-namedeleteByCode/method-name JB method-params JB method-paramint/method-param JB method-params JB jboss-ql JB where code in JB (select x.code from another x where x.flag = ?1) JB /jboss-ql JB /deleter JB This leaves the JBoss-QL part read-only (it just qualifies the instances to JB be deleted). We know we're deleting Transactions as the method would be on JB the home interface for the Transaction EJB. JB It would be easy enough to extend this to bulk update as well - ok, easy if JB you limited the update to single-valued fields. JB Bulk create would be harder (need to pass in a lot of data), and probably JB unnecessary given we plan to have batch insert anyway. --- This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will allow you to extend the highest allowed 128 bit encryption to all your clients even if they use browsers that are limited to 40 bit encryption. Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[6]: [JBoss-dev] URLConnection and opened files
Here are my findings.
First, JBoss-3.0 is ok. The problem is in JBoss-3.2 and HEAD.
Second, I found the cause.
The resources we want to load with our custom handlers
through class loaders must be added to the classpath AFTER the
(custom) URLStreamHandlerFactory is setup.
URLClassLoaders hold their URLs.
The URLs created before the custom URLStreamHandlerFactory is set up
have Sun's handler. System class loader is a subclass of the
URLClassLoader. Thus, its URLs have Sun's handler. (It seems to me even
if java.protocol.handler.pkgs is setup. Is it a VM's bug or mine?)
Suppose we attempt to load resource that was in the classpath before
the custom handler factory was setup. The URL for the resource is
constructed with: URL(URL context, String spec).
where the context URL comes from the class loader with Sun's handler.
Then resource's URL's handler is assigned context.handler.
So, it doesn't matter whether the custom handler factory is setup.
alex
Tuesday, January 14, 2003, 9:49:45 PM, you wrote:
SMS Oh, I now remeber looking at this but I can't remember the context. There
SMS is a cache of handlers as the URL level. If the file protocol is referenced
SMS before the custom JBoss handler is available then the default Sun one will
SMS be used. Is there a difference between 3.0 and 3.2 with regard to when the
SMS custom protocol handlers are installed? I'll check later today.
SMS
SMS Scott Stark
SMS Chief Technology Officer
SMS JBoss Group, LLC
SMS
SMS - Original Message -
SMS From: Alex Loubyansky [EMAIL PROTECTED]
SMS To: Scott M Stark [EMAIL PROTECTED]
SMS Sent: Tuesday, January 14, 2003 7:07 AM
SMS Subject: Re[4]: [JBoss-dev] URLConnection and opened files
I'm a bit confused. I wrote a simple standalone test.
- main
public static void main(String[] args) throws Exception
{
// set handler pkgs
System.out.println(java.protocol.handler.pkgs: +
System.getProperty(java.protocol.handler.pkgs));
URL url = new URL(file, null, args[0]);
System.out.println(url: + url);
URLConnection urlCon = url.openConnection();
System.out.println(connection class: + urlCon.getClass().getName());
url = new URL(other, null, args[0]);
System.out.println(url: + url);
urlCon = url.openConnection();
System.out.println(connection class: + urlCon.getClass().getName());
}
- run
java -Djava.protocol.handler.pkgs=org.avoka.test.files.protocol -classpath %cp%
org.avoka.test.files.FilesTest build.xml
- output
java.protocol.handler.pkgs: org.avoka.test.files.protocol
url: file:build.xml
connection class: sun.net.www.protocol.file.FileURLConnection
url: other:build.xml
connection class: org.avoka.test.files.protocol.other.OtherURLConnection
I do have org.avoka.test.files.protocol.file.Handler and
org.avoka.test.files.protocol.file.FileURLConnection on the classpath.
My file.Handler isn't called. Am I missing something?
This same thing happens with JBoss-3.2 and HEAD but not JBoss-3.0 (my
3.0 is not up to date).
JDK1.3.1_05, J2SDK1.4.0
Win2K
Thanks,
alex
---
This SF.NET email is sponsored by: Take your first step towards giving
your online business a competitive advantage. Test-drive a Thawte SSL
certificate - our easy online guide will show you how. Click here to get
started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Fw: [jboss-cvs] jboss-common/src/main/org/jboss/net/protocol/resource ResourceURLConnection.java
JBoss-3.2 doesn't have
+ String urlStr = target.toString();
+ target = new URL(urlStr);
But just adding this doesn't help me.
BTW, is java.protocol.handler.pkgs setup after the SCL is created?
As I see it is, but how is it supposed to be? I would expect vice
versa.
alex
Wednesday, January 15, 2003, 2:17:48 AM, you wrote:
SMS Here is the context in which I looked into the JBoss file protocol handler not
being used.
SMS As far as I remember, the issue was that very early on there are file URLs being
SMS created and these were picking up the default file protocol handler. Recreating
the
SMS URL after the URLStreamHandlerFactory was installed resulted in the JBoss file
SMS protocol handler being used.
SMS
SMS Scott Stark
SMS Chief Technology Officer
SMS JBoss Group, LLC
SMS
SMS - Original Message -
SMS From: Scott M Stark [EMAIL PROTECTED]
SMS To: [EMAIL PROTECTED]
SMS Sent: Sunday, September 29, 2002 12:05 PM
SMS Subject: [jboss-cvs] jboss-common/src/main/org/jboss/net/protocol/resource
ResourceURLConnection.java
User: starksm
Date: 02/09/29 13:05:18
Modified:src/main/org/jboss/net/protocol/resource Tag: Branch_3_0
ResourceURLConnection.java
Log:
Recreate the URL obtained from the class loader as the file URLs are not
using the org.jboss.net.protocol.file handler for some reason. Creating a
new URL from the CL URL string does use our URLStreamHandlerFactory. This
fixes a problem with the log4j.xml file changes not being seen due to
the invalid lastModified of the default sun file protocol handler.
Revision ChangesPath
No revision
No revision
1.2.2.2 +17 -5
jboss-common/src/main/org/jboss/net/protocol/resource/ResourceURLConnection.java
Index: ResourceURLConnection.java
===
RCS file:
/cvsroot/jboss/jboss-common/src/main/org/jboss/net/protocol/resource/ResourceURLConnection.java,v
retrieving revision 1.2.2.1
retrieving revision 1.2.2.2
diff -u -r1.2.2.1 -r1.2.2.2
--- ResourceURLConnection.java 17 May 2002 22:25:41 - 1.2.2.1
+++ ResourceURLConnection.java 29 Sep 2002 20:05:18 - 1.2.2.2
@@ -22,7 +22,7 @@
/**
* Provides access to system resources as a URLConnection.
*
- * @version tt$Revision: 1.2.2.1 $/tt
+ * @version tt$Revision: 1.2.2.2 $/tt
* @author a href=mailto:[EMAIL PROTECTED];Jason Dillon/a
*/
public class ResourceURLConnection
@@ -50,7 +50,8 @@
ClassLoader cl = Thread.currentThread().getContextClassLoader();
URL target = cl.getResource(name);
- if (target == null) {
+ if (target == null)
+ {
cl = ClassLoader.getSystemClassLoader();
target = cl.getResource(name);
}
@@ -58,12 +59,23 @@
if (target == null)
throw new FileNotFoundException(Could not locate resource: + name);
- if (log.isTraceEnabled()) {
+ /* The file URLs being returned by the class loaders are not using the
+ org.jboss.net.protocol.file handler for some reason so here we
+ recreate the url to make sure it goes through our
+ URLStreamHandlerFactory. The cause should be tracked down but this
+ works for now.
+ */
+ String urlStr = target.toString();
+ target = new URL(urlStr);
+ if (log.isTraceEnabled())
+ {
log.trace(Target resource URL: + target);
- try {
+ try
+ {
log.trace(Target resource URL connection: +
target.openConnection());
}
- catch (Exception ignore) {}
+ catch (Exception ignore)
+ {}
}
return target;
---
This SF.NET email is sponsored by: Take your first step towards giving
your online business a competitive advantage. Test-drive a Thawte SSL
certificate - our easy online guide will show you how. Click here to get
started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: Re[2]: [JBoss-dev] JNuke dev
I meant specifying them in XDoclet style, not XML.
/**
* @classAttr
*/
class MyClass {
/**
* @fieldAttr
*/
private int myField;
/**
* @methodAttr
*/
public void myMethod() {
BTW, could you please exmplain what is the purpose of the 'name' attribute
in class-metadata element?
In the forum or here.
Thanks,
alex
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On
Behalf Of Bill Burke
Sent: Wednesday, January 15, 2003 4:23 PM
To: [EMAIL PROTECTED]
Subject: RE: Re[2]: [JBoss-dev] JNuke dev
Yes definately Alex. I've incorporated the idea of class/method/field
metadata in the AOP framework I've been working on. Please
refer to the AOP
forum.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On
Behalf Of Alex
Loubyansky
Sent: Wednesday, January 15, 2003 1:01 AM
To: Dain Sundstrom
Subject: Re[2]: [JBoss-dev] JNuke dev
I also thought about support class/method/field level metadata
attributes for aspects deploying the source file this way.
But this could be a limiting solution for aspects development.
alex
Tuesday, January 14, 2003, 9:16:20 PM, you wrote:
DS Bill,
DS This reminds me of an I deal I has last night (couldn't
sleep). I was
DS thinking of the script based MBean support Sacha added,
and I thought
DS can we make plain old java work like a scripting
language. Here is
DS what I came up with:
DS+ The user writes a class BlahService.java
DS+ This source file is places in our deployment directory
DS+ We run Xdoclet on it to generate the MBean
deployment descriptor
DS+ We compile the java file
DS+ Deploy
DS Java as a scripting language.
DS What do you think?
DS -dain
---
This SF.NET email is sponsored by: Take your first step towards giving
your online business a competitive advantage. Test-drive a Thawte SSL
certificate - our easy online guide will show you how. Click here to get
started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[4]: [JBoss-dev] JNuke dev
BB This may or may not disappear. The thought is to name the whole metadata
BB block for purposes of redeployment or undeployment. Am I making sense?
Frankly, I don't see, currently. I am not asking to remove it, just to
clarify.
Thanks,
alex
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Alex
Loubyansky
Sent: Wednesday, January 15, 2003 10:56 AM
To: [EMAIL PROTECTED]
Subject: RE: Re[2]: [JBoss-dev] JNuke dev
I meant specifying them in XDoclet style, not XML.
/**
* @classAttr
*/
class MyClass {
/**
* @fieldAttr
*/
private int myField;
/**
* @methodAttr
*/
public void myMethod() {
BTW, could you please exmplain what is the purpose of the 'name' attribute
in class-metadata element?
In the forum or here.
Thanks,
alex
---
This SF.NET email is sponsored by: A Thawte Code Signing Certificate
is essential in establishing user confidence by providing assurance of
authenticity and code integrity. Download our Free Code Signing guide:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[8]: [JBoss-dev] URLConnection and opened files
Thursday, January 16, 2003, 1:38:59 AM, you wrote: JB OK - changed this in 3.2 and HEAD and I can now delete a .war archive I JB couldn't before. JB Alex, can you let me know if this worked for you. Sorry about the hassle. Yes, it works now. Thanks, alex --- This SF.NET email is sponsored by: A Thawte Code Signing Certificate is essential in establishing user confidence by providing assurance of authenticity and code integrity. Download our Free Code Signing guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[4]: [JBoss-dev] URLConnection and opened files
I'm a bit confused. I wrote a simple standalone test.
- main
public static void main(String[] args) throws Exception
{
// set handler pkgs
System.out.println(java.protocol.handler.pkgs: +
System.getProperty(java.protocol.handler.pkgs));
URL url = new URL(file, null, args[0]);
System.out.println(url: + url);
URLConnection urlCon = url.openConnection();
System.out.println(connection class: + urlCon.getClass().getName());
url = new URL(other, null, args[0]);
System.out.println(url: + url);
urlCon = url.openConnection();
System.out.println(connection class: + urlCon.getClass().getName());
}
- run
java -Djava.protocol.handler.pkgs=org.avoka.test.files.protocol -classpath %cp%
org.avoka.test.files.FilesTest build.xml
- output
java.protocol.handler.pkgs: org.avoka.test.files.protocol
url: file:build.xml
connection class: sun.net.www.protocol.file.FileURLConnection
url: other:build.xml
connection class: org.avoka.test.files.protocol.other.OtherURLConnection
I do have org.avoka.test.files.protocol.file.Handler and
org.avoka.test.files.protocol.file.FileURLConnection on the classpath.
My file.Handler isn't called. Am I missing something?
This same thing happens with JBoss-3.2 and HEAD but not JBoss-3.0 (my
3.0 is not up to date).
JDK1.3.1_05, J2SDK1.4.0
Win2K
Thanks,
alex
---
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[6]: [JBoss-dev] URLConnection and opened files
Yes, I thought about it too. There are two cases:
- the thread creating URL can't find custom handlers;
- Sun's handler was somehow initialized/used before (before setting the
property or somehow else?)
But I can't understand why my standalone test doesn't work. I set
property in the command line and my handlers are in the classpath.
I don't see any chance for Sun's handler to be used first.
Ok, I'll update JBoss-3.0 and see.
Thanks,
alex
Tuesday, January 14, 2003, 9:49:45 PM, you wrote:
SMS Oh, I now remeber looking at this but I can't remember the context. There
SMS is a cache of handlers as the URL level. If the file protocol is referenced
SMS before the custom JBoss handler is available then the default Sun one will
SMS be used. Is there a difference between 3.0 and 3.2 with regard to when the
SMS custom protocol handlers are installed? I'll check later today.
SMS
SMS Scott Stark
SMS Chief Technology Officer
SMS JBoss Group, LLC
SMS
SMS - Original Message -
SMS From: Alex Loubyansky [EMAIL PROTECTED]
SMS To: Scott M Stark [EMAIL PROTECTED]
SMS Sent: Tuesday, January 14, 2003 7:07 AM
SMS Subject: Re[4]: [JBoss-dev] URLConnection and opened files
I'm a bit confused. I wrote a simple standalone test.
- main
public static void main(String[] args) throws Exception
{
// set handler pkgs
System.out.println(java.protocol.handler.pkgs: +
System.getProperty(java.protocol.handler.pkgs));
URL url = new URL(file, null, args[0]);
System.out.println(url: + url);
URLConnection urlCon = url.openConnection();
System.out.println(connection class: + urlCon.getClass().getName());
url = new URL(other, null, args[0]);
System.out.println(url: + url);
urlCon = url.openConnection();
System.out.println(connection class: + urlCon.getClass().getName());
}
- run
java -Djava.protocol.handler.pkgs=org.avoka.test.files.protocol -classpath %cp%
org.avoka.test.files.FilesTest build.xml
- output
java.protocol.handler.pkgs: org.avoka.test.files.protocol
url: file:build.xml
connection class: sun.net.www.protocol.file.FileURLConnection
url: other:build.xml
connection class: org.avoka.test.files.protocol.other.OtherURLConnection
I do have org.avoka.test.files.protocol.file.Handler and
org.avoka.test.files.protocol.file.FileURLConnection on the classpath.
My file.Handler isn't called. Am I missing something?
This same thing happens with JBoss-3.2 and HEAD but not JBoss-3.0 (my
3.0 is not up to date).
JDK1.3.1_05, J2SDK1.4.0
Win2K
Thanks,
alex
---
This SF.NET email is sponsored by: Take your first step towards giving
your online business a competitive advantage. Test-drive a Thawte SSL
certificate - our easy online guide will show you how. Click here to get
started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] JNuke dev
I also thought about support class/method/field level metadata attributes for aspects deploying the source file this way. But this could be a limiting solution for aspects development. alex Tuesday, January 14, 2003, 9:16:20 PM, you wrote: DS Bill, DS This reminds me of an I deal I has last night (couldn't sleep). I was DS thinking of the script based MBean support Sacha added, and I thought DS can we make plain old java work like a scripting language. Here is DS what I came up with: DS+ The user writes a class BlahService.java DS+ This source file is places in our deployment directory DS+ We run Xdoclet on it to generate the MBean deployment descriptor DS+ We compile the java file DS+ Deploy DS Java as a scripting language. DS What do you think? DS -dain DS On Tuesday, January 14, 2003, at 12:50 PM, Bill Burke wrote: The only negative comment I have in using JMX is that the PHP community may have a tough time switching over to Nukes on JBoss if you have to have a package structure like a SAR or a WAR. I hate to say it, but does it need to be dumbed-down for the PHP community? This type of community needs to be able to edit a JSP and immediately see the change on the webserver. Is it possible to be all JSP based for themes, modules and blocks? You could use a URL fragement and JSP:Include to decide what theme to use. Just a thought. Maybe JMX and such is the way to go. Just want to give you something to think about. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of julien viet Sent: Tuesday, January 14, 2003 11:31 AM To: SourceForge.net Subject: [JBoss-dev] JNuke dev hi folks, JNuke adventure has started. After analysis of PostNuke I've began the development, still early though. I keep everything that's good in PostNuke and throw all the shit away : modules, blocks, permissions system, url system and themes. JMX is used for PostNuke components : themes, modules and blocks are all JMX mbeans. Here are my reasons : A : general 1.we need a component structure, why not JMX ? after all another forum say that's lightweight. 2.theses components do not have to scale, i.e the number of modules, blocks and themes is very small. B : for modules 1.Ability to deploy/undeploy when application is running. 2.It's easy to deploy additional modules as a separate deployment and have them register in the same registry. 3.PostNuke is all about invoking module functions. Url like index.php?module=Userop=register means that the PN must call the method register on module User. For me that means that the servlet retrieves the mbean under the name jnuke:publicmodules:name=User and invokes the operation register(). 4.When a module is installed and configured it plug block mbeans in the JMX. C : for blocks, same reasons as above except 3 and 4 as invocation is typed for 3. D : for themes, same reasons as above except 3 and 4 as invocation is typed for 3. EJB are used for the model : UserEJB, GroupEJB, UserPermissionEJB, UserGroupEJB will be CMP 2.0 beans. We'll use local invocations and same trick as in forum to make them faster. Plus more beans. Each module is made of : 1.ModuleMBean : is the module itself, does not provide fucntionnalities, it's used to manager the PublicModule. Main operations are lifecycle (initialize, activate, unactivate, uninitialize) 2.PublicModuleMBean : is created when ModuleMBean activates and is responsible for serving requests. The MBean is dynamic and operations with no arguments and no returns are served. It's up to the module to do as he wants : if he wants MVC it can, it it wants to mix HTML and code, it can. First modules won't be MVC as they simply don't need. It's up to the model to have the persistence mecanisms it wants. First modules will use EJB. With lifecycle operations, each module can install itself, for instance : a ModuleMBean is plugged : 1.module configuration, setup of variables 2.initialize : module can creates table, deploy EJB, plugs block. 3.activate : module then go to block admin and creates instances of blocks (if module use blocks), display them on the page. Each block is made of : 1.BlockMBean : manages BlockInstanceMBean. 2.BlockInstanceMBean : is a block instance, it contains a title and a position on web page + 3 operations : display(), edit(), update(). display() : displays the block instance edit() : used to edit the block in block administration update() : used to upate the block in block admin Each them is made of various callbacks that displays HTML on the page. It has to provide location of files like css, gifs, etc... THe first them I did is made of a servlet that register to JMX and the doGet operation serves the files. It's default
[JBoss-dev] URLConnection and opened files
I am investingating the problem with inability remove deployed files.
First, I've found that URLDeploymentScanner uses
sun.net.www.protocol.file.FileURLConnection. For example here:
URLConnection connection;
if (watchUrl != null)
{
connection = watchUrl.openConnection();
}
else
{
connection = url.openConnection();
}
The connection is of type sun.net.www.protocol.file.FileURLConnection.
There are at least two problems with it:
1. incorrect last modified (occurs to be always 0)
2. after invoking connection.getLastModified() the target file can't
be removed on windows.
I guess org.jboss.net.protocol.file.FileURLConnection shuold be used
instead. But haven't figured out how to set it instead of Sun's.
Could someone hint?
Thanks,
alex
---
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] opened files
I quickly searched the source for opening files with FileInputStream. I fixed closing it after reading is done in several places. I want to warn. The common, I think mistake, in loading properties is Properties props = new Properties(); props.load(new FileInputStream(new File(filename))); After this the file will remain opened and can't be removed on windows. I am not sure whether it will be possible after gc will reclaim FileInputStream. So, the correct way is Properties props = new Properties(); FileInputStream fis = new FileInputStream(new File(filename)); props.load(fis); fis.close(); A few other places I met quickly surfing the source that look fishily. Maybe streams are closed in other methods? org.mortbay.html.Image.java 101: public Image setSizeFromGif(File gif) org.jboss.web.AbstractWebContainer 838,841: protected WebMetaData parseMetaData(String ctxPath, URL warURL) org.mortbay.http.HashUserRealm 111: public void load(String config) // loading properties org.mortbay.http.JDBCUserRealm 100: public void loadConfig(String config) // loading properties (line numbers for JBoss-3.2) alex --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: URLConnection and opened files
Forgot to add. This is for JBoss-3.2.
But in HEAD I can't remove deployed/watching files on windows either.
So, I guess, HEAD has the same problem.
alex
Monday, January 13, 2003, 2:10:51 PM, you wrote:
AL I am investingating the problem with inability remove deployed files.
AL First, I've found that URLDeploymentScanner uses
AL sun.net.www.protocol.file.FileURLConnection. For example here:
AL URLConnection connection;
AL if (watchUrl != null)
AL {
ALconnection = watchUrl.openConnection();
AL }
AL else
AL {
ALconnection = url.openConnection();
AL }
AL The connection is of type sun.net.www.protocol.file.FileURLConnection.
AL There are at least two problems with it:
AL 1. incorrect last modified (occurs to be always 0)
AL 2. after invoking connection.getLastModified() the target file can't
AL be removed on windows.
AL I guess org.jboss.net.protocol.file.FileURLConnection shuold be used
AL instead. But haven't figured out how to set it instead of Sun's.
AL Could someone hint?
AL Thanks,
AL alex
---
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] URLConnection and opened files
Thanks for pointing to this, but I think the problem is not there.
I suspect the classes are somehow not getting to the classpath.
I'm running jdk1.3.1_05. Note, earlier I ran JBoss w/o these problems
on this same VM.
Please, let me know whether it's only me watching it.
Thanks,
alex
Monday, January 13, 2003, 7:31:06 PM, you wrote:
SMS Our FileURLConnection should be picked due to the org.jboss.net.protocol
SMS package being placed into the java.protocol.handler.pkgs by thiscode in
SMS org.jboss.system.server.ServerImpl.doInit:
SMS // Include the default JBoss protocol handler package
SMS String handlerPkgs = System.getProperty(java.protocol.handler.pkgs);
SMS if (handlerPkgs != null)
SMS {
SMS handlerPkgs += |org.jboss.net.protocol;
SMS }
SMS else
SMS {
SMS handlerPkgs = org.jboss.net.protocol;
SMS }
SMS System.setProperty(java.protocol.handler.pkgs, handlerPkgs);
SMS
SMS Scott Stark
SMS Chief Technology Officer
SMS JBoss Group, LLC
SMS
SMS - Original Message -
SMS From: Alex Loubyansky [EMAIL PROTECTED]
SMS To: JBoss-Dev [EMAIL PROTECTED]
SMS Sent: Monday, January 13, 2003 4:10 AM
SMS Subject: [JBoss-dev] URLConnection and opened files
I am investingating the problem with inability remove deployed files.
First, I've found that URLDeploymentScanner uses
sun.net.www.protocol.file.FileURLConnection. For example here:
URLConnection connection;
if (watchUrl != null)
{
connection = watchUrl.openConnection();
}
else
{
connection = url.openConnection();
}
The connection is of type sun.net.www.protocol.file.FileURLConnection.
There are at least two problems with it:
1. incorrect last modified (occurs to be always 0)
2. after invoking connection.getLastModified() the target file can't
be removed on windows.
I guess org.jboss.net.protocol.file.FileURLConnection shuold be used
instead. But haven't figured out how to set it instead of Sun's.
Could someone hint?
Thanks,
alex
---
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[4]: [JBoss-dev] URLConnection and opened files
I meet it in JBoss-3.2 and HEAD. I am afraid if I update JBoss-3.0
it'll get infected too. I'll try to figure it out.
alex
Tuesday, January 14, 2003, 12:18:41 AM, you wrote:
SMS They are definitely in the classpath in the lib/jboss-common.jar, but may not
SMS be available to the class loader being used. What version of JBoss are we
SMS talking about here?
SMS
SMS Scott Stark
SMS Chief Technology Officer
SMS JBoss Group, LLC
SMS
SMS - Original Message -
SMS From: Alex Loubyansky [EMAIL PROTECTED]
SMS To: Scott M Stark [EMAIL PROTECTED]
SMS Sent: Monday, January 13, 2003 11:30 AM
SMS Subject: Re[2]: [JBoss-dev] URLConnection and opened files
Thanks for pointing to this, but I think the problem is not there.
I suspect the classes are somehow not getting to the classpath.
I'm running jdk1.3.1_05. Note, earlier I ran JBoss w/o these problems
on this same VM.
Please, let me know whether it's only me watching it.
Thanks,
alex
Monday, January 13, 2003, 7:31:06 PM, you wrote:
SMS Our FileURLConnection should be picked due to the org.jboss.net.protocol
SMS package being placed into the java.protocol.handler.pkgs by thiscode in
SMS org.jboss.system.server.ServerImpl.doInit:
SMS // Include the default JBoss protocol handler package
SMS String handlerPkgs = System.getProperty(java.protocol.handler.pkgs);
SMS if (handlerPkgs != null)
SMS {
SMS handlerPkgs += |org.jboss.net.protocol;
SMS }
SMS else
SMS {
SMS handlerPkgs = org.jboss.net.protocol;
SMS }
SMS System.setProperty(java.protocol.handler.pkgs, handlerPkgs);
---
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] new problems on Win2K
I am watching the following problem. Once ejb-jar module is copied in the deploy directory and deployed it can't be removed until the server is stopped. This occurs on Windows2000 with HEAD only. JVM is Sun 1.3.1_05. Am I alone? Thanks, alex --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: HEAD build problem with foe-deployer tests
Hello David, I'm working on it. Probably, I'll disable it again. Sorry for troubles. alex Sunday, December 15, 2002, 3:53:02 PM, you wrote: DJ I think there is still a problem with the recently re-enabled foe deployer DJ tests. I can't build the testsuite on a clean checkout: DJ [ejbdoclet] Generating weblogic-cmp-rdbms-jar.xml. DJ [ejbdoclet] org.xml.sax.SAXParseException: Element weblogic-rdbms-bean DJ does not allow field-map here. DJ [ejbdoclet] at org.apache.crimson.parser.Parser2.error(Parser2.java:3160) DJ [ejbdoclet] at org.apache.crimson.parser.ValidatingParser$ChildrenValidator.consume(ValidatingParser.java:349) DJ [ejbdoclet] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1 -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: HEAD build problem with foe-deployer tests
I ended up with disabling WebLogic DDs validation, thus relying on XDoclet to generate correct DDs. If someone knows the reason why it happens on first run. Please, let me know. Thanks, alex Sunday, December 15, 2002, 4:12:39 PM, you wrote: AL Hello David, AL I'm working on it. Probably, I'll disable it again. AL Sorry for troubles. AL alex AL Sunday, December 15, 2002, 3:53:02 PM, you wrote: DJ I think there is still a problem with the recently re-enabled foe deployer DJ tests. I can't build the testsuite on a clean checkout: DJ [ejbdoclet] Generating weblogic-cmp-rdbms-jar.xml. DJ [ejbdoclet] org.xml.sax.SAXParseException: Element weblogic-rdbms-bean DJ does not allow field-map here. DJ [ejbdoclet] at org.apache.crimson.parser.Parser2.error(Parser2.java:3160) DJ [ejbdoclet] at org.apache.crimson.parser.ValidatingParser$ChildrenValidator.consume(ValidatingParser.java:349) DJ [ejbdoclet] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1 -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Foo Deployer (WL Deployer)
Hello Marcus, MR what is the latest version of the WL deployer? it doesn't have its own version. MR Is it currently integrated in MR 3.x MR or in HEAD? It's in HEAD only and works, as I remember, with JBoss-3.2 and HEAD. If you are interested in it I can provide any info. Let's discuss it in jboss-user. PS: it's not Foo, it's Foe :) alex --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBoss Training @ Geneva
Hello Sacha, clicking on Read More on the site I get HTTP ERROR: 404 /services/training Not Found alex Monday, November 04, 2002, 7:12:31 PM, you wrote: SL Hello, SL It seems that no e-mail address was available on JBoss.org web site to SL subscribe to the Geneva training. SL If you want to register for the JBoss Advanced Training taking place in SL Geneva at the end of the month (25-28 November 2002), please use this e-mail SL address: SL mailto:sales;jboss.org?subject=Geneva SL It's gonna be a great training! (well, like all JBoss trainings ;) ) SL Cheers, SL Sacha -- Best regards, Alex Loubyansky --- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] JBoss Training @ Geneva
it misses '.jsp' alex Monday, November 04, 2002, 9:26:03 PM, you wrote: AL Hello Sacha, AL clicking on Read More on the site I get AL HTTP ERROR: 404 /services/training Not Found AL alex AL Monday, November 04, 2002, 7:12:31 PM, you wrote: SL Hello, SL It seems that no e-mail address was available on JBoss.org web site to SL subscribe to the Geneva training. SL If you want to register for the JBoss Advanced Training taking place in SL Geneva at the end of the month (25-28 November 2002), please use this e-mail SL address: SL mailto:sales;jboss.org?subject=Geneva SL It's gonna be a great training! (well, like all JBoss trainings ;) ) SL Cheers, SL Sacha -- Best regards, Alex Loubyansky --- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[6]: [JBoss-dev] can't add a dir to thirdparty
Hello Jason, thank you for taking care. I saw commits but I neither see the apache-commons in the thirdparty nor can find commons-collections.jar. Could you please look at it? Thank you very much. alex Tuesday, October 29, 2002, 2:47:50 AM, you wrote: JD Apache commons collections has been imported in apache-commons. JD --jason -Original Message- From: [EMAIL PROTECTED] [mailto:jboss- [EMAIL PROTECTED]] On Behalf Of Alex Loubyansky Sent: Friday, October 25, 2002 1:30 PM To: Jason Dillon Subject: Re[4]: [JBoss-dev] can't add a dir to thirdparty You are cool. I respect you. Please, guide me through this. I have jboss-head/thirdparty/tmp/ that contains: readme lib/ META-INF/ license manifest.mf *.class Then I execute the following: cvs import -mimported apache commons-collections version 2.0, dated 02/04/2002. thirdparty/apache/commons-collections apache commons- collections_2_0 How can I edit modules file? Were is it? alex I want to add to thirdparty the following: apache-commons/ readme lib/ commons-collections.jar I started with 'cvs add apache-commons' and got the error I wrote about. As to the jar, I would add the following way: cvs add -kb commons-collections.jar cvs ci -mapache commons collections commons-collections.jar Is it correct? JD Nope. The thirdparty module is setup in a different fashion from JD how it JD is checked out. Perhaps that should be changed eventually, but JD for now JD that is how it works. I think the build system faq covers this, JD but I JD will give you the short version. JD The physical repository looks like this: JD /thirdparty/ JD apache/ JD log4j/ JD lib/* JD For jboss-head this will get mapped to /thirdparty/apache-log4j. JD This JD is a recent change to prevent `cvs update` from checking out all JD files JD under 'apache', when only a subset is required. JD To add a new thirdparty library do something like this: JD 1) download the archive of the library JD 2) extract the archive into a temporary directory JD 3) remove all non-essential files (docs, examples, whatever) JD basically we only want basic README, COPYRIGHT lib/* files. JD 4) Make sure that all library files live in lib (move them if JD the JD archive does not have them in this order JD 5) If the library has a README and/or COPYRIGHT docs, make sure JD they JD are in the root. JD 6) Make sure you are in the top-level of the archive (where lib JD is a JD direct JD child) and: JD cvs -d CVSROOT import thirdparty/vendor/package vender JD package_version JD So for Apache/Jakarta Commons v1.1 you would: JD cvs -d CVSROOT import thirdparty/apache/commons apache JD commons_1_1 JD The check in comments are basically describing the new import, so JD list JD the full name version of the imported bits. JD Then, you need to edit CVSROOT/modules, in the bottom there is a JD thirdparty library section, copy the format of other entries for JD the new JD entry. Then add the module include to which ever projects you JD need to JD access it from. JD Then, finally, edit tools/etc/buildfragments/libraries.ent and add JD definitions of the root, lib and classpath's for this library. JD Note JD that you should use exact paths (no filesets) so that the build JD system JD does not freak out when this library is not present. JD That is it... rather simple once you get the hang of it. JD Again, if you like I can handle this for you if you tell me what JD you JD need done exactly. JD --jason -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[4]: [JBoss-dev] -service.xml generator
Hello Sacha, I thought about it too. As alternative or other implementation of MBean persistence. Though, I am not familiar with MBean persistence stuff yet. Are they meant to be serialized as java objects? I think, having MBeans persisted in xml form is much better. Because I can see what is persisted and change something manually. alex Monday, October 28, 2002, 10:06:36 AM, you wrote: SL Hello, SL Exactly, it may help to solve one of the current biggest issue wrt SL configuration: any configuration done through any GUI (or mbean, etc.) is not persisted = only transient configuration can be started remotly or SL programatically. Having a generic way to build new persisted mbean SL definition is important. SL But we spoke about this on this ML a few weeks ago and we still have some SL issues wrt implicit dependencies. Anyway, we need a way to persist SL configuration that is currently only transient. SL cheers, SL Sacha -Message d'origine- De : [EMAIL PROTECTED] [mailto:jboss-development-admin;lists.sourceforge.net]De la part de Alex Loubyansky Envoye : lundi, 28 octobre 2002 07:17 A : Anatoly Akkerman Objet : Re[2]: [JBoss-dev] -service.xml generator Anatoly, this looks cool and draws other perspectives. I'm in thought. Any other thoughts/comments? Thanks. alex Sunday, October 27, 2002, 4:07:15 PM, you wrote: AA Hi, Alex AA Jelly would give you similar ease of use but without having to write any AA XSL. You would initialize the JellyContext by creating in first and then AA setting variables in it from attributes like this: AA ctx.setVariable(name, value); AA (values can be any Java objects) AA you load your modified *-service.xml script from a URL into Jelly and AA run it as a script in the context which you just set up. The result of AA this operation is XML again. AA This is simplest usage of Jelly. You do need a library, though, and AA possibly, not one but a bunch from jakarta-commons. AA I am using Jelly in a slightly more advanced fashion. I wrote a few very AA simple tags that allow output of Jelly to be a jar file. Something like: AA j:jelly xmlns:j=jelly:core xmlns:zipper=jelly:mypackage.MyTagLib AA zipper:zip AA zipper:entry name=META-INF/ejb-jar.xml AA parametrized ejb-jar.xml contents go here AA /zipper:entry AA zipper:entry name=META-INF/jboss.xml AA parametrized jboss-xml contents go here AA /zipper:entry AA /zipper:zip AA /j:jelly AA Set up the JellyContext for running this script with appropriately AA configured variables (say from a DB of configurations or from attributes AA of an MBean). Run the script in the context. AA After running this script, the JellyContext contains a Jar archive (as a AA byte[] stored under some variable name) of reconfigured descriptors. AA The way I use it is to have a servlet that parses its path request and AA deduces from the path request which script to run and which AA configuration to pull from storage. The servlet outputs either XML or AA JAR depending on the requested module and its script. AA So, you can just point the JBoss deployer to deploy a URL of the kind: AA myservlet/componentA/configX.jar AA or AA myservlet/serviceB/configY.xml AA and the servlet automatically generates properly configured jar or xml AA which the Deployer happily deploys. AA Jelly has many usages this is just what I could come up with. It would AA be more than adequate for what you need to do, but if you are AA dissatisfied with JBoss library dependency growth, then, Jelly is out of AA the picture. AA Alex Loubyansky wrote: Thanks, Anatoly. I'll check it. Also I thought about Velocity which looks similar to Jelly from your description, though I am not familiar with the last one. Could you, please, look at the following idea with XML/XSL, compare it with Jelly and give your opinion? - before transformation, each MBean's attribute is set as a parameter to the Transformer with Transformer.setParameter(...) with the name equal to the corresponding parameter name used in XSL stylesheet; - transform XML template with Transformer and XSL stylesheet. As for me, XML/XSL requires two templates (XML and XSL) while Jelly/Velocity requires only one. Also, I wouldn't add any thirdparty library unless it really helps. The JBoss becomes so heavy. I think it's problem. -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development -- Best regards, Alex Loubyansky
Re[2]: [JBoss-dev] -service.xml generator
I am thinking about this stuff of reconfiguring and redeployment. It would be cool to have metadata of the deployed apps to be exposed for modifications through jmx-console. And not only for changing existing attributes but adding some resource references etc. Then one can modify some stuff and redeploy the app. alex Sunday, October 27, 2002, 4:07:15 PM, you wrote: AA Hi, Alex AA Jelly would give you similar ease of use but without having to write any AA XSL. You would initialize the JellyContext by creating in first and then AA setting variables in it from attributes like this: AA ctx.setVariable(name, value); AA (values can be any Java objects) AA you load your modified *-service.xml script from a URL into Jelly and AA run it as a script in the context which you just set up. The result of AA this operation is XML again. AA This is simplest usage of Jelly. You do need a library, though, and AA possibly, not one but a bunch from jakarta-commons. AA I am using Jelly in a slightly more advanced fashion. I wrote a few very AA simple tags that allow output of Jelly to be a jar file. Something like: AA j:jelly xmlns:j=jelly:core xmlns:zipper=jelly:mypackage.MyTagLib AA zipper:zip AA zipper:entry name=META-INF/ejb-jar.xml AA parametrized ejb-jar.xml contents go here AA /zipper:entry AA zipper:entry name=META-INF/jboss.xml AA parametrized jboss-xml contents go here AA /zipper:entry AA /zipper:zip AA /j:jelly AA Set up the JellyContext for running this script with appropriately AA configured variables (say from a DB of configurations or from attributes AA of an MBean). Run the script in the context. AA After running this script, the JellyContext contains a Jar archive (as a AA byte[] stored under some variable name) of reconfigured descriptors. AA The way I use it is to have a servlet that parses its path request and AA deduces from the path request which script to run and which AA configuration to pull from storage. The servlet outputs either XML or AA JAR depending on the requested module and its script. AA So, you can just point the JBoss deployer to deploy a URL of the kind: AA myservlet/componentA/configX.jar AA or AA myservlet/serviceB/configY.xml AA and the servlet automatically generates properly configured jar or xml AA which the Deployer happily deploys. AA Jelly has many usages this is just what I could come up with. It would AA be more than adequate for what you need to do, but if you are AA dissatisfied with JBoss library dependency growth, then, Jelly is out of AA the picture. AA Alex Loubyansky wrote: Thanks, Anatoly. I'll check it. Also I thought about Velocity which looks similar to Jelly from your description, though I am not familiar with the last one. Could you, please, look at the following idea with XML/XSL, compare it with Jelly and give your opinion? - before transformation, each MBean's attribute is set as a parameter to the Transformer with Transformer.setParameter(...) with the name equal to the corresponding parameter name used in XSL stylesheet; - transform XML template with Transformer and XSL stylesheet. As for me, XML/XSL requires two templates (XML and XSL) while Jelly/Velocity requires only one. Also, I wouldn't add any thirdparty library unless it really helps. The JBoss becomes so heavy. I think it's problem. -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[4]: [JBoss-dev] -service.xml generator
Yes. And by the way there are to ways. The first is MBean persistence. The second is changing the app's DDs themself. As I understand right, Anatoly uses the last one. alex Monday, October 28, 2002, 11:46:57 AM, you wrote: SL ... and making these changes persistent! ;) SL Yes, that would be really cool -Message d'origine- De : [EMAIL PROTECTED] [mailto:jboss-development-admin;lists.sourceforge.net]De la part de Alex Loubyansky Envoye : lundi, 28 octobre 2002 10:03 A : Anatoly Akkerman Objet : Re[2]: [JBoss-dev] -service.xml generator I am thinking about this stuff of reconfiguring and redeployment. It would be cool to have metadata of the deployed apps to be exposed for modifications through jmx-console. And not only for changing existing attributes but adding some resource references etc. Then one can modify some stuff and redeploy the app. alex Sunday, October 27, 2002, 4:07:15 PM, you wrote: AA Hi, Alex AA Jelly would give you similar ease of use but without having to write any AA XSL. You would initialize the JellyContext by creating in first and then AA setting variables in it from attributes like this: AA ctx.setVariable(name, value); AA (values can be any Java objects) AA you load your modified *-service.xml script from a URL into Jelly and AA run it as a script in the context which you just set up. The result of AA this operation is XML again. AA This is simplest usage of Jelly. You do need a library, though, and AA possibly, not one but a bunch from jakarta-commons. AA I am using Jelly in a slightly more advanced fashion. I wrote a few very AA simple tags that allow output of Jelly to be a jar file. Something like: AA j:jelly xmlns:j=jelly:core xmlns:zipper=jelly:mypackage.MyTagLib AA zipper:zip AA zipper:entry name=META-INF/ejb-jar.xml AA parametrized ejb-jar.xml contents go here AA /zipper:entry AA zipper:entry name=META-INF/jboss.xml AA parametrized jboss-xml contents go here AA /zipper:entry AA /zipper:zip AA /j:jelly AA Set up the JellyContext for running this script with appropriately AA configured variables (say from a DB of configurations or from attributes AA of an MBean). Run the script in the context. AA After running this script, the JellyContext contains a Jar archive (as a AA byte[] stored under some variable name) of reconfigured descriptors. AA The way I use it is to have a servlet that parses its path request and AA deduces from the path request which script to run and which AA configuration to pull from storage. The servlet outputs either XML or AA JAR depending on the requested module and its script. AA So, you can just point the JBoss deployer to deploy a URL of the kind: AA myservlet/componentA/configX.jar AA or AA myservlet/serviceB/configY.xml AA and the servlet automatically generates properly configured jar or xml AA which the Deployer happily deploys. AA Jelly has many usages this is just what I could come up with. It would AA be more than adequate for what you need to do, but if you are AA dissatisfied with JBoss library dependency growth, then, Jelly is out of AA the picture. AA Alex Loubyansky wrote: Thanks, Anatoly. I'll check it. Also I thought about Velocity which looks similar to Jelly from your description, though I am not familiar with the last one. Could you, please, look at the following idea with XML/XSL, compare it with Jelly and give your opinion? - before transformation, each MBean's attribute is set as a parameter to the Transformer with Transformer.setParameter(...) with the name equal to the corresponding parameter name used in XSL stylesheet; - transform XML template with Transformer and XSL stylesheet. As for me, XML/XSL requires two templates (XML and XSL) while Jelly/Velocity requires only one. Also, I wouldn't add any thirdparty library unless it really helps. The JBoss becomes so heavy. I think it's problem. -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] -service.xml generator
Hello David, DJ how does what you want differ from the *-ds.xml deployer in 3.2 and 4? just dealing with JMX agent view and not XML files. I think, it would be easier, especially to start, to use some GUI instead of XML. I am not talking about datasources only. Do you really think it's an overlap? DJ It uses a chainable xsl-sub-deployer that transforms dd's on the fly. I DJ suspect there is considerable overlap with the foe-deployer transformation DJ stuff. Not yet. It just transforms DDs and doesn't generate/setup other services like datasources, connection factories and so on. Thanks. alex DJ david jencks DJ On 2002.10.26 09:11:31 -0400 Alex Loubyansky wrote: I am thinking about writting an MBean that will generate *-service.xml files for datasources. I see it the following way. - MBean attributes corresponding to values needed to construct -service.xml (such as url, driver, user, password, etc); - XML template with dummy/default values; - XSL stylesheet similar to what David wrote for -ds.xml; - managed operation 'generate' that will transform XML template, probably, mostly substituting dummy values with managed attribute values. Actually, I am looking for a nice way to configure datasources in FoeDeployer but I think it could be useful behind it. Also the same way any -service.xml file can be generated. Any thoughts? Thanks. -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] -service.xml generator
Thanks, Anatoly. I'll check it. Also I thought about Velocity which looks
similar to Jelly from your description, though I am not familiar with the last
one.
Could you, please, look at the following idea with XML/XSL, compare it with
Jelly and give your opinion?
- before transformation, each MBean's attribute is set as a parameter to the
Transformer with Transformer.setParameter(...) with the name equal to the
corresponding parameter name used in XSL stylesheet;
- transform XML template with Transformer and XSL stylesheet.
As for me, XML/XSL requires two templates (XML and XSL) while Jelly/Velocity
requires only one.
Also, I wouldn't add any thirdparty library unless it really helps. The JBoss
becomes so heavy. I think it's problem.
Thanks.
alex
On Sat, 26 Oct 2002 20:08:08 -0400
Anatoly Akkerman [EMAIL PROTECTED] wrote:
Alex Loubyansky wrote:
I am thinking about writting an MBean that will generate *-service.xml
files for datasources.
I see it the following way.
- MBean attributes corresponding to values needed to construct
-service.xml (such as url, driver, user, password, etc);
- XML template with dummy/default values;
- XSL stylesheet similar to what David wrote for -ds.xml;
- managed operation 'generate' that will transform XML template,
probably, mostly substituting dummy values with managed attribute values.
Actually, I am looking for a nice way to configure datasources in
FoeDeployer but I think it could be useful behind it.
Also the same way any -service.xml file can be generated.
Any thoughts?
Thanks.
I would strongly recommend using Jelly (from Apache) (found out about it
from Rickard Oberg's weblog). You take your service-xml file and just
replace values you might will need to change with expressions like
${varname}. Then you can run the XML file as a script in Jelly in a
JellyContext in which you set up all the needed variables, say, from the
MBean's attributes. The result of running it through Jelly is XML with the
expressions properly evaluated. (Jelly is a much better replacement to JSPs
and similar things, what is good about it you can run it w/o any container
nonsense). You can also create your custom tag libraries like in JSPs,
though it is much better than JSPs. There is not much documentation but it
is pretty straight forward. Get back to me if you are having difficulties.
(You would not need XSLT either, actually, I am using Jelly in this way to
automatically reconfigure application components, like EJBs or others and
system-level components, like MBeans. If anyone is interested, I can share
some of that stuff)
Anatoly.
Free Mail http://ua.fm
---
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] -service.xml generator
Anatoly, this looks cool and draws other perspectives. I'm in thought. Any other thoughts/comments? Thanks. alex Sunday, October 27, 2002, 4:07:15 PM, you wrote: AA Hi, Alex AA Jelly would give you similar ease of use but without having to write any AA XSL. You would initialize the JellyContext by creating in first and then AA setting variables in it from attributes like this: AA ctx.setVariable(name, value); AA (values can be any Java objects) AA you load your modified *-service.xml script from a URL into Jelly and AA run it as a script in the context which you just set up. The result of AA this operation is XML again. AA This is simplest usage of Jelly. You do need a library, though, and AA possibly, not one but a bunch from jakarta-commons. AA I am using Jelly in a slightly more advanced fashion. I wrote a few very AA simple tags that allow output of Jelly to be a jar file. Something like: AA j:jelly xmlns:j=jelly:core xmlns:zipper=jelly:mypackage.MyTagLib AA zipper:zip AA zipper:entry name=META-INF/ejb-jar.xml AA parametrized ejb-jar.xml contents go here AA /zipper:entry AA zipper:entry name=META-INF/jboss.xml AA parametrized jboss-xml contents go here AA /zipper:entry AA /zipper:zip AA /j:jelly AA Set up the JellyContext for running this script with appropriately AA configured variables (say from a DB of configurations or from attributes AA of an MBean). Run the script in the context. AA After running this script, the JellyContext contains a Jar archive (as a AA byte[] stored under some variable name) of reconfigured descriptors. AA The way I use it is to have a servlet that parses its path request and AA deduces from the path request which script to run and which AA configuration to pull from storage. The servlet outputs either XML or AA JAR depending on the requested module and its script. AA So, you can just point the JBoss deployer to deploy a URL of the kind: AA myservlet/componentA/configX.jar AA or AA myservlet/serviceB/configY.xml AA and the servlet automatically generates properly configured jar or xml AA which the Deployer happily deploys. AA Jelly has many usages this is just what I could come up with. It would AA be more than adequate for what you need to do, but if you are AA dissatisfied with JBoss library dependency growth, then, Jelly is out of AA the picture. AA Alex Loubyansky wrote: Thanks, Anatoly. I'll check it. Also I thought about Velocity which looks similar to Jelly from your description, though I am not familiar with the last one. Could you, please, look at the following idea with XML/XSL, compare it with Jelly and give your opinion? - before transformation, each MBean's attribute is set as a parameter to the Transformer with Transformer.setParameter(...) with the name equal to the corresponding parameter name used in XSL stylesheet; - transform XML template with Transformer and XSL stylesheet. As for me, XML/XSL requires two templates (XML and XSL) while Jelly/Velocity requires only one. Also, I wouldn't add any thirdparty library unless it really helps. The JBoss becomes so heavy. I think it's problem. -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: Re[4]: [JBoss-dev] can't add a dir to thirdparty
Hi Jason, I am confused a little... why does lib/* contain what looks like an uncompressed jar? :)) sorry, I was frightened. Ok, so jboss-head/thirdparty/tmp/ contains: readme lib/commons-collections.jar then being in tmp I execute cvs import -mimported apache commons-collections version 2.0, dated 02/04/2002. thirdparty/apache/commons-collections apache commons-collections_2_0 How can I modify the modules file? Where is it? Thanks. alex --jason -Original Message- From: [EMAIL PROTECTED] [mailto:jboss- [EMAIL PROTECTED]] On Behalf Of Alex Loubyansky Sent: Friday, October 25, 2002 1:30 PM To: Jason Dillon Subject: Re[4]: [JBoss-dev] can't add a dir to thirdparty You are cool. I respect you. Please, guide me through this. I have jboss-head/thirdparty/tmp/ that contains: readme lib/ META-INF/ license manifest.mf *.class Then I execute the following: cvs import -mimported apache commons-collections version 2.0, dated 02/04/2002. thirdparty/apache/commons-collections apache commons- collections_2_0 How can I edit modules file? Were is it? Free Mail http://ua.fm --- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] -service.xml generator
I am thinking about writting an MBean that will generate *-service.xml files for datasources. I see it the following way. - MBean attributes corresponding to values needed to construct -service.xml (such as url, driver, user, password, etc); - XML template with dummy/default values; - XSL stylesheet similar to what David wrote for -ds.xml; - managed operation 'generate' that will transform XML template, probably, mostly substituting dummy values with managed attribute values. Actually, I am looking for a nice way to configure datasources in FoeDeployer but I think it could be useful behind it. Also the same way any -service.xml file can be generated. Any thoughts? Thanks. alex Free Mail http://ua.fm --- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] can't add a dir to thirdparty
I am meeting this problem when attempting to add apache-commons dir to thirdparty. I am said: cvs [add aborted]: cannot add to /cvsroot/jboss/CVSROOT/Emptydir Could someone clarify it, please? I just added a dir in varia successfully. Thanks. alex --- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] can't add a dir to thirdparty
Hello Jason, I want to add to thirdparty the following: apache-commons/ readme lib/ commons-collections.jar I started with 'cvs add apache-commons' and got the error I wrote about. As to the jar, I would add the following way: cvs add -kb commons-collections.jar cvs ci -mapache commons collections commons-collections.jar Is it correct? Thank you. alex Friday, October 25, 2002, 10:18:09 PM, you wrote: JD How are you adding the directory? Care must be taken when adding new JD thirdparty libraries. If you do not know who that system works you can JD break things. JD Please explain how you attempted to add the directory and also tell me JD what specific libraries you are trying to import. I need to add some JD other thirdparty libs, I can add yours as well. JD --jason -Original Message- From: [EMAIL PROTECTED] [mailto:jboss- [EMAIL PROTECTED]] On Behalf Of Alex Loubyansky Sent: Friday, October 25, 2002 10:45 AM To: JBoss-Dev Subject: [JBoss-dev] can't add a dir to thirdparty I am meeting this problem when attempting to add apache-commons dir to thirdparty. I am said: cvs [add aborted]: cannot add to /cvsroot/jboss/CVSROOT/Emptydir Could someone clarify it, please? I just added a dir in varia successfully. Thanks. -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[4]: [JBoss-dev] can't add a dir to thirdparty
You are cool. I respect you. Please, guide me through this. I have jboss-head/thirdparty/tmp/ that contains: readme lib/ META-INF/ license manifest.mf *.class Then I execute the following: cvs import -mimported apache commons-collections version 2.0, dated 02/04/2002. thirdparty/apache/commons-collections apache commons-collections_2_0 How can I edit modules file? Were is it? alex I want to add to thirdparty the following: apache-commons/ readme lib/ commons-collections.jar I started with 'cvs add apache-commons' and got the error I wrote about. As to the jar, I would add the following way: cvs add -kb commons-collections.jar cvs ci -mapache commons collections commons-collections.jar Is it correct? JD Nope. The thirdparty module is setup in a different fashion from how it JD is checked out. Perhaps that should be changed eventually, but for now JD that is how it works. I think the build system faq covers this, but I JD will give you the short version. JD The physical repository looks like this: JD /thirdparty/ JD apache/ JD log4j/ JD lib/* JD For jboss-head this will get mapped to /thirdparty/apache-log4j. This JD is a recent change to prevent `cvs update` from checking out all files JD under 'apache', when only a subset is required. JD To add a new thirdparty library do something like this: JD 1) download the archive of the library JD 2) extract the archive into a temporary directory JD 3) remove all non-essential files (docs, examples, whatever) JD basically we only want basic README, COPYRIGHT lib/* files. JD 4) Make sure that all library files live in lib (move them if the JD archive does not have them in this order JD 5) If the library has a README and/or COPYRIGHT docs, make sure they JD are in the root. JD 6) Make sure you are in the top-level of the archive (where lib is a JD direct JD child) and: JD cvs -d CVSROOT import thirdparty/vendor/package vender JD package_version JD So for Apache/Jakarta Commons v1.1 you would: JD cvs -d CVSROOT import thirdparty/apache/commons apache commons_1_1 JD The check in comments are basically describing the new import, so list JD the full name version of the imported bits. JD Then, you need to edit CVSROOT/modules, in the bottom there is a JD thirdparty library section, copy the format of other entries for the new JD entry. Then add the module include to which ever projects you need to JD access it from. JD Then, finally, edit tools/etc/buildfragments/libraries.ent and add JD definitions of the root, lib and classpath's for this library. Note JD that you should use exact paths (no filesets) so that the build system JD does not freak out when this library is not present. JD That is it... rather simple once you get the hang of it. JD Again, if you like I can handle this for you if you tell me what you JD need done exactly. JD --jason -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re[2]: [jboss-cvs] jboss-common/src/main/org/jboss/util WeakValueHashMap.java
the map whose mappings are to be placed in this
JD map.
* @since1.3
*/
public WeakValueHashMap(Map t) {
this(Math.max(2*t.size(), 11), 0.75f);
putAll(t);
}
/* -- Simple queries -- */
/**
* Returns the number of key-value mappings in this map.
* strongNote:/strong emIn contrast with most
JD implementations
of the
* codeMap/code interface, the time required by this
JD operation is
* linear in the size of the map./em
*/
public int size() {
processQueue();
return hash.size();
}
/**
* Returns codetrue/code if this map contains no key-value
mappings.
*/
public boolean isEmpty() {
processQueue();
return hash.isEmpty();
}
/**
* Returns codetrue/code if this map contains a mapping for
JD the
* specified key.
*
* @param key The key whose presence in this map is to be
JD tested
*/
public boolean containsKey(Object key) {
processQueue();
return hash.containsKey(key);
}
/* -- Lookup and modification operations -- */
/**
* Returns the value to which this map maps the specified
codekey/code.
* If this map does not contain a value for this key, then return
* codenull/code.
*
* @param key The key whose associated value, if any, is to be
returned
*/
public Object get(Object key) {
processQueue();
WeakReference ref = (WeakReference)hash.get(key);
if (ref != null) return ref.get();
return null;
}
/**
* Updates this map so that the given codekey/code maps to
JD the
given
* codevalue/code. If the map previously contained a mapping
JD for
* codekey/code then that mapping is replaced and the
JD previous
value is
* returned.
*
* @param keyThe key that is to be mapped to the given
*codevalue/code
* @param value The value to which the given codekey/code
JD is to
be
*mapped
*
* @return The previous value to which this key was mapped, or
* codenull/code if if there was no mapping for the
JD key
*/
public Object put(Object key, Object value)
{
processQueue();
Object rtn = hash.put(key, WeakValueRef.create(key, value,
queue));
if (rtn != null) rtn = ((WeakReference)rtn).get();
return rtn;
}
/**
* Removes the mapping for the given codekey/code from this
JD map,
if
* present.
*
* @param key The key whose mapping is to be removed
*
* @return The value to which this key was mapped, or
codenull/code if
* there was no mapping for the key
*/
public Object remove(Object key)
{
processQueue();
return hash.remove(key);
}
/**
* Removes all mappings from this map.
*/
public void clear() {
processQueue();
hash.clear();
}
}
--
Best regards,
Alex Loubyansky
---
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] HEAD is broken: storeEntity must always be called
The bug is in CMP. Many-to-many relationships are not working.
Though, the tests-db are passing successfully.
The bug was introduced by the following change (this is not a real
cvs diff):
public boolean isModified(EntityEnterpriseContext ctx)
{
- return isModifiedCommand.execute( ctx );
+ return !(getEntityBridge().getDirtyFields(ctx).isEmpty());
}
Currently, EntityContainer.storeEntity() must always be called.
Current implementation is:
public void storeEntity(EntityEnterpriseContext ctx) throws Exception
{
if (ctx.getId() != null)
{
if(getPersistenceManager().isModified(ctx)) {
getPersistenceManager().storeEntity(ctx);
}
}
}
isModifiedCommand.execute( ctx ) always returns true. Thus, in
pre-changed version storeEntity() was always called.
Proposed change calls entityStore() only if cmp fields or cmr with
foreign keys were changed. But it misses many-to-many.
And the change doesn't make sense because in JDBCStoreEntityCommand
dirty fields are checked and entity is updated accordingly.
The reason tests were passed successfully is that, all the operations
were run in one transaction dealing only with cached values.
So, we need to change isModified back and, probably, correct the
tests.
Unfortunately, currently sf.net is not available the whole day.
alex
---
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavote
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] suggestion for JBOSS_CMP
Suppose, customerBean has a one-to-many relationship with accountBean accountBean has a one-to-one relationship with addressBean customerBean has a one-to-one relationship with phoneBean then what about read-ahead !-- read customers -- strategyon-load/strategy page-size100/page-size eager-load-groupcustomer_group/eager-load-group !-- read customer's accounts -- read-ahead cmr-fieldaccounts/cmr-field strategyon-load/strategry page-size10/page-size eager-load-groupaccount_group/eager-load-group !-- read account's address -- read-ahead cmr-fieldaddress/cmr-field strategyon-find/strategry eager-load-groupaddress_group/eager-load-group /read-ahead /read-ahead !-- read customer's phone -- read-ahead cmr-fieldphone/cmr-field strategyon-find/strategry eager-load-groupphone_group/eager-load-group /read-ahead /read-ahead Note, sql statements for these queries could return duplicates. alex Wednesday, October 23, 2002, 5:23:30 AM, you wrote: DS I totally agree and this is already planned for JBoss 4.0. The real DS problem is not the code to do the loading but figuring out a simple xml DS structure to define the loading. DS -dain DS Emerson Cargnin - SICREDI Serviços wrote: I have a suggestion regarding to CMP : why not create a configuration to a find method to allow the container to load the relationships of a bean? This could be useful in the cases you have to read all the beans(or a good amount of then) and all (or almost all) relationships of them. eg : in a report you will have a sql to finding the pk's, one (at least) to load the bean data and one sql to each relation you have to report (for each bean). I think that one of the worse problem with CMP is that : database overhead. CMP generates too much sql commands that in some cases could be handled by fewer (if not one) sql commands. The DBA's in my company didn't like very much the trace they saw in the database for a very simple app. -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-client.jar vs jboss-all-client.jar
It seems that jboss-client.jar is a subset of jboss-all-client.jar. What is the reason? Thanks. alex --- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] jboss-client.jar vs jboss-all-client.jar
aha... ... jboss-all-client.jar containing everything a client app needs ... but is there a reason for other *-client.jar in the client dir? alex Wednesday, October 23, 2002, 8:03:44 PM, you wrote: AL It seems that jboss-client.jar is a subset of jboss-all-client.jar. AL What is the reason? AL Thanks. AL alex AL --- AL This sf.net email is sponsored by: Influence the future AL of Java(TM) technology. Join the Java Community AL Process(SM) (JCP(SM)) program now. AL http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en AL ___ AL Jboss-development mailing list AL [EMAIL PROTECTED] AL https://lists.sourceforge.net/lists/listinfo/jboss-development -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] developing on windows
Hello Jason, Saturday, October 19, 2002, 12:35:41 AM, you wrote: JD Does setting -Xms640m help/resolve the problems you are having on win32? No :( It occured even worth. The build process hung. I had to terminate the task. alex JD --jason -Original Message- From: [EMAIL PROTECTED] [mailto:jboss- [EMAIL PROTECTED]] On Behalf Of Matt Munz Sent: Friday, October 18, 2002 2:24 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] developing on windows Alex, I have had the same problems -- you are not alone. As long as I JD don't clean, once I have a good build (usually the third try), the JD problems go away. It seems like a memory problem to me too. Perhaps someone should JD run the build system using a profiler ;) One of the ant tasks probably JD leaks... - Matt -Original Message- From: [EMAIL PROTECTED] [mailto:jboss-development-admin;lists.sourceforge.net]On Behalf Of JD Alex Loubyansky Sent: Friday, October 18, 2002 5:03 PM To: JBoss-Dev Subject: [JBoss-dev] developing on windows Developing on Windows became a nightmare. Sometimes to bulid the server or run a testsuite I need to run build.bat several times. The worst thing it fails with so dreadful errors. It's hard to determine whether I did something wrong or not enough memory. I am on P4, 1.7GHz, 512M Win2K SP2 Sun JDK1.3.1_01 in scripts I add -Xmx640m. Is it only me facing it? Any workarounds? -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by: Access Your PC Securely with GoToMyPC. Try Free Now https://www.gotomypc.com/s/OSND/DD ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] developing on windows
DJ low memory (256 mb) machine. What does take a lot of time is running DJ xdoclet hundreds of times, as in the testsuite compile. DJ It does take an annoying amount of time if there are no changed files. DJ I think we should make a flag file that we can do an uptodate check on to DJ completely avoid calling xdoclet if no changes have occurred since the last DJ compile. It would be great. Relative problem is why I should build all testcases if I want to run only tests-db or tests-foe-deployer-unit? It seems this was mentioned in earlier threads but I don't remember the resolution. Adding the flag could help with this problem too, e.i. building everything only once and then rebuilding the tests I am working on. alex --- This sf.net email is sponsored by: Access Your PC Securely with GoToMyPC. Try Free Now https://www.gotomypc.com/s/OSND/DD ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Fwd: [jboss-cvs] jboss/src/main/org/jboss/ejb/plugins/cmp/jdbc JDBCLoadEntityCommand.java
AB Without the !isReadOnly() check, the preloaded readahead fields
AB were ignored.
Exactly. My mistake. When fixing read-only/read-time-out fields
loading I made rw fields to be loaded always. Sorry. I'll correct it
in other branches.
But in fresh Branch_3_2
org.jboss.test.cmp2.readonly.ReadonlyUnitTestCase fails with due to
EJBTestRunner not bound.
I'll try to figure out, but if someone knows the cause, please, let me
know.
Thanks.
alex
EJBTestRunner not bound
javax.naming.NameNotFoundException: EJBTestRunner not bound
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:245)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:220)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:122)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:456)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:440)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at net.sourceforge.junitejb.EJBTestCase.getEJBTestRunner(EJBTestCase.java:162)
at net.sourceforge.junitejb.EJBTestCase.runBare(EJBTestCase.java:109)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:131)
at net.sourceforge.junitejb.EJBTestCase.run(EJBTestCase.java:95)
at junit.framework.TestSuite.runTest(TestSuite.java:173)
at junit.framework.TestSuite.run(TestSuite.java:168)
at junit.framework.TestSuite.runTest(TestSuite.java:173)
at junit.framework.TestSuite.run(TestSuite.java:168)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:325)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:524)
AB Regards,
AB Adrian
From: Adrian Brock [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [jboss-cvs] jboss/src/main/org/jboss/ejb/plugins/cmp/jdbc
JDBCLoadEntityCommand.java
Date: Sun, 13 Oct 2002 15:53:53 -0700
User: ejort
Date: 02/10/13 15:53:53
Modified:src/main/org/jboss/ejb/plugins/cmp/jdbc Tag: Branch_3_2
JDBCLoadEntityCommand.java
Log:
Fix readahead and load-groups
Revision ChangesPath
No revision
No revision
1.19.2.4 +6 -2
jboss/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCLoadEntityCommand.java
Index: JDBCLoadEntityCommand.java
===
RCS file:
/cvsroot/jboss/jboss/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCLoadEntityCommand.java,v
retrieving revision 1.19.2.3
retrieving revision 1.19.2.4
diff -u -r1.19.2.3 -r1.19.2.4
--- JDBCLoadEntityCommand.java 5 Oct 2002 10:18:08 - 1.19.2.3
+++ JDBCLoadEntityCommand.java 13 Oct 2002 22:53:53 - 1.19.2.4
@@ -40,7 +40,7 @@
* @author a href=mailto:[EMAIL PROTECTED];Justin Forder/a
* @author a href=mailto:[EMAIL PROTECTED];Dirk Zimmermann/a
* @author a href=mailto:[EMAIL PROTECTED];danch (Dan
Christopherson)/a
- * @version $Revision: 1.19.2.3 $
+ * @version $Revision: 1.19.2.4 $
*/
public class JDBCLoadEntityCommand {
private final JDBCStoreManager manager;
@@ -286,7 +286,11 @@
// - it is already loaded
// - it is a read-only _already_loaded_ field that isn't timed
out yet
if( field.isPrimaryKeyMember()
-|| ( field.isLoaded( ctx ) !field.isReadTimedOut( ctx )
)) {
+|| ( field.isLoaded( ctx )
+ ( !field.isReadOnly() || !field.isReadTimedOut( ctx
) )
+ )
+ )
+ {
fields.remove();
}
}
--
Best regards,
Alex Loubyansky
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] ArrayIndexOutOfBoundsException in testsuite
Running tests-db in current HEAD on jdk1.3.1 on Win2000 I get the exception below. There are two test-cases that fail. Sometimes they fail eventually. Sometime, one of them, sometime both. Do someone see it too? The problem is in MetaData.java in getChildrenByTagName alex 2002-10-14 15:56:48,029 ERROR [org.jboss.deployment.MainDeployer] could not create deployment: file:/C:/CVSROOT/jboss-head/testsuite/output/lib/cmp2-simple.jar org.jboss.deployment.DeploymentException: Failed to load metadata; - nested throwable: (java.lang.ArrayIndexOutOfBoundsException) at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:335) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:791) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:641) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:606) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:590) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:56) at org.jboss.mx.server.Invocation.invoke(Invocation.java:81) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:159) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:547) at org.jboss.jmx.adaptor.rmi.RMIAdaptorImpl.invoke(RMIAdaptorImpl.java:265) at java.lang.reflect.Method.invoke(Native Method) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:241) at sun.rmi.transport.Transport$1.run(Transport.java:152) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:148) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:465) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:706) at java.lang.Thread.run(Thread.java:484) + nested throwable: java.lang.ArrayIndexOutOfBoundsException at org.apache.xerces.dom.DeferredDocumentImpl.getChunkIndex(DeferredDocumentImpl.java:1823) at org.apache.xerces.dom.DeferredDocumentImpl.getNodeObject(DeferredDocumentImpl.java:815) at org.apache.xerces.dom.DeferredElementImpl.synchronizeData(DeferredElementImpl.java:160) at org.apache.xerces.dom.ElementImpl.getTagName(ElementImpl.java:273) at org.jboss.metadata.MetaData.getChildrenByTagName(MetaData.java:63) at org.jboss.metadata.MetaData.getUniqueChild(MetaData.java:85) at org.jboss.metadata.BeanMetaData.importEjbJarXml(BeanMetaData.java:593) at org.jboss.metadata.EntityMetaData.importEjbJarXml(EntityMetaData.java:210) at org.jboss.metadata.ApplicationMetaData.importEjbJarXml(ApplicationMetaData.java:242) at org.jboss.metadata.XmlFileLoader.load(XmlFileLoader.java:159) at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:329) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:791) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:641) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:606) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:590) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:72) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:56) at org.jboss.mx.server.Invocation.invoke(Invocation.java:81) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:159) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:547) at org.jboss.jmx.adaptor.rmi.RMIAdaptorImpl.invoke(RMIAdaptorImpl.java:265) at java.lang.reflect.Method.invoke(Native Method) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:241) at sun.rmi.transport.Transport$1.run(Transport.java:152) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:148) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:465) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:706) at java.lang.Thread.run(Thread.java:484) --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Fwd: [jboss-cvs] jboss/src/main/org/jboss/ejb/plugins/cmp/jdbc JDBCLoadEntityCommand.java
Hello Adrian,
sorry, I saw cvs-commits first and wrote to you personally.
I'll try to figure out.
in isReadTimedOut( ctx ) isReadOnly( ctx ) is checked.
Weird...
alex
Monday, October 14, 2002, 2:07:48 AM, you wrote:
AB Hi,
AB Could one of the CMP experts check this fix? It is in 3.2 only.
AB Without the !isReadOnly() check, the preloaded readahead fields
AB were ignored.
AB Regards,
AB Adrian
From: Adrian Brock [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [jboss-cvs] jboss/src/main/org/jboss/ejb/plugins/cmp/jdbc
JDBCLoadEntityCommand.java
Date: Sun, 13 Oct 2002 15:53:53 -0700
User: ejort
Date: 02/10/13 15:53:53
Modified:src/main/org/jboss/ejb/plugins/cmp/jdbc Tag: Branch_3_2
JDBCLoadEntityCommand.java
Log:
Fix readahead and load-groups
Revision ChangesPath
No revision
No revision
1.19.2.4 +6 -2
jboss/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCLoadEntityCommand.java
Index: JDBCLoadEntityCommand.java
===
RCS file:
/cvsroot/jboss/jboss/src/main/org/jboss/ejb/plugins/cmp/jdbc/JDBCLoadEntityCommand.java,v
retrieving revision 1.19.2.3
retrieving revision 1.19.2.4
diff -u -r1.19.2.3 -r1.19.2.4
--- JDBCLoadEntityCommand.java 5 Oct 2002 10:18:08 - 1.19.2.3
+++ JDBCLoadEntityCommand.java 13 Oct 2002 22:53:53 - 1.19.2.4
@@ -40,7 +40,7 @@
* @author a href=mailto:[EMAIL PROTECTED];Justin Forder/a
* @author a href=mailto:[EMAIL PROTECTED];Dirk Zimmermann/a
* @author a href=mailto:[EMAIL PROTECTED];danch (Dan
Christopherson)/a
- * @version $Revision: 1.19.2.3 $
+ * @version $Revision: 1.19.2.4 $
*/
public class JDBCLoadEntityCommand {
private final JDBCStoreManager manager;
@@ -286,7 +286,11 @@
// - it is already loaded
// - it is a read-only _already_loaded_ field that isn't timed
out yet
if( field.isPrimaryKeyMember()
-|| ( field.isLoaded( ctx ) !field.isReadTimedOut( ctx )
)) {
+|| ( field.isLoaded( ctx )
+ ( !field.isReadOnly() || !field.isReadTimedOut( ctx
) )
+ )
+ )
+ {
fields.remove();
}
}
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
jboss-cvs-commits mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-cvs-commits
AB _
AB Chat with friends online, try MSN Messenger: http://messenger.msn.com
--
Best regards,
Alex Loubyansky
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] SARDeployer strange ordering of archives
org.jboss.deployment.SARDeployer method parseXMLClasspath on line 292 This method parses the Classpath element. But it adds each archive to a HashSet. Then iterates over the elements in the HashSet and deploys them. Changing the HashSet to an java.util.ArrayList or java.util.Vector solves this problem and retains the deployment order given by the archive list. I wonder is there a particular need for the use of a HashSet. DJ A set is nice, avoids duplicates. BTW, in CMP we are going to implement a so called sequenced set that will contain unique elements in the order they were added. It should help here too. But the question is how this fix is nice. alex --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] HEAD build problem: Win2000, jdk1.3.1
I can't build current fresh HEAD on Win2000 with jdk1.3.1. 1. I had to add -Xmx640m as in build.sh 2. BUILD FAILED file:C:/CVSROOT/jboss-all/security/build.xml:166: Reference javac.classpath not found. alex --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] undeploying ejb-jar in Branch_3_2
Undeploying ejb-jar with one entity and one session beans in current Branch_3_2, the exception below is thrown. Am I alone? alex 2002-10-05 13:19:58,447 INFO [org.jboss.ejb.plugins.EntityInstancePool] Destroyed 2002-10-05 13:19:58,447 ERROR [org.jboss.ejb.EntityContainer] Destroying failed java.lang.NullPointerException at org.jboss.ejb.plugins.EntityReentranceInterceptor.setContainer(EntityReentranceInterceptor.java:51) at org.jboss.ejb.EntityContainer.destroyService(EntityContainer.java:459) at org.jboss.system.ServiceMBeanSupport.destroy(ServiceMBeanSupport.java:264) at org.jboss.ejb.Container.invoke(Container.java:737) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1026) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:960) at $Proxy9.destroy(Unknown Source) at org.jboss.system.ServiceController.destroy(ServiceController.java:515) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy46.destroy(Unknown Source) at org.jboss.ejb.EjbModule.destroyService(EjbModule.java:502) at org.jboss.system.ServiceMBeanSupport.destroy(ServiceMBeanSupport.java:264) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:960) at $Proxy9.destroy(Unknown Source) at org.jboss.system.ServiceController.destroy(ServiceController.java:515) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy18.destroy(Unknown Source) at org.jboss.ejb.EJBDeployer.destroy(EJBDeployer.java:508) at org.jboss.deployment.MainDeployer.destroy(MainDeployer.java:508) at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:453) at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:447) at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:420) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy7.undeploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.undeploy(URLDeploymentScanner.java:426) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:513) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:195) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:206) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:185) 2002-10-05 13:19:58,447 INFO [org.jboss.ejb.EntityContainer] Destroyed --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Set interface implementation
I'm working on a bug 576410. The problem is that we need a Set implementation that will order elements by its addition to the set. I called it SequencedSet. There are two main approaches: implement it from scratch extending AbstractSet or on top of something. I talked with Dain and he advised me on-top and pointed to SequencedHashMap from Apache commons-collections (it's really nice). Now the problem: - SequencedSet needs to be in client's class path in both approaches. Let it be. - in on-top approach the class SequencedHashMap needs to be in client's classpath too. i.e. +1 jar for client. That's not so nice. Indeed, SequencedHashMap can be taken out from commons-collections.jar. But that's not nice too. Any thoughts? Thanks. alex PS: Dain currently isn't available. --- This sf.net email is sponsored by: DEDICATED SERVERS only $89! Linux or FreeBSD, FREE setup, FAST network. Get your own server today at http://www.ServePath.com/indexfm.htm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-user] RE: [JBoss-dev] SUBMITTING DOCUMENTATION PLEASE READ
Whom should I send it? alex I want to change that once and for all, I will ask that as you submit new code you also submit the JUnit tests if you have them as the documentation. The documentation can come mf This doesn't make sense. I mean, just like you have you junit test, mf submit doco Doco is not the junit obviously so the junit as doco mf doesn't make sense, yes I am still talking about word files for the mf documentation so that we can easily include them in our books. mf And I don't want this to degenerate in 'What format should we use for mf doco bla bla bla just gives us WORD documents and we will deal with mf them (text if you use linux) mf marc f in 2 sets. The documentation should include a beginner getting started couple of paragraph, explaining the feature and how to use it for the getting started book. If your feature is complex enough, it should also come with FOR-PAY pages. These pages will be included in the for-pay documentation of JBoss and the author compensated based on the revenues. You don't need to produce a booklet (few stuff like the CMP stuff is big enough to warrant a booklet). Is it clear? Please follow these guidelines for the new submissions it is the only way your features will be used at all and it is also a simple way to make some easy money with us. regards marc f xx Marc Fleury, Ph.D. President, Founder JBoss Group, LLC xx --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS problems / broken build
Hello guys, I probably broke the build. I committed one file and then the connection to cvs was lost. I am very sorry and will correct it as soon as I am able. -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JBossCMP: new ways to create entity beans
Hello folks! JBossCMP now provides some new ways to setup and create entity beans. It is based on so called entity commands. First some working examples (snippet from jbosscmp-jdbc.xml): entity ejb-nameMyCMPBean/ejb-name table-namemycmp_table/table-name !-- auto-incremented primary key (jdk1.3/1.4) for now supported only for MySQL. -- cmp-field field-nameid/field-name column-nameknownid/column-name jdbc-typeINTEGER/jdbc-type sql-typeINTEGER(11)/sql-type auto-increment/ /cmp-field !-- entity command to create the entity -- entity-command name=mysql-get-generated-keys/ !-- unknown primary key generated with SQL statement -- unknown-pk unknown-pk-classjava.lang.Integer/unknown-pk-class column-namegenid/column-name jdbc-typeTIMESTAMP/jdbc-type sql-typeDATETIME/sql-type /unknown-pk entity-command name=pk-sql/ -- !-- pk-sql generated unknown-pk; overriding default sql unknown-pk unknown-pk-classjava.lang.Integer/unknown-pk-class column-namegenid/column-name jdbc-typeINTEGER/jdbc-type sql-typeINTEGER/sql-type /unknown-pk entity-command name=pk-sql attribute name=pk-sqlSELECT SEQ_2279_1.nextval FROM DUAL/attribute /entity-command -- !-- mysql generated unknown-pk unknown-pk unknown-pk-classjava.lang.Integer/unknown-pk-class column-namegenid/column-name jdbc-typeINTEGER/jdbc-type sql-typeINTEGER(11)/sql-type auto-increment/ /unknown-pk entity-command name=mysql-get-generated-keys class=org.jboss.ejb.plugins.cmp.jdbc.mysql.MySQLCreateEntityCommand/ -- !-- the use of key generator for unknown-pk unknown-pk unknown-pk-classjava.lang.String/unknown-pk-class column-namegenid/column-name jdbc-typeVARCHAR/jdbc-type sql-typeVARCHAR(32)/sql-type /unknown-pk entity-command name=key-generator class=org.jboss.ejb.plugins.cmp.jdbc.JDBCKeyGeneratorCreateCommand attribute name=key-generator-factoryUUIDKeyGeneratorFactory/attribute /entity-command -- /entity The general syntax of entity-command is: entity-command name=CommandName class=ComandClass attribute name=attr1value1/attribute attribute name=attr2value2/attribute /entity-command Only the 'name' is required. You can check the list of available commands in standardjbosscmp-jdbc.xml in entity-commands element. The default entity command is specified in 'defaults' element and can be overriden in each entity element as above. If entity-command in the entity provides 'class' or 'attribute' it overrides the corresponding element of in the known command. For now the feature is available in HEAD version. -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[3]: [JBoss-dev] jboss 4 build system changes, possible jboss.net and catalina impact.
The same problem using build.sh under Win2K with cygwin. Could someone clean successfully under windows 2000? Thanks. alex Wednesday, September 11, 2002, 8:27:30 PM, you wrote: AL Hello David, AL Wednesday, September 11, 2002, 8:00:25 PM, you wrote: DJ Maybe this is a windows only problem? I didn't have a problem cleaning on DJ linux. AL Maybe.. I have it permanently. Am I along here? DJ BTW I didn't modify the build.bat files to increase the memory, which was DJ required on my linux system to do build.sh all. Could you try build.bat DJ all and add the -X. stuff if necessary? AL set ANT_OPTS=%ANT_OPTS% -Xmx640m AL As in build.sh but it doesn't help. AL Thank you. AL alex DJ On 2002.09.11 12:45:30 -0400 Alex Loubyansky wrote: Another problem, David. When cleaning up I get the following exception. The file exists and can deleted manually w/o problems. Or is it just my own problem? Thank you. alex _buildmagic:clean: [delete] Deleting directory C:\CVSROOT\jboss-all\j2ee\output BUILD FAILED jar:file:/C:/CVSROOT/jboss-all/tools/lib/buildmagic-tasks.jar!/org/jboss/tools/buildmagic/common.xml:124: Unable to delete file C:\CVSROOT\jboss-all\j2ee\output\lib\jboss-j2ee.jar at org.apache.tools.ant.taskdefs.Delete.removeDir(Delete.java:388) at org.apache.tools.ant.taskdefs.Delete.removeDir(Delete.java:381) at org.apache.tools.ant.taskdefs.Delete.execute(Delete.java:327) at org.apache.tools.ant.Task.perform(Task.java:317) at org.apache.tools.ant.Target.execute(Target.java:309) at org.apache.tools.ant.Target.performTasks(Target.java:334) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.jboss.tools.buildmagic.task.Ant.execute(Ant.java:261) at org.jboss.tools.buildmagic.task.module.ExecuteModules.executeModule(ExecuteModules.java:292) at org.jboss.tools.buildmagic.task.module.ExecuteModules.execute(ExecuteModules.java:194) at org.apache.tools.ant.Task.perform(Task.java:317) at org.apache.tools.ant.Target.execute(Target.java:309) at org.apache.tools.ant.Target.performTasks(Target.java:334) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.Project.executeTargets(Project.java:1250) at org.apache.tools.ant.Main.runBuild(Main.java:610) at org.apache.tools.ant.Main.start(Main.java:196) at org.apache.tools.ant.Main.main(Main.java:235) -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CMP vendor specific code
Hello, guys! David and Dain, I guess, you are the persons who can help me here. Currently, I am writting CMP code that supports db-vendor specific API. I need to cast PreparedStatement/Statement to vendor specific ones. So, the statements need to be casted to WrappedStatement first and then getUnderlyingStatement() method should be called. This works fine. But I have a couple of questions. 1. the wrapping classes are in local-ra-jdbc-libs.jar. I need this jar in the classpath during compilation. According to recent buildfragments changes, what is the right place to add in the classpath: modules.ent or build.xml? 2. using wrapping classes makes CMP code dependent on connector implementation. What do you think about it? 3. compilation also requires driver or a stub for the dirver. As Dain suggested, I should checkin the binary in the thirdparty module. Sorry, Dain, did you mean the driver or a stub? Thank you. alex --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] jboss 4 build system changes, possible jboss.net and catalina impact.
Hello David,
jboss-all/server/build.xml needs ${build.parsers} and ${build.beans}
properties. These are missed in locations.ent.
Should they be added to jboss-all/server/build.xml or locations.ent?
Thank you.
alex
Wednesday, September 11, 2002, 1:15:11 AM, you wrote:
DJ I replaced many of the repetitive elements in the build.xml files with
DJ parameter entities, including the definition of xdoclet tasks. As far as I
DJ can tell this hasn't affected anything according to the testsuite.
DJ However, one effect is that xdoclet is now always the global xdoclet in
DJ thirdparty. Previously it looks like a local version was being used in
DJ jboss.net. I don't know if there are any tests of jboss.net: the module
DJ appears to compile fine.
DJ If this has broken something let me know. I'd prefer to fix it in xdoclet
DJ if possible since the xdoclet 1.2 release is imminent.
DJ
DJ I also don't know if the catalina module still works and don't know how to
DJ test it. I only partially converted that build.xml, leaving the previous
DJ definitions commented out. Again, info appreciated.
DJ thanks
DJ david jencks
--
Best regards,
Alex Loubyansky
---
In remembrance
www.osdn.com/911/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] jboss 4 build system changes, possible jboss.net and catalina impact.
Another problem, David. When cleaning up I get the following exception. The file exists and can deleted manually w/o problems. Or is it just my own problem? Thank you. alex _buildmagic:clean: [delete] Deleting directory C:\CVSROOT\jboss-all\j2ee\output BUILD FAILED jar:file:/C:/CVSROOT/jboss-all/tools/lib/buildmagic-tasks.jar!/org/jboss/tools/buildmagic/common.xml:124: Unable to delete file C:\CVSROOT\jboss-all\j2ee\output\lib\jboss-j2ee.jar at org.apache.tools.ant.taskdefs.Delete.removeDir(Delete.java:388) at org.apache.tools.ant.taskdefs.Delete.removeDir(Delete.java:381) at org.apache.tools.ant.taskdefs.Delete.execute(Delete.java:327) at org.apache.tools.ant.Task.perform(Task.java:317) at org.apache.tools.ant.Target.execute(Target.java:309) at org.apache.tools.ant.Target.performTasks(Target.java:334) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.jboss.tools.buildmagic.task.Ant.execute(Ant.java:261) at org.jboss.tools.buildmagic.task.module.ExecuteModules.executeModule(ExecuteModules.java:292) at org.jboss.tools.buildmagic.task.module.ExecuteModules.execute(ExecuteModules.java:194) at org.apache.tools.ant.Task.perform(Task.java:317) at org.apache.tools.ant.Target.execute(Target.java:309) at org.apache.tools.ant.Target.performTasks(Target.java:334) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.Project.executeTargets(Project.java:1250) at org.apache.tools.ant.Main.runBuild(Main.java:610) at org.apache.tools.ant.Main.start(Main.java:196) at org.apache.tools.ant.Main.main(Main.java:235) Wednesday, September 11, 2002, 1:15:11 AM, you wrote: DJ I replaced many of the repetitive elements in the build.xml files with DJ parameter entities, including the definition of xdoclet tasks. As far as I DJ can tell this hasn't affected anything according to the testsuite. DJ However, one effect is that xdoclet is now always the global xdoclet in DJ thirdparty. Previously it looks like a local version was being used in DJ jboss.net. I don't know if there are any tests of jboss.net: the module DJ appears to compile fine. DJ If this has broken something let me know. I'd prefer to fix it in xdoclet DJ if possible since the xdoclet 1.2 release is imminent. DJ DJ I also don't know if the catalina module still works and don't know how to DJ test it. I only partially converted that build.xml, leaving the previous DJ definitions commented out. Again, info appreciated. DJ thanks DJ david jencks -- Best regards, Alex Loubyansky --- In remembrance www.osdn.com/911/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] jboss 4 build system changes, possible jboss.net and catalina impact.
Hello David, Wednesday, September 11, 2002, 8:00:25 PM, you wrote: DJ Maybe this is a windows only problem? I didn't have a problem cleaning on DJ linux. Maybe.. I have it permanently. Am I along here? DJ BTW I didn't modify the build.bat files to increase the memory, which was DJ required on my linux system to do build.sh all. Could you try build.bat DJ all and add the -X. stuff if necessary? set ANT_OPTS=%ANT_OPTS% -Xmx640m As in build.sh but it doesn't help. Thank you. alex DJ On 2002.09.11 12:45:30 -0400 Alex Loubyansky wrote: Another problem, David. When cleaning up I get the following exception. The file exists and can deleted manually w/o problems. Or is it just my own problem? Thank you. alex _buildmagic:clean: [delete] Deleting directory C:\CVSROOT\jboss-all\j2ee\output BUILD FAILED jar:file:/C:/CVSROOT/jboss-all/tools/lib/buildmagic-tasks.jar!/org/jboss/tools/buildmagic/common.xml:124: Unable to delete file C:\CVSROOT\jboss-all\j2ee\output\lib\jboss-j2ee.jar at org.apache.tools.ant.taskdefs.Delete.removeDir(Delete.java:388) at org.apache.tools.ant.taskdefs.Delete.removeDir(Delete.java:381) at org.apache.tools.ant.taskdefs.Delete.execute(Delete.java:327) at org.apache.tools.ant.Task.perform(Task.java:317) at org.apache.tools.ant.Target.execute(Target.java:309) at org.apache.tools.ant.Target.performTasks(Target.java:334) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.jboss.tools.buildmagic.task.Ant.execute(Ant.java:261) at org.jboss.tools.buildmagic.task.module.ExecuteModules.executeModule(ExecuteModules.java:292) at org.jboss.tools.buildmagic.task.module.ExecuteModules.execute(ExecuteModules.java:194) at org.apache.tools.ant.Task.perform(Task.java:317) at org.apache.tools.ant.Target.execute(Target.java:309) at org.apache.tools.ant.Target.performTasks(Target.java:334) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.Project.executeTargets(Project.java:1250) at org.apache.tools.ant.Main.runBuild(Main.java:610) at org.apache.tools.ant.Main.start(Main.java:196) at org.apache.tools.ant.Main.main(Main.java:235) --- In remembrance www.osdn.com/911/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jdk dependent build
Hello, guys!
I remember threads on this but don't remember the conclusion (if it
was made).
To support JDBC-3.0 code, I have to decide whether to compile sources
depending on the JDK version.
For now I solve it this way
target name=set-java-version
condition property=jdk1.4
equals arg1=${ant.java.version} arg2=1.4/
/condition
/target
target name=compile-for-1.4 if=jdk1.4 depends=set-java-version
...
/target
I consider it rough. Especially when the sources are processed by
XDoclet. Do someone know/use a better way?
alex
---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JCAConnectionFactory undeployment bug and patch
Hello Andreas,
to my pity, I don't have it now and, probably, will see it next time on Monday.
But the only thing I changed is the way to construct search criteria in
JCAConnectionFactory.destroy(...) method. Please, look at the original post for
the details.
You're right I just added two properties J2EEServer=Local and JCAResource=JCA.
And it started to work.
I noted one more thing. The original query (without the changes) was executed
twice. ( At least I saw it twice in the log ) Probably, from another code
source.
It's still not clear for me too. I'll try to dig further.
Thank you for the comments.
alex
On Fri, 16 Aug 2002 20:05:22 -0700
Andreas Schaefer [EMAIL PROTECTED] wrote:
Hi Alex
Can you send me your changed JCAConnectionFactory because
what you write doesn't make sense for me (except adding new
parameters there is no differences AFAI see).
Thanx - Andy
- Original Message -
From: Alex Loubyansky [EMAIL PROTECTED]
To: JBoss-Dev [EMAIL PROTECTED]
Sent: Friday, August 16, 2002 12:54 PM
Subject: [JBoss-dev] JCAConnectionFactory undeployment bug and patch
Hello guys,
there is a bug in JCAConnectionFactory undeployment (I guess in all
3.0 branches). Here are the details (I played with MySQL). When it is
created the
J2EEManagedObject is created with a name like:
J2EEServer=Local,JCAResource=JCA,j2eeType=JCAConnectionFactory,name=MySqlDS-
LocalTxCM
But when it is undeployed, this object isn't removed and remains
registered. Thus redeployment will fail.
The JCAConnectionFactory.destroy() method searches with criteria:
J2EEManagedObject.getDomainName() + : +
J2EEManagedObject.TYPE + = + JCAConnectionFactory.J2EE_TYPE + , +
name= + pName + , +
*
which results in
jboss.management.local:j2eeType=JCAConnectionFactory,name=MySqlDS-LocalTxCM,
*
Id it correct? I am still not good at it but it doesn't work.
I changed the criteria to:
ObjectName lServer = null;
try {
lServer = (ObjectName) pServer.queryNames(
new ObjectName(
J2EEManagedObject.getDomainName() + : +
J2EEManagedObject.TYPE + = + J2EEServer.J2EE_TYPE + , +
*
),
null
).iterator().next();
}
catch( Exception e ) {
lLog.error( Could not locate JSR-77 Server: + pName, e );
}
ObjectName lJCAResource = null;
try {
// Check if the JCA Resource exists and if not create one
Set lNames = pServer.queryNames(
new ObjectName(
J2EEManagedObject.getDomainName() + : +
J2EEManagedObject.TYPE + = + JCAResource.J2EE_TYPE + , +
*
),
null
);
if( lNames.isEmpty() ) {
// Now create the JCA resource
lJCAResource = JCAResource.create( pServer, JCA );
} else {
lJCAResource = (ObjectName) lNames.iterator().next();
}
}
catch( Exception e ) {
lLog.error( Could not create JSR-77 JCA resource, e );
}
String searchCriteria =
J2EEManagedObject.getDomainName() + : +
J2EEServer.J2EE_TYPE + = +
lServer.getKeyProperty( name ) + , +
JCAResource.J2EE_TYPE + = +
lJCAResource.getKeyProperty( name ) + , +
J2EEManagedObject.TYPE + = + JCAConnectionFactory.J2EE_TYPE + , +
name= + pName + , +
*;
This criteria is:
J2EEServer=Local,JCAResource=JCA,j2eeType=JCAConnectionFactory,name=MySqlDS-
LocalTxCM,*
And it works. I guess it's a weird way. Please, comment it.
TIA!
--
Best regards,
Alex Loubyansky
---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
~
Alex Loubyansky
http://mobila.net.ua
???
---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] JCAConnectionFactory undeployment bug and patch
Hello guys,
there is a bug in JCAConnectionFactory undeployment (I guess in all
3.0 branches). Here are the details (I played with MySQL). When it is created the
J2EEManagedObject is created with a name like:
J2EEServer=Local,JCAResource=JCA,j2eeType=JCAConnectionFactory,name=MySqlDS-LocalTxCM
But when it is undeployed, this object isn't removed and remains
registered. Thus redeployment will fail.
The JCAConnectionFactory.destroy() method searches with criteria:
J2EEManagedObject.getDomainName() + : +
J2EEManagedObject.TYPE + = + JCAConnectionFactory.J2EE_TYPE + , +
name= + pName + , +
*
which results in
jboss.management.local:j2eeType=JCAConnectionFactory,name=MySqlDS-LocalTxCM,*
Id it correct? I am still not good at it but it doesn't work.
I changed the criteria to:
ObjectName lServer = null;
try {
lServer = (ObjectName) pServer.queryNames(
new ObjectName(
J2EEManagedObject.getDomainName() + : +
J2EEManagedObject.TYPE + = + J2EEServer.J2EE_TYPE + , +
*
),
null
).iterator().next();
}
catch( Exception e ) {
lLog.error( Could not locate JSR-77 Server: + pName, e );
}
ObjectName lJCAResource = null;
try {
// Check if the JCA Resource exists and if not create one
Set lNames = pServer.queryNames(
new ObjectName(
J2EEManagedObject.getDomainName() + : +
J2EEManagedObject.TYPE + = + JCAResource.J2EE_TYPE + , +
*
),
null
);
if( lNames.isEmpty() ) {
// Now create the JCA resource
lJCAResource = JCAResource.create( pServer, JCA );
} else {
lJCAResource = (ObjectName) lNames.iterator().next();
}
}
catch( Exception e ) {
lLog.error( Could not create JSR-77 JCA resource, e );
}
String searchCriteria =
J2EEManagedObject.getDomainName() + : +
J2EEServer.J2EE_TYPE + = +
lServer.getKeyProperty( name ) + , +
JCAResource.J2EE_TYPE + = +
lJCAResource.getKeyProperty( name ) + , +
J2EEManagedObject.TYPE + = + JCAConnectionFactory.J2EE_TYPE + , +
name= + pName + , +
*;
This criteria is:
J2EEServer=Local,JCAResource=JCA,j2eeType=JCAConnectionFactory,name=MySqlDS-LocalTxCM,*
And it works. I guess it's a weird way. Please, comment it.
TIA!
--
Best regards,
Alex Loubyansky
---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Container.getJmxName()
Hello!
Recently, I had problems with scoped-EARs deployment. I checked the
working test case and found that a bean despite of whether it has
only a local interface must have unique jndi-name besides
local-jndi-name.
The reason is that Container's jmx name is constructed with the
following method:
public ObjectName getJmxName()
{
String jndiName = getBeanMetaData().getJndiName();
if (jndiName == null)
{
throw new IllegalStateException(cannot get Container object name unless jndi
name is set!);
} // end of if ()
if (jmxName == null)
{
jmxName = ObjectNameFactory.create(BASE_EJB_CONTAINER_NAME + ,jndiName= +
jndiName);
} // end of if ()
return jmxName;
}
My beans with local intf didn't suspect this and didn't specify
jndi-name. When container was registered it asked a jndi-name.
BeanMetaData can't refuse with null value and returns ejb-name if
jndi-name is absent. Thus I couldn't get EARs scoped-deployed.
The conclusion is: to get EARs scoped-deployed, beans should have
different ejb-name, or jndi-name.
Or maybe it's better to change jmx name for container?
Say, change jndiName in the getJmxName() as:
BeanMetaData bmd = getBeanMetaData();
jndiName = bmd.getHome() != null ? bmd.getJndiName() : bmd.getLocalJndiName();
or construct jmxName as ObjectNameFactory.create(BASE_EJB_CONTAINER_NAME +
,localJndiName= + localJndiName);
if bean doesn't have remote intf. But in this case conatiners will
have different name structure.
Any comments? TIA.
--
Best regards,
Alex Loubyansky
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[6]: [JBoss-dev] Container.getJmxName()
SMS There is only one level of commit access, so your 3.0 working SMS directory must be checked out as anonymous or something. If SMS you can commit to head you can commit to any branch. But that's not my fiction. It's a quote. Maybe it was eventually. SMS I'm working on a scoping issue so leave the branches to me. Ok, so, no problem. Thanks! -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] problems with JBossMQ
Uh... Today even worse. Just have checked out cvs and couldn't even start JBoss w/o that exception. -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] problems with JBossMQ
(MBeanServerImpl.java:549) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy5.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:804) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:634) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:599) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:582) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy6.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:232) at org.jboss.Main.boot(Main.java:152) at org.jboss.Main$1.run(Main.java:385) at java.lang.Thread.run(Thread.java:484) -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] current cvs version can't be built
Hello guys,
just have checked out cvs for jboss-3.1.0alpha and couldn't build it.
compile-classes:
[javac] Compiling 165 source files to C:\CVSROOT\jboss-all\messaging\output\classes
C:\CVSROOT\jboss-all\messaging\src\main\org\jboss\mq\server\jmx\DelayInterceptor.java:42:
cannot resolve symbol
symbol : class DelayInterceptorMBean
location: class org.jboss.mq.server.jmx.DelayInterceptor
implements DelayInterceptorMBean {
^
C:\CVSROOT\jboss-all\messaging\src\main\org\jboss\mq\server\jmx\DestinationManager.java:44:
cannot resolve symbol
symbol : class DestinationManagerMBean
location: class org.jboss.mq.server.jmx.DestinationManager
implements DestinationManagerMBean
^
C:\CVSROOT\jboss-all\messaging\src\main\org\jboss\mq\server\jmx\InterceptorLoader.java:25:
cannot resolve symbol
symbol : class InterceptorLoaderMBean
location: class org.jboss.mq.server.jmx.InterceptorLoader
implements InterceptorLoaderMBean
^
C:\CVSROOT\jboss-all\messaging\src\main\org\jboss\mq\server\jmx\Invoker.java:25:
cannot resolve symbol
symbol : class InvokerMBean
location: class org.jboss.mq.server.jmx.Invoker
implements InvokerMBean
^
C:\CVSROOT\jboss-all\messaging\src\main\org\jboss\mq\server\jmx\Queue.java:29: cannot
resolve symbol
symbol : class QueueMBean
location: class org.jboss.mq.server.jmx.Queue
implements QueueMBean
^
C:\CVSROOT\jboss-all\messaging\src\main\org\jboss\mq\server\jmx\Topic.java:33: cannot
resolve symbol
symbol : class TopicMBean
location: class org.jboss.mq.server.jmx.Topic
implements TopicMBean
^
6 errors
BUILD FAILED
file:C:/CVSROOT/jboss-all/messaging/build.xml:390: Compile failed; see the compiler
error output for details.
at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:842)
at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:682)
at org.apache.tools.ant.Task.perform(Task.java:317)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:334)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.jboss.tools.buildmagic.task.Ant.execute(Ant.java:261)
at
org.jboss.tools.buildmagic.task.module.ExecuteModules.executeModule(ExecuteModules.java:292)
at
org.jboss.tools.buildmagic.task.module.ExecuteModules.execute(ExecuteModules.java:194)
at org.apache.tools.ant.Task.perform(Task.java:317)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:334)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
at org.apache.tools.ant.Main.runBuild(Main.java:610)
at org.apache.tools.ant.Main.start(Main.java:196)
at org.apache.tools.ant.Main.main(Main.java:235)
--
Best regards,
Alex Loubyansky
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] current cvs version can't be built
Hello Hiram,
builds successfully. Thanks!
alex
Monday, July 22, 2002, 3:43:31 PM, you wrote:
HC try it again.. I forgot to check something in.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Alex
Loubyansky
Sent: Monday, July 22, 2002 2:54 AM
To: JBoss-Dev
Subject: [JBoss-dev] current cvs version can't be built
Hello guys,
just have checked out cvs for jboss-3.1.0alpha and couldn't build it.
compile-classes:
[javac] Compiling 165 source files to
C:\CVSROOT\jboss-all\messaging\output\classes
C:\CVSROOT\jboss-all\messaging\src\main\org\jboss\mq\server\jmx\De
layInterceptor.java:42: cannot resolve symbol
symbol : class DelayInterceptorMBean
location: class org.jboss.mq.server.jmx.DelayInterceptor
implements DelayInterceptorMBean {
^
C:\CVSROOT\jboss-all\messaging\src\main\org\jboss\mq\server\jmx\De
stinationManager.java:44: cannot resolve symbol
symbol : class DestinationManagerMBean
location: class org.jboss.mq.server.jmx.DestinationManager
implements DestinationManagerMBean
^
C:\CVSROOT\jboss-all\messaging\src\main\org\jboss\mq\server\jmx\In
terceptorLoader.java:25: cannot resolve symbol
symbol : class InterceptorLoaderMBean
location: class org.jboss.mq.server.jmx.InterceptorLoader
implements InterceptorLoaderMBean
^
C:\CVSROOT\jboss-all\messaging\src\main\org\jboss\mq\server\jmx\In
voker.java:25: cannot resolve symbol
symbol : class InvokerMBean
location: class org.jboss.mq.server.jmx.Invoker
implements InvokerMBean
^
C:\CVSROOT\jboss-all\messaging\src\main\org\jboss\mq\server\jmx\Qu
eue.java:29: cannot resolve symbol
symbol : class QueueMBean
location: class org.jboss.mq.server.jmx.Queue
implements QueueMBean
^
C:\CVSROOT\jboss-all\messaging\src\main\org\jboss\mq\server\jmx\To
pic.java:33: cannot resolve symbol
symbol : class TopicMBean
location: class org.jboss.mq.server.jmx.Topic
implements TopicMBean
^
6 errors
BUILD FAILED
file:C:/CVSROOT/jboss-all/messaging/build.xml:390: Compile
failed; see the compiler error output for details.
at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:842)
at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:682)
at org.apache.tools.ant.Task.perform(Task.java:317)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:334)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.jboss.tools.buildmagic.task.Ant.execute(Ant.java:261)
at
org.jboss.tools.buildmagic.task.module.ExecuteModules.executeModul
e(ExecuteModules.java:292)
at
org.jboss.tools.buildmagic.task.module.ExecuteModules.execute(Exec
uteModules.java:194)
at org.apache.tools.ant.Task.perform(Task.java:317)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:334)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
at org.apache.tools.ant.Main.runBuild(Main.java:610)
at org.apache.tools.ant.Main.start(Main.java:196)
at org.apache.tools.ant.Main.main(Main.java:235)
--
Best regards,
Alex Loubyansky
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
HC ---
HC This sf.net email is sponsored by:ThinkGeek
HC Welcome to geek heaven.
HC http://thinkgeek.com/sf
HC ___
HC Jboss-development mailing list
HC [EMAIL PROTECTED]
HC https://lists.sourceforge.net/lists/listinfo/jboss-development
--
Best regards,
Alex Loubyansky
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Realm TomcatJboss Configuration
Hello Ruben, Wednesday, July 17, 2002, 2:11:17 PM, you wrote: RN Hello, i am trying to configure Tomcat to add a JDBC Realm, i have installed Do you want to configure JDBC based loging module? It's done in login-config.xml. There are examples for datasource login configurations in docs directory. Or you want to configure DabaseServerLoginModule? alex RN the TomcatJboss embedded version, i need to know what config file i need to RN change to add the realm... RN I would like too to have some tutorials or any kind of help about the RN Realms... RN Thanks good bye RN --- RN This sf.net email is sponsored by:ThinkGeek RN Welcome to geek heaven. RN http://thinkgeek.com/sf RN ___ RN Jboss-development mailing list RN [EMAIL PROTECTED] RN https://lists.sourceforge.net/lists/listinfo/jboss-development -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] Realm TomcatJboss Configuration
What JBoss version do you use? login-config.xml is used since 3.0. And you should find docs directory with examples for datasource configurations including login configuration. alex RN hello Alex, thanks for your time... i havent found the login-config.xml... , RN and yes, i want to configure JDBC based loging module, i have readed that RN the realms are for this... i have found documentation for tomcat, but for RN the embedded installation nothing... RN Thanks again RN Ruben RN -Original Message- RN From: Alex Loubyansky [mailto:[EMAIL PROTECTED]] RN Sent: 17 July 2002 13:30 RN To: Ruben Nistal RN Cc: '[EMAIL PROTECTED]' RN Subject: Re: [JBoss-dev] Realm TomcatJboss Configuration RN Hello Ruben, RN Wednesday, July 17, 2002, 2:11:17 PM, you wrote: RN Hello, i am trying to configure Tomcat to add a JDBC Realm, i have RN installed RN Do you want to configure JDBC based loging module? RN It's done in login-config.xml. RN There are examples for datasource login configurations in docs RN directory. RN Or you want to configure DabaseServerLoginModule? RN alex RN the TomcatJboss embedded version, i need to know what config file i RN need to RN change to add the realm... RN I would like too to have some tutorials or any kind of help about the RN Realms... RN Thanks good bye RN --- RN This sf.net email is sponsored by:ThinkGeek RN Welcome to geek heaven. RN http://thinkgeek.com/sf RN ___ RN Jboss-development mailing list RN [EMAIL PROTECTED] RN https://lists.sourceforge.net/lists/listinfo/jboss-development -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] Realm TomcatJboss Configuration
Hello marc, I am sorry, guys. I haven't looked at the address. Yes, I'll do next time. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] Build broken?
Hello Dain, don't feel alone, I'm with you. Monday, July 01, 2002, 7:02:45 PM, you wrote: DS I ment I CAN'T build a clean checkout. DS Dain Sundstrom wrote: What is up the cvs HEAD? I can build a clean checkout. I get the following errors: [execmodules] /home/dain/work/jboss/jboss-all/jmx/src/main/org/jboss/mx/util/MBe anInstaller.java:79: cannot resolve symbol [execmodules] symbol : method getVersions () [execmodules] location: class org.jboss.mx.loading.MBeanElement [execmodules] if (element.getVersions() == null) [execmodules] ^ [execmodules] /home/dain/work/jboss/jboss-all/jmx/src/main/org/jboss/mx/util/MBe anInstaller.java:125: cannot resolve symbol [execmodules] symbol : method getVersions () [execmodules] location: class org.jboss.mx.loading.MBeanElement [execmodules] MLetVersion newVersion = new MLetVersion(element.getVersion s()); [execmodules]^ [execmodules] /home/dain/work/jboss/jboss-all/jmx/src/main/org/jboss/mx/util/MBe anInstaller.java:149: cannot resolve symbol [execmodules] symbol : method getVersions () [execmodules] location: class org.jboss.mx.loading.MBeanElement [execmodules] if (element.getVersions() != null) [execmodules] ^ [execmodules] /home/dain/work/jboss/jboss-all/jmx/src/main/org/jboss/mx/util/MBe anInstaller.java:150: cannot resolve symbol [execmodules] symbol : method getVersions () [execmodules] location: class org.jboss.mx.loading.MBeanElement [execmodules] valueMap.put(VERSIONS, element.getVersions()); [execmodules]^ -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] relationship keys mapping
Hi Dain, I remember someone was working on the problem of mapping primary keys of one bean to related primary keys of another bean. I'd like to know whether it's in progress now. If not maybe I could help solve it? Thanks. -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] unsubcribe
NOT AT ALL. Now you belong to us, man... PS: go to http://lists.sourceforge.net/lists/listinfo/jboss-user enter your e-mail select Edit Options and so on... Thursday, June 27, 2002, 3:25:58 PM, you wrote: AV __ AV Do You Yahoo!? AV Yahoo! - Official partner of 2002 FIFA World Cup AV http://fifaworldcup.yahoo.com AV --- AV Sponsored by: AV ThinkGeek at http://www.ThinkGeek.com/ AV ___ AV Jboss-development mailing list AV [EMAIL PROTECTED] AV https://lists.sourceforge.net/lists/listinfo/jboss-development -- Best regards, Alex Loubyansky --- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] deploying waiting deployments
Hello David,
thank you for your feedback.
DJ Maybe you should factor out the try all waiting packages with new
DJ deployer functionality so it can be triggered by a new deployer or you can
DJ call it directly from the foe deployer.
Factor out?.. What do you mean? In what place?
For now, all foe apps are deployed with FoeDeployer. All converters
inherit Converter interface. Like deployers are registered with
MainDeployer when started with MainDeployer.addDeployer(), converters are
registered with FoeDeployer by FoeDeployer.addConverter(). In
FoeDeployer.addConverter() converter is added to the list of
converters and in this method I try to deploy waiting deployments. So,
it's done in FoeDeployer.
Do you mean adding functionality to try redeploy waiting deployments to MainDeployer?
I follow the idea that FoeDeployer isn't a core service of JBoss and
shouldn't cause changes of core JBoss classes if possible.
DJ Or you could change your design a bit and make each converter into a
DJ subdeployer that registers with MainDeployer, using centralized services
DJ from a FoeDeploymentServices mbean. (Just an idea, I haven't actually
DJ looked at your design).
This is the solution too. Though, I would, probably, inherit
converters from FoeDeployer and make them independent in this case.
For now we agreed with Andreas to not change the existing design and
implement at least WebLogicConvertor to get something actually working.
But nevertheless I had to redeploy waiting deployments. So, that's the
reason of the question. I think for now I just leave it as it is.
Thank you again! :)
alex
DJ please refactor MainDeployer before copying its functionality.
DJ david jencks
DJ On 2002.06.26 13:55:53 -0400 Alex Loubyansky wrote:
Hi guys,
what is the best way to deploy waiting deployments?
As I understand it right, the only time when waiting deployments have
a chance to be deployed is when their deployer is started.
That works with existing deployers. But FoeDeployer has dynamic
diployment abilities, i.e. once it is able to deploy some deployments and
later it could not be able to deploy them or could be able to deploy
deployments that couldn't be able to deploy earlier.
This is due to adding and removing vendor specific convertors (that
are mbeans and depend on foe-deployer).
So, for now when new convertor is added I have to try to deploy waiting
deployments. I do it this way:
Collection waitingDeployments = mMainDeployer.listWaitingForDeployer();
if((waitingDeployments != null) (waitingDeployments.size() 0))
{
for(Iterator iter = waitingDeployments.iterator(); iter.hasNext();)
{
DeploymentInfo di = (DeploymentInfo)iter.next();
// check whether the convertor accepts the deployment
if(!newConvertor.accepts(di, null)) continue;
log.debug(trying to deploy with new convertor: + di.shortName);
try
{
mMainDeployer.undeploy(di);
mMainDeployer.deploy(di);
}
catch (DeploymentException e)
{
log.error(DeploymentException while trying to deploy a package
with a new convertor, e);
}
}
}
Looks roughly as for me. What do you think? Any suggestions?
TIA
--
Best regards,
Alex Loubyansky
---
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Getting UserTransaction object for Transaction Management
Hello Dharma, actually, UserTransaction is its JNDI name. It's bound in the global context. You can verify whether it's really boud by checking JNDIView (localhost:8082) alex -Original Message- From: Dharma Kishore [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Tue, 11 Jun 2002 11:48:37 +0530 Subject: [JBoss-dev] Getting UserTransaction object for Transaction Management Hello, I am trying to use Transaction Management facility in Jboss server. To do that first I tried to get the UserTransaction object using JNDI look up.But I don't know what JNDI name I should use to get the UserTransaction Objet. Can anyone provide me the solution with code? Thanks in advance. Thanks and Regards, Dharma Kishore ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development - ðÏÌÕÞÉÔÅ ÂÅÓÐÌÁÔÎÙÊ ÐÏÞÔÏ×ÙÊ ÑÝÉË @ukr.net ÎÁ http://freemail.ukr.net ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] web security constraints
Hi, I have problems with defining security constraints in web.xml. I defined two roles. For each role I defined its own security-constraint. But only the first defined constraint works properly. It seems like the constraint for the second role is omitted. And accessing restricted urls with the second role results in Access to requested resource has been denied. If I change the order of security-constraint elements in web.xml then other role is authenticated/authorized properly. Has anyone experienced such a problem? What do I do wrong? TIA, alex Environment: JBoss-3.1.0alpha/Tomcat-4.0.2, Win2000, JDK-1.4 Here is the security constraints: security-constraint web-resource-collection web-resource-nameMTCatalog Admin/web-resource-name descriptionadmin constraint/description url-pattern/*/url-pattern http-methodHEAD/http-method http-methodGET/http-method http-methodPOST/http-method http-methodPUT/http-method http-methodDELETE/http-method /web-resource-collection auth-constraint role-nameAdmin/role-name /auth-constraint user-data-constraint descriptionno description/description transport-guaranteeNONE/transport-guarantee /user-data-constraint /security-constraint security-constraint web-resource-collection web-resource-nameMTCatalog ResourceOwner/web-resource-name descriptionowner constraint/description url-pattern/*/url-pattern http-methodHEAD/http-method http-methodGET/http-method http-methodPOST/http-method http-methodPUT/http-method http-methodDELETE/http-method /web-resource-collection auth-constraint role-nameResourceOwner/role-name /auth-constraint user-data-constraint descriptionno description/description transport-guaranteeNONE/transport-guarantee /user-data-constraint /security-constraint -- Best regards, Alex Loubyansky ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: web security constraints
Sorry for posting to dev-list. Unintentionally Monday, June 10, 2002, 11:56:54 AM, you wrote: AL Hi, AL I have problems with defining security constraints in web.xml. I AL defined two roles. For each role I defined its own security-constraint. AL But only the first defined constraint works properly. It seems like the constraint AL for the second role is omitted. And accessing restricted urls with the AL second role results in Access to requested resource has been denied. AL If I change the order of security-constraint elements in web.xml then AL other role is authenticated/authorized properly. AL Has anyone experienced such a problem? What do I do wrong? AL TIA, AL alex AL Environment: JBoss-3.1.0alpha/Tomcat-4.0.2, Win2000, JDK-1.4 AL Here is the security constraints: AL security-constraint AL web-resource-collection AL web-resource-nameMTCatalog Admin/web-resource-name AL descriptionadmin constraint/description AL url-pattern/*/url-pattern AL http-methodHEAD/http-method AL http-methodGET/http-method AL http-methodPOST/http-method AL http-methodPUT/http-method AL http-methodDELETE/http-method AL /web-resource-collection AL auth-constraint AL role-nameAdmin/role-name AL /auth-constraint AL user-data-constraint AL descriptionno description/description AL transport-guaranteeNONE/transport-guarantee AL /user-data-constraint AL /security-constraint AL security-constraint AL web-resource-collection AL web-resource-nameMTCatalog ResourceOwner/web-resource-name AL descriptionowner constraint/description AL url-pattern/*/url-pattern AL http-methodHEAD/http-method AL http-methodGET/http-method AL http-methodPOST/http-method AL http-methodPUT/http-method AL http-methodDELETE/http-method AL /web-resource-collection AL auth-constraint AL role-nameResourceOwner/role-name AL /auth-constraint AL user-data-constraint AL descriptionno description/description AL transport-guaranteeNONE/transport-guarantee AL /user-data-constraint AL /security-constraint -- Best regards, Alex Loubyansky ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] WL's persistence to JBoss' commit-options
Hi guys, please look at this and tell whether you agree or don't. I need your either yes and no votes. So, here one of the most interesting stuff in wl to jboss mapping goes: commit options. I've done it this way: 1. !-- IF -- !-- Descr: The read-timeout-seconds is the number of seconds between ejbLoad calls on a Read-Only entity bean. If read-timeout-seconds is 0, ejbLoad will only be called when the bean is brought into the cache. -- !-- Requirements: optional -- !-- Range: 0 to maxSeconds -- !-- Default: 600 -- read-timeout-seconds0/read-timeout-seconds concurrency-strategyReadOnly/concurrency-strategy !-- other possible values for concurrency-strategy are: - Exclusive: The exclusive locking scheme used in WebLogic Server versions 3.1 through 5.1 - Database: A scheme where a separate Entity Bean instance is allocated for each transaction and the locking and caching is handled by the database. These aren't used while convertion -- !-- OR -- !-- Descr: The value of db-is-shared must be True or False. This parameter applies only to entity beans. If the value is set to False the container will assume that it has exclusive access to the bean data in the persistence store. If it is set to True the bean will assume that the bean data could be modified between transactions and will therefore reload data at the beginning of each transaction. -- !-- Requirements: optional -- !-- Range: true, false -- !-- Default: true -- db-is-sharedfalse/db-is-shared !-- THEN -- commit-optionA/commit-option 2. !-- IF -- read-timeout-secondsN/read-timeout-seconds !-- N is not 0 -- concurrency-strategyReadOnly/concurrency-strategy !-- THEN -- commit-optionD/commit-option optiond-refresh-rateN/optiond-refresh-rate 3. !-- IF -- db-is-sharedtrue/db-is-shared !-- THEN -- commit-optionC/commit-option That's all. I haven't found a configuration matching commit-option B. Below are other wl's settings that affect beans' persistence but I omitted them. All thoughts and propositions are greatly appreciated. TIA, alex *** !-- Descr: The passivation-strategy can be either default or transaction. With the default setting the container will attempt to keep a working set of beans in the cache. With the transaction setting, the container will passivate the bean after every transaction (or method call for a non-transactional invocation). -- !-- Requirements: optional -- !-- Range: default, transaction -- !-- Default: default -- passivation-strategydefault/passivation-strategy Omitted because: With all four commit options the container must synchronize the bean instances cached state with the persistent storage (via ejbStore) at the end of each transaction (just before a commit is done) to be sure the whole transactions state is consistently persistent *** !--Descr: Applies to bean managed persistence or EJB 1.1 container-managed persistence entity EJBs. EJB 2.0 entity EJBs do not need to implement an is-modified-method. The EJB container can automatically detect which fields were modified in a transaction. This parameter declares the name of an EJBean method that tells the container whether the bean data has been modified. The method is called when the bean managed EJBean is stored. If a method is not specified, WebLogic always assumes that the EJBean has been modified and always saves it. Providing a method and setting it as appropriate will improve performance. -- !-- Requirements: optional -- is-modified-method-namesemidivine/is-modified-method-name In recent docs BEA doesn't recomend to use this tag and suggest to rely on the container for updating modified fields. Heh :))) Thanks, BEA! *** !-- Descr: Applicable to entity beans only (both container- and bean-managed). This optional optimization affects when changes to a bean's state propogated to the persistent store. If this is set to True (which is the default) updates of the persistent store of all beans in the transaction will be performed just before the end of the transaction. If this is set to False the pstore update of a bean will be performed at the conclusion of each method invoke. -- !-- Requirements: optional -- !-- Range: true, false -- !-- Default: true -- delay-updates-until-end-of-txfalse/delay-updates-until-end-of-tx ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -
Re[2]: [JBoss-dev] WL's persistence to JBoss' commit-options
Thanks David! !-- Descr: The passivation-strategy can be either default or transaction. With the default setting the container will attempt to keep a working set of beans in the cache. With the transaction setting, the container will passivate the bean after every transaction (or method call for a non-transactional invocation). -- !-- Requirements: optional -- !-- Range: default, transaction -- !-- Default: default -- passivation-strategydefault/passivation-strategy Omitted because: With all four commit options the container must synchronize the bean instances cached state with the persistent storage (via ejbStore) at the end of each transaction (just before a commit is done) to be sure the whole transactions state is consistently persistent isn't this one the difference between options B and C? First, I thought about it too. And still not sure As I understand, the only difference between B and C is that for B ejbLoad is called only for methods running in a transaction while for C ejbLoad is called for every one. Also, ejbStore is called just before the commit of a transaction is done for all options. And as online docs says: Never write access a bean outside a transaction context believing ejbStore will be called for synchronization, it typically will not (though somtimes it might, when the container passivates the bean) be called So, I don't think it's definitely option B. Thus, I consider it to be C. Other thought? TIA, alex ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] resource-ref vs resource-env-ref
Hi guys. I need your advice. I map weblogic's dd's to jboss' equivalents for foe-deployer. Gloomy stuff :) But nevertheless... In WL6.X there is a resource-description tag that is an equivalent of ours resource-ref and there is resource-env-description that is an equivalent of ours resource-env-ref. Their dtd's look like this: !ELEMENT resource-description (res-ref-name, jndi-name) !ELEMENT resource-env-description (res-env-ref-name, jndi-name) And for current WL's version (7.0 beta) BEA said that resource-description is no longer supported. It seems like ok for their dtd. But what about mapping to jboss? I haven't actually tried to declare datasource resources in resource-env-ref but I don't see any drawback either. Is there any actually? May I just close my eyes on it? TIA, alex ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Deployers lifecycle/logging question
Hello,
I am now testing FoeDeployer and have a question that, probably, affects
behaviour of other deployers too.
Suppose we have deployment units in the deploy dir waiting for the
deployer. And the deployer is at last deployed. I expect the following
sequence of calls on the deployer: createService(), startService and
then start to deploy utnits waiting for the deployer (done in
MainDeployer.addDeployer()). The code proves it but logging doesn't.
Here is the log:
INFO [org.jboss.deployment.MainDeployer] Starting deployment of package:
file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/wlar-examples.wlar
INFO [org.jboss.deployment.MainDeployer] Deployment of package:
file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/wlar-examples.wlar
is waiting for an appropriate deployer.
INFO [org.jboss.deployment.MainDeployer] Starting deployment of package:
file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/foe-deployer.sar
INFO [org.jboss.deployment.SARDeployer] Created ServiceModule:
jboss.management.single:J2EEServer=Single,j2eeType=ServiceModule,name=foe-deployer.sar
INFO [org.jboss.varia.deployment.FoeDeployer] Creating
INFO [org.jboss.varia.deployment.FoeDeployer] Created
INFO [org.jboss.varia.deployment.convertor.WebLogicConvertor] Creating
INFO [org.jboss.varia.deployment.convertor.WebLogicConvertor] Created
INFO [org.jboss.deployment.SARDeployer] Create MBean, name:
jboss:service=FoeDeployer, SAR Module:
jboss.management.single:J2EEServer=Single,j2eeType=ServiceModule,name=foe-deployer.sar
INFO [org.jboss.deployment.SARDeployer] Create MBean, name:
jboss:service=Convertor,type=WebLogic, SAR Module:
jboss.management.single:J2EEServer=Single,j2eeType=ServiceModule,name=foe-deployer.sar
INFO [org.jboss.varia.deployment.FoeDeployer] Starting
INFO [org.jboss.deployment.MainDeployer] Adding deployer:
org.jboss.varia.deployment.FoeDeployer@e8606c
INFO [org.jboss.deployment.MainDeployer] Starting deployment of package:
file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/wlar-examples.wlar
DEBUG [org.jboss.varia.deployment.FoeDeployer] create(), got info:
org.jboss.deployment.DeploymentInfo@ee07486d{
url=file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/wlar-examples.wlar
}
DEBUG [org.jboss.varia.deployment.FoeDeployer] undeploying document
file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/wlar-examples.wlar
INFO [org.jboss.deployment.MainDeployer] Successfully completed deployment of
package:
file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/wlar-examples.wlar
INFO [org.jboss.varia.deployment.FoeDeployer] Started
INFO [org.jboss.varia.deployment.convertor.WebLogicConvertor] Starting
INFO [org.jboss.varia.deployment.convertor.WebLogicConvertor] Started
INFO [org.jboss.deployment.MainDeployer] Successfully completed deployment of
package:
file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/foe-deployer.sar
INFO [org.jboss.deployment.MainDeployer] Starting deployment of package:
file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/wlar-examples.jar
...
So, the log says that waiting for the deployer units
(wlar-examples.wlar) are deployed before the deployer (FoeDeployer) is
actually started. And WebLogicConverter isn't started at all by the
time of successful deployment of wlar.
In FoeDeployer super.startService() is the last line in method
startService(). And converters (WebLogicConverter) are invoked in
FoeDeployer.create() method.
Could someone clarify it, please? Is it just logging?
--
Best regards,
Alex Loubyansky
___
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] Deployers lifecycle/logging question
Hello Tobias,
good question. I'd like to know too.
Friday, May 24, 2002, 1:55:26 PM, you wrote:
TF Hi Alex!
TF Does log4j guarantee to display the log messages in the order they
TF timely occured ?
TF With the old logging that wasn't the case (it was NOT guaranteed). It do
TF not know for log4j.
TF Just a thought,
TF Tobias
TF Alex Loubyansky wrote:
Hello,
I am now testing FoeDeployer and have a question that, probably, affects
behaviour of other deployers too.
Suppose we have deployment units in the deploy dir waiting for the
deployer. And the deployer is at last deployed. I expect the following
sequence of calls on the deployer: createService(), startService and
then start to deploy utnits waiting for the deployer (done in
MainDeployer.addDeployer()). The code proves it but logging doesn't.
Here is the log:
INFO [org.jboss.deployment.MainDeployer] Starting deployment of package:
file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/wlar-examples.wlar
INFO [org.jboss.deployment.MainDeployer] Deployment of package:
file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/wlar-examples.wlar
is waiting for an appropriate
deployer.
INFO [org.jboss.deployment.MainDeployer] Starting deployment of package:
file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/foe-deployer.sar
INFO [org.jboss.deployment.SARDeployer] Created ServiceModule:
jboss.management.single:J2EEServer=Single,j2eeType=ServiceModule,name=foe-deployer.sar
INFO [org.jboss.varia.deployment.FoeDeployer] Creating
INFO [org.jboss.varia.deployment.FoeDeployer] Created
INFO [org.jboss.varia.deployment.convertor.WebLogicConvertor] Creating
INFO [org.jboss.varia.deployment.convertor.WebLogicConvertor] Created
INFO [org.jboss.deployment.SARDeployer] Create MBean, name:
jboss:service=FoeDeployer, SAR Module:
jboss.management.single:J2EEServer=Single,j2eeType=ServiceModule,name=foe-deployer.sar
INFO [org.jboss.deployment.SARDeployer] Create MBean, name:
jboss:service=Convertor,type=WebLogic, SAR Module:
jboss.management.single:J2EEServer=Single,j2eeType=ServiceModule,name=foe-deployer.sar
INFO [org.jboss.varia.deployment.FoeDeployer] Starting
INFO [org.jboss.deployment.MainDeployer] Adding deployer:
org.jboss.varia.deployment.FoeDeployer@e8606c
INFO [org.jboss.deployment.MainDeployer] Starting deployment of package:
file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/wlar-examples.wlar
DEBUG [org.jboss.varia.deployment.FoeDeployer] create(), got info:
org.jboss.deployment.DeploymentInfo@ee07486d{
url=file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/wlar-examples.wlar
}
DEBUG [org.jboss.varia.deployment.FoeDeployer] undeploying document
file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/wlar-examples.wlar
INFO [org.jboss.deployment.MainDeployer] Successfully completed deployment of
package:
file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/wlar-examples.wlar
INFO [org.jboss.varia.deployment.FoeDeployer] Started
INFO [org.jboss.varia.deployment.convertor.WebLogicConvertor] Starting
INFO [org.jboss.varia.deployment.convertor.WebLogicConvertor] Started
INFO [org.jboss.deployment.MainDeployer] Successfully completed deployment of
package:
file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/foe-deployer.sar
INFO [org.jboss.deployment.MainDeployer] Starting deployment of package:
file:/C:/CVSROOT/jboss-all/build/output/jboss-3.1.0alpha/server/default/deploy/wlar-examples.jar
...
So, the log says that waiting for the deployer units
(wlar-examples.wlar) are deployed before the deployer (FoeDeployer) is
actually started. And WebLogicConverter isn't started at all by the
time of successful deployment of wlar.
In FoeDeployer super.startService() is the last line in method
startService(). And converters (WebLogicConverter) are invoked in
FoeDeployer.create() method.
Could someone clarify it, please? Is it just logging?
--
Best regards,
Alex Loubyansky
___
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] Deployers lifecycle/logging question
Hello David, I asked that because I found it strange that the deployer not being started already deploys some units, if the log is right. So, the log is like: [FoeDeployer] Starting [MainDeployer] Adding deployer: [MainDeployer] Starting deployment of package: waitinig unit [FoeDeployer] create() ... [FoeDeployer] Started when I expected it like this: [FoeDeployer] Starting [FoeDeployer] Started [MainDeployer] Adding deployer: [MainDeployer] Starting deployment of package: waitinig unit [FoeDeployer] create() ... Am I wrong? Friday, May 24, 2002, 4:20:33 PM, you wrote: DJ From your description below I think FoeDeployer depends on DJ WebLogicConverter. If you explicitly state this dependency with a depends DJ tag the deployment system will create WLC before FD and start WLC before DJ FD. If FD is designed to accept lots of converters you can use a DJ depends-list element. DJ How does FD know about WLC now? I'd recommend using an ObjectName and DJ calling through the mbean server. DJ If you want to allow dynamically adding converters you will have to make FD DJ keep a list of undeployables that it tries to deploy whenever a new DJ converter is registered. I don't think I recommend this. DJ david jencks -- Best regards, Alex Loubyansky ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] Deployers lifecycle/logging question
Hello David, Friday, May 24, 2002, 4:20:33 PM, you wrote: DJ From your description below I think FoeDeployer depends on DJ WebLogicConverter. If you explicitly state this dependency with a depends DJ tag the deployment system will create WLC before FD and start WLC before DJ FD. If FD is designed to accept lots of converters you can use a DJ depends-list element. No. WebLogicConvertor depends on FoeDeployer. And it's expressed with a depends element. In the architecture as it is exists for now I think it's the right choice. Because WLC has a deployer's name and in startService() it's added to it's deployer (FD) which contains the list of convertors. DJ How does FD know about WLC now? I'd recommend using an ObjectName and DJ calling through the mbean server. Actually, already answered. It's done this way. DJ If you want to allow dynamically adding converters you will have to make FD DJ keep a list of undeployables that it tries to deploy whenever a new DJ converter is registered. I don't think I recommend this. Do you have other remarks? Please, let me know. I am becoming crazy of it but feel have to learn more :) alex ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[3]: [JBoss-dev] Deployers lifecycle/logging question
Hello Alex, I've got it. [FoeDeployer] Starting - the beginning of the method FoeDeployer.startService() [FoeDeployer] Started - the end of it. But it looks messy in case of deploying (actually any) deployer when there are waiting deployable units. alex Friday, May 24, 2002, 4:53:33 PM, you wrote: AL Hello David, AL I asked that because I found it strange that the deployer not being AL started already deploys some units, if the log is right. So, the log AL is like: AL [FoeDeployer] Starting AL [MainDeployer] Adding deployer: AL [MainDeployer] Starting deployment of package: waitinig unit AL [FoeDeployer] create() AL ... AL [FoeDeployer] Started AL when I expected it like this: AL [FoeDeployer] Starting AL [FoeDeployer] Started AL [MainDeployer] Adding deployer: AL [MainDeployer] Starting deployment of package: waitinig unit AL [FoeDeployer] create() AL ... AL Am I wrong? AL Friday, May 24, 2002, 4:20:33 PM, you wrote: DJ From your description below I think FoeDeployer depends on DJ WebLogicConverter. If you explicitly state this dependency with a depends DJ tag the deployment system will create WLC before FD and start WLC before DJ FD. If FD is designed to accept lots of converters you can use a DJ depends-list element. DJ How does FD know about WLC now? I'd recommend using an ObjectName and DJ calling through the mbean server. DJ If you want to allow dynamically adding converters you will have to make FD DJ keep a list of undeployables that it tries to deploy whenever a new DJ converter is registered. I don't think I recommend this. DJ david jencks -- Best regards, Alex Loubyansky ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
