[JBoss-dev] [Design of Mail Services] - Re: Default ports and use of SMTP MSA?
I agree with no ports being inherently "safer" than others... I myself was wary at first that this RFC was trying to implement a "security through obscurity" process. After trying to understand the practical use of running 2 SMTP servers with different functions and on different ports I came to realize that there was a real need for this measure. I know this is sort of "off-topic" for this forum, but for those that stumble onto this thread it may make sense to understand why I think that the possibility of running 2 SMTP servers was after all not a bad idea, and should definitely be available in JBoss Mail (and btw I am glad to see that it will be). Because spammers abuse open relays, which most often are found on port 25 SMTP servers, some ISPs block out-of-network calls to this port if they don't originate from their mail servers. Now, a well configured TLS/SSL SMTP server is not an open relay, nor an easy target for abuse... regardless of what port it's on, but an ISP has no way of knowing whether this is the case or not. Blocking port 25 across the board is their only way to make sure a spammer can't use their network to abuse an open relay. If SMTP servers found on port 587 are implemented with TLS/SSL as a standard measure (which seems to be the common practice), they will very rarely be the target of abuse (i.e. only if the security is weak, like bad passwords). Therefore servers running on these ports won't be subjected to the same blocking policies as port 25 because ISPs won't see the spammer abuse on those ports very often at all. The ability to use port 587 is really most beneficial to roaming users and users permanently outside the network, since inside your own network your users should send mail through your server anyway. Normally if you couldn't connect to port 25 for your mail server from a remote network, you'd have the option to use that network's mail server and still send email with your regular domain's email address... however, SPF and DomainKeys are changing the rules for that in an effort to curb some forms of spam and now using your domain's mail server has become the preferred method for on and out-of network users. Of course, if everyone implements TLS/SSL for relaying on every SMTP server out there, the problem would be solved and using port 587 would be unnecessary. The reality is that SMTP servers on port 25 are an unknown entity right now so standardizing the use of an alternate port helps migrate everyone in a way that can be easily tested by ISP's firewall rules. Ideal?... no, but it serves the right purpose. Pablo. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870498#3870498 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870498 --- 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: (JBMAIL-7) add a JAASUserRepository and support for JAAS-based security
[ http://jira.jboss.com/jira/browse/JBMAIL-7?page=comments#action_12316214 ] Andrew Oliver commented on JBMAIL-7: Sure. I'll put a follow on for a later milestone. JB's JACC implementation seems to be a bit of a moving target ATM. Moreover, we'll want to support existing stuff more or less. > add a JAASUserRepository and support for JAAS-based security > > > Key: JBMAIL-7 > URL: http://jira.jboss.com/jira/browse/JBMAIL-7 > Project: JBoss Mail > Type: Feature Request > Components: Security > Versions: 1.0-M3 > Reporter: Andrew Oliver > Assignee: Dawie Malan > Priority: Critical > Fix For: 1.0-M3 > > Original Estimate: 1 day > Remaining: 1 day > > Mailboxes should be secured by "roles" and accounts should be checked by JAAS > authentication. There should be a JAASUserRepository which merely checks > with JAAS in the test method and contains a jaas:/securityBlaBla > Extend the present UserRepository interface for hasPermission(roleName, > user). -- 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: (JBMAIL-7) add a JAASUserRepository and support for JAAS-based security
[ http://jira.jboss.com/jira/browse/JBMAIL-7?page=comments#action_12316213 ] Ivelin Ivanov commented on JBMAIL-7: When JACC is enabled (J2EE 1.4) it should be preferred to JAAS. > add a JAASUserRepository and support for JAAS-based security > > > Key: JBMAIL-7 > URL: http://jira.jboss.com/jira/browse/JBMAIL-7 > Project: JBoss Mail > Type: Feature Request > Components: Security > Versions: 1.0-M3 > Reporter: Andrew Oliver > Assignee: Dawie Malan > Priority: Critical > Fix For: 1.0-M3 > > Original Estimate: 1 day > Remaining: 1 day > > Mailboxes should be secured by "roles" and accounts should be checked by JAAS > authentication. There should be a JAASUserRepository which merely checks > with JAAS in the test method and contains a jaas:/securityBlaBla > Extend the present UserRepository interface for hasPermission(roleName, > user). -- 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 the new POJO MicroContainer] - Re: Kernel XML format
The schema for the property element should also support an xsd:any extension
type so that one is not constrained to simple constructs. For example, I can
use mulitple namespaces to introduce custom types that are marshalled with
either jbossxb or jaxb:
|
|
|
| 127.0.0.1
| Sun Jan 2 23:26:49 PST
2005
|
| prop1=value1
| prop2=value2
| prop3=${prop3.systemProperty}
|
| name1,name2,name3
| http://www.jboss.org
|
|
|
|
|
|Java
|Duke
|
|
|
|
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870495#3870495
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870495
---
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 Remoting, Unified Invokers] - Re: JBoss Remoting or JXTA ??
JBoss Remoting is built into JBoss AS (at least the newer versions), so will be there by default, so won't have to worry about plugging it in. My guess is that JBoss Remoting will be faster than JXTA for typical invocations (based on most JXTA implementations being XML based). I feel confident that the API and configuration is easier to deal with than with JXTA. Can also very easily switch out the transport protocol being used with JBoss Remoting. However, JBoss Remoting does not currently support multiple endpoints for invocations (but is on the road map). I'm not sure about the autoconnect/disconnect features of JXTA, so am not really sure about what this is or how it works. JBoss Remoting does require explicit connecting to remote endpoints (when using stateful transports). Hope that helps. -Tom View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870494#3870494 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870494 --- 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 the new POJO MicroContainer] - Re: Kernel XML format
Also, why not just borrow from the spring property model: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870493#3870493 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870493 --- 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 Remoting, Unified Invokers] - JBoss Remoting or JXTA ??
We are building an application that needs to share data between multiple JBoss servers. The original system architect, who has since left the project, suggested using the JXTA P2P stack for sending messages and objects between servers. Well, I'm not really fond of the way JXTA was plugged into JBoss, so I need to fix that portion of the implementation anyway. Fortunately ( or unfortunately ) there isn't that much JXTA framework in place that needs to be refactored, so I'm pretty much starting from scratch. I know if I build a proper JXTA implemtation, I will get auto-discovery of other peers in the group, it handles autoconnect / disconnect, and I can marshall data to the remote server to multiple endpoints with their pipes interface. Would I get any extra benefit from switching to Jboss remoting, other that possibly easier configuration ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870492#3870492 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870492 --- 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 the new POJO MicroContainer] - Re: Kernel XML format
Does this support nested java beans, or is that the Beans as values item? Also,
what about custom object factories based on namespaces? This is an example from
head I'm working on for the legacy service descritpor:
|
|
| ...
|
|
|
|
|
| 127.0.0.1
| Sun Jan 2 23:26:49 PST
2005
|
| prop1=value1
| prop2=value2
| prop3=${prop3.systemProperty}
|
| name1,name2,name3
| http://www.jboss.org
|
|
| ...
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870491#3870491
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870491
---
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.887 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050316232818Lbuild.887 BUILD COMPLETE - build.887Date of build: 03/16/2005 23:28:18Time to build: 18 minutes 41 secondsLast changed: 03/16/2005 23:22:45Last log entry: JBREM-83 - changed so InvocationMarshaller will support non org.jboss.Invocation payloads. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (1)1.2modifiedtelrodserver/src/main/org/jboss/invocation/unified/marshall/InvocationMarshaller.javaJBREM-83 - changed so InvocationMarshaller will support non org.jboss.Invocation payloads.
[JBoss-dev] [Design of JBoss Remoting, Unified Invokers] - Re: Problem with datatype=invocation in the socket connector
Hey Tom, that was pretty quick. Thanks a lot. Regards, Francisco View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870489#3870489 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870489 --- 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: (JBREM-83) Updated Invocation marshalling to support standard payloads
[ http://jira.jboss.com/jira/browse/JBREM-83?page=history ] Tom Elrod resolved JBREM-83: - Resolution: Done Updated the InvocationMarshaller so will allow for non org.jboss.Invocation payloads. Should be able to send any Serialiable payloads and responses using datatype=invocation. This is not really for the remoting release as these marshallers have been moved under the server module where they belong. > Updated Invocation marshalling to support standard payloads > --- > > Key: JBREM-83 > URL: http://jira.jboss.com/jira/browse/JBREM-83 > Project: JBoss Remoting > Type: Task > Components: marshall > Versions: 1.0.1 final > Reporter: Tom Elrod > Assignee: Tom Elrod > Priority: Critical > Fix For: 1.2.0 beta > > > Need to update InvocationMarshaller/InvocationUnMarshaller so that if payload > not org.jboss.Invocation or org.jboss.MarshalledInvocation, will just > marshall/unmarshaller using default parent behavior > (SerializableMarshaller/SerializableUnMarshaller). > Currently will throw exception otherwise. -- 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 Remoting, Unified Invokers] - Re: Problem with datatype=invocation in the socket connector
Have made the change so InvocationMarshaller/InvocationUnMarshaller will support standard (non org.jboss.Invocation) payloads. So should be able to use the datatype=invocation for any Serializable payloads (see jira issue JBREM-83). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870486#3870486 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870486 --- 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: ConcurrentModificationException in TransactionTable
sorry, garbled... > JBoss 4.0.0?with jboss-cache.jar of JBossCache1.2.1? JBoss 4.0.0 with jboss-cache.jar of JBossCache1.2.1 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870485#3870485 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870485 --- 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] - ConcurrentModificationException in TransactionTable
Hi,
I put jboss-cache.jar of JBossCache1.2.1 into JBoss4.0.0. And I tested a
web-application in the JBoss with heavy load.
environment:
Redhat Enterprise 3.0
JDK 1.4.2
JBoss 4.0.0?with jboss-cache.jar of JBossCache1.2.1?
2 node cluster
load-balanced by Apache2+mod_jk2
http session replication enabled
replication-trigger SET
replication-granularity SESSION
I got the following Exception.
2005-03-17 11:30:25,703 ERROR [org.jgroups.blocks.RpcDispatcher] failed
invoking method
| java.util.ConcurrentModificationException
| at java.util.HashMap$HashIterator.nextEntry(HashMap.java:782)
| at java.util.HashMap$EntryIterator.next(HashMap.java:824)
| at
org.jboss.cache.TransactionTable.getLocalTransaction(TransactionTable.java:71)
| at
org.jboss.cache.interceptors.ReplicationInterceptor.replicate(ReplicationInterceptor.java:187)
| at org.jboss.cache.TreeCache._replicate(TreeCache.java:2682)
| at sun.reflect.GeneratedMethodAccessor74.invoke(Unknown Source)
| at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:324)
| at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:236)
| at org.jgroups.blocks.RpcDispatcher.handle(RpcDispatcher.java:220)
| at
org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:615)
| at
org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:512)
| at
org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:326)
| at
org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUp(MessageDispatcher.java:722)
| at
org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.access$300(MessageDispatcher.java:554)
| at
org.jgroups.blocks.MessageDispatcher$1.run(MessageDispatcher.java:691)
| at java.lang.Thread.run(Thread.java:534)
I checked org.jboss.cache.TransactionTable.
tx_map is synchronized in getLocalTransaction(GlobalTransaction gtx), but
tx_map may be modified in put(Transaction tx, GlobalTransaction gtx) or
remove(Transaction tx).
I guess some synchronized blocks are needed like:
public void put(Transaction tx, GlobalTransaction gtx) {
| if(tx == null) {
| log.error("key (Transaction) is null");
| return;
| }
| synchronized(tx_map) {
| tx_map.put(tx, gtx);
| }
|}
public GlobalTransaction remove(Transaction tx) {
| if(tx == null)
| return null;
| GlobalTransaction gtx = null;
| synchronized(tx_map) {
| gtx = (GlobalTransaction)tx_map.remove(tx);
| }
| return gtx;
|}
Is this irrelevant ?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870484#3870484
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870484
---
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.886 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050316220053Lbuild.886 BUILD COMPLETE - build.886Date of build: 03/16/2005 22:00:53Time to build: 23 minutes 36 secondsLast changed: 03/16/2005 19:46:20Last log entry: - Update to Tomcat CVS build for testing. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (26)1.9modifiedremmthirdparty/apache-tomcat55/tomcat-coyote.jar- Update to Tomcat CVS build for testing.1.8modifiedremmthirdparty/apache-tomcat55/tomcat-http.jar- Update to Tomcat CVS build for testing.1.9modifiedremmthirdparty/apache-tomcat55/tomcat-util.jar- Update to Tomcat CVS build for testing.1.10modifiedremmthirdparty/apache-tomcat55/jasper-compiler.jar- Update to Tomcat CVS build for testing.1.10modifiedremmthirdparty/apache-tomcat55/jasper-runtime.jar- Update to Tomcat CVS build for testing.1.9modifiedremmthirdparty/apache-tomcat55/naming-resources.jar- Update to Tomcat CVS build for testing.1.9modifiedremmthirdparty/apache-tomcat55/servlets-cgi.renametojar- Update to Tomcat CVS build for testing.1.9modifiedremmthirdparty/apache-tomcat55/servlets-default.jar- Update to Tomcat CVS build for testing.1.9modifiedremmthirdparty/apache-tomcat55/servlets-invoker.jar- Update to Tomcat CVS build for testing.1.9modifiedremmthirdparty/apache-tomcat55/servlets-ssi.renametojar- Update to Tomcat CVS build for testing.1.9modifiedremmthirdparty/apache-tomcat55/servlets-webdav.jar- Update to Tomcat CVS build for testing.1.9modifiedremmthirdparty/apache-tomcat55/tomcat-ajp.jar- Update to Tomcat CVS build for testing.1.6modifiedremmthirdparty/apache-tomcat55/jasper-compiler-jdt.jar- Update to Tomcat CVS build for testing.1.10modifiedremmthirdparty/apache-tomcat55/README- Update to Tomcat CVS build for testing.1.9modifiedremmthirdparty/apache-tomcat55/catalina-manager.jar- Update to Tomcat CVS build for testing.1.9modifiedremmthirdparty/apache-tomcat55/catalina-optional.jar- Update to Tomcat CVS build for testing.1.10modifiedremmthirdparty/apache-tomcat55/catalina.jar- Update to Tomcat CVS build for testing.1.6modifiedtelrodremoting/tests/src/org/jboss/remoting/transport/mock/MockServerInvoker.javaJBREM-82 - Changed so the ObjectName generated from the server invoker is unique to the locator uri, so if new server invoker is created by the InvokerRegistry, will register it as a new MBean within the MBeanServer. Otherwise, will detect that it has already be registered and skip registration. Also updated api for getting the registered handlers so can see which ones are registered with a Connector's Server Invoker. This change includes returning old handler when new one is added with the same subsystem value.1.1addedtelrodremoting/tests/src/org/jboss/remoting/deploy/DualDeploymentTestCase.javaJBREM-82 - Changed so the ObjectName generated from the server invoker is unique to the locator uri, so if new server invoker is created by the InvokerRegistry, will register it as a new MBean within the MBeanServer. Otherwise, will detect that it has already be registered and skip registration. Also updated api for getting the registered handlers so can see which ones are registered with a Connector's Server Invoker. This change includes returning old handler when new one is added with the same subsystem value.1.20modifiedtelrodremoting/src/main/org/jboss/remoting/InvokerRegistry.javaJBREM-82 - Changed so the ObjectName generated from the server invoker is unique to the locator uri, so if new server invoker is created by the InvokerRegistry, will register it as a new MBean within the MBeanServer. Otherwise, will detect that it has already be registered and skip registration. Also updated api for getting the registered handlers so can see which ones are registered with a Connector's Server Invoker. This change includes returning old handler when new one is added with the same subsystem value.1.24modifiedtelrodremoting/src/main/org/jboss/remoting/ServerInvoker.javaJBREM-82 - Changed so the ObjectName generated from the server invoker is unique to the locator uri, so if new server invoker is created by the InvokerRegistry, will register it as a new MBean within the MBeanServer. Otherwise, will detect that it has already be registered and skip registration. Also updated api for getting the registered handlers so can see which ones are registered with a Connector's Server Invoker. This change includes returning old handler when new one is added with the same subsystem value.1.26modifiedtelrodremoting/src/main/org/jboss/remoting/transport/Connector.javaJBREM-82 - Changed so the ObjectName generated from the server invoker is unique to the locator uri, so if new server invoker is created by the InvokerRegistry, will register it as a new MBean within the MBeanServer. Otherwise, will detect that it has already be registere
[JBoss-dev] [JBoss JIRA] Created: (JBMAIL-41) Basic IMAP support
Basic IMAP support -- Key: JBMAIL-41 URL: http://jira.jboss.com/jira/browse/JBMAIL-41 Project: JBoss Mail Type: Feature Request Versions: 1.0-M4 Reporter: Andrew Oliver Assigned to: Andrew Oliver Priority: Blocker Fix For: 1.0-M4 Basic IMAP protocol support. Create subtasks from here. This will most likely cause substantial changes in security and mailboxes. -- 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: (JBMAIL-40) Support Virtual Host/Domains
Support Virtual Host/Domains Key: JBMAIL-40 URL: http://jira.jboss.com/jira/browse/JBMAIL-40 Project: JBoss Mail Type: Feature Request Components: SMTP, POP, Security Reporter: Andrew Oliver Assigned to: Andrew Oliver Fix For: 1.0-M4 Large mail hosting systems may allow the same username on multiple hosts. Meaning if I connect to: mail.nowhere.com with user "andy" and password "foobar" then that would be treated as a completely different account (POTENTIALLY) than if I connect to mail.somewhere.com with user "andy" and password "barfoo" (or this may be even the same password). This should use the domain list mbeans and will require some changes in the user repository contracts. -- 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.439 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20050316212115Lbuild.439 BUILD COMPLETE - build.439Date of build: 03/16/2005 21:21:15Time to build: 22 minutes 21 secondsLast changed: 03/16/2005 19:41:41Last log entry: - Update to Tomcat CVS build for testing. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (17)1.1.2.4modifiedremmthirdparty/apache-tomcat55/servlets-invoker.jar- Update to Tomcat CVS build for testing.1.1.2.4modifiedremmthirdparty/apache-tomcat55/servlets-ssi.renametojar- Update to Tomcat CVS build for testing.1.1.2.4modifiedremmthirdparty/apache-tomcat55/servlets-webdav.jar- Update to Tomcat CVS build for testing.1.1.2.4modifiedremmthirdparty/apache-tomcat55/tomcat-ajp.jar- Update to Tomcat CVS build for testing.1.1.2.4modifiedremmthirdparty/apache-tomcat55/tomcat-coyote.jar- Update to Tomcat CVS build for testing.1.5.2.4modifiedremmthirdparty/apache-tomcat55/tomcat-http.jar- Update to Tomcat CVS build for testing.1.1.2.4modifiedremmthirdparty/apache-tomcat55/tomcat-util.jar- Update to Tomcat CVS build for testing.1.1.2.4modifiedremmthirdparty/apache-tomcat55/servlets-default.jar- Update to Tomcat CVS build for testing.1.1.2.4modifiedremmthirdparty/apache-tomcat55/jasper-compiler.jar- Update to Tomcat CVS build for testing.1.1.2.4modifiedremmthirdparty/apache-tomcat55/jasper-runtime.jar- Update to Tomcat CVS build for testing.1.1.2.4modifiedremmthirdparty/apache-tomcat55/naming-resources.jar- Update to Tomcat CVS build for testing.1.1.2.4modifiedremmthirdparty/apache-tomcat55/servlets-cgi.renametojar- Update to Tomcat CVS build for testing.1.1.2.4modifiedremmthirdparty/apache-tomcat55/catalina-optional.jar- Update to Tomcat CVS build for testing.1.1.2.4modifiedremmthirdparty/apache-tomcat55/catalina.jar- Update to Tomcat CVS build for testing.1.1.2.3modifiedremmthirdparty/apache-tomcat55/jasper-compiler-jdt.jar- Update to Tomcat CVS build for testing.1.1.2.4modifiedremmthirdparty/apache-tomcat55/catalina-manager.jar- Update to Tomcat CVS build for testing.1.2.2.4modifiedremmthirdparty/apache-tomcat55/README- Update to Tomcat CVS build for testing.
[JBoss-dev] [Design of Mail Services] - HEADS UP: Milestone 3 pre1 in 1.5 weeks.
Next monday after this one (or possible the weekend before), I plan to put out a m3-pre1 release. This will be a bit different than previous pre releases because we still haven't realized the bulk of M3 features and I don't intend to branch yet. We are however close to two of the most important. A release is a way to checkpoint and make sure the loose ends get tied up and as things get more complex that becomes more important. What I need from you guys is to get your stuff in shape and make sure it is configurable from the dist target. I plan to round things out but I may miss pieces especially what I don't know is there. Go through jira and check/update the status of thing you have worked on. One piece I want to start knocking on is JAAS. There are a lot more eyes on us and a lot more opportunity now (in either direction) so let's make a good show of it. -Andy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870479#3870479 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870479 --- 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: Default ports and use of SMTP MSA?
So feature complete in SMTP is a loaded term. Does that mean there won't be features that affect SMTP in the future? No (Never will reach that level of "feature complete"). I mean that we'll be able to run feasibly in a secure multi-user environment. There are presently issues that would allow authenticated users to forge other authenticated users. Not a biggy, most mail servers let you do this anyhow and the logging can still cause said person to be fired. However these will be fixed in M3. There will of course be RFCs and other things that aren't supported (S/MIME for instance). The letterprobably not in M3. That RFC seems to talk about partial incremental mail transfers. Thats a ball of wax I don't even want to get in to yet. The spirit, It will be possible to have this configuration in M3. We'll support the right set of features to allow you to set up a TLS/SSL on 587 and SMTP on 25. The one not allowing relaying without authentication and the other only allowing sending to local users. Of course I regard the multi-port thing as a bit silly. Require STARTTLS and authentication for relaying, no port 587 required. (I do not believe that some ports are inherently more secure than others). however you should be able to do that in the final M3. I think you're right. It should be 995. I think it was set to 443 because no one new what port it should be. I'll fix it. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870478#3870478 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870478 --- 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] - Default ports and use of SMTP MSA? (Repost)
I am new to JBoss and hence to the Mail project as well. I have run through the process of downloading the source, building, etc... and have a couple questions/suggestions: - Based on the milestones, M3 will have SMTP feature complete... are there any plans to allow for RFC 2476 implementation? i.e. running SMTP on 2 ports, 25 and 587. I think typically port 25 would then be setup as no relay allowed, and 587 would be a TLS/SSL only server that would allow relaying. - Also, I noticed POP3/SSL is setup to default to port 443... I believe the standard port for this is 995. Perhaps the installer simply has 443 because of a personal configuration on your dev boxes and there are plans to make it 995 later. Just thought I'd point it out just in case. Pablo. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870460#3870460 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870460 --- 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: Locks
Isolation level will take care of the node locking for you. That's the whole idea actually. -Ben View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870476#3870476 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870476 --- 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
The module name is jboss-test, I believe. But if you want to run the testsuite, you can check out the whole jboss-head using anonymous cvs. We are in the process getting the tutorial updated. So thanks for the suggestion. However, your bind_addr problem works for most of the machines, actually (it works for mine). Then the jboss-aop.xml in release 1.2.1 is the right one. So I am not sure which one you are referring to exactly? -Ben View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870475#3870475 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870475 --- 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: Some JBOSSCache questions...
To answer some of your questions: 1. Yes. You will need to specifically do a put whenever your object has been modified. 2. Replication takes place for the whole myVector in your case. (This is where TreeCacheAop comes where you can do fine-grain replication.) 3. SFSN will manage the state change for you vs. you will need to manage yourself (unless again you are using aop for fine grain replication). 4. We have some old numbers on 2 nodes replication. But it's outdated so we will be working with new ones now. -Ben View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870473#3870473 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870473 --- 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.885 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050316185626Lbuild.885 BUILD COMPLETE - build.885Date of build: 03/16/2005 18:56:26Time to build: 39 minutes 14 secondsLast changed: 03/16/2005 18:04:14Last log entry: Remove the commented out old implementation. Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (27)1.14modifiedejortkernel/src/main/org/jboss/kernel/plugins/deployment/xml/XMLKernelDeployer.javaRemove the commented out old implementation.1.1addedkabkhanejb3x/src/main/javax/persistence/EntityNotFoundException.javaMore ejb3 exceptions1.3modifiedkabkhanejb3x/src/main/javax/persistence/EntityManager.javaMore ejb3 exceptions1.2deletedkabkhanejb3x/src/main/javax/persistence/ObjectNotFoundException.javaMore ejb3 exceptions1.2modifiedkabkhanejb3/src/test/org/jboss/ejb3/test/entityexception/unit/EntityExceptionTestCase.javaMore ejb3 exceptions1.2modifiedkabkhanejb3/src/test/org/jboss/ejb3/test/entityexception/ExceptionTest.javaMore ejb3 exceptions1.2modifiedkabkhanejb3/src/test/org/jboss/ejb3/test/entityexception/ExceptionTestBean.javaMore ejb3 exceptions1.1addedkabkhanejb3/src/test/org/jboss/ejb3/test/entityexception/NonEntity.javaMore ejb3 exceptions1.2modifiedkabkhanejb3/src/test/org/jboss/ejb3/test/entityexception/Person.javaMore ejb3 exceptions1.7modifiedkabkhanejb3/src/main/org/jboss/ejb3/entity/EntityManagerImpl.javaMore ejb3 exceptions1.3modifiedkabkhanejb3/src/main/org/jboss/ejb3/entity/HibernateSessionFactory.javaMore ejb3 exceptions1.4modifiedkabkhanejb3/src/main/org/jboss/ejb3/entity/QueryImpl.javaMore ejb3 exceptions1.13modifiedejortkernel/src/main/org/jboss/kernel/plugins/deployment/xml/XMLKernelDeployer.javaCutover to the new MetadataDrivenObjectModelFactory1.6modifiedejortkernel/src/tests/org/jboss/test/kernel/xml/test/XMLTestCase.javaCutover to the new MetadataDrivenObjectModelFactory1.5modifiedejortkernel/src/tests/org/jboss/test/kernel/xml/support/SimpleBeanImpl.javaCutover to the new MetadataDrivenObjectModelFactory1.3modifiedejortkernel/src/resources/xml-test/org/jboss/test/kernel/xml/test/testAttributeDependency.xmlCutover to the new MetadataDrivenObjectModelFactory1.3modifiedejortkernel/src/resources/xml-test/org/jboss/test/kernel/xml/test/testAttributeDependencyDependentState.xmlCutover to the new MetadataDrivenObjectModelFactory1.3modifiedejortkernel/src/resources/xml-test/org/jboss/test/kernel/xml/test/testConfigure.xmlCutover to the new MetadataDrivenObjectModelFactory1.2modifiedejortkernel/src/resources/xml-test/org/jboss/test/kernel/xml/test/testConstructorDependency.xmlCutover to the new MetadataDrivenObjectModelFactory1.2modifiedejortkernel/src/resources/xml-test/org/jboss/test/kernel/xml/test/testDemandSupply.xmlCutover to the new MetadataDrivenObjectModelFactory1.2modifiedejortkernel/src/resources/xml-test/org/jboss/test/kernel/xml/test/testDemandSupplyWhenRequired.xmlCutover to the new MetadataDrivenObjectModelFactory1.2modifiedejortkernel/src/resources/xml-test/org/jboss/test/kernel/xml/test/testFactoryDependency.xmlCutover to the new MetadataDrivenObjectModelFactory1.3modifiedejortkernel/src/resources/xml-test/org/jboss/test/kernel/xml/test/testSimpleCollection.xmlCutover to the new MetadataDrivenObjectModelFactory1.2modifiedejortkernel/src/resources/xml-test/org/jboss/test/kernel/xml/test/testStaticFactoryDependency.xmlCutover to the new MetadataDrivenObjectModelFactory1.2modifiedorbcache/docs/faq/en/master.xmlfix cache docs problems, except links1.1addedorbcache/docs/TreeCache/en/images/TreeNodeExample.giffix cache docs problems, except links1.1addedorbcache/docs/TreeCache/en/images/TreeCacheArchitecture.giffix cache docs problems, except links
[JBoss-dev] [JBossCache] - Some JBOSSCache questions...
Ok, so now that I have successfully implemented a plain JBossCache within JBoss 3.2.6, I have some basic, performance related questions. 1. In the plain JBossCache, it looks like I need to do a put everytime after an object is changed. Is that right? For example, if I have a vector assigned as value to a key, then in order to add an element in the vector, I need to do a put(fqn, key, myVector) after every change. Am I correct? 2. If #1 is correct, then does the replication take place on the entire object every time, or does is somehow only replicate the incrementals? 3. I am mostly using JBossCache to store the state information of my class. Right now, the class is a POJO. What is better performance wise - convert the POJO into a stateful session bean and use SFSN in state memory replication, or use TreeCache? 4. Are there any performance timings/statistics available for put and get using plain TreeCache? 5. What is the performance impact of doing a get on the TreeCache vs doing a get on a local hashmap? Is it worthwhile to invalidate the cache and only get values from cache is something has changed? I guess thats a lot of questions. All answers are deeply appreciated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870472#3870472 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870472 --- 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-1512) misspelling of UserPrinicpalRequest and UserPrinicipalServletRequest
[ http://jira.jboss.com/jira/browse/JBAS-1512?page=history ] Scott M Stark closed JBAS-1512: --- Resolution: Done Fix Version: JBossAS-4.0.2 Final These classes are gone in the 4.0.2 release. Spelng muns noting to ma in gnrl. > misspelling of UserPrinicpalRequest and UserPrinicipalServletRequest > > > Key: JBAS-1512 > URL: http://jira.jboss.com/jira/browse/JBAS-1512 > Project: JBoss Application Server > Type: Bug > Components: Security > Versions: JBossAS-4.0.1 Final > Environment: all environments > Reporter: nwc > Priority: Trivial > Fix For: JBossAS-4.0.2 Final > > Original Estimate: 1 minute > Remaining: 1 minute > > This is not a bug, just an annoying feature of the class > org.jboss.web.tomcat.security.CustomPrincipalValve -- 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] Assigned: (JBAS-1555) HTTP Status 403 on using org.jboss.web.tomcat.security.JaccAuthorizationRealm
[ http://jira.jboss.com/jira/browse/JBAS-1555?page=history ] Scott M Stark reassigned JBAS-1555: --- Assign To: Scott M Stark > HTTP Status 403 on using org.jboss.web.tomcat.security.JaccAuthorizationRealm > -- > > Key: JBAS-1555 > URL: http://jira.jboss.com/jira/browse/JBAS-1555 > Project: JBoss Application Server > Type: Bug > Components: Security > Versions: JBossAS-4.0.1 SP1 > Environment: JBoss 4.0.1 sp1, tomcat 5.0.28 > Reporter: Roland R?z > Assignee: Scott M Stark > > > Hello, > I try to run JBoss Duke Bank application on JBoss 4.0.1 sp1 and it works fine > until I'm using org.jboss.web.tomcat.security.JBossSecurityMgrRealm in the > server.xml configuration. > ... > certificatePrincipal="org.jboss.security.auth.certs.SubjectDNMapping"/> > ... > As soon I replace this realm by > org.jboss.web.tomcat.security.JaccAuthorizationRealm: > > certificatePrincipal="org.jboss.security.auth.certs.SubjectDNMapping"/> > the logon is still successful but the every second call to the servlet is > responded with "HTTP Status 403 - Access to the requested resource has been > denied". > On debugging I noticed that the Subject in the SecurityAssociation, required > by JaccAuthorizationRealm is null, therefore the permission check fails. > Kind regards -- 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-1590) Container does not call commit or refresh for the JACC provider
[ http://jira.jboss.com/jira/browse/JBAS-1590?page=history ] Scott M Stark updated JBAS-1590: Assign To: Scott M Stark Fix Version: JBossAS-4.0.2 Final JBossAS-5.0 Alpha > 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 > Assignee: Scott M Stark > Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2 Final > > Original Estimate: 2 days > Remaining: 2 days > > 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 JIRA] Updated: (JBAS-1592) JaccAuthorizationRealm always returns false on subsequent requests
[ http://jira.jboss.com/jira/browse/JBAS-1592?page=history ]
Scott M Stark updated JBAS-1592:
Assign To: Scott M Stark
Component: Web (Tomcat) service
Fix Version: JBossAS-4.0.2 Final
JBossAS-5.0 Alpha
> JaccAuthorizationRealm always returns false on subsequent requests
> --
>
> Key: JBAS-1592
> URL: http://jira.jboss.com/jira/browse/JBAS-1592
> Project: JBoss Application Server
> Type: Bug
> Components: Deployment Service, Security, Web (Tomcat) service
> Versions: JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1
> Environment: Windows XP SP2
> JDK 1.5.0
> Reporter: Stephen Kinser
> Assignee: Scott M Stark
> Priority: Critical
> Fix For: JBossAS-4.0.2 Final, JBossAS-5.0 Alpha
>
> Original Estimate: 1 day
> Remaining: 1 day
>
> After the initial login, the JaccAuthorizationRealm always returns false
> because the PolicyContext handler for the Subject is not yet initialized when
> the realm is called. To figure out the root of the problem, an understanding
> of the calling order is necessary.
> The standard pipeline is composed of the following valves, in this order:
> - JaccContextValve
> - FormAuthenticator (the authenticator valve in my case)
> - SecurityAssociationValve
> - CustomPrincipalValve
> - StandardContextValve
> The SecurityAssociationValve is added to the pipeline after the authenticator
> valve due to the ordering of the code in the
> TomcatDeployer.performDeployInternal method. The SecurityAssociationValve is
> added after the init call to the server. The init call results in the
> authenticator valve being added to the pipeline.
> When a request is received by an authenticated user, the authenticator valve
> obtains control before the SecurityAssociationValve. The authenticator valve
> calls the JaccAuthorizationRealm for the authorization check. Part of the
> check is as follows:
> Subject caller = null;
> try
> {
>caller = (Subject) PolicyContext.getContext(SUBJECT_CONTEXT_KEY);
> }
> catch (PolicyContextException e)
> {
>if( trace )
> log.trace("Failed to get subject from PolicyContext", e);
> }
> if( caller == null ) //*** is always true!
> {
>if( trace )
> log.trace("Denied, no active subject found in PolicyContext");
>return false;
> }
> The realm expects to have an initialized caller (Subject), but the caller is
> always null because it wasn't initialized yet since the
> SecurityAssociationValve that initializes the caller (Subject) doesn't
> receive control until after the authenticator valve is finished.
--
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-1593) Bad CRC checksum on files in downloaded archive
[ http://jira.jboss.com/jira/browse/JBAS-1593?page=history ] Scott M Stark closed JBAS-1593: --- Resolution: Won't Fix 329678 is the correct uncompressed size: [EMAIL PROTECTED] console-mgr.sar]$ ls -l total 1388 -rw-rw-r--1 starksm starksm141239 Mar 14 09:17 console-mgr-classes.jar -rw-rw-r--1 starksm starksm329678 Mar 14 09:17 jcommon.jar and is what I see from the jboss-4.0.2RC1.zip I downloaded. I have found winzip to be broken for jar files in the past. Just use the jdk jar tool or zip from cygwin as these always work. I have seen a bug report about Ant not creating completely valid archives in the past, but this was supposed to be fixed in Ant 1.5.x and we use 1.6.2. > Bad CRC checksum on files in downloaded archive > --- > > Key: JBAS-1593 > URL: http://jira.jboss.com/jira/browse/JBAS-1593 > Project: JBoss Application Server > Type: Bug > Versions: JBossAS-4.0.2RC1 > Environment: WinZip > Reporter: Jimi Thompson > Priority: Minor > > > This is pretty minor, but I've downloaded the archive from 2 different > mirrors and I'm getting the same error message on the same files from WinZip. > It seems to think that a couple of the files in the archive should be a > slightly different size. I'm attaching the pertinent snippets of the WinZip > log file. > HTH, > Jimi > Extracting axis-ws4ee.jar > bad CRC 9fa08afd (should be 8af0284d) > Warning: the size of the extracted file (1286558) does not match the > uncompressed size (1286652) recorded in the zip file > Extracting jcommon.jar > bad CRC 77e5b8c2 (should be 743169a3) > Warning: the size of the extracted file (329611) does not match the > uncompressed size (329678) recorded in the zip file > Extracting jfreechart.jar -- 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: (JBAS-1206) UTF8 encoded http URL is not recognized
[ http://jira.jboss.com/jira/browse/JBAS-1206?page=history ] Remy Maucherat resolved JBAS-1206: -- Resolution: Rejected As with standalone Tomcat, please refer to the URL encoding related attributes of the connector in Tomcat's documentation. > UTF8 encoded http URL is not recognized > --- > > Key: JBAS-1206 > URL: http://jira.jboss.com/jira/browse/JBAS-1206 > Project: JBoss Application Server > Type: Bug > Components: Web (Tomcat) service > Versions: JBossAS-4.0.0 Final > Reporter: SourceForge User > Assignee: Remy Maucherat > > > SourceForge Submitter: tim_tye . > This works with 3.2. > I have a model where the html page names include UTF8 > encoded characters. 3.2 version found the names and > returned the page. > 4.0 gives 404 error and returns the page name as invalid. -- 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: (JBAS-1516) Tomcat5: StandardContext getConfigBase tries to create a directory
[ http://jira.jboss.com/jira/browse/JBAS-1516?page=history ]
Remy Maucherat resolved JBAS-1516:
--
Resolution: Done
> Tomcat5: StandardContext getConfigBase tries to create a directory
> --
>
> Key: JBAS-1516
> URL: http://jira.jboss.com/jira/browse/JBAS-1516
> Project: JBoss Application Server
> Type: Bug
> Components: Web (Tomcat) service
> Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final
> Environment: JBoss 4.0.1sp1, Solaris8
> Reporter: Roland R?z
> Assignee: Remy Maucherat
> Priority: Critical
> Fix For: JBossAS-4.0.2 Final, JBossAS-5.0 Alpha, JBossAS-3.2.8 Final
>
> Original Estimate: 10 minutes
> Remaining: 10 minutes
>
> Hello,
> Just to explain you the circumstances why this request has arised.
> I try to secure JBoss with a java security policy. The policy should prevent
> somebody from writing in the JBoss installation directory.
> For this reason I set a File permission that allows only reading on the
> JBoss installation directory.
> It looks like this
> grant {
> permission java.io.FilePermission "${jboss.home.dir}/-", "read";
> ...
> };
> Now when I start JBoss and deploy a War file I receive the following
> AccessPermissionException
> Caused by: java.security.AccessControlException: access denied
> (java.io.FilePermission
> /opt/jboss/4.0.1/server/myserver/conf/jboss.web/localhost write)
> at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:269)
> at java.security.AccessController.checkPermission(AccessController.java:401)
> at java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
> at java.lang.SecurityManager.checkWrite(SecurityManager.java:954)
> at java.io.File.mkdir(File.java:1097)
> at java.io.File.mkdirs(File.java:1122)
> at
> org.apache.catalina.core.StandardContext.getConfigBase(StandardContext.java:4858)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4071)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
> at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:121)
> at
> org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:143)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:805)
> at org.a
> pache.catalina.core.StandardHost.addChild(StandardHost.java:595)
> 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.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
> ... 152 more
> The method that creates the Exception looks like this
> private File org.apache.catalina.core.StandardContext#getConfigBase()
> {
> File configBase = new File(System.getProperty("catalina.base"),
> "conf");
> if(!configBase.exists())
> return null;
> Container container = this;
> Container host = null;
> Container engine = null;
> for(; container != null; container = container.getParent())
> {
> if(container instanceof Host)
> host = container;
> if(container instanceof Engine)
> engine = container;
> }
> if(engine != null)
> configBase = new File(configBase, engine.getName());
> if(host != null)
> configBase = new File(configBase, host.getName());
> configBase.mkdirs(); // here it crashes
> return configBase;
> }
> JBoss sets the saveConfig Flag of the StandardContext to false.
> (see TomcatDeployer#performDeployInternal)
> configBase.mkdirs() should only be invoked if the saveConfig Flag is set to
> true.
> Regards
--
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 Build System] - Re: Autonomous Project
What about the access rights? If somebody has write access to it, it has access to the whole CVS root. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870470#3870470 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870470 --- 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: (JBREM-84) Duplicate Connector shutdown using same server invoker
Duplicate Connector shutdown using same server invoker -- Key: JBREM-84 URL: http://jira.jboss.com/jira/browse/JBREM-84 Project: JBoss Remoting Type: Bug Components: general Versions: 1.0.1 final Reporter: Tom Elrod Assigned to: Tom Elrod Fix For: 1.2.0 beta if shutdown a connector that is using the same server invoker as another connector, will be shutting down the server invoker underneath the other connector (without warning or notification). -- 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 the new POJO MicroContainer] - Re: Kernel XML format
As discussed on other threads, I also want to have "use case" configurations that simplify the more long winded bean descriptions. This will probably require some pluggable xml parsing using namespaces? e.g. instead of | | | someURL | | | you could have the equivalent: | | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870469#3870469 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870469 --- 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 the new POJO MicroContainer] - Re: Kernel XML format
Known features still not complete (or at least properly tested which is the same thing in my book :-) are: 1) Specifying types on values, e.g. the elements of a collection http://jira.jboss.com/jira/browse/JBMICROCONT-29 2) Beans as values http://jira.jboss.com/jira/browse/JBMICROCONT-28 3) Annotation overrides http://jira.jboss.com/jira/browse/JBMICROCONT-18 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870468#3870468 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870468 --- 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 the new POJO MicroContainer] - Kernel XML format
Although it relatively simple to write your own xml->kernel metadata deployer I'm interested in any suggestions to make the xml less verbose and more intuitive. This xml format will be used by the BeanDeployer the basic POJO -> jboss deployer similar to SARDeployer that does MBean -> jboss deployer You can find examples in jboss-head kernel/src/resources/xml-test/org/jboss/test/kernel/xml/test Speak now before we finalize the base format. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870467#3870467 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870467 --- 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: (JBREM-82) Bad warning in Connector.
[ http://jira.jboss.com/jira/browse/JBREM-82?page=history ]
Tom Elrod closed JBREM-82:
---
Resolution: Done
Fix Version: 1.2.0 beta
Have updated the ObjectName generated for the server invoker to be unique to
the locator uri so that if a new server invoker is created by the
InvokerRegistry, then that invoker will be registered with the MBeanServer. If
InvokerRegistry does not create a new server invoker, but returns an existing
one because the locator uri was the same, then it will not re-register that
invoker with the MBeanServer.
> Bad warning in Connector.
> -
>
> Key: JBREM-82
> URL: http://jira.jboss.com/jira/browse/JBREM-82
> Project: JBoss Remoting
> Type: Bug
> Components: transport
> Versions: 1.2.0 beta
> Environment: In Jboss Head (CVS)
> Reporter: rimmeraj
> Assignee: Tom Elrod
> Priority: Minor
> Fix For: 1.2.0 beta
>
>
> JBoss head:
> remoting/src/main/org/jboss/remoting/transport/Connector.java , start method
> after you create the server invoker you try to register it with the mbean
> server. If it fails you register a warning. When you are using the ejb3
> deployers it registers its own socket Connector. It is quite legal to have
> the standard Connector in conf/jboss-service.xml registers a socket
> protocol. The EJB3 deployer registers a socket listener on a different port.
> This triggers an annoying warning that in my option is more of a programming
> error that a valid warning.
>
> Warning.
> Error registering invoker [EMAIL PROTECTED] with MBeanServer.
> javax.management.InstanceAlreadyExistsException:
> jboss.remoting:service=invoker,transport=socket already registered.
> Suggested Fix.
> 1. org/jboss/remoting/transport/InvokerRegistry.java, createServerInvoker
> should log a warning if the InvokerLocator is already found.
> 2. Connector.java, start should check to see if the object name is not
> registered before trying. Something like
> ObjectName name=new ObjectName(invoker.getMBeanObjectName());
> try
> {
> server.getInstance(name);
> }
> catch(InstanceNotFoundException e)
> {
>server.registerMBean(invoker, name);
>invoker.setMBeanServer(server);
> }
>
--
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 Mail Services] - Default ports and use of SMTP MSA?
I am new to JBoss and hence to the Mail project as well. I have run through the process of downloading the source, building, etc... and have a couple questions/suggestions: - Based on the milestones, M3 will have SMTP feature complete... are there any plans to allow for RFC 2476 implementation? i.e. running SMTP on 2 ports, 25 and 587. I think typically port 25 would then be setup as no relay allowed, and 587 would be a TLS/SSL only server that would allow relaying. - Also, I noticed POP3/SSL is setup to default to port 443... I believe the standard port for this is 995. Perhaps the installer simply has 443 because of a personal configuration on your dev boxes and there are plans to make it 995 later. Just thought I'd point it out just in case. Pablo. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870460#3870460 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870460 --- 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 JBossXB] - Re: Reusing xml element definitions/bindings
Just to make it more concrete, I'm looking to parse something like:
|
|
| SomeValue
|
|
|
|
|
|
| into
|
| PropertyMetaData pmd = new PropertyMetaData();
|
| CollectionMetaData cmd = new CollectionMetaData();
| SomeValue
| StringValueMetaData smd = new StringValueMetaData();
| smd.setValue("SomeValue");
| cmd.add(smd);
|
| ListValueMetaData lmd = new ListValueMetaData();
|
| DependencyValueMetaData dvmd = new DependencyValueMetaData();
| dvmd.setValue("xxx");
| lmd.add(dvmd);
| cmd.add(lmd);
| pmd.setValue(cmd);
|
but property could easily be replaced with parameter/ParameterMetaData
that needs to do the exactly same thing on its setValue().
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870459#3870459
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870459
---
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: JBoss Portal 2.0 Beta 1
BTW, as there seems to be some confusion I know I can modify the local properties to make it work with other databases, however I would then need the database scripts to set up these other databases. You provide only the MySQL script. I at one time created a HSQL script that would do just this, but you have not seen fit to provide it. Is it easy to make, fairly, but that's not really the point. The work was done for you and you threw it away for some unknown reason. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870458#3870458 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870458 --- 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 JBossXB] - Reusing xml element definitions/bindings
Is there a way in the MetadataDrivenObjectModelFactory to reuse element bindings? e.g. In dtd terms I have something like: | | | | | | | | etc. | But value and value-type are not real artificats in my javabean model they represent the same property with the same semantics on different javabeans. I can't see a way to define this type of reusable element binding that can be mapped onto multiple element bindings? I couldn't see how to do this? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870457#3870457 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870457 --- 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: JBoss Portal 2.0 Beta 1
volunteer? I already wrote you a HSQL script that you didn't include. Shall I volunteer to write more code that will be discarded? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870455#3870455 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870455 --- 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 activities execution
[ http://jira.jboss.com/jira/browse/JBPM-27?page=history ] Juan Cantu updated JBPM-27: --- Summary: structured activities execution (was: structured blocks execution) > structured activities execution > --- > > Key: JBPM-27 > URL: http://jira.jboss.com/jira/browse/JBPM-27 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Versions: jBPM 3.0 BPEL extension alpha 1 > Reporter: Juan Cantu > Assignee: Juan Cantu > Fix For: jBPM 3.0 BPEL extension alpha 1 > > 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] [Design of JBossXB] - Re: TypeBinding replacement?
Although, in this case it is not a true Enum (singleton instances) so I could probably work around the problem by modifying the class to have a setter? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870453#3870453 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870453 --- 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 JBossXB] - TypeBinding replacement?
I've switched over the kernel xml deployer to use the
MetadataDrivenObjectModelFactory,
but I don't see a replacement for the TypeBinding processing?
I use this previously to initialize an Enum from a String
|
|/**
| * A KernelControllerState converter
| */
|protected static class StateConverter implements TypeBinding
|{
| /** We only need one instance */
| public static final StateConverter instance = new StateConverter();
|
| public String marshal(Object value)
| {
| throw new NotImplementedException("NYI");
| }
|
| public Object unmarshal(String value)
| {
| return new KernelControllerState(value);
| }
|}
| [/code[
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870450#3870450
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870450
---
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-80) Event Handling
[ http://jira.jboss.com/jira/browse/JBPM-80?page=history ] Juan Cantu updated JBPM-80: --- Description: Environment: Version: jBPM 3.0 BPEL extension alpha 2 Fix Version: jBPM 3.0 BPEL extension alpha 2 > Event Handling > -- > > Key: JBPM-80 > URL: http://jira.jboss.com/jira/browse/JBPM-80 > Project: JBoss jBPM > Type: Sub-task > Versions: jBPM 3.0 BPEL extension alpha 2 > Reporter: Juan Cantu > Fix For: jBPM 3.0 BPEL extension alpha 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: (JBPM-79) Compensation Handling
[ http://jira.jboss.com/jira/browse/JBPM-79?page=history ] Juan Cantu updated JBPM-79: --- Fix Version: jBPM 3.0 BPEL extension alpha 2 > Compensation Handling > - > > Key: JBPM-79 > URL: http://jira.jboss.com/jira/browse/JBPM-79 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Versions: jBPM 3.0 BPEL extension alpha 2 > Reporter: Juan Cantu > Assignee: Juan Cantu > Fix For: jBPM 3.0 BPEL extension alpha 2 > > Original Estimate: 3 days > Remaining: 3 days > > -Implement the state transitions for scope instances when compensate / > compensated signals are received > -support implicit compensation -- 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-78) Fault and Termination Handling
[ http://jira.jboss.com/jira/browse/JBPM-78?page=history ] Juan Cantu updated JBPM-78: --- Fix Version: jBPM 3.0 BPEL extension alpha 2 > Fault and Termination Handling > -- > > Key: JBPM-78 > URL: http://jira.jboss.com/jira/browse/JBPM-78 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Versions: jBPM 3.0 BPEL extension alpha 2 > Reporter: Juan Cantu > Assignee: Juan Cantu > Fix For: jBPM 3.0 BPEL extension alpha 2 > > Original Estimate: 2 days > Remaining: 2 days > > -Implement the state transitions for scope instances when cancel or faulted > signals are received > -Provide the fault catching logic -- 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 ] Juan Cantu updated JBPM-77: --- Version: jBPM 3.0 BPEL extension alpha 1 Fix Version: jBPM 3.0 BPEL extension 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 > Versions: jBPM 3.0 BPEL extension alpha 1 > Reporter: Juan Cantu > Assignee: Juan Cantu > Fix For: jBPM 3.0 BPEL extension alpha 1 > > 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 JIRA] Updated: (JBPM-74) transformation from bpel 1.1 to 2.0
[ http://jira.jboss.com/jira/browse/JBPM-74?page=history ] Juan Cantu updated JBPM-74: --- Version: jBPM 3.0 BPEL extension alpha 1 Fix Version: jBPM 3.0 BPEL extension 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 > Versions: jBPM 3.0 BPEL extension alpha 1 > Environment: jaxp 1.1 > Reporter: Juan Cantu > Assignee: Juan Cantu > Fix For: jBPM 3.0 BPEL extension alpha 1 > > 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-65) bpel configuration files parsing
[ http://jira.jboss.com/jira/browse/JBPM-65?page=history ] Juan Cantu updated JBPM-65: --- Version: jBPM 3.0 BPEL extension alpha 1 Fix Version: jBPM 3.0 BPEL extension 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 > Versions: jBPM 3.0 BPEL extension alpha 1 > Environment: jaxp 1.1 > Reporter: Juan Cantu > Assignee: Juan Cantu > Fix For: jBPM 3.0 BPEL extension alpha 1 > > 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-63) Refactor BpelActivity class hierarchy
[ http://jira.jboss.com/jira/browse/JBPM-63?page=history ] Juan Cantu updated JBPM-63: --- Version: jBPM 3.0 BPEL extension alpha 1 Fix Version: jBPM 3.0 BPEL extension 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 > Versions: jBPM 3.0 BPEL extension alpha 1 > Reporter: Juan Cantu > Assignee: Juan Cantu > Fix For: jBPM 3.0 BPEL extension alpha 1 > > 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-62) Implement link semantics with jbpm Milestones
[ http://jira.jboss.com/jira/browse/JBPM-62?page=history ] Juan Cantu updated JBPM-62: --- Version: jBPM 3.0 BPEL extension alpha 1 Fix Version: jBPM 3.0 BPEL extension 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 > Versions: jBPM 3.0 BPEL extension alpha 1 > Reporter: Juan Cantu > Assignee: Juan Cantu > Fix For: jBPM 3.0 BPEL extension alpha 1 > > 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-28) Link Semantics (12.5.1) and Death Path elimination (12.5.2)
[ http://jira.jboss.com/jira/browse/JBPM-28?page=history ] Juan Cantu updated JBPM-28: --- Version: jBPM 3.0 BPEL extension alpha 1 Fix Version: jBPM 3.0 BPEL extension 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 > Versions: jBPM 3.0 BPEL extension alpha 1 > Reporter: Juan Cantu > Assignee: Juan Cantu > Fix For: jBPM 3.0 BPEL extension alpha 1 > > 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-25) bpel activities xml parsing
[ http://jira.jboss.com/jira/browse/JBPM-25?page=history ] Juan Cantu updated JBPM-25: --- Version: jBPM 3.0 BPEL extension 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 > Versions: jBPM 3.0 BPEL extension alpha 1 > 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-27) structured blocks execution
[ http://jira.jboss.com/jira/browse/JBPM-27?page=history ] Juan Cantu updated JBPM-27: --- Version: jBPM 3.0 BPEL extension alpha 1 Fix Version: jBPM 3.0 BPEL extension 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 > Versions: jBPM 3.0 BPEL extension alpha 1 > Reporter: Juan Cantu > Assignee: Juan Cantu > Fix For: jBPM 3.0 BPEL extension alpha 1 > > 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-26) bpel archives parsing
[ http://jira.jboss.com/jira/browse/JBPM-26?page=history ] Juan Cantu updated JBPM-26: --- Version: jBPM 3.0 BPEL extension alpha 1 Fix Version: jBPM 3.0 BPEL extension 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 > Versions: jBPM 3.0 BPEL extension alpha 1 > Reporter: Juan Cantu > Assignee: Juan Cantu > Fix For: jBPM 3.0 BPEL extension 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] Commented: (EJBTHREE-9) Proper exception handling
[ http://jira.jboss.com/jira/browse/EJBTHREE-9?page=comments#action_12316202 ] Kabir Khan commented on EJBTHREE-9: --- Added some more exceptions. Still have no support for exceptions relating to detached/removed etc. See TODO comments in org.jboss.ejb3.test.entityexception.ExceptionTestBean > Proper exception handling > - > > Key: EJBTHREE-9 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-9 > Project: EJB 3.0 > Type: Feature Request > Versions: Preview 4 > Reporter: Bill Burke > Assignee: Bill Burke > Fix For: Preview 5 > > Original Estimate: 2 days > Remaining: 2 days > > Need to review all the exception handling that will be in the specification. > All the cases needed to be documentented, implemented, and tested. -- 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-90) Scope (13)
Scope (13) -- Key: JBPM-90 URL: http://jira.jboss.com/jira/browse/JBPM-90 Project: JBoss jBPM Type: Task Components: BPEL Versions: jBPM 3.0 BPEL extension alpha 2 Reporter: Juan Cantu Assigned to: Juan Cantu Fix For: jBPM 3.0 BPEL extension alpha 2 Implement fault, compensation and event handling as specified in ws-bpel 2.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 JIRA] Closed: (EJBTHREE-84) EntityManager.find should throw EntityNotFoundException
[ http://jira.jboss.com/jira/browse/EJBTHREE-84?page=history ] Kabir Khan closed EJBTHREE-84: -- Resolution: Done > EntityManager.find should throw EntityNotFoundException > --- > > Key: EJBTHREE-84 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-84 > Project: EJB 3.0 > Type: Bug > Components: EJB3 Extensions > Versions: Preview 4 > Environment: JBoss 4.0.1SP1, EJB3Preview4, JDK 1.5.0_1, WinXP > Reporter: Stefan Lindner > Assignee: Kabir Khan > Priority: Minor > Fix For: Preview 5 > > > EntityManager.find should throw EntityNotFoundException if the entity does > not exist. In Preview 4 a "org.hibernate.ObjectNotFoundException" is thrown. -- 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-89) create initial persistence for bpel definition and instance classes
[ http://jira.jboss.com/jira/browse/JBPM-89?page=history ] Juan Cantu updated JBPM-89: --- Original Estimate: 288000 (was: 57600) Remaining Estimate: 288000 (was: 57600) > create initial persistence for bpel definition and instance classes > --- > > Key: JBPM-89 > URL: http://jira.jboss.com/jira/browse/JBPM-89 > Project: JBoss jBPM > Type: Task > Components: BPEL > Versions: jBPM 3.0 BPEL extension alpha 1 > Environment: hibernate3 > Reporter: Juan Cantu > Assignee: Juan Cantu > Fix For: jBPM 3.0 BPEL extension alpha 1 > > Original Estimate: 2 weeks > Remaining: 2 weeks > > initial persistence for > 1) definition: process and activities > 2) instance: links, variables, correlations, partnerlinks -- 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 Build System] - Re: Autonomous Project
Can't you just create your own cvs branch? If some directories become redundant (and it is an issue for you) you can ask the sourceforge staff to remove them. If do want a prototype project, all you have to do is: cvs import ... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870447#3870447 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870447 --- 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 Build System] - Autonomous Project
I posted the same topic in the JBoss Labs forum, but it seems it was the wrong forum to post on. Do we currently have the possibility to host an autonomous prototype project? Use Case: I am currently working on the JMS Facade, which is a pretty self contained (to a point) part of the JBoss Messaging. I am tying together JBoss AOP, JBoss Remoting and a lot of new constructs, and 1. I don't know yet how the final architecture will look like 2. I expect a lot of refactoring and package creation/deletion so I need some sort of playground that can be accessed by all contributors to the project, without poluting the main JBoss CVS repository with a lot of stuff that will be eventually thrown away. I can certainly do this on my own machine, but the main reason I want it shared is that I want to involve the contributors early in the process, hence shared CVS access. Requirements: - independent and self-contained CVS space. Nobody depends on it. - i can take care of my own dependencies (j2ee, remoting and aop in this case) by making local copies of the jars but if it would be nice if I can access them from a central location. - controlled public access: everybody can read, designated users can write - autonomous build system - no need for automated builds; it's a prototype, I don't care for unit tests at the moment - the prototype is specifically written with the final goal of being thrown away. The final result (or more likely parts of it) will be manually ported into the main JBoss CVS repository. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870446#3870446 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870446 --- 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.884 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-head?log=log20050316160330Lbuild.884 BUILD COMPLETE - build.884Date of build: 03/16/2005 16:03:30Time to build: 19 minutes 21 secondsLast changed: 03/16/2005 15:49:29Last log entry: Java Types generated using wscompile tool in Sun's JWSDP. Needed by JBWS-147 Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (20)1.1addedosdchicagowebservice/test/resources/tools/xsd-java-checker/wscompile/complextypes/Address.javaJava Types generated using wscompile tool in Sun's JWSDP. Needed by JBWS-1471.2modifiedorbdocbook-support/support/docbook-xsl/fo/qandaset.xslJBDOCS-53: fix qandaset bug1.3modifiedosdchicagowebservice/test/java/org/jboss/test/ws/tools/xsdjava/XSDToJavaTestCase.javaHandle ComplexTypes with Elements plus attributes.1.2modifiedosdchicagowebservice/test/java/org/jboss/test/ws/tools/SchemaLocationRegistryTestCase.javaAuthor tag1.4modifiedosdchicagowebservice/src/main/org/jboss/ws/wsdl/xsd/XSDComplexType.javaHandle attributes in the complex type1.5modifiedosdchicagowebservice/src/main/org/jboss/ws/tools/WSDLToJava.javaBetter handle the elements/attributes in the schema (XSD->Java)1.4modifiedosdchicagowebservice/src/main/org/jboss/ws/tools/SchemaBuilder.javaTake care of xsd:attribute also1.7modifiedosdchicagowebservice/src/main/org/jboss/ws/jaxrpc/LiteralTypeMapping.javaNMToken should be NMTOKEN1.1addedosdchicagowebservice/src/main/org/jboss/ws/wsdl/xsd/XSDAttribute.javaRepresents an element in the schema.1.5modifiedorbdocbook-support/styles/en/html.cssadd extra fonts1.41modifiedbelabancache/docs/Changelog.txtno message1.3modifiedbelabancache/src/main/org/jboss/cache/Version.javano message1.3modifiedtdieslertestsuite/src/resources/webservice/exception/META-INF/jaxrpc-mapping.xmllayout1.4modifiedtdieslertestsuite/src/main/org/jboss/test/webservice/ws4eesimple/ClientStubTestCase.javaRemove unportable code1.1addedosdchicagowebservice/test/resources/tools/xsd/complextypes/ComplexType_ElementsAttrib.xsdSchema files for JBWS-147:XSDSchema to Java comprehensive test collection1.3modifiedejortcontainer/src/main/org/jboss/joinpoint/plugins/config/Config.javaAll some of the typenames to be nullthis allows some simple use cases like1) not having to specify the types when there is only one constructor2) the constructor can be matched on number of parameters.1.234modifiedbelabancache/src/main/org/jboss/cache/TreeCache.javaadded putFailFast() with Fqn1.2modifiedbelabancache/src/main/org/jboss/cache/tests/TreeCacheFunctionalTest.javans1.14modifiedejortkernel/src/main/org/jboss/kernel/plugins/config/Configurator.javaGive a better error message than NPE1.10modifiedejortcommon/src/main/org/jboss/xml/binding/MetadataDrivenObjectModelFactory.javaFix a typo
[JBoss-dev] [JBoss JIRA] Created: (JBREM-83) Updated Invocation marshalling to support standard payloads
Updated Invocation marshalling to support standard payloads --- Key: JBREM-83 URL: http://jira.jboss.com/jira/browse/JBREM-83 Project: JBoss Remoting Type: Task Components: marshall Versions: 1.0.1 final Reporter: Tom Elrod Assigned to: Tom Elrod Priority: Critical Fix For: 1.2.0 beta Need to update InvocationMarshaller/InvocationUnMarshaller so that if payload not org.jboss.Invocation or org.jboss.MarshalledInvocation, will just marshall/unmarshaller using default parent behavior (SerializableMarshaller/SerializableUnMarshaller). Currently will throw exception otherwise. -- 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 Remoting, Unified Invokers] - Re: Problem with datatype=invocation in the socket connector
There are a couple of issues here (I am actually working through a few of them currently due to a bug submitted recently). As it is now a Connector can have one and only one invoker, but can have multiple handlers. The invoker has to have its marshaller/unmarshaller explicitly set for it (either via datatype=XXX in the locator url or by using its default one) when it starts. This is because the unmarshaller will be the one that is actually reading from the server invoker's transport's input stream (so no way to bind this dynamically based on client's preference as is no way to establish the initial handshake between client and server). This means that there is an associated constraint that all users of the Connector (and thus the associated server invoker) will have to use the same marshaller/unmarshaller. The reason that the EJBs using the unified invoker work without the datatype=invocation, as you have noted, is because I have explicitly hardcode the adding of the InvocationMarshaller/InvocationUnmarshaller in the UnifiedInvokerProxy and UnifiedInvoker. This was a hack, because at the time, I had no way to dynamically load marshallers. I have added this feature to remoting (explanation at http://www.jboss.org/wiki/Wiki.jsp?page=Remoting_Marshaller_Configuration), but have not made the fix to the UnifiedInvokerProxy and UnifiedInvoker. When I do make the fix (jira issue JBREM-62), I will need the datatype=invocation back in the locator (plus a few other parameters). So for now, probably best to define a new connector for the DTM. Another fix I can make pretty quickly is to update the InvocationMarshaller/InvocationUnMarshaller is to allow default marshalling behavior if is not of type org.jboss.Invocation (the EJB payload type). In essence, would mean any other users besides the ejb users, would see the exact same behavior as the SerializableMarshaller/SerializableUnMarshaller. I will be thinking about better long term solution for this problem (where can bind marshallers/unmarshaller dynamically). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870445#3870445 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870445 --- 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] - manage jsp files
Hi, I tried using the text editor in Portal to create a jsp file but it sees it as a binary file and once I save I can no longer edit it. Is there any way to manage jsp files with the ability to edit them? Thanx View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870444#3870444 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870444 --- 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: MailStore Integration
I have modified the Entity Mailbox to hold a serialized copy of the mail body. I think there is enough of the store in place now that the new mailbox implementation could be integrated. Most of the changes outstanding for the store will be behind the Store interfaces (e.g. configurable minimum stored message size). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870435#3870435 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870435 --- 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=log20050316144152 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/16/2005 14:41:52Time to build: 29 minutes 24 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: (10)1.2.8.2modifiedejortmessaging/src/main/org/jboss/mq/pm/TxManager.java[JBAS-1589] - Typo in TxManager1.2.2.6modifiedanddsystem/src/main/org/jboss/system/ServiceMBean.javaJBAS-1577: white-space in ServiceMBean EVENT types, removed1.1.4.1modifiedanddsystem/src/main/org/jboss/system/filterfactory/AttributeChangeNotificationFilterFactory.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/filterfactory/MBeanServerNotificationFilterFactory.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/filterfactory/NotificationFilterSupportFactory.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.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.1.20.2.25modifiedstarksmcluster/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.
[JBoss-dev] [JBoss JIRA] Created: (JBPM-89) create initial persistence for bpel definition and instance classes
create initial persistence for bpel definition and instance classes --- Key: JBPM-89 URL: http://jira.jboss.com/jira/browse/JBPM-89 Project: JBoss jBPM Type: Task Components: BPEL Versions: jBPM 3.0 BPEL extension alpha 1 Environment: hibernate3 Reporter: Juan Cantu Assigned to: Juan Cantu Fix For: jBPM 3.0 BPEL extension alpha 1 initial persistence for 1) definition: process and activities 2) instance: links, variables, correlations, partnerlinks -- 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] [Nukes Development] - problem with curly Quotes
Help Curly Quotes are being chnged to ? marks when i import into html editor in nukes anonymous wrote : ? should be a curly quote please help View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870432#3870432 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870432 --- 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-1593) Bad CRC checksum on files in downloaded archive
Bad CRC checksum on files in downloaded archive --- Key: JBAS-1593 URL: http://jira.jboss.com/jira/browse/JBAS-1593 Project: JBoss Application Server Type: Bug Versions: JBossAS-4.0.2RC1 Environment: WinZip Reporter: Jimi Thompson Priority: Minor This is pretty minor, but I've downloaded the archive from 2 different mirrors and I'm getting the same error message on the same files from WinZip. It seems to think that a couple of the files in the archive should be a slightly different size. I'm attaching the pertinent snippets of the WinZip log file. HTH, Jimi Extracting axis-ws4ee.jar bad CRC 9fa08afd (should be 8af0284d) Warning: the size of the extracted file (1286558) does not match the uncompressed size (1286652) recorded in the zip file Extracting jcommon.jar bad CRC 77e5b8c2 (should be 743169a3) Warning: the size of the extracted file (329611) does not match the uncompressed size (329678) recorded in the zip file Extracting jfreechart.jar -- 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-31) bpel message properties and correlation
[ http://jira.jboss.com/jira/browse/JBPM-31?page=history ] Alejandro GuÃzar resolved JBPM-31: -- Resolution: Done > bpel message properties and correlation > --- > > Key: JBPM-31 > URL: http://jira.jboss.com/jira/browse/JBPM-31 > Project: JBoss jBPM > Type: Task > Components: BPEL > Versions: jBPM 3.0 BPEL extension alpha 1 > Environment: w3c dom, jaxen > Reporter: Alejandro GuÃzar > Assignee: Alejandro GuÃzar > Fix For: jBPM 3.0 BPEL extension alpha 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_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-79) Compensation Handling
[ http://jira.jboss.com/jira/browse/JBPM-79?page=history ] Juan Cantu updated JBPM-79: --- Version: jBPM 3.0 BPEL extension alpha 2 (was: jBPM 3.0 alpha 2) > Compensation Handling > - > > Key: JBPM-79 > URL: http://jira.jboss.com/jira/browse/JBPM-79 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Versions: jBPM 3.0 BPEL extension alpha 2 > Reporter: Juan Cantu > Assignee: Juan Cantu > > Original Estimate: 3 days > Remaining: 3 days > > -Implement the state transitions for scope instances when compensate / > compensated signals are received > -support implicit compensation -- 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-78) Fault and Termination Handling
[ http://jira.jboss.com/jira/browse/JBPM-78?page=history ] Juan Cantu updated JBPM-78: --- Version: jBPM 3.0 BPEL extension alpha 2 (was: jBPM 3.0 alpha 1) > Fault and Termination Handling > -- > > Key: JBPM-78 > URL: http://jira.jboss.com/jira/browse/JBPM-78 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Versions: jBPM 3.0 BPEL extension alpha 2 > Reporter: Juan Cantu > Assignee: Juan Cantu > > Original Estimate: 2 days > Remaining: 2 days > > -Implement the state transitions for scope instances when cancel or faulted > signals are received > -Provide the fault catching logic -- 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-64) Scope (13)
[ http://jira.jboss.com/jira/browse/JBPM-64?page=history ] Juan Cantu updated JBPM-64: --- Version: jBPM 3.0 BPEL extension alpha 2 (was: jBPM 3.0 alpha 1) > Scope (13) > -- > > Key: JBPM-64 > URL: http://jira.jboss.com/jira/browse/JBPM-64 > Project: JBoss jBPM > Type: Sub-task > Components: BPEL > Versions: jBPM 3.0 BPEL extension alpha 2 > Reporter: Juan Cantu > Assignee: Juan Cantu > > > Implement fault, compensation and event handling as specified in ws-bpel 2.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] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: JMS Facade
Yes A good place to start is EJB3. I am using the same stuff they're using. Just create the simplest stateless session bean and track an invocation with a debugger. That's pretty much it. I am pushing really hard to put the protoype out, so we'll have a common ground to base our discussions on. I also want to rewrite Adrian's facade design document http://www.jboss.org/wiki/Wiki.jsp?page=JBossMessagingDesign, it's outdated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870427#3870427 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870427 --- 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 Messaging on JBoss (Messaging/JBoss)] - Re: JMS Facade
Okay, we cross-posted on the other thread. I'll be looking for it in the near future. I'll probably look at the interceptors first. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870426#3870426 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870426 --- 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.78 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-jdk-matrix?log=log20050316133929Lbuild.78 BUILD COMPLETE - build.78Date of build: 03/16/2005 13:39:29Time to build: 39 minutes 49 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] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: What to work on
Remoting is used behind the JMS API. Use case: Your client code looks up a ConnectionFactory in JNDI and it uses it to create a Connection. The ConectionFactory implementation (which delegates to a dynamic proxy) will use Remoting to connect to a server pair, which will create a ConnectionDelegate proxy and return it on the client. Over Remoting. The client then will use Connection.createSession() which will also use Remoting in the background. Same for Session.createProducer() and Session.createConsumer(). So Remoting is used by the JMS Facade runtime to interact with a server peer. The server peer will accept a message and it will forward it locally to a consumer or it will forward it to another peer, over JGroups. The destination peer will forward the message to its consumer, over Remoting. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870422#3870422 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870422 --- 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 Messaging on JBoss (Messaging/JBoss)] - Re: What to work on
Actually, above you say: As for the communication between remote clients and server peers, I will use Tom Elrod's Remoting. So it seems that the Remoting is just for clients wanting to use Messaging outside of the JMS API? Or will you create a JMS client as well? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870420#3870420 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870420 --- 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 Messaging on JBoss (Messaging/JBoss)] - Re: What to work on
This thread continues at http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870417#3870417 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870418#3870418 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870418 --- 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 Messaging on JBoss (Messaging/JBoss)] - JMS Facade
Hey Steve, This is a continuation of http://www.jboss.org/index.html?module=bb&op=viewtopic&t=61068 I actually already have a full JMS Facade prototype that makes obvious how I want to use Remoting and the AOP API for interceptors. It's still in my private CVS and the reason I didn't put it out is that I am still doing a lot of refactoring while I am trying new things, and I don't want to polute the main repository with directories that become obsolete overnight. I asked our build guys if isn't possible to have a separate "prototype project" http://www.jboss.org/index.html?module=bb&op=viewtopic&t=61366, but nobody answered so I guess it isn't. I think I should get over it and put it out, assuming the risk of annoying you guys because of a lot of refactoring :) To answer your questions: The JMS Facade will be exposed by a set of classes (JBossConnectionFactory, JBossConnection, JBossSession, etc) that will delegate to a layer of "JMS delegates". These are actually dynamic proxies + interceptors , following the unified interceptor patterns (AOP API and all). The last interceptor in the chain is an org.jboss.aspects.remoting.InvokeRemoteInterceptor which delegates the transport to Remoting. On the server-side, there is a Connector with at least one handler (the org.jboss.aop.Dispatcher singleton instance) to which we register one or more Advisors. This is the part I am working on right now, but I guess I should put it out in the open. Let's see if I can do this today View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870417#3870417 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870417 --- 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 Messaging on JBoss (Messaging/JBoss)] - Re: What to work on
Hello Ovidiu. I've looked over the remoting stuff. Which Handler(s) do you expect to have, and how many? Will you expose the JMS facade directly over the remoting API (i.e. use a Remoting Client to use JMS) or are the remote handlers just for JMS<->JMS communication? As in, between servers that serve JMS? I'm guessing the latter, but I'm just checking. THanks, View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870416#3870416 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870416 --- 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: (JBMAIL-36) Support (optional) CRC or long hashkey generation for bodies
[ http://jira.jboss.com/jira/browse/JBMAIL-36?page=comments#action_12316195 ] Ricardo Arguello commented on JBMAIL-36: Shouldn't a hash function (ie SHA-1) be more appropiate for this task? > Support (optional) CRC or long hashkey generation for bodies > > > Key: JBMAIL-36 > URL: http://jira.jboss.com/jira/browse/JBMAIL-36 > Project: JBoss Mail > Type: Sub-task > Versions: 1.0-M4 > Reporter: Andrew Oliver > Assignee: Andrew Oliver > Priority: Critical > Fix For: 1.0-M4 > > Original Estimate: 1 week > Remaining: 1 week > > The M3 Message Store prevents bodies from being stored multiple times and > allows messages to stream directly to the DB. For large messages a line by > line hash should be calculable and if it matches an existing message (this > optimizes for disk size but costs performance) then the Mailbox entry is > reassigned to the existing mailstore and then the new body is deleted. > Example. > 1. Assume that the following is a 64mb stream that comes in (minus headers) > in duplicate for both mails (meaning we're sending the same file): > body line CRC/checksum/whatever > X...XXX123456 > Y...YYY654321 > Z...ZZZ321654 > ..... > X...XXX123456 > Y...YYY654321 > Z...ZZZ321654 > cumulative checksum accurate to at least 1/5000 > 12341235125132412512 > if a "select body_id from bodies where checksum='12341235125132412512'" > returns more than 1 result then the new body is deleted and the mailbox is > assigned to the older of the two. > So the idea above is important, algorythmic and method suggestions are not (I > don't know my posterior from my elbow when it comes to efficient binary > similarity detection -- I'm just pretty sure that's not to be done by direct > matching on content!). > It is important that minor revisions not cause collisions. So the 1/5000 > target for minimum collision should not be taken to mean if you send me a > doc, I edit it and send it back that it drops my edits and that's okay. It > means that for this to be a viable algoyrthm if I upload the text of a speech > and you upload a completely different speech and somehow the checksum comes > out just rightwe could have that 1/50,000,000 chance of two very > different documents getting the same check, a minor revision to either should > fix it. > It is also important that proper boundries be created (no chance that one > time we include fuzz surrounding the body and another time we don't). -- 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-jdk-matrix build.109 Build Successful
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0-jdk-matrix?log=log20050316123446Lbuild.109 BUILD COMPLETE - build.109Date of build: 03/16/2005 12:34:46Time to build: 54 minutes 34 secondsLast changed: 03/15/2005 23:48:20Last log entry: Add the 4.0.1 serial version uid mappings Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (53)1.1.2.1modifiedstarksmtestsuite/src/etc/serialVersionUID/401.serAdd the 4.0.1 serial version uid mappings1.406.2.45modifiedstarksmtestsuite/build.xmlAdd jbosstest.src.etc and jbosstest.dist properties1.1.2.1modifiedstarksmtestsuite/src/main/org/jboss/test/compatibility/test/SerialVersionUIDUnitTestCase.javaTests of serial version uid compatibility across jboss versions1.1.2.1modifiedstarksmvaria/src/main/org/jboss/tools/SerialVersionUID.javaUpdate to just parse the lib and server/all jars.1.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.1modifiedtdieslerjaxrpc/src/main/org/jboss/axis/enums/Enum.javaReplace the jdk-1.5 keyword enum1.1.2.1modifiedtdieslerjaxrpc/src/main/org/jboss/axis/enums/Scope.javaReplace the jdk-1.5 keyword enum1.1.2.1modifiedtdieslerjaxrpc/src/main/org/jboss/axis/enums/Style.javaReplace the jdk-1.5 keyword enum1.1.2.1modifiedtdieslerjaxrpc/src/main/org/jboss/axis/enums/Use.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.2modifiedt
[JBoss-dev] [JBossCache] - ATG Dynamo Cache LockManager versus JBoss Cache
Have anyone done the porting of ATG Cache LockManager to JBossCache? If so, please share with us how to come about doing it. We have so many problems with using the ATG Cache LockManager (deadlock, single Point of Failure etc..) and we are planning to find a solution that we allow help us resolving the issue. Thanks much Tom View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870415#3870415 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870415 --- 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 Remoting, Unified Invokers] - Re: Problem with datatype=invocation in the socket connector
Noticed that not only my own code works fine with no "datatype=invocation" parameter in the socket connector MBean, but EJB testcases work too. To me this was surprising, as those testcases perform EJB calls through the unified invoker. (Maybe EJB calls work with no "datatype=invocation" because UnifiedInvokerProxy.init explicitly sets the invocation marshaller?) Anyway, by now I have just removed the "datatype=invocation" parameter from the locator URI in the socket connector MBean. Francisco View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870414#3870414 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870414 --- 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: cannot login
It was updated in the beta docs and the wiki: http://docs.jboss.com/jbportal/v2.0beta1/user-guide/html/installation.html#d0e245 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870408#3870408 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870408 --- 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: (JBCACHE-112) Added putFailFast(Fqn, ...)
[ http://jira.jboss.com/jira/browse/JBCACHE-112?page=history ] Bela Ban resolved JBCACHE-112: -- Resolution: Done > Added putFailFast(Fqn, ...) > --- > > Key: JBCACHE-112 > URL: http://jira.jboss.com/jira/browse/JBCACHE-112 > Project: JBoss Cache > Type: Feature Request > Versions: 1.2.1 > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 1.2.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] Created: (JBCACHE-112) Added putFailFast(Fqn, ...)
Added putFailFast(Fqn, ...) --- Key: JBCACHE-112 URL: http://jira.jboss.com/jira/browse/JBCACHE-112 Project: JBoss Cache Type: Feature Request Versions: 1.2.1 Reporter: Bela Ban Assigned to: Bela Ban Fix For: 1.2.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] [Design of JBoss Portal] - Re: help with setup
what version are you using ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870398#3870398 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870398 --- 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-1592) JaccAuthorizationRealm always returns false on subsequent requests
JaccAuthorizationRealm always returns false on subsequent requests
--
Key: JBAS-1592
URL: http://jira.jboss.com/jira/browse/JBAS-1592
Project: JBoss Application Server
Type: Bug
Components: Security, Deployment Service
Versions: JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1
Environment: Windows XP SP2
JDK 1.5.0
Reporter: Stephen Kinser
Priority: Critical
After the initial login, the JaccAuthorizationRealm always returns false
because the PolicyContext handler for the Subject is not yet initialized when
the realm is called. To figure out the root of the problem, an understanding of
the calling order is necessary.
The standard pipeline is composed of the following valves, in this order:
- JaccContextValve
- FormAuthenticator (the authenticator valve in my case)
- SecurityAssociationValve
- CustomPrincipalValve
- StandardContextValve
The SecurityAssociationValve is added to the pipeline after the authenticator
valve due to the ordering of the code in the
TomcatDeployer.performDeployInternal method. The SecurityAssociationValve is
added after the init call to the server. The init call results in the
authenticator valve being added to the pipeline.
When a request is received by an authenticated user, the authenticator valve
obtains control before the SecurityAssociationValve. The authenticator valve
calls the JaccAuthorizationRealm for the authorization check. Part of the
check is as follows:
Subject caller = null;
try
{
caller = (Subject) PolicyContext.getContext(SUBJECT_CONTEXT_KEY);
}
catch (PolicyContextException e)
{
if( trace )
log.trace("Failed to get subject from PolicyContext", e);
}
if( caller == null ) //*** is always true!
{
if( trace )
log.trace("Denied, no active subject found in PolicyContext");
return false;
}
The realm expects to have an initialized caller (Subject), but the caller is
always null because it wasn't initialized yet since the
SecurityAssociationValve that initializes the caller (Subject) doesn't receive
control until after the authenticator valve is finished.
--
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] - help with setup
When i run the build file I get this error message. BUILD FAILED | D:\workspace\jbossportal\tools\etc\buildfragments\tools.ent:140: taskdef A class needed by | class org.apache.cactus.integration.ant.CactusTask cannot be found: junit/framework/Test I know that this is probably something very simple, but i am new to ant, and can't figure it out. Could someone please tell me how i can fix this. Thx. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870397#3870397 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870397 --- 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: Strurts portlets on jBoss Portal?
The code: struts-config.xml: | | | | | main.ftl | <#assign html=JspTaglibs["/WEB-INF/struts-html.tld"]> | <#assign bean=JspTaglibs["/WEB-INF/struts-bean.tld"]> | This is main.ftl in stack2.war. | If you see this, it means basic Struts action-mapping is working. | <@html.link action="trial.do">Show Trial | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870394#3870394 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870394 --- 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] - Strurts portlets on jBoss Portal?
Has anyone transferred their Struts application to run as a JSR168 portet in
jBoss Portal??
I am using jBossAS 4.0.1sp1 and jBoss Portal v2.0.
Whats confusing me is this: In struts, every action defines the
html/jsp/freemarker etc page that should be displayed. on the user's screen.
However, to display something in a portlet, it should be called inside the
doView() function of the portlet,
This statement is in the doView() function of my portlet's class:
..
PortletRequestDispatcher rd =
getPortletContext().getRequestDispatcher("/main.do");
..
My struts-config:
.
The above scenario displays the content of main.ftl in the portlet's window,
just like it should, i.e. the portlet called main.do, and whatever main.do
returns (main.ftl) is sent to the portlet to be displayed. But, when I put a
link in main.ftl which points to another action, (say, trial.do), the result of
those actions is not displayed in the portal.
My main.ftl:
<#assign html=JspTaglibs["/WEB-INF/struts-html.tld"]>
<#assign bean=JspTaglibs["/WEB-INF/struts-bean.tld"]>
This is main.ftl in stack2.war.
If you see this, it means basic Struts action-mapping is working.
<@html.link action="trial.do">Show Trial
When I click on the "Show Trial" link on main.ftl, the application leaves the
portal and shows the content of trial.ftl on the browser (no portal/portlets,
just trial.ftl).
How do I make sure that whatever I do in struts stays inside the portlet window?
Regards,
Karan
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870392#3870392
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870392
---
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=log20050316113715 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/16/2005 11:37:15Time to build: 29 minutes 17 seconds Unit Tests: (0) Total Errors and Failures: (0) Modifications since last build: (0)
[JBoss-dev] [JBossCache] - Re: TreeCacheAop can't add an object of a class which extend
"[EMAIL PROTECTED]" wrote : | I have checked in the code under jboss-head/testsuite/src/main/test/cache/test/standAloneAop/CollectionProxyAopTest. Check it out. | -Ben When I browse the CVS repository here http://cvs.sourceforge.net/viewcvs.py/jboss/ I don't see the file, in fact I don't see anything at all under jboss-head. Is there another way to access this file ? As far as using the wrong distribution for examples I think it happened because in the JBossCache tutorial (http://docs.jboss.org/jbcache/Tutorial.html) there is a an instruction to download the stand alone TreeCache code from SourceForge, and to use the configuration files under the jboss-cache/etc directory. This is a bit ambiguous as far as which actual distribution should be downloaded, and so I downloaded JBossCache-1.2.zip which does have the directory and files mentioned. Unfortunately the configuration files are out of date, and contain a bug which prevents replication. Specifically the replSync-service.xml contains an entry in the ClusterConfig attribute, bind_addr="localhost", which prevents synchronous replication from working. This set me back for days, but once I located this bug the replication started working as advertised. The example jboss-aop.xml contains invalid entries, but at least the correct entries are described in another document, and now that I am using these "prepare" entries all is well. My suggestion is to modify the tutorial so that it no longer points new users to the wrong distribution for examples, as this will make learning how to use JBossCache much less frustrating. I'm still not clear as to which exact distribution has correct examples, as I don't see a jboss-cache/etc under the JBossAOP distribution. Perhaps there are good examples in the new JBossCache release ? In any event I now have my application running with JBossCache using TreeCacheAop. The replication works really well -- kudos to Ben and Bela and to the rest of the team who put this all together. --James View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870389#3870389 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870389 --- 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
