[JBoss-dev] [Design of Mail Services] - Re: M3 MSGSTORE->Mailbox
The hibernate msgstore will be migrating to become part of the org.jboss.mail.store package (my current task, hopefully done at end of this week). I have a couple of small tasks to do to complete the integration of the mail store (done in the next day or 2). Once that is done, things should be settled enought for Dawie to integrate the new Mailbox implementation. Dawie if you have any questions about interacting with the store let me know. MailBody/MailBodyManagerMBean should be the only classes that you need to work with. The rest is pretty much transparent. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870154#3870154 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870154 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-testsuite?log=log20050314065733
BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:66: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See tests.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 03/14/2005 06:57:33Time to build: 1,273 minutes 46 secondsLast changed: 03/13/2005 23:33:18Last log entry: Replace the Filter attribute with a FilterInstance attribute that allows the ignored prefixes, suffixes and matches. Resolves (JBAS-1494) Need to expose the filter list for the default Filter implementation on URLDeploymentScanner.
Unit Tests: (0) Total Errors and Failures: (0)
Modifications since last build: (24)1.117.2.5modifiedstarksmserver/src/etc/conf/default/jboss-service.xmlReplace the Filter attribute with a FilterInstance attribute that allows the ignored prefixes, suffixes and matches. Resolves (JBAS-1494) Need to expose the filter list for the default Filter implementation on URLDeploymentScanner.1.32.2.1modifiedstarksmsystem/src/main/org/jboss/deployment/scanner/URLDeploymentScanner.javaAdd a FilterInstance attribute that allows one to set the URLFilter instance1.6.6.1modifiedstarksmsystem/src/main/org/jboss/deployment/scanner/DeploymentFilter.javaAdd getters/setters for suffixes, prefixes and matches.1.6.4.2modifiedstarksmtestsuite/src/main/org/jboss/test/util/test/PropertyEditorsUnitTestCase.javaUpdate the string array tests to test escaped commas.1.6.6.1modifiedstarksmcommon/src/main/org/jboss/util/propertyeditor/StringArrayEditor.javaUpdate to support escaped commas specified using a backslash: \, to incorporate commas in a string element.1.173.2.8modifiedstarksmserver/build.xmlRemove the obsolete org/jboss/ejb/timer/* classes from the xdoclet build1.7.4.1modifiedstarksmj2ee/src/main/javax/security/jacc/EJBMethodPermission.javaFix the serialVersionUID variable name1.3.6.1modifiedstarksmj2ee/src/main/javax/security/jacc/EJBRoleRefPermission.javaFix the serialVersionUID variable name1.3.2.10modifiedstarksmtools/etc/buildmagic/version-info.xmlUpdate for the 4.0.2RC1 release1.18.2.15modifiedstarksmtools/etc/buildmagic/buildmagic.entUpdate for the 4.0.2RC1 release1.1.2.6modifiedstarksmbuild/docs/readme.htmlUpdate for the 4.0.2RC1 release1.43.2.2modifiedstarksmcluster/src/main/org/jboss/ha/framework/server/HAPartitionImpl.javaUpdate the rpc handler comment1.43.2.1modifiedstarksmcluster/src/main/org/jboss/ha/framework/server/HAPartitionImpl.javaSimply return any throwable seen during the rpc handler method call dispatch as this is the only way to propagate an exception to the caller. Resolves (JBAS-1571) Logging of cluster rpc method exceptions at warn level is incorrect.1.406.2.44modifiedstarksmtestsuite/build.xmlUse the XMLJUnitMultipleResultFormatter to seperate the JACC tests rerun with a security manager.1.3.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/cts/test/MDBInvoker.javaAdd some additional logging of the invoker.1.15.4.2modifiedstarksmtestsuite/src/resources/cts/META-INF/jboss.xmlUpdate the SubclassMDB destination to queue/C as the B queue is used by the cts test client.1.5.4.4modifiedstarksmsecurity/src/main/org/jboss/security/jacc/DelegatingPolicy.javaInclude the delegate policy ProtectionDomain permissions when building the PermissionCollection in getPermissions(ProtectionDomain). Resolves (JBAS-1526) Jacc: Request for the DelegatingPolicy.getPermissions(x) to also return the permissions of the replaced delegate.1.355.2.26modifiedstarksmbuild/build.xmlRemove the unused jbossha-httpsession.sar1.28.6.4modifiedstarksmcluster/src/etc/cluster-service.xmlExpose all HANamingService attributes by default.1.2.4.7modifiedstarksmcluster/src/main/org/jboss/ha/jndi/DetachedHANamingService.javaRemove all local thread creation and instead use the thread pool passed in via the LookupPool. If no LookupPool is specified a BasicThreadPool("HANamingBootstrap Pool") is created. Resolves (JBAS-1558) HAJNDI should use a thread pool.1.2.4.3modifiedstarksmcluster/src/main/org/jboss/ha/jndi/DetachedHANamingServiceMBean.javaRemove all local thread creation and instead use the thread pool passed in via the LookupPool. If no LookupPool is specified a BasicThreadPool("HANamingBootstrap Pool") is created. Resolves (JBAS-1558) HAJNDI should use a thread pool.1.1.2.1modifiedstarksmthirdparty/jboss-aop/lib/jboss-aop.jarUpdate the aop deployer and library from code on the Branch_EJB_3_0_PREVIEW_3_0 as the previous checkout did not match this tag1.1.2.1modifiedstarksmthirdparty/jboss-aop/lib/jboss-aspect-library.jarUpdate the aop deployer and library from code on the Branch_EJB_3_0_PREVIEW_3_0 as the previous checkout did not match this tag1.1.2.1modifiedstarksmthirdparty/jboss-a
[JBoss-dev] jboss-3.2 build.310 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050315043526Lbuild.310 BUILD COMPLETE - build.310Date of build: 03/15/2005 04:35:26Time to build: 41 minutes 32 secondsLast changed: 03/14/2005 15:38:49Last log entry: JBAS-1577: white-space in ServiceMBean EVENT types, removed Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (5)1.2.2.6modifiedanddsystem/src/main/org/jboss/system/ServiceMBean.javaJBAS-1577: white-space in ServiceMBean EVENT types, removed1.1.2.3modifiedanddsystem/src/main/org/jboss/system/ListenerServiceMBean.javaNew Feature: JBAS-1365 - extension to ListenerServiceMBeanSupportThe filter mechanism has been extended to support specificationof arbitrary filters, using dynamic filter factory pluginsimplementing the NotificationFilterFactory interface.Three filter factories corresponding to the "standard" jmxnotification filters are supplied by default in packageorg.jboss.system.filterfactory.1.1.2.7modifiedanddsystem/src/main/org/jboss/system/ListenerServiceMBeanSupport.javaNew Feature: JBAS-1365 - extension to ListenerServiceMBeanSupportThe filter mechanism has been extended to support specificationof arbitrary filters, using dynamic filter factory pluginsimplementing the NotificationFilterFactory interface.Three filter factories corresponding to the "standard" jmxnotification filters are supplied by default in packageorg.jboss.system.filterfactory.1.1.4.1modifiedanddsystem/src/main/org/jboss/system/NotificationFilterFactory.javaNew Feature: JBAS-1365 - extension to ListenerServiceMBeanSupportThe filter mechanism has been extended to support specificationof arbitrary filters, using dynamic filter factory pluginsimplementing the NotificationFilterFactory interface.Three filter factories corresponding to the "standard" jmxnotification filters are supplied by default in packageorg.jboss.system.filterfactory.1.1.2.4modifiedanddsystem/src/resources/org/jboss/metadata/jboss-subscription.dtdNew Feature: JBAS-1365 - extension to ListenerServiceMBeanSupportThe filter mechanism has been extended to support specificationof arbitrary filters, using dynamic filter factory pluginsimplementing the NotificationFilterFactory interface.Three filter factories corresponding to the "standard" jmxnotification filters are supplied by default in packageorg.jboss.system.filterfactory.
[JBoss-dev] [JBoss JIRA] Commented: (JBWEB-12) mod_jk 1.2.10
[ http://jira.jboss.com/jira/browse/JBWEB-12?page=comments#action_12316164 ] Mladen Turk commented on JBWEB-12: -- JK 1.2.9 is ready to roll out. The release process will start on 3/17/2005, and it will take a week to finish. Since IMHO we have the best mod_jk ever, there is no need to go trough rigorous release process as for 1.2.8. > mod_jk 1.2.10 > - > > Key: JBWEB-12 > URL: http://jira.jboss.com/jira/browse/JBWEB-12 > Project: JBoss Web > Type: Task > Components: Tomcat Connectors > Reporter: Mladen Turk > Assignee: Mladen Turk > > Original Estimate: 4 weeks >Time Spent: 2 weeks > Remaining: 2 weeks > > Add shared memory and status page for mod_jk. > Shared memory allows true load balancer status, > and notifying all child processes. > Status page like in JK2 but more advanced like in > new mod_proxy will allow to dynamically change node > status (shutting down node for maintenance without > loosing existing session), and changing all configuration > parameters at runtime using simple web page. > Currently the shared memory is 80% finished, allowing > worker and balancer dynamic data. What's left is adding > uri mapping. > The release schedule for JK 1.2.10 is first half of March '05. > The beta version (1.2.9 Beta 1) is planned for end of this month. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPM-87) remove bidirectional relations management
remove bidirectional relations management - Key: JBPM-87 URL: http://jira.jboss.com/jira/browse/JBPM-87 Project: JBoss jBPM Type: Task Reporter: Tom Baeyens Assigned to: Tom Baeyens Fix For: jBPM 3.0 alpha 2 removed the automatic supermagical bidirectional relations management. now bidirectional relations management is done on the many-side of many-to-one relations. (much easier to understand) -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBPM-87) remove bidirectional relations management
[ http://jira.jboss.com/jira/browse/JBPM-87?page=history ] Tom Baeyens resolved JBPM-87: - Resolution: Done > remove bidirectional relations management > - > > Key: JBPM-87 > URL: http://jira.jboss.com/jira/browse/JBPM-87 > Project: JBoss jBPM > Type: Task > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Fix For: jBPM 3.0 alpha 2 > > Original Estimate: 1 day > Remaining: 1 day > > removed the automatic supermagical bidirectional relations management. now > bidirectional relations management is done on the many-side of many-to-one > relations. (much easier to understand) -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-58) create initial persistence for graph, context and taskmgmt
[ http://jira.jboss.com/jira/browse/JBPM-58?page=history ]
Tom Baeyens updated JBPM-58:
Summary: create initial persistence for graph, context and taskmgmt
(was: persistence)
Description:
initial persistence for
1) graph : process definitions & process executions
2) context : process variables
3) task management
was:
1) how to delete process instances and process definitions : cascading deletes ?
2) long or Long for id's. is there a preference. i have experienced some
problems with the null-value not being interpreted as i had hoped in case of
long but that might be my ignorance.
3) query tokens and/or process instances based on process variables. how to
query the
4) Variable persistence: is the serializable type of hibernate better then my
ServializableValue (using commons base64 encoding)
5) what is the most portable way to store the variable types float and double ?
6) does a private default constructor blocks some optimizations. (i want to
get rid of most of the default constructors in the javadocs and making them
private seems the easiest way)
7) try-finally-catch-catch-finally-try blocks around hibernate operations...
the book was not clear to me. related: i read something about runtime
exceptions... did you change that in hibernate 3.
8) which inheritence mapping to choose from ? what about the base class
(GraphElement) relations ?
9) new session per transaction. is that regular/good practice ? what
alternatives are there ?
10) how to issue a shutdown the hypersonic database and remove all the
connections from the pool ?
11) evaluate mechanisms
- storing variables ('detyped stuff')
- instantiatable delegates
12) varchar lengths problem (255 default)
13) can someone explain the inverse="true" again
14) values and entities (what about nodes in a process) ?
> create initial persistence for graph, context and taskmgmt
> --
>
> Key: JBPM-58
> URL: http://jira.jboss.com/jira/browse/JBPM-58
> Project: JBoss jBPM
> Type: Task
> Components: Core Engine
> Reporter: Tom Baeyens
> Assignee: Tom Baeyens
> Priority: Critical
> Fix For: jBPM 3.0 alpha 2
>
> Original Estimate: 3 weeks
> Remaining: 3 weeks
>
> initial persistence for
> 1) graph : process definitions & process executions
> 2) context : process variables
> 3) task management
--
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.436 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050315060110Lbuild.436 BUILD COMPLETE - build.436Date of build: 03/15/2005 06:01:10Time to build: 28 minutes 48 secondsLast changed: 03/15/2005 01:53:05Last log entry: Fix attachments on the return path (JBWS-146) Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (38)1.1.2.8modifiednihilitytestsuite/src/main/org/jboss/test/webservice/attachment/AttachmentProxyTestCase.javaFix attachments on the return path (JBWS-146)1.1.2.2modifiednihilityjaxrpc/src/main/org/jboss/axis/encoding/DefaultTypeMappingImpl.javaFix attachments on the return path (JBWS-146)1.1.2.2modifiednihilityjaxrpc/src/main/org/jboss/axis/wsdl/toJava/Utils.javaFix attachments on the return path (JBWS-146)1.3.6.1deletedstarksmvaria/src/main/org/jboss/tools/Boot.javano message1.2.6.1modifiedejorttestsuite/src/main/org/jboss/test/jbossmq/test/UIL2ConnectionUnitTestCase.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.1.4.6.2modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/msgs/ReceiveRequestMsg.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.1.4.6.1modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/ServerSocketManagerHandler.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.1.3.6.2modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILClientIL.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.1.3.6.1modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILClientILService.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.1.3.6.1modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILServerILFactory.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.1.5.6.3modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILServerILService.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.1.3.6.1modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILClientIL.javaAdd the missing serialVersionUID1.1.2.3modifiedejortconnector/src/resources/dtd/jboss-ds_1_5.dtd[JBAS-1564] - Autocommit and PreparedStatementCacheThe prepared statement is not reused when autocommit is on.Reuse is defined as asking for the same prepared statement twice in the same transactionwithout closing the first request statement.Since this behaviour is not in the spec, I've also disabled reuse for autocommit==falsehowever if your database supports it, you can re-enable it withtruein your -ds.xml1.10.4.1modifiedejortconnector/src/resources/xa-rar/META-INF/ra.xml[JBAS-1564] - Autocommit and PreparedStatementCacheThe prepared statement is not reused when autocommit is on.Reuse is defined as asking for the same prepared statement twice in the same transactionwithout closing the first request statement.Since this behaviour is not in the spec, I've also disabled reuse for autocommit==falsehowever if your database supports it, you can re-enable it withtruein your -ds.xml1.12.4.1modifiedejortconnector/src/resources/local-rar/META-INF/ra.xml[JBAS-1564] - Autocommit and PreparedStatementCacheThe prepared statement is not reused when autocommit is on.Reuse is defined as asking for the same prepared statement twice in the same transactionwithout closing the first request statement.Since this behaviour is not in the spec, I've also disabled reuse for autocommit==falsehowever if your database supports it, you can re-enable it withtruein your -ds.xml1.22.2.4modifiedejortconnector/src/resources/stylesheets/ConnectionFactoryTemplate.xsl[JBAS-1564] - Autocommit and PreparedStatementCacheThe prepared statement is not reused when autocommit is on.Reuse is defined as asking for the same prepared statement twice in the same transactionwithout closing the first request statement.Since this behaviour is not in the spec, I've also disabled reuse for autocommit==falsehowever if your database supports it, you can re-enable it withtruein your -ds.xml1.6.4.3modifiedejortconnector/src/main/org/jboss/resource/adapter/jdbc/BaseWrapperManagedConnection.java[JBAS-1564] - Autocommit and PreparedStatementCacheThe prepared stateme
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-68) finish pluggability for par parsers
[ http://jira.jboss.com/jira/browse/JBPM-68?page=history ] Tom Baeyens updated JBPM-68: Fix Version: jBPM 3.0 alpha 3 (was: jBPM 3.0 alpha 2) > finish pluggability for par parsers > --- > > Key: JBPM-68 > URL: http://jira.jboss.com/jira/browse/JBPM-68 > Project: JBoss jBPM > Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Fix For: jBPM 3.0 alpha 3 > > Time Spent: 1 day >Remaining: 1 hour > > when users want to extend jbpm with their custom modules, we should also > support pluggability of the module parsers. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-83) finish xml generation features
[ http://jira.jboss.com/jira/browse/JBPM-83?page=history ] Tom Baeyens updated JBPM-83: Summary: finish xml generation features (was: remove xml generation features) Description: finish the xml generation of process definitions. (was: since the designer plugin will build it's own model on top of an xml structure (instead of the jbpm object model), xml generation from the model is not necessary any more. this removes the necessity in the jbpm object model for keeping ordering (many lists can be replaced with maps) and it removes the reason of existence for the bidirectional relations housekeeping.) Priority: Minor (was: Major) Component: Core Engine Fix Version: (was: jBPM 3.0 alpha 2) it turns out that the graphical designer will not use the xml generation stuff from the jbpm domain model. it is half-finished at the moment. we'll leave it as a task for another 6 months so that someone from the community can pick it up. eventually we'll have to decide whether to finish the work or rip it out completely. > finish xml generation features > -- > > Key: JBPM-83 > URL: http://jira.jboss.com/jira/browse/JBPM-83 > Project: JBoss jBPM > Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Priority: Minor > > Original Estimate: 2 days > Remaining: 2 days > > finish the xml generation of process definitions. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-25) bpel activities xml parsing
[ http://jira.jboss.com/jira/browse/JBPM-25?page=history ] Tom Baeyens updated JBPM-25: Description: Perform xml - to graph translation by representing bpel activities as jbpm nodes. BPEL 1.1 defines the following activities: Basic Activities: -receive, reply, invoke, assign, wait, scope, throw, terminate, compensate, empty Structured Activities: -sequence, switch, while, pick, flow was: Perform xml - to graph translation by representing bpel activities as jbpm nodes. BPEL 1.1 defines the following activities: Basic Activities: -receive, reply, invoke, assign, wait, scope, throw, terminate, compensate, empty Structured Activities: -sequence, switch, while, pick, flow Environment: Remaining Estimate: (was: 0) Version: (was: jBPM 3.0 alpha 1) Fix Version: jBPM 3.0 BPEL extension alpha 1 (was: jBPM 3.0 alpha 1) > bpel activities xml parsing > --- > > Key: JBPM-25 > URL: http://jira.jboss.com/jira/browse/JBPM-25 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Reporter: Juan Cantu > Assignee: Juan Cantu > Fix For: jBPM 3.0 BPEL extension alpha 1 > > Original Estimate: 2 weeks >Time Spent: 2 weeks, 3 days > > Perform xml - to graph translation by representing bpel activities as jbpm > nodes. BPEL 1.1 defines the following activities: > Basic Activities: > -receive, reply, invoke, assign, wait, scope, throw, terminate, compensate, > empty > Structured Activities: > -sequence, switch, while, pick, flow -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-26) bpel archives parsing
[ http://jira.jboss.com/jira/browse/JBPM-26?page=history ] Tom Baeyens updated JBPM-26: Environment: Version: (was: jBPM 3.0 alpha 1) > bpel archives parsing > - > > Key: JBPM-26 > URL: http://jira.jboss.com/jira/browse/JBPM-26 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Reporter: Juan Cantu > Assignee: Juan Cantu > Fix For: jBPM 3.0 alpha 1 > > Original Estimate: 3 days >Time Spent: 2 days > Remaining: 1 day > > Read a bpel process definition with its corresponding wsdl definition > imports. These definitions include partner link types and messages types, > properties and aliases. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-26) bpel archives parsing
[ http://jira.jboss.com/jira/browse/JBPM-26?page=history ] Tom Baeyens updated JBPM-26: Fix Version: (was: jBPM 3.0 alpha 1) > bpel archives parsing > - > > Key: JBPM-26 > URL: http://jira.jboss.com/jira/browse/JBPM-26 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Reporter: Juan Cantu > Assignee: Juan Cantu > > Original Estimate: 3 days >Time Spent: 2 days > Remaining: 1 day > > Read a bpel process definition with its corresponding wsdl definition > imports. These definitions include partner link types and messages types, > properties and aliases. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-65) bpel configuration files parsing
[ http://jira.jboss.com/jira/browse/JBPM-65?page=history ] Tom Baeyens updated JBPM-65: Remaining Estimate: (was: 0) Version: (was: jBPM 3.0 alpha 1) Fix Version: (was: jBPM 3.0 alpha 1) > bpel configuration files parsing > > > Key: JBPM-65 > URL: http://jira.jboss.com/jira/browse/JBPM-65 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Environment: jaxp 1.1 > Reporter: Juan Cantu > Assignee: Juan Cantu > > Original Estimate: 3 days >Time Spent: 1 week > > A process archive consists of both definition and configuration files. A > mechanism must be provided to merge both files in a single process document. > This will allow that the logic for reading any kind of elements is > centralized in the parsers. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-14) bpel data handling and expression evaluation
[ http://jira.jboss.com/jira/browse/JBPM-14?page=history ] Tom Baeyens updated JBPM-14: Description: Environment: Fix Version: (was: jBPM 3.0 alpha 1) > bpel data handling and expression evaluation > > > Key: JBPM-14 > URL: http://jira.jboss.com/jira/browse/JBPM-14 > Project: JBoss jBPM > Type: Task > Components: BPEL > Reporter: Tom Baeyens > Assignee: Alejandro GuÃzar > > -- 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://ads.osdn.com/?ad_ide95&alloc_id396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-35) expose link status to expressions in join conditions (9.1, 12.5.1)
[ http://jira.jboss.com/jira/browse/JBPM-35?page=history ] Tom Baeyens updated JBPM-35: Version: (was: jBPM 3.0 alpha 1) Fix Version: (was: jBPM 3.0 alpha 1) > expose link status to expressions in join conditions (9.1, 12.5.1) > -- > > Key: JBPM-35 > URL: http://jira.jboss.com/jira/browse/JBPM-35 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Environment: dom4j, jaxen > Reporter: Alejandro GuÃzar > Assignee: Juan Cantu > > Original Estimate: 1 day >Time Spent: 1 day > > Mantain link status in the context instance. > Expose status of an activity's incoming links to the join condition > associated with that activity. > Implement the bpws:getLinkStatus() extension function. -- 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://ads.osdn.com/?ad_ide95&alloc_id396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-28) Link Semantics (12.5.1) and Death Path elimination (12.5.2)
[ http://jira.jboss.com/jira/browse/JBPM-28?page=history ] Tom Baeyens updated JBPM-28: Environment: Version: (was: jBPM 3.0 alpha 1) Fix Version: (was: jBPM 3.0 alpha 1) > Link Semantics (12.5.1) and Death Path elimination (12.5.2) > --- > > Key: JBPM-28 > URL: http://jira.jboss.com/jira/browse/JBPM-28 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Reporter: Juan Cantu > Assignee: Juan Cantu > > Original Estimate: 1 week, 2 days >Time Spent: 4 days > Remaining: 3 days > > Implement the routing constraints enforced by source and target links of bpel > activities. This mechanism is defined in chapter 12.5.1 and 12.5.2 of the > bpel spec. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-62) Implement link semantics with jbpm Milestones
[ http://jira.jboss.com/jira/browse/JBPM-62?page=history ] Tom Baeyens updated JBPM-62: Version: (was: jBPM 3.0 alpha 1) Fix Version: (was: jBPM 3.0 alpha 1) > Implement link semantics with jbpm Milestones > - > > Key: JBPM-62 > URL: http://jira.jboss.com/jira/browse/JBPM-62 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Reporter: Juan Cantu > Assignee: Juan Cantu > > Original Estimate: 3 days >Time Spent: 2 days > Remaining: 1 day > > Move Milestone and MilestoneInstance classes to the jbpm graph package. > Leverage this functionality to implement bpel link semantics. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-74) transformation from bpel 1.1 to 2.0
[ http://jira.jboss.com/jira/browse/JBPM-74?page=history ] Tom Baeyens updated JBPM-74: Remaining Estimate: (was: 0) Version: (was: jBPM 3.0 alpha 1) Fix Version: (was: jBPM 3.0 alpha 1) > transformation from bpel 1.1 to 2.0 > --- > > Key: JBPM-74 > URL: http://jira.jboss.com/jira/browse/JBPM-74 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Environment: jaxp 1.1 > Reporter: Juan Cantu > Assignee: Juan Cantu > > Original Estimate: 3 days >Time Spent: 3 days > > Use xslt to transform bpel archives (process definition, wsdl extensions) > from bpel 1.1 to 2.0 version. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-27) structured blocks execution
[ http://jira.jboss.com/jira/browse/JBPM-27?page=history ] Tom Baeyens updated JBPM-27: Environment: Remaining Estimate: (was: 0) Version: (was: jBPM 3.0 alpha 1) Fix Version: (was: jBPM 3.0 alpha 1) > structured blocks execution > --- > > Key: JBPM-27 > URL: http://jira.jboss.com/jira/browse/JBPM-27 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Reporter: Juan Cantu > Assignee: Juan Cantu > > Original Estimate: 1 week >Time Spent: 1 week, 3 days > > Add to bpel structured activities the logic needed to perform their expected > routing behavior. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-63) Refactor BpelActivity class hierarchy
[ http://jira.jboss.com/jira/browse/JBPM-63?page=history ] Tom Baeyens updated JBPM-63: Remaining Estimate: (was: 0) Version: (was: jBPM 3.0 alpha 1) Fix Version: (was: jBPM 3.0 alpha 1) > Refactor BpelActivity class hierarchy > - > > Key: JBPM-63 > URL: http://jira.jboss.com/jira/browse/JBPM-63 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Reporter: Juan Cantu > Assignee: Juan Cantu > > Original Estimate: 3 days >Time Spent: 4 days > > Modify the class hierarchy of bpel activities. They used to be implemented by > extending from two lines of inheritance (Node and SuperState). The goal is to > create a single base class (BpelActivity) and remove any dependency with > super states. The parent - child relation behavior is reimplemented at the > CompositeActivity subclass. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPM-77) Remove jbpm milestone
[ http://jira.jboss.com/jira/browse/JBPM-77?page=history ] Tom Baeyens updated JBPM-77: Remaining Estimate: (was: 0) Version: (was: jBPM 3.0 alpha 1) Component: (was: Core Engine) Fix Version: (was: jBPM 3.0 alpha 1) > Remove jbpm milestone > - > > Key: JBPM-77 > URL: http://jira.jboss.com/jira/browse/JBPM-77 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Reporter: Juan Cantu > Assignee: Juan Cantu > > Original Estimate: 2 days >Time Spent: 2 days > > Move the jbpm Milestone functionality from the core engine to the bpel > package. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.880 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050315071517Lbuild.880 BUILD COMPLETE - build.880Date of build: 03/15/2005 07:15:17Time to build: 40 minutes 49 secondsLast changed: 03/15/2005 01:34:40Last log entry: A tool for calculating all the serialVersionUIDs in a jboss dist. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (76)1.4deletedstarksmvaria/src/main/org/jboss/tools/Boot.javaA tool for calculating all the serialVersionUIDs in a jboss dist.1.1addedstarksmvaria/src/main/org/jboss/tools/ClassVersionInfo.javaA tool for calculating all the serialVersionUIDs in a jboss dist.1.1addedstarksmvaria/src/main/org/jboss/tools/SerialVersionUID.javaA tool for calculating all the serialVersionUIDs in a jboss dist.1.5modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/msgs/ReceiveRequestMsg.javaPort ReceiveRequestMsg enhancements from JBoss41.5modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/ServerSocketManagerHandler.javaPort ReceiveRequestMsg enhancements from JBoss41.4modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILClientIL.javaPort ReceiveRequestMsg enhancements from JBoss41.4modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILServerILFactory.javaPort ReceiveRequestMsg enhancements from JBoss41.8modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILServerILService.javaPort ReceiveRequestMsg enhancements from JBoss41.4modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILClientILService.javaPort ReceiveRequestMsg enhancements from JBoss41.4modifiedejortconnector/src/resources/dtd/jboss-ds_1_5.dtdPort from jboss41.11modifiedejortconnector/src/resources/xa-rar/META-INF/ra.xmlPort from jboss41.13modifiedejortconnector/src/resources/local-rar/META-INF/ra.xmlPort from jboss41.28modifiedejortconnector/src/resources/stylesheets/ConnectionFactoryTemplate.xslPort from jboss41.9modifiedejortconnector/src/main/org/jboss/resource/adapter/jdbc/BaseWrapperManagedConnection.javaPort from jboss41.5modifiedejortconnector/src/main/org/jboss/resource/adapter/jdbc/CachedPreparedStatement.javaPort from jboss41.17modifiedejortconnector/src/main/org/jboss/resource/adapter/jdbc/BaseWrapperManagedConnectionFactory.javaPort from jboss41.1addedbwang00testsuite/src/main/org/jboss/test/cache/test/standAloneAop/CollectionProxyAopTest.javaNewly added.1.30modifiedejortmessaging/src/main/org/jboss/mq/pm/jdbc2/PersistenceManager.javaPort fixes from JBoss41.3modifiedejortmessaging/src/etc/server/examples/deploy/null-persistence-service.xmlPort fixes from JBoss41.7modifiedejortmessaging/src/main/org/jboss/mq/sm/jdbc/JDBCStateManager.javaPort fixes from JBoss41.8modifiedanddsystem/src/main/org/jboss/system/ServiceMBean.javaJBAS-1577: white-space in ServiceMBean EVENT types, removed1.1addedanddsystem/src/main/org/jboss/system/NotificationFilterFactory.javabranches: 1.1.2; 1.1.4;New Feature: JBAS-1365 - extension to ListenerServiceMBeanSupportThe filter mechanism has been extended to support specificationof arbitrary filters, using dynamic filter factory pluginsimplementing the NotificationFilterFactory interface.Three filter factories corresponding to the "standard" jmxnotification filters are supplied by default in packageorg.jboss.system.filterfactory.1.7modifiedanddsystem/src/main/org/jboss/system/ListenerServiceMBeanSupport.javaNew Feature: JBAS-1365 - extension to ListenerServiceMBeanSupportThe filter mechanism has been extended to support specificationof arbitrary filters, using dynamic filter factory pluginsimplementing the NotificationFilterFactory interface.Three filter factories corresponding to the "standard" jmxnotification filters are supplied by default in packageorg.jboss.system.filterfactory.1.4modifiedanddsystem/src/main/org/jboss/system/ListenerServiceMBean.javaNew Feature: JBAS-1365 - extension to ListenerServiceMBeanSupportThe filter mechanism has been extended to support specificationof arbitrary filters, using dynamic filter factory pluginsimplementing the NotificationFilterFactory interface.Three filter factories corresponding to the "standard" jmxnotification filters are supplied by default in packageorg.jboss.system.filterfactory.1.4modifiedanddsystem/src/resources/dtd/jboss-subscription.dtdNew Feature: JBAS-1365 - extension to ListenerServiceMBeanSupportThe filter mechanism has been extended to support specificationof arbitrary filters, using dynamic filter factory pluginsimplementing the NotificationFilterFactory interface.Three filter factories corresponding to the "standard" jmxnotification filters are supplied by default in packageorg.jboss.system.filterfactory.1.20modifiedejortremoting/.classpathFix the eclipse build AGAIN!1.21modifiedosdchicagowebservice/src/main/org/jboss/ws/wsdl/WSDL20Reader.javaTake care of the Included schema issue for wsdl 2.01.131modifiedstarksmserver/src/
[JBoss-dev] [Design of JBoss Portal] - Oracle setup for Portal
Hi everyone, I'm having a hard time getting JBoss Portal to work with Oracle. I have setup the database just like was specified in the DDL file with no problems. The users are in there and the page load in the browser. However when I try to login it get this error. Any help that you can provide would be great! Thanks, Matt 09:56:15,864 WARN [JDBCExceptionReporter] SQL Error: 933, SQLState: 42000 09:56:15,864 ERROR [JDBCExceptionReporter] ORA-00933: SQL command not properly ended 09:56:15,865 WARN [JDBCExceptionReporter] SQL Error: 933, SQLState: 42000 09:56:15,865 ERROR [JDBCExceptionReporter] ORA-00933: SQL command not properly ended 09:56:15,865 ERROR [JDBCExceptionReporter] Could not execute query java.sql.SQLException: ORA-00933: SQL command not properly ended at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134) at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289) at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:573) at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891) at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Protocol.java:830) at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2391) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2672) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:527) at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:296) at net.sf.hibernate.impl.BatcherImpl.getResultSet(BatcherImpl.java:87) at net.sf.hibernate.loader.Loader.getResultSet(Loader.java:875) at net.sf.hibernate.hql.QueryTranslator.iterate(QueryTranslator.java:868) at net.sf.hibernate.impl.SessionImpl.iterate(SessionImpl.java:1609) at net.sf.hibernate.impl.QueryImpl.iterate(QueryImpl.java:27) at org.jboss.portal.core.security.jaas.HibernateLoginModule$2.run(HibernateLoginModule.java:145) at org.jboss.portal.common.transaction.Transactions.requiresNew(Transactions.java:75) at org.jboss.portal.core.security.jaas.HibernateLoginModule.getRoleSets(HibernateLoginModule.java:128) at org.jboss.security.auth.spi.AbstractServerLoginModule.commit(AbstractServerLoginModule.java:187) 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 javax.security.auth.login.LoginContext.invoke(LoginContext.java:675) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:129) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:610) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:607) at javax.security.auth.login.LoginContext.login(LoginContext.java:535) at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:480) at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:420) at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:237) at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:210) at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.authenticate(JBossSecurityMgrRealm.java:239) at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:235) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:446) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:54) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.jav
[JBoss-dev] [Design of JBoss Portal] - Re: Oracle setup for Portal
I couldn't try it on Oracle so far. You should see the HQL and SQL requests made in $JBOSS_HOME/server/default/log/server.log Also ake sure you specified the correct Hibernate Dialect for Oracle. You can send me the compressed server.log by email if you want View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870205#3870205 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870205 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Oracle setup for Portal
Thanks - I have sent you the server log. Matt View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870206#3870206 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870206 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBREM-8) Ability to stream files via remoting
[ http://jira.jboss.com/jira/browse/JBREM-8?page=comments#action_12316169 ] John Mazzitelli commented on JBREM-8: - FWIW, The JBoss Network's Application Management System will need this capability. We plan on being able to distribute applications (like wars, ears, sars) to remote JBoss instances. Since these can be large, having a streaming capability is a must. > Ability to stream files via remoting > > > Key: JBREM-8 > URL: http://jira.jboss.com/jira/browse/JBREM-8 > Project: JBoss Remoting > Type: Feature Request > Components: general > Versions: 1.0.1 alpha > Reporter: Tom Elrod > Assignee: Tom Elrod > Priority: Minor > Fix For: 1.2.0 beta > > > Would like to add ability for user to stream files using remoting. Initially > requested by Dimitris for deploying files from management console using > remoting. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head-testsuite?log=log20050315094701 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:66: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See tests.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 03/15/2005 09:47:01Time to build: 30 minutes 15 secondsLast changed: 03/15/2005 07:44:18Last log entry: adjusted tests after api refactoring Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (103)1.13modifiedloubyanskytestsuite/src/main/org/jboss/test/xml/MiscUnitTestCase.javaadjusted tests after api refactoring1.37modifiedloubyanskycommon/src/main/org/jboss/xml/binding/ObjectModelBuilder.javafixed switching to a new object model factory when the factory is actually the same for the previous and next namespace URI1.4deletedstarksmvaria/src/main/org/jboss/tools/Boot.javaA tool for calculating all the serialVersionUIDs in a jboss dist.1.1addedstarksmvaria/src/main/org/jboss/tools/ClassVersionInfo.javaA tool for calculating all the serialVersionUIDs in a jboss dist.1.1addedstarksmvaria/src/main/org/jboss/tools/SerialVersionUID.javaA tool for calculating all the serialVersionUIDs in a jboss dist.1.5modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/msgs/ReceiveRequestMsg.javaPort ReceiveRequestMsg enhancements from JBoss41.5modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/ServerSocketManagerHandler.javaPort ReceiveRequestMsg enhancements from JBoss41.4modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILClientIL.javaPort ReceiveRequestMsg enhancements from JBoss41.4modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILServerILFactory.javaPort ReceiveRequestMsg enhancements from JBoss41.8modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILServerILService.javaPort ReceiveRequestMsg enhancements from JBoss41.4modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILClientILService.javaPort ReceiveRequestMsg enhancements from JBoss41.4modifiedejortconnector/src/resources/dtd/jboss-ds_1_5.dtdPort from jboss41.11modifiedejortconnector/src/resources/xa-rar/META-INF/ra.xmlPort from jboss41.13modifiedejortconnector/src/resources/local-rar/META-INF/ra.xmlPort from jboss41.28modifiedejortconnector/src/resources/stylesheets/ConnectionFactoryTemplate.xslPort from jboss41.9modifiedejortconnector/src/main/org/jboss/resource/adapter/jdbc/BaseWrapperManagedConnection.javaPort from jboss41.5modifiedejortconnector/src/main/org/jboss/resource/adapter/jdbc/CachedPreparedStatement.javaPort from jboss41.17modifiedejortconnector/src/main/org/jboss/resource/adapter/jdbc/BaseWrapperManagedConnectionFactory.javaPort from jboss41.1addedbwang00testsuite/src/main/org/jboss/test/cache/test/standAloneAop/CollectionProxyAopTest.javaNewly added.1.30modifiedejortmessaging/src/main/org/jboss/mq/pm/jdbc2/PersistenceManager.javaPort fixes from JBoss41.3modifiedejortmessaging/src/etc/server/examples/deploy/null-persistence-service.xmlPort fixes from JBoss41.7modifiedejortmessaging/src/main/org/jboss/mq/sm/jdbc/JDBCStateManager.javaPort fixes from JBoss41.8modifiedanddsystem/src/main/org/jboss/system/ServiceMBean.javaJBAS-1577: white-space in ServiceMBean EVENT types, removed1.1addedanddsystem/src/main/org/jboss/system/NotificationFilterFactory.javabranches: 1.1.2; 1.1.4;New Feature: JBAS-1365 - extension to ListenerServiceMBeanSupportThe filter mechanism has been extended to support specificationof arbitrary filters, using dynamic filter factory pluginsimplementing the NotificationFilterFactory interface.Three filter factories corresponding to the "standard" jmxnotification filters are supplied by default in packageorg.jboss.system.filterfactory.1.7modifiedanddsystem/src/main/org/jboss/system/ListenerServiceMBeanSupport.javaNew Feature: JBAS-1365 - extension to ListenerServiceMBeanSupportThe filter mechanism has been extended to support specificationof arbitrary filters, using dynamic filter factory pluginsimplementing the NotificationFilterFactory interface.Three filter factories corresponding to the "standard" jmxnotification filters are supplied by default in packageorg.jboss.system.filterfactory.1.4modifiedanddsystem/src/main/org/jboss/system/ListenerServiceMBean.javaNew Feature: JBAS-1365 - extension to ListenerServiceMBeanSupportThe filter mechanism has been extended to support specificationof arbitrary filters, using dynamic filter factory pluginsimplementing the NotificationFilterFactory interface.Three filter factories corresponding to the "standard" jmxnotification filters are supplied by default in packageorg.jboss.system.filterfactory.1.4modifiedanddsystem/src/resources/dtd/jboss-subscription.dtdNew Feature: JBAS-1365 - extension to ListenerServiceMBeanSupp
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1552) JBoss use wrong version of javax.resource.ResourceException class file
[
http://jira.jboss.com/jira/browse/JBAS-1552?page=comments#action_12316170 ]
Adrian Brock commented on JBAS-1552:
I just submitted a potential fix to JBoss Head
on how to change the SerialVersionUID to allow both j2eeri and legacy JBoss
compatibility.
In javax.resource.ResourceException:
private static final long serialVersionUID;
static
{
if (SerialVersion.version == SerialVersion.LEGACY)
serialVersionUID = -1809703985388987999L;
else
serialVersionUID = 547071213627824490L;
}
Where SerialVersion decides which version to use from a system property:
/*
* JBoss, the OpenSource J2EE webOS
*
* Distributable under LGPL license.
* See terms of license at gnu.org.
*/
package org.jboss.j2ee.util;
import java.security.AccessController;
import java.security.PrivilegedAction;
/**
* Serialization Helper.
*
* Contains static constants and attributes to help is serialization
* versioning.
*
* Set the system property org.jboss.j2ee.LegacySerialization
* to serialization compatibility with older jboss.
*
* @author mailto:[EMAIL PROTECTED]">Adrian Brock.
* @version $Revision: 1.1 $
*/
public class SerialVersion
{
// Static
/** Legacy */
public static final int LEGACY = 0;
/** The serialization compatible with Sun's RI */
public static final int J2EE = 1;
/**
* The serialization version to use
*/
public static int version = J2EE;
/** Determine the serialization version */
static
{
AccessController.doPrivileged(new PrivilegedAction()
{
public Object run()
{
try
{
if (System.getProperty("org.jboss.j2ee.LegacySerialization") !=
null)
version = LEGACY;
}
catch (Throwable ignored)
{
}
return null;
}
});
}
}
> JBoss use wrong version of javax.resource.ResourceException class file
> --
>
> Key: JBAS-1552
> URL: http://jira.jboss.com/jira/browse/JBAS-1552
> Project: JBoss Application Server
> Type: Bug
> Components: JCA service
> Versions: JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1
> Environment: All platforms
> Reporter: Manfred Rosenboom
> Fix For: JBossAS-4.0.2 Final
>
>
> When passing a javax.resource.ResourceException via RMI into the JBoss
> application server we get the following error message:
> ...
> javax.resource.ResourceException; local class incompatible: stream classdesc
> serialVersionUID = 547071213627824490, local class serialVersionUID =
> 4770679801401540475
> at net.fsc.jca.tutorial.SimpleOltpConnectBean.callService(Unknown
> Source)
> 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)
> ...
> When comparing class files, you can see, that JBoss 4.0.x doesn't use the
> same class file as is used in Sun's j2ee.jar (J2EE 1.4 reference
> implementation).
> Both Sun Java System Application Server Platform Edition 8.1 2005Q1 and
> Oracle OC4J 10.1.3 use the same class file, which differes from the JBoss
> version. So I assume, that this is a JBoss related 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1552) JBoss use wrong version of javax.resource.ResourceException class file
[ http://jira.jboss.com/jira/browse/JBAS-1552?page=history ] Adrian Brock updated JBAS-1552: --- Attachment: build.xml > JBoss use wrong version of javax.resource.ResourceException class file > -- > > Key: JBAS-1552 > URL: http://jira.jboss.com/jira/browse/JBAS-1552 > Project: JBoss Application Server > Type: Bug > Components: JCA service > Versions: JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1 > Environment: All platforms > Reporter: Manfred Rosenboom > Fix For: JBossAS-4.0.2 Final > Attachments: build.properties, build.xml > > > When passing a javax.resource.ResourceException via RMI into the JBoss > application server we get the following error message: > ... > javax.resource.ResourceException; local class incompatible: stream classdesc > serialVersionUID = 547071213627824490, local class serialVersionUID = > 4770679801401540475 > at net.fsc.jca.tutorial.SimpleOltpConnectBean.callService(Unknown > Source) > 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) > ... > When comparing class files, you can see, that JBoss 4.0.x doesn't use the > same class file as is used in Sun's j2ee.jar (J2EE 1.4 reference > implementation). > Both Sun Java System Application Server Platform Edition 8.1 2005Q1 and > Oracle OC4J 10.1.3 use the same class file, which differes from the JBoss > version. So I assume, that this is a JBoss related 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1552) JBoss use wrong version of javax.resource.ResourceException class file
[ http://jira.jboss.com/jira/browse/JBAS-1552?page=history ] Adrian Brock updated JBAS-1552: --- Attachment: build.properties Need to change jboss.home and j2ee.home > JBoss use wrong version of javax.resource.ResourceException class file > -- > > Key: JBAS-1552 > URL: http://jira.jboss.com/jira/browse/JBAS-1552 > Project: JBoss Application Server > Type: Bug > Components: JCA service > Versions: JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1 > Environment: All platforms > Reporter: Manfred Rosenboom > Fix For: JBossAS-4.0.2 Final > Attachments: build.properties, build.xml > > > When passing a javax.resource.ResourceException via RMI into the JBoss > application server we get the following error message: > ... > javax.resource.ResourceException; local class incompatible: stream classdesc > serialVersionUID = 547071213627824490, local class serialVersionUID = > 4770679801401540475 > at net.fsc.jca.tutorial.SimpleOltpConnectBean.callService(Unknown > Source) > 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) > ... > When comparing class files, you can see, that JBoss 4.0.x doesn't use the > same class file as is used in Sun's j2ee.jar (J2EE 1.4 reference > implementation). > Both Sun Java System Application Server Platform Edition 8.1 2005Q1 and > Oracle OC4J 10.1.3 use the same class file, which differes from the JBoss > version. So I assume, that this is a JBoss related 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1552) JBoss use wrong version of javax.resource.ResourceException class file
[ http://jira.jboss.com/jira/browse/JBAS-1552?page=comments#action_12316172 ] Adrian Brock commented on JBAS-1552: I've attached a simple ant build that can be used to determine serialVersionUID for both JBoss and J2EE classes. e.g. ant jboss -Dclass=javax.resource.ResourceException ant j2ee -Dclass=javax.resource.ResourceException > JBoss use wrong version of javax.resource.ResourceException class file > -- > > Key: JBAS-1552 > URL: http://jira.jboss.com/jira/browse/JBAS-1552 > Project: JBoss Application Server > Type: Bug > Components: JCA service > Versions: JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1 > Environment: All platforms > Reporter: Manfred Rosenboom > Fix For: JBossAS-4.0.2 Final > Attachments: build.properties, build.xml > > > When passing a javax.resource.ResourceException via RMI into the JBoss > application server we get the following error message: > ... > javax.resource.ResourceException; local class incompatible: stream classdesc > serialVersionUID = 547071213627824490, local class serialVersionUID = > 4770679801401540475 > at net.fsc.jca.tutorial.SimpleOltpConnectBean.callService(Unknown > Source) > 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) > ... > When comparing class files, you can see, that JBoss 4.0.x doesn't use the > same class file as is used in Sun's j2ee.jar (J2EE 1.4 reference > implementation). > Both Sun Java System Application Server Platform Edition 8.1 2005Q1 and > Oracle OC4J 10.1.3 use the same class file, which differes from the JBoss > version. So I assume, that this is a JBoss related 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Oracle setup for Portal
The good info is here:
2005-03-15 10:15:53,051 DEBUG [net.sf.hibernate.impl.SessionImpl] opened session
| 2005-03-15 10:15:53,051 DEBUG [net.sf.hibernate.impl.SessionImpl] iterate:
SELECT g.name FROM UserImpl AS u LEFT JOIN u.roles AS g WHERE
u.userName=:username
| 2005-03-15 10:15:53,051 DEBUG [net.sf.hibernate.engine.QueryParameters]
named parameters: {username=mpaterso}
| 2005-03-15 10:15:53,051 DEBUG [net.sf.hibernate.impl.SessionImpl] flushing
session
| 2005-03-15 10:15:53,051 DEBUG [net.sf.hibernate.impl.SessionImpl] Flushing
entities and processing referenced collections
| 2005-03-15 10:15:53,051 DEBUG [net.sf.hibernate.impl.SessionImpl]
Processing unreferenced collections
| 2005-03-15 10:15:53,051 DEBUG [net.sf.hibernate.impl.SessionImpl]
Scheduling collection removes/(re)creates/updates
| 2005-03-15 10:15:53,052 DEBUG [net.sf.hibernate.impl.SessionImpl] Flushed:
0 insertions, 0 updates, 0 deletions to 0 objects
| 2005-03-15 10:15:53,052 DEBUG [net.sf.hibernate.impl.SessionImpl] Flushed:
0 (re)creations, 0 updates, 0 removals to 0 collections
| 2005-03-15 10:15:53,052 DEBUG [net.sf.hibernate.impl.SessionImpl] Dont need
to execute flush
| 2005-03-15 10:15:53,052 DEBUG [net.sf.hibernate.hql.QueryTranslator] HQL:
SELECT g.name FROM org.jboss.portal.core.impl.user.UserImpl AS u LEFT JOIN
u.roles AS g WHERE u.userName=:username
| 2005-03-15 10:15:53,052 DEBUG [net.sf.hibernate.hql.QueryTranslator] SQL:
select roleimpl2_.jbp_name as x0_0_ from jbp_users userimpl0_ left outer join
jbp_role_membership roles1_ on userimpl0_.jbp_uid=roles1_.jbp_uid left outer
join jbp_roles roleimpl2_ on roles1_.jbp_rid=roleimpl2_.jbp_rid where
(userimpl0_.jbp_uname=? )
| 2005-03-15 10:15:53,052 DEBUG [net.sf.hibernate.impl.BatcherImpl] about to
open: 0 open PreparedStatements, 0 open ResultSets
| 2005-03-15 10:15:53,052 DEBUG [net.sf.hibernate.SQL] select
roleimpl2_.jbp_name as x0_0_ from jbp_users userimpl0_ left outer join
jbp_role_membership roles1_ on userimpl0_.jbp_uid=roles1_.jbp_uid left outer
join jbp_roles roleimpl2_ on roles1_.jbp_rid=roleimpl2_.jbp_rid where
(userimpl0_.jbp_uname=? )
| 2005-03-15 10:15:53,052 DEBUG [net.sf.hibernate.impl.BatcherImpl] preparing
statement
| 2005-03-15 10:15:53,053 DEBUG [net.sf.hibernate.type.StringType] binding
'mpaterso' to parameter: 1
| 2005-03-15 10:15:53,056 DEBUG [net.sf.hibernate.util.JDBCExceptionReporter]
SQL Exception
| java.sql.SQLException: ORA-00933: SQL command not properly ended
It looks like another Oracle JDBC driver problem. Is there any other jdbc
driver you can try ? Do you have the latest one ?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870215#3870215
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870215
---
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: Can't lookup cache service through JNDI
Sorry, the docs on the website are out-of-date (not generated from the CVS docs). I'll look into updating the website. The docs that ship with the 1.2.1 distro are updated View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870216#3870216 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870216 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Mail Services] - Re: M3 MSGSTORE->Mailbox
Yeah, my view is that MailBoxes are the provincia of hibernate and the STORE is the provincia of mike's blob stuff. Hibernate will never likely have adequate blob support for all databases. For at least a little while (read: at least another milestone release) I'd like to still support the CMP 2.x nasty stuff. It was on the docket for 1.0 but I think by then EJB3 will be at least out (probably missing J2EE 1.5, but ready) and we can forget the monstrosity that was CMP anyhow so why bother beyond another milestone or so. (open to conflicting opinions from you two and other code contributors) -Andy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870218#3870218 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870218 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBREM-8) Ability to stream files via remoting
[ http://jira.jboss.com/jira/browse/JBREM-8?page=history ] Tom Elrod updated JBREM-8: --- Priority: Major (was: Minor) > Ability to stream files via remoting > > > Key: JBREM-8 > URL: http://jira.jboss.com/jira/browse/JBREM-8 > Project: JBoss Remoting > Type: Feature Request > Components: general > Versions: 1.0.1 alpha > Reporter: Tom Elrod > Assignee: Tom Elrod > Fix For: 1.2.0 beta > > > Would like to add ability for user to stream files using remoting. Initially > requested by Dimitris for deploying files from management console using > remoting. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [TODO -- DEVELOPMENT] - Re: joesnmp modified source code
Looking at JBoss CVS I see: joesnmp.jar 1.6 4 months andd joesnmp v0.3.3 with minor fixes Just wondered what the ?minor fixes? are? I already modified the code from http://sourceforge.net/projects/joesnmp and applied the following changes: 1. Enabling the SnmpSessionHandler to know about the caller by setting the right peer information. 2. Fixed SnmpPortal to work correctly with the ThreadPool (fast executers). It was calling wait(100) without holding a lock (which of course triggers IllegalMonitorStateException) . I actually changed to code to make it cleaner instead of having a magic wait value of "200". 3. Modified SnmpPortal to enable setting the receive/send buffers 4. Removed the use of the Cleanup task by utilizing the callbacks to from SnmpRequest to update the session. (I left the task just for protection though I am pretty sure it is not needed anymore) 5. If a Peer was given in the send command then the session considers only its IP address and port but not its community strings. So I fixed that. 6. Enable the SnmpSession to use the SnmpPortal with thread pool (just added a new constructor). 7. Optimized BerEncoder 8. Replaced SnmpTimer with a more scalable code (not using linear search) (which is JVM 1.2 compatible as the previous one). In that respect I also modified SnmpSession to use a better structure then LinkedList for m_requests. I use the modified code to collect from 100K devices periodically and it looks pretty good so far (it is running for weeks now). I will be more then happy to incorporate any of those changes back to joesnmp source code. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870219#3870219 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870219 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Oracle setup for Portal
Just to be sure what version of Oracle are you using, what version of the JDBC driver and can you show me your oracle.properties (minus the password if it is a secret one) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870220#3870220 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870220 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: TreeCacheAop can't add an object of a class which extend
Thanks Ben. The class is a POJO, in that it extends ArrayList and adds a user ID property. I created this class in order to try to take advantage of the ability to use the caching without "aspectizing" my class, as described in the FAQ, but as you have pointed out this only works if the class is not a POJO. With this in mind I'll go back to using my original class which contains an ArrayList and a String as members and try to properly "aspectize" this class so that it can be fully replicated by the TreeCacheAop. Can you reference the definitive documentation which outlines how I should "aspectize" my class? I have found two examples of how this should be done via the jboss-aop.xml file, but neither has worked for me so far. For example in the jboss-cache 1.2 distribution there is a jboss-aop.xml (found in jboss-cache/etc/META-INF) which looks like this: | | | | | And in the TreeCacheAop document (http://docs.jboss.org/jbcache/TreeCacheAop.html) it looks like this: | | | | | Which, if either, of these approaches for jboss-aop.xml is correct? If one or the other is to be used then perhaps I am missing some other piece of the puzzle, as I have tried both with no joy so far. --James View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870222#3870222 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870222 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0-jdk-matrix build.108 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20050315104640Lbuild.108 BUILD COMPLETE - build.108Date of build: 03/15/2005 10:46:40Time to build: 38 minutes 26 secondsLast changed: 03/15/2005 01:53:05Last log entry: Fix attachments on the return path (JBWS-146) Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (62)1.1.2.8modifiednihilitytestsuite/src/main/org/jboss/test/webservice/attachment/AttachmentProxyTestCase.javaFix attachments on the return path (JBWS-146)1.1.2.2modifiednihilityjaxrpc/src/main/org/jboss/axis/encoding/DefaultTypeMappingImpl.javaFix attachments on the return path (JBWS-146)1.1.2.2modifiednihilityjaxrpc/src/main/org/jboss/axis/wsdl/toJava/Utils.javaFix attachments on the return path (JBWS-146)1.3.6.1deletedstarksmvaria/src/main/org/jboss/tools/Boot.javano message1.2.6.1modifiedejorttestsuite/src/main/org/jboss/test/jbossmq/test/UIL2ConnectionUnitTestCase.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.1.4.6.2modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/msgs/ReceiveRequestMsg.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.1.4.6.1modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/ServerSocketManagerHandler.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.1.3.6.2modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILClientIL.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.1.3.6.1modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILClientILService.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.1.3.6.1modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILServerILFactory.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.1.5.6.3modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILServerILService.java[JBAS-1578] - Send ReceiveRequestMsg as one-wayWhen delivering messages to the client, there is no need for the delivery thread to wait for the clientto say it got them.1.3.6.1modifiedejortmessaging/src/main/org/jboss/mq/il/uil2/UILClientIL.javaAdd the missing serialVersionUID1.1.2.3modifiedejortconnector/src/resources/dtd/jboss-ds_1_5.dtd[JBAS-1564] - Autocommit and PreparedStatementCacheThe prepared statement is not reused when autocommit is on.Reuse is defined as asking for the same prepared statement twice in the same transactionwithout closing the first request statement.Since this behaviour is not in the spec, I've also disabled reuse for autocommit==falsehowever if your database supports it, you can re-enable it withtruein your -ds.xml1.10.4.1modifiedejortconnector/src/resources/xa-rar/META-INF/ra.xml[JBAS-1564] - Autocommit and PreparedStatementCacheThe prepared statement is not reused when autocommit is on.Reuse is defined as asking for the same prepared statement twice in the same transactionwithout closing the first request statement.Since this behaviour is not in the spec, I've also disabled reuse for autocommit==falsehowever if your database supports it, you can re-enable it withtruein your -ds.xml1.12.4.1modifiedejortconnector/src/resources/local-rar/META-INF/ra.xml[JBAS-1564] - Autocommit and PreparedStatementCacheThe prepared statement is not reused when autocommit is on.Reuse is defined as asking for the same prepared statement twice in the same transactionwithout closing the first request statement.Since this behaviour is not in the spec, I've also disabled reuse for autocommit==falsehowever if your database supports it, you can re-enable it withtruein your -ds.xml1.22.2.4modifiedejortconnector/src/resources/stylesheets/ConnectionFactoryTemplate.xsl[JBAS-1564] - Autocommit and PreparedStatementCacheThe prepared statement is not reused when autocommit is on.Reuse is defined as asking for the same prepared statement twice in the same transactionwithout closing the first request statement.Since this behaviour is not in the spec, I've also disabled reuse for autocommit==falsehowever if your database supports it, you can re-enable it withtruein your -ds.xml1.6.4.3modifiedejortconnector/src/main/org/jboss/resource/adapter/jdbc/BaseWrapperManagedConnection.java[JBAS-1564] - Autocommit and PreparedStatementCacheThe prepa
[JBoss-dev] [Design of Clustering on JBoss (Clusters/JBoss)] - Re: org.jgroups.blocks.RpcDispatcher and Exceptions
Successful invocation: Rsp.received == true Failure during invocation: Rsp.received == true and Rsp.retval instanceof Throwable == true View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870223#3870223 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870223 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: Synchronous replication (REPL_SYNC) does not block the c
#1 don't override _put() #2 don't even *call* _put() directly. The only reason this is public is that the interceptors use it, this will go away once we provide interfaces rather than direct impl access #3 Do you have a unit test showing the issue you're seeing ? We have a bunch of unit tests that test sync repl, you may want to make sure they run OK before submitting your onw unit test Cheers, Bela View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870225#3870225 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870225 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: Synchronous replication (REPL_SYNC) does not block the c
when calling put() directly, you are bypassing any of the interceptors, therefore ignoring locking, cacheloading etc View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870226#3870226 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870226 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - evict
what is difference between evict and remove? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870227#3870227 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870227 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2-jdk-matrix build.77 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20050315115542Lbuild.77 BUILD COMPLETE - build.77Date of build: 03/15/2005 11:55:42Time to build: 37 minutes 1 second Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (0)
[JBoss-dev] [JBossCache] - Re: Can't lookup cache service through JNDI
Here's a temp URL to documentation: http://docs.jboss.org/nightly/cache/TreeCache/html_single/ View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870234#3870234 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870234 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: JBossCache 1.2.1 released
Sorry, the doc on the website is slightly out-of-date. Here's a temp URL for the doc, until we have updated it: http://docs.jboss.org/nightly/cache/TreeCache/html_single/ View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870235#3870235 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870235 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JCA on JBoss] - JCA1.0 with JBOSS4.X
Is it possible to deploy a JCA1.0 based Adapter in JBoss 4.x (JCA1.5)? (only change -ds.xml file?). Has someone any ideas how to do that? thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870238#3870238 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870238 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: evict
evict() removes from memory, remove() removes from memory and (if enabled) CacheLoader View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870240#3870240 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870240 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-3.2-testsuite Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20050315123258 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:66: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See tests.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 03/15/2005 12:32:58Time to build: 21 minutes 28 seconds Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (0)
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1573) NPE in SQLUtil.appendColumnNamesClause
[ http://jira.jboss.com/jira/browse/JBAS-1573?page=comments#action_12316173 ] cgs commented on JBAS-1573: --- For the class that this selector is in, I am using: * @jboss.eager-load-group * name="most" * * @jboss.load-group * name="most" * * @jboss.read-ahead * strategy="on-find" * page-size="25" * eager-load-group="most" By disabling the read-ahead with: * ---jboss.read-ahead * strategy="on-find" * page-size="25" * eager-load-group="most" ... the QL is compiled. > NPE in SQLUtil.appendColumnNamesClause > -- > > Key: JBAS-1573 > URL: http://jira.jboss.com/jira/browse/JBAS-1573 > Project: JBoss Application Server > Type: Bug > Components: CMP service > Versions: JBossAS-4.0.1 Final > Environment: Windows XP Pro SP2, JBoss 4.0.1, Sun JDK 1.5.0_01 > Reporter: cgs > Assignee: Alexey Loubyansky > > > ejbSelect JBoss-QL query does not build successfully and throws NPE in > SQLUtil.appendColumnNamesClause. This query works for bean X relating to the > same related bean Y, but not for bean Z. They are both M:N relations. > * @jboss.query > * signature="java.util.Collection > ejbSelectContactList(com.xxx.emm.interfaces.CampaignLocal campaignLocal, int > offset, int limit)" > * query="SELECT DISTINCT OBJECT(co) > * FROM campaign c, > * IN (c.contactList) AS co > * WHERE c = ?1 > * ORDER BY co.id ASC > * OFFSET ?2 > * LIMIT ?3" > * > Here's the stack trace: > 2005-03-12 00:30:05,607 DEBUG > [org.jboss.ejb.plugins.cmp.jdbc.JDBCJBossQLQuery.Campaign#ejbSelectContactList] > JBossQL: SELECT DISTINCT OBJECT(co) FROM campaign c, IN (c.contactList) AS > co WHERE c = ?1 ORDER BY co.id ASC OFFSET ?2 LIMIT ?3 > 2005-03-12 00:30:05,607 INFO [STDOUT] java.lang.NullPointerException > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.appendColumnNamesClause(SQLUtil.java:386) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler.selectEntity(JDBCEJBQLCompiler.java:1849) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler.visit(JDBCEJBQLCompiler.java:1012) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.ejb.plugins.cmp.ejbql.ASTSelect.jjtAccept(ASTSelect.java:25) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler.visit(JDBCEJBQLCompiler.java:510) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.ejb.plugins.cmp.ejbql.ASTEJBQL.jjtAccept(ASTEJBQL.java:23) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLCompiler.compileJBossQL(JDBCEJBQLCompiler.java:197) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.ejb.plugins.cmp.jdbc.JDBCJBossQLQuery.(JDBCJBossQLQuery.java:43) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createJBossQLQuery(JDBCCommandFactory.java:72) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.ejb.plugins.cmp.jdbc.JDBCQueryManager.start(JDBCQueryManager.java:260) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.startStoreManager(JDBCStoreManager.java:490) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:381) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:157) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.ejb.EntityContainer.startService(EntityContainer.java:340) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > java.lang.reflect.Method.invoke(Method.java:585) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > 2005-03-12 00:30:05,607 INFO [STDOUT]at > org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) > 2005-03-12 00:
[JBoss-dev] [Design of JBoss Eclipse IDE (dev)] - JBoss-IDE 1.4.1
Errors on install Plug-in "org.eclipse.xsd" version "2.0.1" referenced by this feature is missing. Plug-in "org.eclipse.emf.ecore" version "2.0.1" referenced by this feature is missing. Plug-in "org.eclipse.emf.common" version "2.0.1" referenced by this feature is missing. does anyone know where I can get these plug-ins. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870253#3870253 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870253 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050315134535 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 03/15/2005 13:45:35Time to build: 27 minutes 9 secondsLast changed: 03/15/2005 13:07:22Last log entry: Remove unnecessary isDebugEnabled Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (27)1.2modifiedejortkernel/src/main/org/jboss/kernel/KernelFactory.javaRemove unnecessary isDebugEnabled1.13modifiedejortcommon/src/main/org/jboss/logging/Logger.javaAdd a basic overview of how the various logging levels should be used.Deprecate isInfoEnabled() and isDebugEnabled().These levels are for low volume logging which should notrequire this checking.1.12modifiedejortcommon/src/main/org/jboss/logging/Logger.javaAdd the missing serialVersionUUID1.7modifiedmnf999webservice/src/main/org/jboss/ws/soap/NodeImpl.javachanges to get webservices to compile on JDK51.2modifiedmnf999webservice/src/main/org/jboss/ws/soap/SOAPBodyDocElement.javachanges to get webservices to compile on JDK51.2modifiedmnf999webservice/src/main/org/jboss/ws/soap/SOAPBodyRpcElement.javachanges to get webservices to compile on JDK51.6modifiedmnf999jaxrpc/src/main/org/apache/axis/message/NodeImpl.javaSome fixes to be able to compile on JDK51.5modifiedmnf999jaxrpc/src/main/org/apache/axis/message/SOAPElementImpl.javaSome fixes to be able to compile on JDK51.5modifiedmnf999jaxrpc/src/main/org/apache/axis/message/SOAPPartImpl.javaSome fixes to be able to compile on JDK51.4modifiedmnf999jaxrpc/src/main/org/apache/axis/message/SOAPDocumentImpl.javaSome fixes to be able to compile on JDK51.5modifiedejortj2ee/src/main/javax/resource/ResourceException.javaTemplate solution for resolvingj2eeri and legacy serialization compatibility1.13modifiedloubyanskytestsuite/src/main/org/jboss/test/xml/MiscUnitTestCase.javaadjusted tests after api refactoring1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/sunday/unmarshalling/impl/AttributeBindingImpl.javafixes and refactoring1.2deletedloubyanskycommon/src/main/org/jboss/xml/binding/sunday/unmarshalling/impl/AttributeTypeImpl.javafixes and refactoring1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/sunday/unmarshalling/impl/DocumentHandlerImpl.javafixes and refactoring1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/sunday/unmarshalling/impl/ElementBindingImpl.javafixes and refactoring1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/sunday/unmarshalling/impl/ElementHandlerImpl.javafixes and refactoring1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/sunday/unmarshalling/impl/ElementStack.javafixes and refactoring1.2deletedloubyanskycommon/src/main/org/jboss/xml/binding/sunday/unmarshalling/impl/ElementTypeImpl.javafixes and refactoring1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/sunday/unmarshalling/impl/TextContentImpl.javafixes and refactoring1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/sunday/unmarshalling/AttributeBinding.javafixes and refactoring1.2deletedloubyanskycommon/src/main/org/jboss/xml/binding/sunday/unmarshalling/AttributeType.javafixes and refactoring1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/sunday/unmarshalling/DocumentHandler.javafixes and refactoring1.1addedloubyanskycommon/src/main/org/jboss/xml/binding/sunday/unmarshalling/ElementBinding.javafixes and refactoring1.2modifiedloubyanskycommon/src/main/org/jboss/xml/binding/sunday/unmarshalling/ElementHandler.javafixes and refactoring1.2deletedloubyanskycommon/src/main/org/jboss/xml/binding/sunday/unmarshalling/ElementType.javafixes and refactoring1.37modifiedloubyanskycommon/src/main/org/jboss/xml/binding/ObjectModelBuilder.javafixed switching to a new object model factory when the factory is actually the same for the previous and next namespace URI
[JBoss-dev] [TODO -- DEVELOPMENT] - Re: joesnmp modified source code
Here's the full history: http://cvs.sourceforge.net/viewcvs.py/joesnmp/joesnmp/CHANGELOG.txt?view=markup It seems you've done some serious fixes there! Send me a private email, I'll try to get you rw access to joesnmp... Good stuff! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870255#3870255 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870255 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - TreeCache inside JBOSS 3.2.6
Can I use TreeCacheAOP - thereby replicating only attributes that change, as opposed to replicating entire objects or sessions across servers - within JBOSS 3.2.6 with POJOs? Thanks. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870256#3870256 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870256 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - cannot login
When I try using admin/admin to log in for the first time, I get a '404 page not found' in the main window.(The URL at that point is http://localhost:8080/portal/auth/j_security_check) Thanx in advance for the help. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870260#3870260 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870260 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBPM-88) add a statelog that includes enter-time, leave-time and difference
add a statelog that includes enter-time, leave-time and difference -- Key: JBPM-88 URL: http://jira.jboss.com/jira/browse/JBPM-88 Project: JBoss jBPM Type: Task Components: Core Engine Reporter: Tom Baeyens Assigned to: Tom Baeyens Priority: Minor Fix For: jBPM 3.0 alpha 3 add a state-enter-time on the token when a state is entered. add a state log record when the state is left. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: error when I loggin in jboss portal
If the 'jboss' DB username's host is localhost, try changeing it to localhost.localdomain (It might be completely unrelated to your problem but I had a problem accessing the DB until I did this). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870265#3870265 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870265 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Mail Services] - Re: What I am (not) Looking For In A Java-Based E-mail Serve
Andy, Thanks for that reply. I am curious to learn more of your thoughts about the Mailet API. In considering James, I liked the idea of being able to chain standard and custom matchers to handle mail processing. It seems like a very flexible, almost aspect-oriented, approach to handling mail processing. Also, it's a 100% Java API, not JavaScript, BeanShell, php, perl, or some other non-Java solution. Jack View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870270#3870270 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870270 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050315160037 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 03/15/2005 16:00:37Time to build: 43 minutes 31 secondsLast changed: 03/15/2005 15:49:09Last log entry: Undoing my own changes :) Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (60)1.8modifiedmnf999webservice/src/main/org/jboss/ws/soap/NodeImpl.javaUndoing my own changes :)1.3modifiedmnf999webservice/src/main/org/jboss/ws/soap/SOAPBodyDocElement.javaUndoing my own changes :)1.3modifiedmnf999webservice/src/main/org/jboss/ws/soap/SOAPBodyRpcElement.javaUndoing my own changes :)1.18modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/WSDL11ToJavaTestCase.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.3modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/WSDL11ToWSDL20TestCase.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.7modifiedmnf999jaxrpc/src/main/org/apache/axis/message/NodeImpl.javaUndoing my changes :) never mind I guess we will stick JDK1.4 for now :)1.5modifiedmnf999jaxrpc/src/main/org/apache/axis/message/SOAPDocumentImpl.javaUndoing my changes :) never mind I guess we will stick JDK1.4 for now :)1.6modifiedmnf999jaxrpc/src/main/org/apache/axis/message/SOAPElementImpl.javaUndoing my changes :) never mind I guess we will stick JDK1.4 for now :)1.6modifiedmnf999jaxrpc/src/main/org/apache/axis/message/SOAPPartImpl.javaUndoing my changes :) never mind I guess we will stick JDK1.4 for now :)1.3modifiedtdieslerwebservice/test/java/org/jboss/test/ws/soap/SOAPFaultTestCase.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.19modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDL11Reader.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.7modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDL11Writer.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.16modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDL20Writer.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.21modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDLDefinitions.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.4modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDLDocumentation.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.5modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDLEndpoint.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.11modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDLInterface.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.6modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDLInterfaceFault.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.5modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDLInterfaceOperationOutfault.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.13modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDLWriter.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.2modifiedtdieslerwebservice/src/main/org/jboss/ws/soap/DetailImpl.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.9modifiedtdieslerwebservice/src/main/org/jboss/ws/server/ServiceEndpoint.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.4modifiedtdieslerwebservice/src/main/org/jboss/ws/jaxrpc/FaultException.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.1addedtdieslerwebservice/src/main/org/jboss/ws/jaxrpc/desc/FaultDesc.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.27modifiedtdies
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1589) Type in JBossMQ's TxManager
Type in JBossMQ's TxManager
---
Key: JBAS-1589
URL: http://jira.jboss.com/jira/browse/JBAS-1589
Project: JBoss Application Server
Type: Bug
Components: JMS service
Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1
Reporter: Adrian Brock
Priority: Blocker
Fix For: JBossAS-4.0.2 Final
There is a typo in org.jboss.mq.pm.TxManager:
public void rollbackTx(Tx txId) throws JMSException
{
txId.commit(persistenceManager);
}
should be
public void rollbackTx(Tx txId) throws JMSException
{
txId.rollback(persistenceManager);
}
--
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1589) Type in JBossMQ's TxManager
[ http://jira.jboss.com/jira/browse/JBAS-1589?page=history ]
Adrian Brock closed JBAS-1589:
--
Resolution: Done
Fixed
> Type in JBossMQ's TxManager
> ---
>
> Key: JBAS-1589
> URL: http://jira.jboss.com/jira/browse/JBAS-1589
> Project: JBoss Application Server
> Type: Bug
> Components: JMS service
> Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1
> Reporter: Adrian Brock
> Priority: Blocker
> Fix For: JBossAS-4.0.2 Final
>
>
> There is a typo in org.jboss.mq.pm.TxManager:
>public void rollbackTx(Tx txId) throws JMSException
>{
> txId.commit(persistenceManager);
>}
> should be
>public void rollbackTx(Tx txId) throws JMSException
>{
> txId.rollback(persistenceManager);
>}
--
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1589) Typo in JBossMQ's TxManager
[ http://jira.jboss.com/jira/browse/JBAS-1589?page=history ]
Adrian Brock updated JBAS-1589:
---
Summary: Typo in JBossMQ's TxManager (was: Type in JBossMQ's TxManager)
> Typo in JBossMQ's TxManager
> ---
>
> Key: JBAS-1589
> URL: http://jira.jboss.com/jira/browse/JBAS-1589
> Project: JBoss Application Server
> Type: Bug
> Components: JMS service
> Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1
> Reporter: Adrian Brock
> Priority: Blocker
> Fix For: JBossAS-4.0.2 Final
>
>
> There is a typo in org.jboss.mq.pm.TxManager:
>public void rollbackTx(Tx txId) throws JMSException
>{
> txId.commit(persistenceManager);
>}
> should be
>public void rollbackTx(Tx txId) throws JMSException
>{
> txId.rollback(persistenceManager);
>}
--
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Closed: (JBAS-1589) Typo in JBossMQ's TxManager
[ http://jira.jboss.com/jira/browse/JBAS-1589?page=history ]
Adrian Brock closed JBAS-1589:
--
Resolution: Done
> Typo in JBossMQ's TxManager
> ---
>
> Key: JBAS-1589
> URL: http://jira.jboss.com/jira/browse/JBAS-1589
> Project: JBoss Application Server
> Type: Bug
> Components: JMS service
> Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1
> Reporter: Adrian Brock
> Priority: Blocker
> Fix For: JBossAS-4.0.2 Final
>
>
> There is a typo in org.jboss.mq.pm.TxManager:
>public void rollbackTx(Tx txId) throws JMSException
>{
> txId.commit(persistenceManager);
>}
> should be
>public void rollbackTx(Tx txId) throws JMSException
>{
> txId.rollback(persistenceManager);
>}
--
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: TreeCache inside JBOSS 3.2.6
You can but it will take a lot of effort. As a matter of fact, I am implementing in jboss-head for the fine-grain http session replication down to the field level. So we will have granularity of SESSION, ATTRIBUTE, and FIELD. I need couple weeks to test it out and then back port it back to 4.0.x release sometime. -Ben View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870283#3870283 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870283 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Reopened: (JBAS-1589) Type in JBossMQ's TxManager
[ http://jira.jboss.com/jira/browse/JBAS-1589?page=history ]
Adrian Brock reopened JBAS-1589:
> Type in JBossMQ's TxManager
> ---
>
> Key: JBAS-1589
> URL: http://jira.jboss.com/jira/browse/JBAS-1589
> Project: JBoss Application Server
> Type: Bug
> Components: JMS service
> Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1
> Reporter: Adrian Brock
> Priority: Blocker
> Fix For: JBossAS-4.0.2 Final
>
>
> There is a typo in org.jboss.mq.pm.TxManager:
>public void rollbackTx(Tx txId) throws JMSException
>{
> txId.commit(persistenceManager);
>}
> should be
>public void rollbackTx(Tx txId) throws JMSException
>{
> txId.rollback(persistenceManager);
>}
--
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBossCache] - Re: TreeCacheAop can't add an object of a class which extend
Where did you find the first jboss-aop.xml example again? It should be "prepare" since JBossAop beta. The first one has been outdated. Best way is to run the the aop examples under distro and take it from there. -Ben View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870285#3870285 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870285 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Mail Services] - Re: What I am (not) Looking For In A Java-Based Enterprise E
Look, it sounds like you really like JAMES and want to use JAMES, so go use JAMES. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870286#3870286 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870286 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of Mail Services] - MailListeners and Beanshells
The beanshell or javascript thing will be one MailListener which may or may not route things to other maillisteners. You'll not be obligated to use it. I do however want some deployment semantics around it (meaning the abillity to deploy new mail beanshell/javascript scripts for routing/processing/eliminating mail). Selective matching of mail listeners. An example of this is the James matchers/selectors/etc. They are for conditionally applying workers in a chain of command pattern (Basically a mix of the reactor pattern and chain of command pattern). We may indeed implement something very like this but for the next several milestones, I intend to keep a single simple (easy to debug) chain rather than a branched chain. I'm also not 100% sold on a branched chain being implicitly supported rather than explicitly. Meaning I may opt for special MailListeners that take the chain of mail listeners and then apply conditions to the mail listeners that they contain rather than support matching/selecting in the core framework itself. (In fact I'm nearly positive that I'll do this) Basically a kind of combination of the chain of command and composite pattern in which the composite object happens to itself impelement a combination of the chain of command and reactor pattern (similar to the behavior in james). What we need to do right now is start enhancing Mail.java to provide more robust features for altering/reading/searching/matching headers. I'd also like to see some thoughts on how a MailListener which can perform operations on said Mail and other things like chain termination. Eventually it should provide imperative modes of maillistener chain aggregation. I have some inklings to use AOP for security and it might be possible to use AOP to implement the chain but I'm resistent to the idea as a generic construct. Thoughts (from code contributors/developers or active users only please)? -Andy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870287#3870287 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870287 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1589) Typo in JBossMQ's TxManager
[
http://jira.jboss.com/jira/browse/JBAS-1589?page=comments#action_12316175 ]
Ivelin Ivanov commented on JBAS-1589:
-
Is there a test case committed for this bug? If not, QA can make sure there is
one.
> Typo in JBossMQ's TxManager
> ---
>
> Key: JBAS-1589
> URL: http://jira.jboss.com/jira/browse/JBAS-1589
> Project: JBoss Application Server
> Type: Bug
> Components: JMS service
> Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1
> Reporter: Adrian Brock
> Priority: Blocker
> Fix For: JBossAS-4.0.2 Final
>
>
> There is a typo in org.jboss.mq.pm.TxManager:
>public void rollbackTx(Tx txId) throws JMSException
>{
> txId.commit(persistenceManager);
>}
> should be
>public void rollbackTx(Tx txId) throws JMSException
>{
> txId.rollback(persistenceManager);
>}
--
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1589) Typo in JBossMQ's TxManager
[
http://jira.jboss.com/jira/browse/JBAS-1589?page=comments#action_12316177 ]
Adrian Brock commented on JBAS-1589:
Of course there is, I would be wasting my time if I had to refix the problem in
6 months time.
> Typo in JBossMQ's TxManager
> ---
>
> Key: JBAS-1589
> URL: http://jira.jboss.com/jira/browse/JBAS-1589
> Project: JBoss Application Server
> Type: Bug
> Components: JMS service
> Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1
> Reporter: Adrian Brock
> Priority: Blocker
> Fix For: JBossAS-4.0.2 Final
>
>
> There is a typo in org.jboss.mq.pm.TxManager:
>public void rollbackTx(Tx txId) throws JMSException
>{
> txId.commit(persistenceManager);
>}
> should be
>public void rollbackTx(Tx txId) throws JMSException
>{
> txId.rollback(persistenceManager);
>}
--
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1590) Container does not call commit or refresh for the JACC provider
Container does not call commit or refresh for the JACC provider --- Key: JBAS-1590 URL: http://jira.jboss.com/jira/browse/JBAS-1590 Project: JBoss Application Server Type: Bug Components: Security Versions: JBossAS-4.0.1 SP1 Environment: Windows XP SP2 Reporter: Stephen Kinser The JBoss Application Server does not call commit on the PolicyConfiguration objects when the container has finished adding policy statements to it. In other words, the policy configuration remains in the open state and is never transitioned to the inService state. This is needed to conform to the JACC 1.0 requirement in section 3.1. This is the case for web modules and ejb modules. Further, the application server does not call refresh on the Policy object when the policy configurations have been committed. This is also needed to conform to the requirement in section 3.1. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head Build Failed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050315182622 BUILD FAILEDAnt Error Message: /home/cruisecontrol/work/scripts/build-jboss-head.xml:63: The following error occurred while executing this line: /home/cruisecontrol/work/scripts/build-jboss-head.xml:37: Exit code: 1 See compile.log in Build Artifacts for details. JAVA_HOME=/opt/j2sdk1.4.2_05/Date of build: 03/15/2005 18:26:22Time to build: 27 minutes 24 secondsLast changed: 03/15/2005 16:56:24Last log entry: Unmarshal soap Fault into a user exception and propagate to the calling client. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (66)1.12modifiedtdieslerwebservice/src/main/org/jboss/ws/soap/MessageFactoryImpl.javaUnmarshal soap Fault into a user exception and propagate to the calling client.1.5modifiedtdieslerwebservice/src/main/org/jboss/ws/soap/SOAPFaultImpl.javaUnmarshal soap Fault into a user exception and propagate to the calling client.1.6modifiedtdieslerwebservice/src/main/org/jboss/ws/server/ServiceEndpointInvoker.javaUnmarshal soap Fault into a user exception and propagate to the calling client.1.40modifiedtdieslerwebservice/src/main/org/jboss/ws/jaxrpc/CallImpl.javaUnmarshal soap Fault into a user exception and propagate to the calling client.1.3modifiedtdieslerwebservice/src/main/org/jboss/ws/jaxrpc/CallProxy.javaUnmarshal soap Fault into a user exception and propagate to the calling client.1.5modifiedtdieslerwebservice/src/main/org/jboss/ws/jaxrpc/FaultException.javaUnmarshal soap Fault into a user exception and propagate to the calling client.1.8modifiedmnf999webservice/src/main/org/jboss/ws/soap/NodeImpl.javaUndoing my own changes :)1.3modifiedmnf999webservice/src/main/org/jboss/ws/soap/SOAPBodyDocElement.javaUndoing my own changes :)1.3modifiedmnf999webservice/src/main/org/jboss/ws/soap/SOAPBodyRpcElement.javaUndoing my own changes :)1.18modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/WSDL11ToJavaTestCase.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.3modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/WSDL11ToWSDL20TestCase.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.7modifiedmnf999jaxrpc/src/main/org/apache/axis/message/NodeImpl.javaUndoing my changes :) never mind I guess we will stick JDK1.4 for now :)1.5modifiedmnf999jaxrpc/src/main/org/apache/axis/message/SOAPDocumentImpl.javaUndoing my changes :) never mind I guess we will stick JDK1.4 for now :)1.6modifiedmnf999jaxrpc/src/main/org/apache/axis/message/SOAPElementImpl.javaUndoing my changes :) never mind I guess we will stick JDK1.4 for now :)1.6modifiedmnf999jaxrpc/src/main/org/apache/axis/message/SOAPPartImpl.javaUndoing my changes :) never mind I guess we will stick JDK1.4 for now :)1.3modifiedtdieslerwebservice/test/java/org/jboss/test/ws/soap/SOAPFaultTestCase.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.19modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDL11Reader.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.7modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDL11Writer.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.16modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDL20Writer.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.21modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDLDefinitions.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.4modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDLDocumentation.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.5modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDLEndpoint.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.11modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDLInterface.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.6modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDLInterfaceFault.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.5modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDLInterfaceOperationOutfault.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endp
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1579) Need to cleanup the serialVersionUIDs for Serializable/Externalizable classes
[ http://jira.jboss.com/jira/browse/JBAS-1579?page=comments#action_12316182 ] Scott M Stark commented on JBAS-1579: - Here is a preliminary example of the types of changes I'm seeing. This is a diff between the current 4.0 branch and the 4.0.1 release. This is across all jars in the lib and server/all directories so thirdparty changes are also reflected. WARNING: serialVersionUID error for javax.management.modelmbean.DescriptorSupport$FieldName, 401: 2645619836053638810, current: -6292969195866300415WARNING: serialVersionUID error for javax.security.jacc.EJBMethodPermission, 401: -2677271975280050210, current: 141000WARNING: serialVersionUID error for javax.security.jacc.EJBRoleRefPermission, 401: -4374811682927746472, current: 141000WARNING: serialVersionUID error for javax.xml.namespace.QName, 401: 8217399441836960859, current: 4418622981026545151WARNING: serialVersionUID error for org.apache.axis.AxisEngine, 401: 783705919602087477, current: -6536560628462902930 WARNING: serialVersionUID error for org.apache.axis.AxisFault, 401: 7656291048487769618, current: 1821054234255058350 WARNING: serialVersionUID error for org.apache.axis.ConfigurationException, 401: -2031305405698866120, current: 3128145386557654796 WARNING: serialVersionUID error for org.apache.axis.FaultableHandler, 401: -1318575215335790977, current: -9888308697472666 WARNING: serialVersionUID error for org.apache.axis.InternalException, 401: -7837575501867271417, current: -2439038787028853642 WARNING: serialVersionUID error for org.apache.axis.Message, 401: -673079399072703001, current: -3797053663591575461 WARNING: serialVersionUID error for org.apache.axis.SimpleTargetedChain, 401: 4326784208937906611, current: 6081663876761825537 WARNING: serialVersionUID error for org.apache.axis.attachments.AttachmentsImpl, 401: -3635216569769100668, current: 6592081539679813264 WARNING: serialVersionUID error for org.apache.axis.client.AxisClient, 401: 8628363337655480796, current: 917328696653918636 WARNING: serialVersionUID error for org.apache.axis.client.Service, 401: -3104162953909360111, current: -5518418527298163671 WARNING: serialVersionUID error for org.apache.axis.deployment.wsdd.WSDDDeployableItem, 401: -3260006150211853091, current: -2293858078946363728 WARNING: serialVersionUID error for org.apache.axis.deployment.wsdd.WSDDDeployment, 401: -8079485375776187246, current: -4445495595412038453 WARNING: serialVersionUID error for org.apache.axis.deployment.wsdd.WSDDDocumentation, 401: 3150861050769407999, current: 3995390874236084737 WARNING: serialVersionUID error for org.apache.axis.deployment.wsdd.WSDDElement, 401: 3563586045048588795, current: -592921944454858369 WARNING: serialVersionUID error for org.apache.axis.deployment.wsdd.WSDDGlobalConfiguration, 401: 8096089502610845101, current: -432056797726163452 WARNING: serialVersionUID error for org.apache.axis.deployment.wsdd.WSDDService, 401: -3778233437705831680, current: 7898527740946309006 WARNING: serialVersionUID error for org.apache.axis.description.ParameterDesc, 401: 8514989580706837763, current: 5531650781024519497 WARNING: serialVersionUID error for org.apache.axis.encoding.DeserializerImpl, 401: 3611196368372543212, current: -378592058256066308 WARNING: serialVersionUID error for org.apache.axis.encoding.ser.ArrayDeserializer, 401: 268734140916921026, current: -2333663097459692847 WARNING: serialVersionUID error for org.apache.axis.encoding.ser.ArraySerializer, 401: 7851885505904114045, current: -295100666141518 WARNING: serialVersionUID error for org.apache.axis.encoding.ser.ArraySerializerFactory, 401: 5237560634678155448, current: -440164809313455300 WARNING: serialVersionUID error for org.apache.axis.encoding.ser.Base64Deserializer, 401: 7330763014108753158, current: 6851029229010507274 WARNING: serialVersionUID error for org.apache.axis.encoding.ser.BaseDeserializerFactory, 401: 8950949792689718127, current: -5984246614308993424 WARNING: serialVersionUID error for org.apache.axis.encoding.ser.BaseSerializerFactory, 401: 5578716727285237604, current: -9059108483290118954 WARNING: serialVersionUID error for org.apache.axis.encoding.ser.BeanDeserializer, 401: -1133032377918216855, current: 3852320955478399407 WARNING: serialVersionUID error for org.apache.axis.encoding.ser.BeanDeserializerFactory, 401: 6820538762993201693, current: 9006429762992702423 WARNING: serialVersionUID error for org.apache.axis.encoding.ser.BeanSerializer, 401: 9019938287273362475, current: -7009951737671158500 WARNING: serialVersionUID error for org.apache.axis.encoding.ser.CalendarSerializer, 401: -6302463588379174538, current: 2751762093676757560 WARNING: serialVersionUID error for org.apache.axis.encoding.ser.DateDeserializer, 401: 6145205136706780990, current: 4103689753889895911 WARNING: serialVersionUID error for org.apache.axis.encoding.ser.DateSerializer, 401: 1738433042297509590, c
[JBoss-dev] jboss-3.2 build.311 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2?log=log20050315192050Lbuild.311 BUILD COMPLETE - build.311Date of build: 03/15/2005 19:20:50Time to build: 46 minutes 30 secondsLast changed: 03/15/2005 18:12:58Last log entry: [JBAS-1589] - Typo in TxManager Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.2.8.2modifiedejortmessaging/src/main/org/jboss/mq/pm/TxManager.java[JBAS-1589] - Typo in TxManager
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-88) Make slide use RDBMS instead of FS
[ http://jira.jboss.com/jira/browse/JBPORTAL-88?page=history ] Julien Viet updated JBPORTAL-88: Fix Version: 2.0 Beta 2 (was: 2.0 Beta 1) > Make slide use RDBMS instead of FS > -- > > Key: JBPORTAL-88 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-88 > Project: JBoss Portal > Type: Sub-task > Reporter: Roy Russo > Assignee: Roy Russo > Fix For: 2.0 Beta 2 > > -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-69) Update profile of someone else
[ http://jira.jboss.com/jira/browse/JBPORTAL-69?page=history ] Julien Viet updated JBPORTAL-69: Environment: Security Level: (was: Public) Fix Version: 2.0 Final (was: 2.0 Beta 1) > Update profile of someone else > -- > > Key: JBPORTAL-69 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-69 > Project: JBoss Portal > Type: Sub-task > Components: Portal Core > Versions: 2.0 Alpha > Reporter: Thomas Heute > Assignee: Thomas Heute > Fix For: 2.0 Final > > > For administrators only -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPTL-29) HTML module port
[ http://jira.jboss.com/jira/browse/JBPTL-29?page=history ] Julien Viet updated JBPTL-29: - Environment: Fix Version: 2.0 Final (was: 2.0 Beta 1) > HTML module port > > > Key: JBPTL-29 > URL: http://jira.jboss.com/jira/browse/JBPTL-29 > Project: JBoss Portal > Type: Feature Request > Reporter: Julien Viet > Assignee: Roy Russo > Fix For: 2.0 Final > > > Port the html module -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPTL-27) XWiki integration
[ http://jira.jboss.com/jira/browse/JBPTL-27?page=history ] Julien Viet updated JBPTL-27: - Environment: Fix Version: 2.0 Final (was: 2.0 Beta 1) > XWiki integration > - > > Key: JBPTL-27 > URL: http://jira.jboss.com/jira/browse/JBPTL-27 > Project: JBoss Portal > Type: Feature Request > Reporter: Julien Viet > Assignee: Roy Russo > Fix For: 2.0 Final > > > Look at the integration points (security, indexing, storage, etc...) then do > it -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-190) User with no role generates an error
[ http://jira.jboss.com/jira/browse/JBPORTAL-190?page=history ] Julien Viet updated JBPORTAL-190: - Fix Version: 2.0 Beta 2 (was: 2.0 Beta 1) > User with no role generates an error > > > Key: JBPORTAL-190 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-190 > Project: JBoss Portal > Type: Bug > Components: Portal Core > Versions: 2.0 Beta 2 > Reporter: Thomas Heute > Assignee: Thomas Heute > Fix For: 2.0 Beta 2 > > > If a user is in no role, the following exception happens: > java.lang.NullPointerException > at java.util.Arrays.mergeSort(Arrays.java:1152) > at java.util.Arrays.sort(Arrays.java:1079) > at > org.apache.catalina.realm.GenericPrincipal.(GenericPrincipal.java:77) > at > org.jboss.web.tomcat.security.JBossGenericPrincipal.(JBossGenericPrincipal.java:46) > at > org.jboss.web.tomcat.security.JBossSecurityMgrRealm.getCachingPrincpal(JBossSecurityMgrRealm.jav > a:342) > We need either to make sure a user is in a default immutable role, or that a > user can have no role (but does not crash). > For now, portlet.xml must contain a default role for the user portlet: > > Default role of registered users > defaultRole > Users > > In this case "Users" must be an existing name of role in the database. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBPORTAL-190) User with no role generates an error
[ http://jira.jboss.com/jira/browse/JBPORTAL-190?page=history ] Julien Viet updated JBPORTAL-190: - Version: 2.0 Beta 2 (was: 2.0 Beta 1) > User with no role generates an error > > > Key: JBPORTAL-190 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-190 > Project: JBoss Portal > Type: Bug > Components: Portal Core > Versions: 2.0 Beta 2 > Reporter: Thomas Heute > Assignee: Thomas Heute > Fix For: 2.0 Beta 2 > > > If a user is in no role, the following exception happens: > java.lang.NullPointerException > at java.util.Arrays.mergeSort(Arrays.java:1152) > at java.util.Arrays.sort(Arrays.java:1079) > at > org.apache.catalina.realm.GenericPrincipal.(GenericPrincipal.java:77) > at > org.jboss.web.tomcat.security.JBossGenericPrincipal.(JBossGenericPrincipal.java:46) > at > org.jboss.web.tomcat.security.JBossSecurityMgrRealm.getCachingPrincpal(JBossSecurityMgrRealm.jav > a:342) > We need either to make sure a user is in a default immutable role, or that a > user can have no role (but does not crash). > For now, portlet.xml must contain a default role for the user portlet: > > Default role of registered users > defaultRole > Users > > In this case "Users" must be an existing name of role in the database. -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-4.0 build.437 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050315203351Lbuild.437 BUILD COMPLETE - build.437Date of build: 03/15/2005 20:33:51Time to build: 46 minutes 19 secondsLast changed: 03/15/2005 18:31:15Last log entry: Replace the jdk-1.5 keyword enum Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (47)1.1.2.2deletedtdieslerjaxrpc/src/main/org/jboss/axis/enum/Enum.javaReplace the jdk-1.5 keyword enum1.1.2.2deletedtdieslerjaxrpc/src/main/org/jboss/axis/enum/Scope.javaReplace the jdk-1.5 keyword enum1.1.2.2deletedtdieslerjaxrpc/src/main/org/jboss/axis/enum/Style.javaReplace the jdk-1.5 keyword enum1.1.2.2deletedtdieslerjaxrpc/src/main/org/jboss/axis/enum/Use.javaReplace the jdk-1.5 keyword enum1.8.2.12modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/TypeMappingDescription.javaReplace the jdk-1.5 keyword enum1.22.2.7modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/WSDDGenerator.javaReplace the jdk-1.5 keyword enum1.40.2.17modifiedtdieslerwebservice/src/main/org/jboss/webservice/deployment/ServiceDescription.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/FaultableHandler.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/MessageContext.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/MessagePart.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/SimpleChain.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/wsdl/WSDL2Java.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/wsdl/toJava/Emitter.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/wsdl/toJava/JavaDeployWriter.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/wsdl/toJava/JavaEnumTypeWriter.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/wsdl/toJava/JavaFaultWriter.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/wsdl/toJava/JavaStubWriter.javaReplace the jdk-1.5 keyword enum1.1.2.3modifiedtdieslerjaxrpc/src/main/org/jboss/axis/wsdl/toJava/Utils.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/wsdl/symbolTable/BindingEntry.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/wsdl/symbolTable/FaultInfo.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/wsdl/symbolTable/SymbolTable.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/wsdl/fromJava/Types.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/wsdl/fromJava/Emitter.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/utils/JavaUtils.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/transport/java/JavaSender.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/transport/http/AxisServlet.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/providers/java/JavaProvider.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/providers/java/RPCInvocation.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/message/BodyBuilder.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/message/RPCElement.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/message/SOAPElementAxisImpl.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/message/SOAPEnvelopeAxisImpl.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/i18n/RB.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/handlers/soap/SOAPService.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/encoding/SerializationContextImpl.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/encoding/ser/EnumDeserializer.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/encoding/ser/EnumSerializer.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/encoding/ser/SimpleSerializer.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/encoding/ser/BeanSerializer.javaReplace the jdk-1.5 keyword enum1.1.2.2modifiedtdieslerjaxrpc/src/main/org/jboss/axis/encoding
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1523) JBAS-30 - txtimers created via Servlet init get duplicated
[ http://jira.jboss.com/jira/browse/JBAS-1523?page=history ] Ivelin Ivanov reassigned JBAS-1523: --- Assign To: Alexey Loubyansky Alex, this is an EJBTimer related case. Can you please evaluate it and comment in JIRA? > JBAS-30 - txtimers created via Servlet init get duplicated > -- > > Key: JBAS-1523 > URL: http://jira.jboss.com/jira/browse/JBAS-1523 > Project: JBoss Application Server > Type: Support Patch > Versions: JBossAS-4.0.0 Final > Reporter: Luc Texier > Assignee: Alexey Loubyansky > > > Some customers have expressed the wish to get the issue fixed in JBossAS 4.0.0 -- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] jboss-head build.881 Build Fixed
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050315222823Lbuild.881 BUILD COMPLETE - build.881Date of build: 03/15/2005 22:28:23Time to build: 24 minutes 30 secondsLast changed: 03/15/2005 21:26:16Last log entry: Fix the eclipse build Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (77)1.3modifiedejortjmx-remoting/.classpathFix the eclipse build1.7modifiedejortjaxrpc/src/main/org/apache/axis/message/SOAPPartImpl.javaComplete the 1.5 rollback1.49modifiedtdieslerwebservice/build.xmlFix the build for jdk-1.51.7modifiedtdieslerjaxrpc/build.xmlFix the build for jdk-1.51.3modifiedejorttestsuite/src/main/org/jboss/test/jbossmq/test/XAResourceUnitTestCase.javaPort JBAS-1589 from jboss41.7modifiedejortmessaging/src/main/org/jboss/mq/pm/TxManager.javaPort JBAS-1589 from jboss41.8modifiedtdieslerjaxrpc/src/main/org/apache/axis/message/NodeImpl.javaRollback jdk-1.5 related DOM API changes1.7modifiedtdieslerjaxrpc/src/main/org/apache/axis/message/SOAPElementImpl.javaRollback jdk-1.5 related DOM API changes1.9modifiedtdieslerwebservice/src/main/org/jboss/ws/soap/NodeImpl.javaRollback jdk-1.5 related DOM API changes1.4modifiedtdieslerwebservice/src/main/org/jboss/ws/soap/SOAPBodyDocElement.javaRollback jdk-1.5 related DOM API changes1.4modifiedtdieslerwebservice/src/main/org/jboss/ws/soap/SOAPBodyRpcElement.javaRollback jdk-1.5 related DOM API changes1.12modifiedtdieslerwebservice/src/main/org/jboss/ws/soap/MessageFactoryImpl.javaUnmarshal soap Fault into a user exception and propagate to the calling client.1.5modifiedtdieslerwebservice/src/main/org/jboss/ws/soap/SOAPFaultImpl.javaUnmarshal soap Fault into a user exception and propagate to the calling client.1.6modifiedtdieslerwebservice/src/main/org/jboss/ws/server/ServiceEndpointInvoker.javaUnmarshal soap Fault into a user exception and propagate to the calling client.1.40modifiedtdieslerwebservice/src/main/org/jboss/ws/jaxrpc/CallImpl.javaUnmarshal soap Fault into a user exception and propagate to the calling client.1.3modifiedtdieslerwebservice/src/main/org/jboss/ws/jaxrpc/CallProxy.javaUnmarshal soap Fault into a user exception and propagate to the calling client.1.5modifiedtdieslerwebservice/src/main/org/jboss/ws/jaxrpc/FaultException.javaUnmarshal soap Fault into a user exception and propagate to the calling client.1.8modifiedmnf999webservice/src/main/org/jboss/ws/soap/NodeImpl.javaUndoing my own changes :)1.3modifiedmnf999webservice/src/main/org/jboss/ws/soap/SOAPBodyDocElement.javaUndoing my own changes :)1.3modifiedmnf999webservice/src/main/org/jboss/ws/soap/SOAPBodyRpcElement.javaUndoing my own changes :)1.18modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/WSDL11ToJavaTestCase.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.3modifiedtdieslerwebservice/test/java/org/jboss/test/ws/tools/WSDL11ToWSDL20TestCase.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.7modifiedmnf999jaxrpc/src/main/org/apache/axis/message/NodeImpl.javaUndoing my changes :) never mind I guess we will stick JDK1.4 for now :)1.5modifiedmnf999jaxrpc/src/main/org/apache/axis/message/SOAPDocumentImpl.javaUndoing my changes :) never mind I guess we will stick JDK1.4 for now :)1.6modifiedmnf999jaxrpc/src/main/org/apache/axis/message/SOAPElementImpl.javaUndoing my changes :) never mind I guess we will stick JDK1.4 for now :)1.6modifiedmnf999jaxrpc/src/main/org/apache/axis/message/SOAPPartImpl.javaUndoing my changes :) never mind I guess we will stick JDK1.4 for now :)1.3modifiedtdieslerwebservice/test/java/org/jboss/test/ws/soap/SOAPFaultTestCase.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.19modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDL11Reader.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.7modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDL11Writer.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.16modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDL20Writer.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.21modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDLDefinitions.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.4modifiedtdieslerwebservice/src/main/org/jboss/ws/wsdl/WSDLDocumentation.javaAdd FaultDesc to OperationDesc.Add support for fault details on user defined exceptions thrown from the endpoint impl.1.5modifiedt
[JBoss-dev] jboss-4.0 build.438 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050316003201Lbuild.438 BUILD COMPLETE - build.438Date of build: 03/16/2005 00:32:01Time to build: 28 minutes 36 secondsLast changed: 03/15/2005 23:45:02Last log entry: Add jbosstest.src.etc and jbosstest.dist properties Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (2)1.406.2.45modifiedstarksmtestsuite/build.xmlAdd jbosstest.src.etc and jbosstest.dist properties1.1.2.1modifiedstarksmvaria/src/main/org/jboss/tools/SerialVersionUID.javaUpdate to just parse the lib and server/all jars.
[JBoss-dev] jboss-head build.882 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050316013934Lbuild.882 BUILD COMPLETE - build.882Date of build: 03/16/2005 01:39:34Time to build: 29 minutes 46 secondsLast changed: 03/15/2005 23:53:54Last log entry: Update to just parse the lib and server/all jars. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.2modifiedstarksmvaria/src/main/org/jboss/tools/SerialVersionUID.javaUpdate to just parse the lib and server/all jars.
[JBoss-dev] [Design of Mail Services] - Re: MailListeners and Beanshells
"altering/reading/searching/matching headers": The message store does not currently provide indexing functionality. We can either add this functionality to the store using SQL queries, or maybe implement a Lucene index. Your thoughts Mike? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870318#3870318 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870318 --- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
